Software Requirements Analysis

Subject SWEN90009 (2011)

Note: This is an archived Handbook entry from 2011.

Credit Points: 12.50
Level: 9 (Graduate/Postgraduate)
Dates & Locations:

This subject is not offered in 2011.
Time Commitment: Contact Hours: 36 hours consisting of 24 one-hour lectures (two per week) and 12 one-hour one-hour workshops (one per week)
Total Time Commitment: 120 hours
Prerequisites:

The prerequisites are:

Subject
Study Period Commencement:
Credit Points:
Not offered in 2011
12.50
Corequisites: None
Recommended Background Knowledge: 433-606 Modelling Complex Software Systems
Non Allowed Subjects: 433-646 Requirements Engineering
433-446 Requirements Engineering
Core Participation Requirements: For the purposes of considering request for Reasonable Adjustments under the Disability Standards for Education (Cwth 2005), and Students Experiencing Academic Disadvantage Policy, academic requirements for this subject are articulated in the Subject Description, Subject Objectives, Generic Skills and Assessment Requirements of this entry.The University is dedicated to provide support to those with special requirements. Further details on the Disability support scheme can be found at the Disability Liaison Unit Website: http://www.services.unimelb.edu.au/disability/

Contact

Dr Adrian Pearce

email: adrianrp@unimelb.edu.au

Subject Overview:

The first step in the development of a any non-trivial software system is an analysis of the problem domain in order to formulate a set of ‘requirements’. In this subjects students will explore 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.
Objectives: Please refer to Overview.
Assessment: Project work during semester, expected to take about 36 hours (50%); and a 3-hour end-of-semester written examination (50%). To pass the subject, students must obtain 25/50 in project work, and 25/50 in the written examination.
Prescribed Texts:

None
Breadth Options:

This subject is not available as a breadth subject.
Fees Information: Subject EFTSL, Level, Discipline & Census Date
Generic Skills:

On completion of this subjects the student should:

  • Ability to apply knowledge of science and engineering fundamentals
  • Ability to undertake problem identification, formulation, and solution
  • Ability to utilise a systems approach to complex problems and to design and operational performance
  • Understanding of the business environment
  • Ability to communicate effectively, with the engineering team and with the community at large
  • Ability to manage information and documentation
  • Capacity for creativity and innovation
  • Understanding of professional and ethical responsibilities, and commitment to them
  • Ability to function effectively as an individual and in multidisciplinary and multicultural teams, as a team leader or manager as well as an effective team member
Related Course(s): Bachelor of Computer Science (Honours)
Related Majors/Minors/Specialisations: B-ENG Software Engineering stream
Master of Engineering (Software)

Download PDF version.