COMP SCI 3013 - Event Driven Computing

North Terrace Campus - Semester 2 - 2018

Event driven paradigm: Finite State Automata, their behaviour and implementation. Correspondence with regular expressions. Examples of embedded systems. Introduction to interconnected state machines, Petri Nets, and concurrency. Concepts of state-space and relationship to testing. Push-down automata and applications to parsing. Building Graphical User Interfaces: model view controller paradigm. Building GUIs using modern APIs. Ease of use and human-computer interaction issues.

Open All

Course Details

Course Code	COMP SCI 3013
Course	Event Driven Computing
Coordinating Unit	Computer Science
Term	Semester 2
Level	Undergraduate
Location/s	North Terrace Campus
Units	3
Contact	Up to 2.5 hours per week
Available for Study Abroad and Exchange	Y
Prerequisites	One of COMP SCI 1007, COMP SCI 1009, COMP SCI 1103, COMP SCI 1203, COMP SCI 2103 or COMP SCI 2202
Assumed Knowledge	COMP SCI 1106
Assessment	written exam, assignments

Course Staff

Course Coordinator: Dr Asangi Jayatilaka

Course Timetable

The full timetable of all activities for this course can be accessed from Course Planner.

Course Learning Outcomes

On successful completion of this course students will be able to:

1	Describe the different ways a finite-state machine can be represented
2	Explain how a finite state machine recognises an input string
3	Explain how a non-deterministic finite state machine works
4	Explain the behaviour of regular expressions
5	Translate a regular expression into a corresponding finite-state machine
6	Construct GUI-based software systems
7	Explain a few basic design-patterns, and know when to apply them

The above course learning outcomes are aligned with the Engineers Australia Stage 1 Competency Standard for the Professional Engineer.
The course is designed to develop the following Elements of Competency: 1.2 1.3 1.6 2.1 2.2 2.3 2.4 3.3 3.4 3.5

University Graduate Attributes

This course will provide students with an opportunity to develop the Graduate Attribute(s) specified below:

University Graduate Attribute	Course Learning Outcome(s)
Deep discipline knowledge informed and infused by cutting edge research, scaffolded throughout their program of studies acquired from personal interaction with research active educators, from year 1 accredited or validated against national or international standards (for relevant programs)	5
Critical thinking and problem solving steeped in research methods and rigor based on empirical evidence and the scientific approach to knowledge development demonstrated through appropriate and relevant assessment	4,5
Teamwork and communication skills developed from, with, and via the SGDE honed through assessment and practice throughout the program of studies encouraged and valued in all aspects of learning	1,2,3,4
Career and leadership readiness technology savvy professional and, where relevant, fully accredited forward thinking and well informed tested and validated by work based experiences	5,6,7
Self-awareness and emotional intelligence a capacity for self-reflection and a willingness to engage in self-appraisal open to objective and constructive feedback from supervisors and peers able to negotiate difficult social situations, defuse conflict and engage positively in purposeful debate	7

Learning Resources

Required Resources

There is no required text-book. Comprehensive lecture notes are available for most parts of the course.

Recommended Resources

You can perform all the exercise work required for the course in the University computer Labs. The programming language used is Java. However, if you want to be able to work at home, you could consider installing Java on your own system.

Online Learning

You can find the general information about this course at https://myuni.adelaide.edu.au/courses/25363. Specific information about previous years' offerings can be found at www.cs.adelaide.edu.au/~third/edc.
Learning & Teaching Activities

Learning & Teaching Modes

The course will be taught with lecture/demonstration sessions. There will also be tutorial classes, and practical exercises. You are expected to attend the lectures and take part in the activities, and attempt tutorial questions before the scheduled tutorial session. All lectures will be recorded, but it is unwise to rely on the recordings as your only source to study the course.

Workload

The information below is provided as a guide to assist students in engaging appropriately with the course requirements.

You are expected to attend all scheduled lecture classes (2 hours per week). In addition to the schedule contact hours, you are expected to spend an additional 2-4 hours per week after each lecture to consolidate your understanding of it. You will need to allocate up to 5 hours per week to work on the assignments and tutorials.

Learning Activities Summary

There is an approximate schedule of the topics that will be covered on the course website. The exact timing will depend on the times of public holidays and other eventualities.

The University's policy on Assessment for Coursework Programs is based on the following four principles:

Assessment must encourage and reinforce learning.
Assessment must enable robust and fair judgements about student performance.
Assessment practices must be fair and equitable to students and give them the opportunity to demonstrate what they have learned.
Assessment must maintain academic standards.

Assessment Summary

Assessment Task	Weighting (%)	Individual/ Group	Formative/ Summative	Due (week)*	Hurdle criteria	Learning outcomes	CBOK Alignment**
3 programming exercises	40	Individual	Summative			1. 2. 3. 6. 7.	1.1 1.2 2.2 2.4 2.5 2.6 3.1 3.2 4.1 4.2 4.3 4.4 5.2
Final exam	60	Individual	Summative	n/a	40%	1. 2. 3. 4. 5. 6. 7.	1.1 1.2 4.2 4.3 4.4 5.2
Total	100

