1. Handbook
  2. Subjects
  3. Software Requirements Analysis
  4. Print

Software Requirements Analysis (SWEN90009)

Graduate courseworkPoints: 12.5On Campus (Parkville)

You’re viewing the 2019 Handbook:
Or view archived Handbooks


Year of offer2019
Subject levelGraduate coursework
Subject codeSWEN90009
Semester 1
FeesSubject EFTSL, Level, Discipline & Census Date


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


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.

Generic skills

On completion of this subjects the student should have the following skills:

  • 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 both with the engineering team, clients and the community at large
  • Ability to manage project-related 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

Eligibility and requirements


The following subjects may be taken concurrently:

Code Name Teaching period Credit Points
SWEN30006 Software Modelling and Design
Semester 1
Semester 2
SWEN90016 Software Processes and Management
Semester 1
Semester 2

Prerequisites do not apply to students in the 200 point program of the Master of Engineering.



Non-allowed subjects


Core participation requirements

The University of Melbourne is committed to providing students with reasonable adjustments to assessment and participation under the Disability Standards for Education (2005), and the Assessment and Results Policy (MPF1326). Students are expected to meet the core participation requirements for their course. These can be viewed under Entry and Participation Requirements for the course outlines in the Handbook.

Further details on how to seek academic adjustments can be found on the Student Equity and Disability Support website: http://services.unimelb.edu.au/student-equity/home



A team−based project (60%) throughout the semester with deliveries at various points between Weeks 4 to 12, each member requiring approximately 85 − 90 hours of work, Intended Learning Outcomes,(ILO’s) 2 − 5 are addressed in the project.

A 3−hour end−of−semester written examination (40%). ILO's 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.

Dates & times

  • Semester 1
    CoordinatorEduardo Araujo Oliveira
    Mode of deliveryOn Campus — Parkville
    Contact hours36 hours, comprising of two 1-hour lectures and one 1-hour workshop per week
    Total time commitment200 hours
    Teaching period 4 March 2019 to 2 June 2019
    Last self-enrol date15 March 2019
    Census date31 March 2019
    Last date to withdraw without fail10 May 2019
    Assessment period ends28 June 2019

    Semester 1 contact information

    Eduardo Araujo Oliveira


Time commitment details

200 hours

Further information

  • Texts

    Prescribed texts


  • Subject notes


    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.


    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.


    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.

  • Available through the Community Access Program

    About the Community Access Program (CAP)

    This subject is available through the Community Access Program (also called Single Subject Studies) which allows you to enrol in single subjects offered by the University of Melbourne, without the commitment required to complete a whole degree.

    Entry requirements including prerequisites may apply. Please refer to the CAP applications page for further information.

    Additional information for this subject

    Subject coordinator approval required

  • Available to Study Abroad and/or Study Exchange Students

    This subject is available to students studying at the University from eligible overseas institutions on exchange and study abroad. Students are required to satisfy any listed requirements, such as pre- and co-requisites, for enrolment in the subject.

Last updated: 30 July 2019