GCO2813 Information Systems 2 has been a core unit in the Bachelor of Computing since the inception of the degree. The unit addresses systems development process tools, as well as approaches and role of design, implementation and maintenance.

FEC 3/03 Reasons for Change
GCO2813 Information Systems Design is one of the proposed core units for the Business Systems and Systems Development majors of the Bachelor of Information Technology. 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.

FEC 4/04
Addition of Summer semester 2005

FEC 3/04
2004 update of recommended reading and unit adviser

UGPSC 3/06 and FEC 3/06 {\nl} Change of semester of offering to Semester 2, effective for 2007. Change of Handbook Entry for 2007 Handbook.

UGPSC 2/07
Because many of the topics which previously were covered by GCO2813 will now be covered to the same depth in GCO1813 (which is aligned to FIT2001 until taught-out), the unit FIT2005 which follows on from FIT2001 was 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. That unit now becomes an 'advanced analysis and design' unit, thus extending on its prerequisite. GCO2813 will be teaching the content of FIT2005, so this change is to bring GCO2813 into alignment with FIT2005.

The unit provides students with an advanced understanding of object oriented analysis and design using UML. This enables students to develop detailed system designs which can then be used for implementation.

It also covers issues pertaining to implementation and deployment phases of the SDLC.

The material in this unit follows on from GCO1813 which presents a high-level introduction to the topic of analysis and design. This unit prepares students for the final year project (GCO3700, GCO3800, GCO3900).

As IT develops and become more pervasive throughout organisations, there is an increasing need for graduates who are able to design systems to meet those organisations' software needs. All students in the Bachelor of IT, and in the Bachelor of Computing need to gain experience in the design of systems, and to understand the process by which system designs are developed.

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

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.

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.

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.

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.

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.

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

Same as for FIT2005 (Timetable together)

Same as for FIT2005

Nil

One lecturer for each campus offering each semester. A tutor per tutorial for each campus offering each semester. Unit co-taught with FIT2005 until no more enrolments occur.

• 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:

Library collections for existing GCO2813 will support this unit's needs.

FIT

Nil

Nil

Nil

GCO1813 or GCO2601 or GCO2852 or GCO2826 or equivalent