Undergraduate - UnitFIT2005 - Software analysis, design and architecture

This unit entry is for students who completed this unit in 2014 only. For students planning to study the unit, please refer to the unit indexes in the the current edition of the Handbook. If you have any queries contact the managing faculty for your course or area of study.

print version

6 points, SCA Band 2, 0.125 EFTSL

Refer to the specific census and withdrawal dates for the semester(s) in which this unit is offered, or view unit timetables.

Level	Undergraduate
Faculty	Faculty of Information Technology
Offered	Gippsland Second semester 2014 (Off-campus) South Africa Second semester 2014 (Day)

Synopsis

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 software architecture are examined.
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.

Outcomes

At the completion of this unit students will:

understand object-oriented concepts such as: association, aggregation and composition; polymorphism and generalisation; messaging and object interaction, state and lifespan of objects; encapsulation, connascence, domains, encumbrance, cohesion, coupling;
know the finer details of syntax and semantics of the Unified Modelling Language with respect to modelling class diagrams, interaction diagrams, state machine diagrams, package diagrams, activity diagrams, deployment diagrams, timing diagrams, interface and component diagrams;
be able to consider advanced topics in relation to use cases and specifications when analysing a system;
understand the role of software architecture, and be able to employ several common architectural such as tiered computing, client/server, pipes and filters, P2P, Layered implementation, publisher/subscriber, to design systems;
understand the role of patterns and pattern languages in designing systems, and be familiar with a range of structural, creational and behavioural patterns;
be able to apply theoretical concepts and techniques for problem solving, to design complete software systems in a range of settings;
be able to justify system design decisions with reference to a models quality, limitations, scope for future extension, and to theoretical concepts;
utilise IT practitioner tools to support the process and documentation of systems design;
be able to communicate the design of a system through electronic documents including UML models, other diagrams, and supporting text;
have an awareness of the process by which object-oriented system analysis and design is performed using a framework such as the Unified Process.

Assessment

Examination (3 hours): 60%; In-semester assessment: 40%

Workload requirements

Minimum total expected workload equals 12 hours per week comprising:

(a.) Contact hours for on-campus students:

One 2-hour lecture
One 2-hour laboratory

(b.) Study schedule for off-campus students:

Off-campus students generally do not attend lecture and tutorial sessions, however should plan to spend equivalent time working through the relevant resources and participating in discussion groups each week. Additionally, recordings of on-campus sessions may be available.

(c.) Additional requirements (all students):