ITE505 Enterprise Applications Development (8)
CSU Discipline Area: Unallocated to a CSU Discipline code (OTHER)Unallocated to a CSU Discipline code (OTHER)
Duration: One session
Abstract:
This subject gives students the skills required to design and develop complex applications for an enterprise business environment.
+ Subject Availability Modes and Locations
No offerings have been identified for this subject in 2013.Continuing students should consult the SAL for current offering details prior to contacting their course coordinator: ITE505
Where differences exist between the handbook and the SAL, the SAL should be taken as containing the correct subject offering details.
Prerequisite(s):
Enrolment restrictions:
Available only to students in the Master of Systems Development, Graduate Certificate in Systems Development and Master of Management (IT).
Objectives:
Upon successful completion of this subject, students should:
- be able to evaluate the technical feasibility of an application design concept;
- be able to evaluate the technical specifications for an application to ensure that the business requirements are met;
- be able to evaluate the design of a database;
- be able to evaluate the logical design of an application;
- be able to evaluate the physical design of an application.
- be able to create the high-level design of a component;
- be able to develop the public API of a component;
- be able to develop a component feedback mechanism;
- be able to develop the data access and data handling features of a component;
- be able to choose an appropriate implementation approach for the application design logic;
- be able to perform a code review;
- be able to evaluate the testing strategy;
- be able to perform integration testing;
- be able to evaluate a deployment plan;
- be able to validate the production configuration environment.
Syllabus:
The subject will cover the following topics:
* Aspects of physical design * The life cycle of a component * Application features and goals * Implementation considerations * Pseudo code and UML diagrams * Component design patterns * Tradeoff decisions * Component development * Analysis of data relationships * Profiling * Multimedia message delivery * Data flow structures * Verifying deployment
The information contained in the 2013 CSU Handbook was accurate at the date of publication: 24 April 2013. The University reserves the right to vary the information at any time without notice.