Skip to content | Change text size

M O N A T A R

InfoTech Unit Avatar

GCO9806 Systems analysis and design 2 (DISESTABLISHED FB 05/07)

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

GCO9806 Systems analysis and design 2 (DISESTABLISHED FB 05/07) (14 Dec 2007, 10:18am) [Analysis/Design 2 (25 Apr 2006, 7:25pm)]

Reasons for Introduction

Reasons for Introduction (03 Jun 2004, 1:38pm)

GCO9806 Information Systems 2 is an elective unit in the Graduate Diploma of Computing at Gippsland. The unit addresses systems development process tools, as well as approaches and role of design, implementation and maintenance. It has been renamed GCO9806 Information systems design to correspond to changes in ite prerequisite unit GCO9803 Information Systems Analysis.

This proposal serves several purposes. The first is to enter the unit into the Avatar system. The proposal also updates the name, objectives and content of the unit, and its location of offering. To date the unit has used structured analysis tools and methods. Whilst the unit will continue to address the range of design approaches and tools used in industry, this proposal seeks endorsement of a change to object-oriented analysis methods and tools.

Reasons for Change (26 Jan 2007, 3:18pm)

Original Reason
The Graduate Diploma of Computing and the Masters of Applied Information Technology have been reviewed and restructured jointly by all schools involved in teaching them. The changes have been designed to ensure smoother movement of students between the Graduate Diploma of Computing and the MAIT, and in light of changed immigration rules. This unit is being modified for this revised program. We have changed from OCL mode only to both on-campus and OCL modes.

FEC 3/06
Change of semester of offering to Semester 2, effective for 2007.

PGSC 1/07
Due to changes made to GCO2813, as a result of changes made to FIT2005, as a result of FIT2001 covering many topics previously covered by GCO2813/GCO9806, the description of GCO9806 needs to be brought into alignment with FIT2005/GCO2813.

This unit (GCO9806) is being changed so that it covers object-oriented analysis and design topics in greater depth and detail than previously, with a change of textbook to support it. The unit now becomes an 'advanced analysis and design' unit, thus extending on its prerequisite.

Significant changes: Objectives, Handbook Summary, Textbook, Prohibitions. This unit will be replaced with FIT9014 and GCO9806 will be discontinued.

Role of Unit (03 Jun 2004, 1:26pm)

GCO9806 Information Systems Design follows on from the core unit GCO9803 Information Systems Analysis and is a prerequisite for some of the third and fourth level units in the Graduate Diploma (including GCO3814, GCO3816) and in the MAIT. The unit further develops understanding of IS modelling as well as the implementation and management of systems.

Objectives

Knowledge and Understanding (Cognitive Domain Objectives) (25 Jan 2007, 3:13pm)

On successful completion of this unit students will:

C1. understand object-oriented concepts such as: association, aggregation and composition; polymorphism and generalisation; messaging and object interaction, state and lifespan of objects.

C2. know the syntax and semantics of the Unified Modelling Language with respect to modelling class diagrams, interaction diagrams, state machine diagrams, package diagrams, activity diagrams and deployment diagrams.

C3. have an understanding of the process by which object-oriented system analysis and design is performed using the Unified Process.

C4. be able to interpret or reason about models presented using UML notations and be able to explain the strengths and weaknesses of a particular design models.

C5. know how to present a system analysis or design as a proper collated document/report.

C6. be able to employ several common architectural and design patterns such as tiered computing, client/server, adapter, publisher/subscriber to design systems

C7. be able to explain what is involved in implementing, testing, installing, deploying a system in its final operating environment.

C8. understand aspect-oriented concepts such as: concerns, cross-cutting, aspects, themes, join-points, advice, concept-sharing, themes.

C9. have an understanding of the process by which aspect-oriented systems analysis and design is performed using the theme approach

Attitudes, Values and Beliefs (Affective Domain Objectives) (25 Jan 2007, 3:13pm)

On successful completion of this unit students will

A1. conform to industry agreed standards of representing models of system design by using the Unified Modelling Language

A2. appreciate that there is a diversity of possible different models of a system that could satisfy the requirements for a given system.

A3. be able to justify why they chose one model over other possible models in designing a system by evaluating the models' quality, limitations, scope for future extension.

A4. appreciate that organisations often institute standards to be followed in conducting a systems development project or presenting a systems design report.

A5. appreciate that in real-world systems development projects deliverables must meet agreed deadlines to minimise impact on later phases of the systems development life cycle or project costs.

Practical Skills (Psychomotor Domain Objectives) (25 Jan 2007, 3:14pm)

On successful completion of this unit students will be able to

P1. follow a suitable sequence of steps to produce UML models and associated supporting documentation that represents a software design for a small system.

