Home | About Us | Courses | Units | Student resources | Research |
IT Support | Staff directory | A-Z index |
M O N A T A R |
InfoTech Unit Avatar |
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
Define here the original reasons for the introduction of the unit
Introduced for course architecture programs. Effective semester 1, 2016
07/12/2017 - Unit disestablished at FEC 5/17 Item 7.3.
At the completion of this unit students should be able to:
02013, 02035
The aim of this unit will be to provide students with the opportunity to apply and further enhance their systems development skills. Students will work in teams in a studio environment using an iterative development approach to produce an information system for the different stakeholders of a typical systems development case study. Case study work will begin with the student team being provided with a business scenario and a poorly designed system that has been created, as a first attempt to meet the information needs of the stakeholders in the case study. The starting system will have a number of shortcomings: the functionality will not be sufficient, the interface will be difficult to use, there will be no thought given to security and the database design will not prevent redundant and inconsistent data from being stored in system. The teams will analyze the case study and identify the shortcomings of the current system and develop a phased development plan for the improvement and expansion of the system. The student teams will then implement this plan as they work collaboratively applying, expanding and consolidating the development skills they have acquired in other units. The skills they will apply will include requirements development, requirements prioritization, interface design, database design, iterative software development, source code version management, testing, implementation, report writing and presentations and working in a team.
Minimum total expected workload equals 12 hours per week comprising:
(a.) Contact hours for on-campus students:
TBA
Clayton
Janet Fraser
04 Sep 2015 | Ange Delbianco | Introduced for course architecture programs. Effective semester 1, 2016 |
07 Dec 2017 | Christy Pearson | modified UnitName; modified ReasonsForIntroduction/RChange |
This version:
Copyright © 2022 Monash University ABN 12 377 614 012 – Caution – CRICOS Provider Number: 00008C Last updated: 20 January 2020 – Maintained by eSolutions Service desk – Privacy – Accessibility information |