Note: This is an archived Handbook entry from 2016.
|Dates & Locations:|| |
This subject has the following teaching availabilities in 2016:Semester 1, Parkville - Taught on campus.
Timetable can be viewed here. For information about these dates, click here.
|Time Commitment:||Contact Hours: 36 hours, comprising of two 1-hour lectures and one 1-hour workshop per week |
Total Time Commitment:
The following subjects may be taken concurrently:
Study Period Commencement:
Semester 1, Semester 2
June, Semester 1, Semester 2
|Recommended Background Knowledge:||
4433-606 Modelling Complex Software Systems4
SWEN40004 Modelling Complex Software Systems
|Non Allowed Subjects:||
Students cannot enrol in and gain credit for this subject and:
433-646 Requirements Engineering
|Core Participation Requirements:||
For the purposes of considering request for Reasonable Adjustments under the Disability Standards for Education (Cwth 2005), and Student Support and Engagement Policy, academic requirements for this subject are articulated in the Subject Overview, Learning Outcomes, Assessment and Generic Skills sections of this entry.
It is University policy to take all reasonable steps to minimise the impact of disability upon academic study, and reasonable adjustments will be made to enhance a student's participation in the University's programs. Students who feel their disability may impact on meeting the requirements of this subject are encouraged to discuss this matter with a Faculty Student Adviser and Student Equity and Disability Support: http://services.unimelb.edu.au/disability
CoordinatorDr Alex Lopez Lorca
The aim of this subject is to give students an understanding of the theoretical and technical principles behind systems analysis and software requirements engineering, applying techniques in a real-world project environment to analyse the requirements for systems.
The subject is core in the MC-ENG Master of Engineering (Software) degree.
The first step in the development of any non-trivial software system is an analysis of the problem domain in order to formulate a requirements specification. In this subject students will explore the aims, principles, processes and techniques involved in business and domain analysis and the formulation of requirements. Topics covered will include: an understanding of the domain analysis problem; business and domain analysis; an exploration of methods for eliciting, analysing, specifying and validating requirements; requirements metrics; analysis techniques for ‘special domains’ drawn from a selection of enterprise systems, safety critical systems, usability and security.
INTENDED LEARNING OUTCOMES (ILO)
At the completion of this subject the student is expected to:
1) Be able to understand the role of requirements in software engineering projects
2) Be able to understand the different types of requirements, the methods for their specification and the role that they play in system analysis
3) Be able to understand the methods for the elicitation, analysis and specification of system requirements and to be able to apply those methods in practice
4) Be able to select methods appropriate to a particular application or problem
5) Work together in a team that interacts with clients/stakeholders to elicit requirements.
• A team-based project (60%) with 3 to 5 team members throughout the semester due in Weeks 9 to 10, each member committing approximately 50 - 55 hours of work, ILO’s 3 - 5 are addressed in the project
• An individually-based reflective essay not exceeding 500 words, submitted in week 12, requiring approximately 5 – 10 hours of work, per student (5%) ILO’s 1, 2 and 4 are addressed in the assignment
• An individually-based requirements review, submitted in week 12, requiring approximately 20-30 hours of work, per student (15%) ILO's 1, 2 and 4 are addressed in the assignment
• A 3-hour end-of-semester written examination (40%). ILOs 1, 2, and 4 are addressed by the end-of-semester examination.
Hurdle requirement: To pass the subject, students must obtain at least 50% overall and
• at least 50% (30/60) in project work; and
• at least 50% (20/40) in the written examination.
Intended Learning Outcomes (ILOs) 1 and 2 are addressed by the individual assignments. ILOs 3 - 5 are addressed by the team project. ILOs 1, 2, and 4 are addressed by the end-of-semester examination.
|Prescribed Texts:|| |
|Breadth Options:|| |
This subject is not available as a breadth subject.
|Fees Information:||Subject EFTSL, Level, Discipline & Census Date|
On completion of this subjects the student should have the following skills:
LEARNING AND TEACHING METHODS
The subject comprises a two one-hour lectures and one hour workshop per week. The lectures are used to elaborate and interpret material and the workshops are designed to assist students in applying theory in their project and assignment work. The project forms a major component of the practical application of the subject and is used to focus a significant part of the teaching on a practical problem.
INDICATIVE KEY LEARNING RESOURCES
The subject is administered through the Universities Learning Management System (LMS). Templates for the various artefacts, guidelines on analysis processes and links to requirements analysis tools are available through the LMS. A standard environment is made available that includes modelling and diagramming facilities together with material compiled from a number of popular and current textbooks and available textbooks.
CAREERS / INDUSTRY LINKS
The software industry is expanding and along with it the demand for software engineers that are capable of the analytical and management skills beyond programming. The industry is also changing in the nature of the projects being undertaken with many software engineers now working in multidisciplinary project teams. The skills and experience gained in this subject are valued by employers and are often seen as a necessary grounding for a career in software and technology related industries.
The subject provides students with a realistic environment in which to apply and learn the theory and practice of requirements engineering. Projects are chosen to reflect real-world considerations. Industry guest speakers are invited to provide lectures in relation to specialised project requirements.
Doctor of Philosophy - Engineering |
Master of Philosophy - Engineering
B-ENG Software Engineering stream |
Master of Engineering (Software with Business)
Master of Engineering (Software)
Download PDF version.