P2. prepare and present a design specification for a system.

P3. complete tasks necessary to ensure a set of design models is complete and consistent, by identifying aspects of models which are only partially present, for example ensuring that a method appearing on a sequence diagram appears also in the class diagram.

P4. apply problem solving techniques at different levels of abstraction to develop a system's design.

P5. apply an iterative process of refining system design models to ensure consistency between components.

P6. utilise IT practioner tools to support the process and documentation of systems design.

Relationships, Communication and TeamWork (Social Domain Objectives) (25 Jan 2007, 3:14pm)

On successful completion of this unit student will

S1. be able to present written/printed design-phase deliverables that are usable by other people for implementation of a system.

Unit Content

Summary (25 Jan 2007, 3:15pm)

ASCED Discipline Group classification: 020305 Systems Analysis and Design

This unit examines object-oriented systems modelling/design in greater depth than the prerequisite unit. The key disciplines of the Unified Process will be examined to set a context for analysis and design. Students will learn about static and dynamic modelling, and component-based design, using UML. Some common design patterns will be studied. Some topics about system architecture are examined. The unit also briefly examines the topic of aspect-oriented analysis and design.

The unit prepares students to be able to design large systems such as will be implemented in their final year project unit or after graduation.

Handbook Summary (25 Jan 2007, 3:15pm)

This unit examines object-oriented systems modelling/design in greater depth than the prerequisite unit. The key disciplines of the Unified Process will be examined to set a context for analysis and design. Students will learn about static and dynamic modelling, and component-based design, using UML. Some common design patterns will be studied. Some topics about system architecture are examined. The unit also briefly examines the topic of aspect-oriented analysis and design.

The unit prepares students to be able to design large systems such as will be implemented in their final year project unit or after graduation.

Recommended Reading (25 Jan 2007, 3:15pm)

Prescribed textbook

Arlow, J. & Neustadt, I., UML 2 and the Unified Process, 2nd ed., Addison Wesley Professional, 2005. ISBN: 0321321278

Recommended Reading

Rumbaugh, J., Jacobson, I. & Booch, G., The Unified Modeling Language Reference Manual, 2nd ed., Addison Wesley Professional, 2005. ISBN: 0321245628

Blaha, M. & Rumbaugh, J., Object-Oriented Modeling and Design with UML, 2nd ed., Prentice-Hall, 2005. ISBN: 0131968599

Deacon, J. Object-Oriented Analysis and Design, Addison-Wesley, 2005. ISBN: 0321263170

Booch, G., Rumbaugh, J. & Jacobson, I., The Unified Modeling Language User Guide, 2nd ed., Addison Wesley Professional, 2005. ISBN: 0321267974

Lau, Y.-T., The Art of Objects: Object-Oriented Design and Architecture, Addison-Wesley, 2000. ISBN: 0201711613

Teaching Methods

Mode (02 Jun 2004, 6:14pm)

On-campus and off-campus learning modes

Strategies of Teaching (02 Jun 2004, 6:16pm)

On-campus students attend weekly lectures and tutorial sessions to achieve the objectives of the unit. Lectures will present theoretical concepts and examples for all objectives. Tutorials will give students opportunities to receive feedback on their understanding and implementation of the concepts and techniques covered by the unit.

Off-campus students receive detailed printed study materials, supplemented by web-based resources that lead them through the content of the unit. Students may communicate on matters related to the unit through the newsgroups.

Teaching Methods Relationship to Objectives (25 Jan 2007, 3:16pm)

Unit Book/Readings: C1-C9, A1-A3, S1
As this unit is being offered to both on and off campus students, the main source of information will be the printed materials, supported by other published materials.

Lectures: C1-C9, A1-A3
Lectures do not substitute for the learning that will occur from the readings, but will supplement the reading by offering alternative points of view and provide an interactive environment in which learners can ask questions for clarification, and in which an instructor may demonstrate processes.

Tutorials: C1-C9, A1-A3, P1, P3-P5
Tutorials give an opportunity for students to gain experience in applying the knowledge and in developing skills by doing exercises, and on-campus students will have the added advantage of being able to share and discuss exercise solutions in an interactive environment. (Off campus students will be able to use the asynchronous discussion groups to achieve a similar outcome).

Assignments: C1-C6, A1, A3-A5, P1-P5, S1
Assignments are intended to be learning activities with a particular focus on learning the practical skills (P1-P6), and confirming knowledge objectives by being required to make appropriate design decisions. Feedback on assignment work and sample solutions to assignments are also intended as learning resources for the learner to evaluate how well their performance was against the unit/assignment objectives.

Assessment

Strategies of Assessment (25 Jan 2007, 3:17pm)

Examination (3 hours): 60%
Assignments: 40%

Assessment Relationship to Objectives (02 Jun 2004, 6:22pm)

Examination (3 hours): 60% - Assignments: 40%

The examination will assess all objectives of the unit. The assignments will vary from offering to offering, but may test all objectives in the unit, particularly by encouraging research, reflection and practice. Assignments will serve as learning tools, not simply as assessment tools.

Workloads

Workload Requirement (02 Jun 2004, 6:22pm)

12 hours per week for 13 weeks

Resource Requirements

Lecture Requirements (26 Apr 2006, 2:06pm)

Same as for FIT2005 (schedule classes together, usually only a few students in this unit on campus)

Tutorial Requirements (26 Apr 2006, 2:06pm)

Same as for FIT2005

Laboratory Requirements (25 Jan 2007, 3:18pm)

Nil

Staff Requirements (26 Apr 2006, 2:05pm)

Same as for FIT2005

Software Requirements (25 Jan 2007, 3:18pm)

Same as for FIT2005

Library Requirements (25 Jan 2007, 3:23pm)

The prescribed book is already available in the library at all Australian campuses

Teaching Responsibility (Callista Entry) (26 Apr 2006, 2:05pm)

FIT

Implications for CASPA (25 Jan 2007, 3:19pm)

Nil

Interfaculty Involvement (25 Jan 2007, 3:19pm)

Nil

Interschool Involvement (25 Jan 2007, 3:20pm)

Nil

Other Resource Requirements (25 Jan 2007, 3:20pm)

Nil

Prerequisites

Prerequisite Units (02 Jun 2004, 6:30pm)

GCO9803

Prohibitions (31 May 2007, 3:44pm)

FIT9014 (Translation set FIT9014), GCO2816

Level (02 Jun 2004, 6:41pm)

9

Proposed year of Introduction (for new units) (03 Jun 2004, 1:42pm)

Semester 1, 2005

Frequency of Offering (25 Apr 2006, 7:27pm)

Semester 2

Enrolment (03 Jun 2004, 1:43pm)

25 students

Location of Offering (02 Jun 2004, 6:35pm)

Gippsland

Faculty Information

Proposer

Gour Karmakar

Approvals

School: 14 Dec 2007 (Julianna Dawidowicz)
Faculty Education Committee: 14 Dec 2007 (Julianna Dawidowicz)
Faculty Board: 14 Dec 2007 (Julianna Dawidowicz)
ADT:
Faculty Manager:
Dean's Advisory Council:
Other:

Version History

02 Jun 2004 Gour Karmakar Initial Draft;
03 Jun 2004 Kim Styles This is the initial entry of the unit into the Avatar. Updates and modifications have been made in preparation for inclusion in revised Grad Dip of Computing at Gippsland and in MAIT at Gippsland. Name has been changed, mode of offering now includes on-campus teaching, and enrolments have been updated.
18 Jun 2004 Kim Styles This is the initial entry of the unit into the Avatar. Updates and modifications have been made in preparation for inclusion in revised Grad Dip of Computing at Gippsland and in MAIT at Gippsland. Name has been changed, mode of offering now includes on-campus teaching, and enrolments have been updated. Prohibition to the equivalent undergraduate unit has been added.
18 Jun 2004 Kim Styles GCO School Approval, Approved at GSCIT Education Committee Meeting 3/04, 3/6/04 for transmittal to FEC 4/04
28 Jun 2004 Ralph Gillon FEC Approval
20 Jul 2004 Annabelle McDougall FacultyBoard Approval
17 Oct 2005 David Sole Added Software requrirements template
21 Oct 2005 David Sole Updated requirements template to new format
25 Apr 2006 Shane Moore modified Abbreviation; modified SemesterOfOfferring (for 2007 onwards); modified Prohibitions; modified FacultyInformation/FIContact
26 Apr 2006 Shane Moore modified Handbook Summary and Prescribed Reading (for 2007 onwards)
25 Jan 2007 Shane Moore Due to a change to the unit GCO2813/FIT2005, this unit has needed to be re-aligned for semester 2, 2007. Significant changes: Objectives, Handbook Summary, Textbook, Prohibitions.
26 Jan 2007 Iqbal Gondal modified ReasonsForIntroduction/RChange
26 Jan 2007 Iqbal Gondal
31 May 2007 Shane Moore modified Prohibitions
14 Dec 2007 Julianna Dawidowicz modified UnitName
14 Dec 2007 Julianna Dawidowicz GCO9806 Chief Examiner Approval, ( proxy school approval )
14 Dec 2007 Julianna Dawidowicz FEC Approval
14 Dec 2007 Julianna Dawidowicz FacultyBoard Approval - Faculty Board approved the disestablishment of this unit at 05/07 meeting

This version: