This unit was introduced with the inception of the Bachelor of Information Technology and Systems degree.

It is a core unit for both the Major in Applications Development and Networks and the Major in Business Systems. It explores in detail the design phase of the systems development lifecycle, leading on from the common-core unit FIT2001 (Software Development).

(Note: Since its introduction, it has evolved to have a different focus as reflected by other more-recently approved Monatar fields).

April 2017. On behalf of CE and Lecturer, revising exam duration to 2 hours (with 30 minutes reading and noting time) to meet new University Examination procedures. Effective S2 2017.

September 2012: Added FIT1040 as an alternative prerequisite to FIT1002 for 2013. Approved by CE (Shane Moore) via email 28/08/2012.

The current proposed change is to the weighting of assessment.

In the past there has been 3 assignments and so the weighting placed on the assignments was 50% of the total assessment.

However, driven by a concern raised by the Head of School that the unit has had too much assessment activities (over-assessment) leading to too much time being spent actually assessing/marking the submitted work, compared to the time spent marking in other units in the school, there is a need to reduce the amount of assessment in the unit.

After considering a reordering of the unit's materials, a way has been identified by which it will be possible to adequately assess practical skills in just 2 assignments instead of three (by incorporating some of the third assignment's focus into the first, and move its other aspects into the exam).

So, given that there will now only be 2 assignments, it is considered that a more appropriate split for the unit will be 60% exam, and 40% non-exam, which is more in-line with most other units in the majors for which FIT2005 is included, where there are normally just 2 assignments that give a combined 40% of the marks. The assignment weightings became 50% only when the unit began having three assignments. Prior to then, it had been 40%.

The change is intended to be implemented in semester 2 of 2011.

28/4/2021 - Unit disestablished at FEC 2/21 Item 6.2

The unit provides students with an understanding of object oriented analysis and design using UML, and an understanding of software architecture. It focuses particularly on the dynamic aspects of a software system (interactions, state-machines), and on advanced structural aspects (polymorphism). It explores common patterns and archetypes and how these may be applied in the design of a software system. Software architecture is also examined in order to understand how different individual software items interact to form a larger, distributed system. This enables students to develop detailed system designs, which can then be used for implementation.

This unit prepares students to be able to do their final year project (FIT3047 and FIT3048).

All students in the Applications Development and Networks' and the Business Systems' majors need to gain experience in the design of systems, and to understand the process by which system designs are developed.

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.

020305

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.

On-campus and Off-Campus Learning(OCL)

Examination (2 hours plus 30 minutes reading and noting time): 60%; In-semester assessment: 40%

Minimum total expected workload equals 12 hours per week comprising:

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

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

(c.) Additional requirements (all students):

FIT

(One of FIT1040 or FIT1002) and FIT2001