* The specific due date for each assessment task will be available on MyUni.

This assessment breakdown complies with the University's Assessment for Coursework Programs Policy.

This course has a hurdle requirement. Meeting the specified hurdle criteria is a requirement for passing the course.

**CBOK is the Core Body of Knowledge for ICT Professionals defined by the Australian Computer Society. The alignment in the table above corresponds with the following CBOK Areas:

1. Problem Solving

1.1 Abstraction

1.2 Design

2. Professional Knowledge

2.1 Ethics

2.2 Professional expectations

2.3 Teamwork concepts & issues

2.4 Interpersonal communications

2.5 Societal issues

2.6 Understanding of ICT profession

3. Technology resources

3.1 Hardware & Software

3.2 Data & information

3.3 Networking

4. Technology Building

4.1 Programming

4.2 Human factors

4.3 Systems development

4.4 Systems acquisition

5. ICT Management

5.1 IT governance & organisational

5.2 IT project management

5.3 Service management

5.4 Security management

Assessment Related Requirements

Hurdle Requirement: If your overall mark for the course is greater than 44 F but, your mark for the final written exam is less than 40%, your overall mark for the course will be reduced to 44 F.

Assessment Detail

All practical assignments require you to write programs. Most of them will be marked by an automatic testing script. You are strongly encouraged to begin the exercises early, to allow time for seeking help when needed. You will find that the marking script is aggessively hostile - it will seek to break your program. The test script does not tell you exactly what is being tested, and may provide little or no information that is useful in finding errors. If you submit your exercise at the last minute, and hope to use the automated tester to help you debug your program, you will be seriously disappointed. You should build your program in small stages, and test it thoroughly.

In the case of automatic testing, to encourage you to test your own program, access to the tester may be limited to three test runs. These test runs will be provided with intervals giving you the opportunity to test and re-test your program after subsequent updates.

The testing regime is like this because, you will most likely soon graduate, after which there will be no more automatic testers available - you will need to learn how to test, and write you own testers.

If you hand in your work late, your mark will be capped, based on how many days late it is.

–1 day late – mark capped at 75%
–2 days late – mark capped at 50%
–3 days late – mark capped at 25%
–more than 3 days late – no marks available

Submission

All practical assignments must be submitted using the School of Computer Science online Submission System. All details are included in each assignment description on the course website.

In the case of automatic testing, if you hand in your work late, you will miss the test-runs, and deprive yourself of vital evidence that might help you debug your program. Start early, test often!

Course Grading

Grades for your performance in this course will be awarded in accordance with the following scheme:

M10 (Coursework Mark Scheme)
Grade	Mark	Description
FNS		Fail No Submission
F	1-49	Fail
P	50-64	Pass
C	65-74	Credit
D	75-84	Distinction
HD	85-100	High Distinction
CN		Continuing
NFE		No Formal Examination
RP		Result Pending

Further details of the grades/results can be obtained from Examinations.

Grade Descriptors are available which provide a general guide to the standard of work that is expected at each grade level. More information at Assessment for Coursework Programs.

Final results for this course will be made available through Access Adelaide.

Student Feedback

The University places a high priority on approaches to learning and teaching that enhance the student experience. Feedback is sought from students in a variety of ways including on-going engagement with staff, the use of online discussion boards and the use of Student Experience of Learning and Teaching (SELT) surveys as well as GOS surveys and Program reviews.

SELTs are an important source of information to inform individual teaching practice, decisions about teaching duties, and course and program curriculum design. They enable the University to assess how effectively its learning environments and teaching practices facilitate student engagement and learning outcomes. Under the current SELT Policy (http://www.adelaide.edu.au/policies/101/) course SELTs are mandated and must be conducted at the conclusion of each term/semester/trimester for every course offering. Feedback on issues raised through course SELT surveys is made available to enrolled students through various resources (e.g. MyUni). In addition aggregated course SELT data is available.

You can find the latest SELT survey results on the course website, here:
www.cs.adelaide.du.au/~third/edc
Student Support
Policies & Guidelines
This section contains links to relevant assessment-related policies and guidelines - all university policies.
Fraud Awareness

Students are reminded that in order to maintain the academic integrity of all programs and courses, the university has a zero-tolerance approach to students offering money or significant value goods or services to any staff member who is involved in their teaching or assessment. Students offering lecturers or tutors or professional staff anything more than a small token of appreciation is totally unacceptable, in any circumstances. Staff members are obliged to report all such incidents to their supervisor/manager, who will refer them for action under the university's student’s disciplinary procedures.

The University of Adelaide is committed to regular reviews of the courses and programs it offers to students. The University of Adelaide therefore reserves the right to discontinue or vary programs and courses without notice. Please read the important information contained in the disclaimer.

Authorised by:	Deputy Vice-Chancellor and Vice-President (Academic)
Maintained by:	Course Outlines Administrator