MN507 - Overview of Software Engineering

Credit Points: 20

Prerequisite: N/A

Co-requisite: N/A

Workload: 60 contact hours

Campus: Melbourne, Sydney

Aims & Objectives

This is an elective unit out of a total of 12 units in the Master of Networking (MNet). This unit addresses the MNet course learning outcomes and complements other courses in a related field by developing students’ specialised knowledge in software engineering and applying critical skills in software: enterprise architecture. For further course information refer to: This unit is part of the AQF level 9 (MNet) course.

This unit provides an overview of the field of software engineering, with emphasis on key aspects of the system development lifecycle (SDLC) such as requirements engineering, analysis, design, and testing.   Object oriented and service oriented architectures are introduced, along with information systems design.  There is also an introduction to estimation for software projects, process and project metrics, and the use of CASE tools.

The unit will introduce students to the most common concepts, processes, techniques, and theories essential in software development, and analyse and discuss the common issues that software engineers and developers often face and methods to overcome them.

This unit will cover the following topics:

  1. Software Engineering Overview
  2. Software Process 
  3. Software Planning and Specification
  4. Software Requirements Analysis and Specification
  5. Software Prototyping
  6. Software Design Techniques
  7. Database Design
  8. Object Oriented and Service Oriented Design
  9. Implementation – Software Building, Testing, Documentation and Maintenance
  10. Software Quality Assurance
  11. Software Configuration Management

Learning Outcomes

On successful completion of this unit, students should be able to:

  1. Determine system requirements through requirements elicitation and workshops.
  2. Design processes for verification and validation of system requirements.
  3. Use appropriate modelling techniques to specify system requirements.
  4. Produce and communicate to others the functional specifications of a system.
  5. Compare and contrast different Software Engineering process models: waterfall, evolutionary, spiral, prototyping.
  6. Produce a system implementation, and design and implement integration and testing plans.
  7. Investigate state of the art software engineering techniques and technologies, and their scope of applicability for software Engineering, specifically related to service orientation: e.g. XML, SaaS, SOA.

Teaching Method

Lecture: 2 hours
Laboratory: 2 hours
PBL Tutorial: 1 hours
Face to Face


Assessment Task
Learning Outcomes Assessed
Midterm Test a-c,e*10%
Assignment 1a-c*15%
Assignment 2a-d, f-g*25%
Laboratory and Problem Based Learning participation & submissiona-g*10%
Final Examination (2 hours)a-g*40%
Total 100%

*refer to learning outcomes above.


  • Pressman, Roger S.,. Software Engineering – A Practitioner’s Approach. McGraw-Hill Inc. New York, USA, 8th Edition. 2014

Reference Reading

  • I. Sommerville, Software Engineering 10th ed.. Addison Wesley, Wokingham, England: 2015.
  • J. W. Satzinger, R. B. Jackson, and  S. D. Burd, 7th ed. System Analysis and Design in a Changing World Cambridge. 2015.
  • K. E. Kendall and J. E.  Kendall, Systems Analysis and Design.  9th ed Pearson Education Inc. 2015.

MIT is committed to ensure the course is current, practical and relevant so that graduates are “work ready” and equipped for life-long learning. In order to accomplish this, the MIT Graduate Attributes identify the required knowledge, skills and attributes that prepare students for the industry.
The level to which Graduate Attributes covered in this unit are as follows:

Ability to communicateIndependent and Lifelong LearningEthicsAnalytical and Problem SolvingCultural and Global AwarenessTeamwork Cooperation, Participation and LeadershipSpecialist knowledge of a field of study


Colour coding    

Extent covered

                               The standard  is covered by theory and practice, and addressed by assessed activities in which the students always play an active role, e.g. workshops, lab submissions, assignments, demonstrations, tests, examinations
 The standard is covered by theory or practice, and addressed by assessed activities in which the students mostly play an active role, e.g. discussions, reading, intepreting documents, tests, examinations
 The standard is discussed in theory or practice; it is addressed by assessed activities in which the students may play an active role, e.g. lectures and discussions, reading, interpretation, workshops, presentations 
 The standard is presented as a side issue in theory or practice; it is not specifically assessed, but it is addressed by  activities such as lectures or tutorials
 The standard  is not considered, there is no theory or practice or activities associated with this standard