Skip to content | Change text size

M O N A T A R

InfoTech Unit Avatar

FIT5009 Software engineering for communication systems -DISESTABLISHED AT FEC 4/10

Chief Examiner

This field records the Chief Examiner for unit approval purposes. It does not publish, and can only be edited by Faculty Office staff

To update the published Chief Examiner, you will need to update the Faculty Information/Contact Person field below.

NB: This view restricted to entries modified on or after 19990401000000

Unit Code, Name, Abbreviation

FIT5009 Software engineering for communication systems -DISESTABLISHED AT FEC 4/10 (22 Oct 2010, 2:35pm) [SECommSystems (29 May 2006, 10:54pm)]

Reasons for Introduction

Reasons for Introduction (29 May 2006, 1:37pm)

FIT5009 is a specified elective unit in the Master of Digital Communications degree (MDC). Its introduction is based on two circumstances: (1) as part of the 2006 Faculty restructure, whereby all old units were progressively reviewed and mapped into new FIT coded units; and (2) as part of a review and restructure of the courseware units for the MDC, undertaken in 2006 at the same time as an Engineering Faculty review and restructure of their Master of Telecommunications (MTC) degree. Previously the MTC had an elective unit ECE4/5410 Software Engineering for Telecommunications, but will not be offering such an elective in their revised structure. FIT5009 is intended to fill the need for a unit addressing the important area of software engineering as applied in the field of digital communications.

Reasons for Change (25 May 2006, 11:16pm)

This is the first version of this unit.

Role of Unit (25 May 2006, 11:25pm)

This is a level 5 specified elective unit in the MDC (offered by FIT) and MTC (offered by Engineering). It is also an approved elective for the Master of Computer Science (and may be taken by other coursework masters students and honours students with the required pre-requisite knowledge). It covers software engineering processes, tools and techniques as used in the field of digital communications.

Relationship of Unit (29 May 2006, 1:41pm)

This is a level 5 specified elective unit in the MDC (offered by FIT) and MTC (offered by Engineering). This unit is complimentary to FIT4014 Digital communications software, which looks at the lower level software and programming aspects involved in digital communications. There is a slight overlap of material with FIT4001 Parallel and Distributed Systems to the extent of providing an introduction to parallel and distributed systems for students who have not taken FIT4001 or equivalent.

Relevance of Unit (25 May 2006, 11:30pm)

FIT5009 replaces ECE4/5410 (offered by the Faculty of Engineering) as a specified elective in the Master of Digital Communications, a cognate degree offered by the Faculty of IT. It builds upon assumed prerequisite knowledge at the level of an undergraduate introductory unit in Networks and Data Communications (such as the FIT common core unit FIT1005/2008 or equivalent study), and some undergraduate exposure to both programming and software engineering. This unit provides MDC graduates with advanced knowledge about the application of software engineering methods within the field of digital communications. Both software engineering and digital communcations are important fields in IT and are essential skills and knowledge for a wide range of employment. In addition, both digital communications and software engineering are active areas of research within the Faculty, and this unit (and the other MDC courseware units) contribute to the Faculty's research-teaching nexus.

Objectives

Knowledge and Understanding (Cognitive Domain Objectives) (29 May 2006, 10:55pm)

Upon completion the student will

K1. Have knowledge of software engineering models and methods for digital communications systems

K2. Understand the complexity of large systems and models to master this complexity in prototyping, simulation, design and implementation

and be able to

K3. Apply methods and concepts of component-based software architecture, real-time systems design and concurrent process models

K4. Analyse concurrent, parallel and distributed models for deadlocks and other anomalies

Attitudes, Values and Beliefs (Affective Domain Objectives) (29 May 2006, 10:55pm)

Upon completion, the student will:

A1. be aware of the best practice of concurrent/distributed systems development and the responsibilities placed on software engineers for predictable software systems behaviour

Practical Skills (Psychomotor Domain Objectives) (29 May 2006, 2:08pm)

Upon completion the student will be able to

P1. apply software engineering methods and tools in the development of digital communications software

Relationships, Communication and TeamWork (Social Domain Objectives) (25 May 2006, 11:43pm)

Upon completion, the student will be able to

S1. Work in a software engineering team on a digital communications application.

S2. Present a digital communications software engineering project.

Unit Content

Summary (01 Jun 2006, 3:55pm)

ASCED Discipline Group Classification: 020103 Programming

Additional classification: 02017 Operating Systems

Software engineering models and methods including software specifications, component-based software architectures, object-oriented analysis and design, version control, real-time systems, synchronous and asynchronous systems, concurrency issues, critical sections, mutual exclusions, semaphores, parallel computing, internet protocols and distributed programming.

Handbook Summary (29 May 2006, 1:47pm)

Software engineering models and methods including software specifications, component-based software architectures, object-oriented analysis and design, version control, real-time systems, synchronous and asynchronous systems, concurrency issues, critical sections, mutual exclusions, semaphores, parallel computing, internet protocols and distributed programming.

Recommended Reading (29 May 2006, 10:56pm)

To be advised

Teaching Methods

Mode (26 May 2006, 12:07am)

On campus

Strategies of Teaching (26 May 2006, 12:08am)

2 hours lecture, 2 hours tutorial or laboratory class.

Teaching Methods Relationship to Objectives (29 May 2006, 2:12pm)

The lectures will address objectives K1-K4 and A1. The classes will reinforce K3, K4 and A1 and will address objective P1.

Assessment

Strategies of Assessment (26 May 2006, 12:14am)

Assessment is 100% assignments.

Assessment Relationship to Objectives (29 May 2006, 10:57pm)

Assessment is 100% by assignments. The programming assignments will ensure objectives A1, K3, K4 and P1 are met and will also indirectly test K1-K2. Some assignment work will be undertaken in groups, addressing objectives S1 and S2. Directed reading and research assignments will contribute to objectives K1, K2 and A1.

Workloads

Workload Requirement (26 May 2006, 12:16am)

2 hours of lectures; 2 hours of practical or laboratory class; 8 hours private study, including working on assignments, doing directed reading, preparing for and revising lecture material.

Resource Requirements

Lecture Requirements (26 May 2006, 12:16am)

2 hours of lectures per week for 13 weeks of semester in high-tech lecture theatre

Tutorial Requirements (29 May 2006, 10:58pm)

None

Laboratory Requirements (26 May 2006, 12:17am)

2 hour classes per week in laboratory, which will be a combination of tutorial and practical class.

Staff Requirements (26 May 2006, 12:20am)

Staff member to lecture 2 hours per week, member of staff active in software engineering research area and familiar with digital communications.

Tutor/demonstrator to take 2 hours tutoria/practical class per week, experienced in programming, SE tools and techniques, and digital communications applications.

Software Requirements (29 May 2006, 1:51pm)

Pracs will use modern integrated development environments (IDE) for software such as Eclipse and/or Borland or Rational running under Linux. A recent Java environment will be assumed to exist in labs including appropriate Java support in the IDE itself.

Library Requirements (29 May 2006, 10:58pm)

Copies of the reference books on the reading list to be provided.

Teaching Responsibility (Callista Entry) (26 May 2006, 12:21am)

Faculty of IT

Implications for CASPA (26 May 2006, 12:21am)

None

Interfaculty Involvement (26 May 2006, 12:21am)

None.

Interschool Involvement (26 May 2006, 12:21am)

None

Other Resource Requirements (26 May 2006, 12:22am)

None.

Prerequisites

Prerequisite Units (26 May 2006, 12:23am)

None.

Corequisites (26 May 2006, 12:22am)

None

Prohibitions (01 Jun 2006, 3:54pm)

ECE4410 and ECE5410

Alias Titles (26 May 2006, 12:24am)

None

Level (29 May 2006, 11:49pm)

5

Proposed year of Introduction (for new units) (26 May 2006, 12:24am)

Semester 1 or Semester 2 in 2008.

Frequency of Offering (26 May 2006, 12:25am)

Will probably be offered in alternate years with FIT4014 Digital Communications software.

Enrolment (26 May 2006, 12:26am)

30-60 (estimate only)

Location of Offering (26 May 2006, 12:26am)

Clayton Campus

Faculty Information

Proposer

David Sole

Approvals

School: 22 Oct 2010 (Geraldine DCosta)
Faculty Education Committee: 22 Oct 2010 (Geraldine DCosta)
Faculty Board: 22 Oct 2010 (Geraldine DCosta)
ADT:
Faculty Manager:
Dean's Advisory Council:
Other:

Version History

23 May 2006 David Sole Initial Draft; modified UnitName
26 May 2006 Ann Nicholson modified Abbreviation; modified ReasonsForIntroduction/RIntro; modified ReasonsForIntroduction/RChange; modified ReasonsForIntroduction/RRole; modified ReasonsForIntroduction/RRelation; modified ReasonsForIntroduction/RRole; modified ReasonsForIntroduction/RRelevance; modified UnitObjectives/ObjText; modified UnitObjectives/ObjCognitive; modified UnitObjectives/ObjPsychomotor; modified UnitObjectives/ObjSocial; modified UnitContent/Summary; modified UnitContent/HandbookSummary; modified Teaching/Mode; modified Teaching/Strategies; modified Teaching/Objectives; modified Assessment/Strategies; modified Assessment/Objectives; modified Assessment/Strategies; modified Workload/WorkHours; modified ResourceReqs/LectureReqs; modified ResourceReqs/LabReqs; modified ResourceReqs/LabReqs; modified ResourceReqs/StaffReqs; modified ResourceReqs/SoftwareReqs; modified ResourceReqs/LibraryReqs; modified ResourceReqs/SchoolReqs; modified ResourceReqs/CaspaImpact; modified ResourceReqs/InterFaculty; modified ResourceReqs/IntraFaculty; modified ResourceReqs/OtherResources; modified Corequisites; modified Prohibitions; modified Prerequisites/PreReqUnits; modified Prerequisites/PreReqKnowledge; modified AliasTitles; modified Level; modified DateOfIntroduction; modified Frequency; modified Enrolment; modified Enrolment; modified LocationOfOffering; modified FacultyInformation/FIContact; modified FacultyInformation/FIContact; modified FacultyInformation/FICoordinator
26 May 2006 Ann Nicholson modified UnitObjectives/ObjAffective; modified Classification; modified Classification
29 May 2006 Ann Nicholson modified Level; modified FacultyInformation/FICoordinator
29 May 2006 Ann Nicholson
01 Jun 2006 Ann Nicholson modified UnitContent/Summary; modified Prohibitions; modified UnitContent/Summary
01 Jun 2006 Ann Nicholson
01 Jun 2006 Ann Nicholson
09 Jun 2006 Geraldine DCosta FIT School Approval, Approved for submission FEC Mtg 3/06
19 Jun 2006 Ralph Gillon FEC Approval
29 Jun 2006 Ralph Gillon FacultyBoard Approval
22 Oct 2010 Geraldine DCosta modified UnitName - Added Disestablished comment.
22 Oct 2010 Geraldine DCosta FIT5009 Chief Examiner Approval, ( proxy school approval )
22 Oct 2010 Geraldine DCosta FEC Approval
22 Oct 2010 Geraldine DCosta FacultyBoard Approval - GPC 4/10 endorsed and FEC 4/10-Item 8.7.2- approved disestablishment of this unit. Faculty Board approval has been added to aid administration in Monatar.

This version: