The models used in modern computation no longer include just the algorithmic calculation processes, but have evolved to include additional paradigms, such as the parallel, embedded, distributed, event-driven and interactive process model. The fundamental difference between this latter paradigm and the traditional model is that in the traditional model it is assumed that executions are single-threaded, while the more modern view is that executions should be seen as multi-threaded, or parallel event driven tasks, that reflect the highly diverse and asynchronous activities demanded in the modern computing context. Students should be taught this model of computation as most modern applications (for example: event-driven applications, spreadsheets, databases, GUI and network and internet applications, to name a few) are written this way. By complementing this with object-oriented design, students will be well equipped to handle most modern programming challenges.

This unit was previously called CPE2001 Concurrent Programming Techniques and was in the Bachelor of Network Computing. The unit has been changed to fit in with the faculty requirements for the Bachelor of Information Technology and Systems.

SFEC 4/06: This unit will be co-taught with CPE2001(BNetwork Comp) as part of the teaching-out strategy for that unit.

This is an elective unit of the net-centric major for the Bachelor of Information Technology and Systems.

The unit gives the students the opportunity to learn the principles of concurrent programming which extends students' knowledge in the design and implementation of modern networked, distributed and internet software. Also it will enhance the knowledge of students in network design and implementation covered in other units.

This unit is relevant to the Bachelor of Information Technology and Systems with a major in net-centric computing, in that it provides students with the concurrency concepts and techniques which are very important in the networking area.

At the completion of this subject, students should.

Students will gain important experience of task decomposition and concurrent design concepts in building concurrent applications. They will also gain good skills in building event-based multi-threaded applications and particularly networked and distributed applications using sockets and RMI.

ASCED Discipline Group Classification: 020103 Programming.

This subject focuses on the theory and application of concurrent multi-threaded programming in modern applications development. Concurrent programming primitives: threads, semaphores, rendezvous, critical regions, shared variables. Concurrent programming concepts and designs: concurrency, synchronization, safety, liveness, control policies, layering of policies, flow designs, transaction-based and notification-based designs. Concurrent programming applications: GUI applications, distributed applications - network clients and servers interaction, serialization, remote procedure calls (e.g. Java RMI).

Prescribed text:.

• Lea, D. Concurrent Programming in Java- Design Principles and Patterns. Addison-Wesley. 1997.

References:.

• Atkinson, C. Object-Oriented Reuse, Concurrency and Distribution. Addison-Wesley. Latest Ed..

• Ben-Ari, M. Principles of Concurrent and Distributed Programming, Prentice Hall, Latest Ed..

• Booch, G. Object Oriented Analysis and Design. Benjamin Cummings. Latest Ed..

• Chan, P., and R. Lee. The Java Class Libraries: An Annotated Reference. Vols 1 and 2, 2nd edition, Addison-Wesley. 1998.

• Gamma, E., R. Helm, R. Johnson and J. Vlissides. Design Patterns, Addison-Wesley, Latest Ed..

• Gregory, A. Concurrent Programming: Principles and Practice. Benjamin Cummings. Latest Ed..

• Kleiman, S., D. Shah, and B. Smaalders. Programming with Threads. Prentice Hall. Latest Ed..

• Wilson, G. Practical Parallel Programming. MIT Press. Latest Ed..

On campus

The unit will have a 2 hours of lectures and 2 hours of tutorial (in computer laboratories) per week for one semester. The concepts covered in the lectures are reinforced during the tutorials with the aid of examples and exerices. Hands-on work is included within the tutorials to link the theory with the practice to enhance the understanding. The assignment work allows students to develop research and problem solving skills; individually and within a team environment.

The teaching of the subject will be conducted through lectures and tutorials (in computer labs). The lectures will present the conceptual and theoretical aspects of the subject, addressing objectives 1, 2, 3 and 4. The tutorials/lab-sessions will enhance the students' understanding of the subject materials through guided hands-on exercises, addressing objective 3 and 4. Case studies will also be presented in the tutorials to address objectives 2, 3 and 4.

Assignments: 40% - Examination: 60%

The practical work involves the development of concurrent applications. The tutors will test the students' assignments and interview the students regarding their work. From this practical work, not only the students' understanding of the subject materials are assessed, but also the students receive critical feedback regarding all aspects of their work. The practical work contributes to achieving objectives 1, 2, 3 and 4.

The final examination will assess the students' total understanding of the subject materials, including concurrent programming primitives, concepts and designs, and their ability to apply concurrent designs into the development of applications. It contributes to achieving objectives 1, 2, 3 and 4.

6

Students are expected to spend an average of 12 hours per week for a semester on this subject with the following detailed breakdown:

• 2 hours per week: lecture
• 2 hours per week: tutorial/lab
• 8 hours per week: private study and completing assignments

Standard Monash lecture theatre

Standard computer laboratory

Standard computer laboratory

Lecturer 2 hours per week. Tutors 2 hours per week per tutorial.

• Software Title:
• Vendor:
• Version:
• OS: MS Windows XP ( ) and/or LINUX ( )
• License Details: (A valid software license certificate/s or Vendor permission must be available upon request if the software is to be installed for teaching)
• Are we currently licensed: Yes ( ) or No ( ) (If unsure, please check with your local IT support )
• If (Yes), who is the contact person for this software?:
• If (No), will the software license be arranged by: Staff member requesting the software ( ) or Technical Services* ( ) ? *If the latter is selected, please discuss your requirement/s with myself ASAP, prior to finalising your request, as there could be financial or resourcing implications.
• Is the software to be installed and accessed from a: Client/Workstation ( ), or Server ( ) ?
• Type of license: Site License ( ), Freeware ( ), FOSS (Free and Open Source Software) ( ), Shareware ( ), Lab based ( ) # of Licenses needed ____
• In what week will you commence using the software in class? Semester 1 (Week ___ ) and/or Semester 2 (Week ___ ):
• Nominated Staff For Acceptance Testing Software: (Name) (Phone) (Email)
• Additional Information: Special Requirements, Software Configuration/Installation Requirements, etc:

Standard

Several copies of the recommended reading texts should be held in the library.

Faculty of Information Technology

None

None

None

None

CPE1001 or FIT1002 or equivalent