SG4101 Basic Software Engineering Discipline
This is the first module for all SE students. It lays the groundwork by equipping students with the necessary process knowledge for engineering a software intensive system as well as on object-oriented concepts and programming. This module is compulsory for all SE students.
In the Software Engineering Process submodule, the students will learn about software engineering processes and how to model these processes using an appropriate methodology. It looks at software development life cycle processes, processes for planning and controlling software development and quality management processes.
In the Introduction to Object-Oriented Programming submodule, the students will learn the basic concepts of object orientation. It also covers topics of basic object modelling and object-oriented programming, illustrated with the Java programming language and development environment. Students will also learn about test-driven development and software configuration management.
Two assignments would require the students are to demonstrate their competencies in software engineering process, object modelling and programming
Pre-requisites: Basic Programming Concepts
SG5101 Software Analysis & Design
The module answers the question of what should take place before coding can start, given the user requirements. It covers in details the steps required to get from the requirements specification through the detailed design specification using a use case-driven development approach along with Unified Modelling Language notations.
Given the User Requirements Specification, Requirements Modelling is performed to analyse the functional requirements to produce the Use Case Model which comprises actors, use cases, relationships among actors and/or use cases as well as the description of use cases. The Domain Object Model is also produced to capture the essential business objects of the system.
Analysis Modelling is then performed for a use case where analysis objects are identified along with their state and responsibilities without considerations for implementation. The newly identified information are capture in the Analysis Model.
Based on the non-functional requirements in the User Requirements Specification, a Software Architecture is crafted for a suitable implementation platform; design strategies are devised for the operating environment. Design Modelling is then performed to transition the analysis objects in the Analysis Model to design objects with full class details in the Design Model.
Finally the system is implemented according to the Design Model. The source code are tested and documented.
An assignment would run through the four stages of Requirements, Analysis, Design and Implementation. The students are to demonstrate their competencies in the skills required in those stages.
Pre-requisites: Object Oriented Programming and Software Engineering Process
SG5102 Software Project Management
Project Initiation and Planning
Software development projects are diverse. They can range from developing applications to address specific business needs of an organisation to developing software products for commercial purposes to developing software that control hardware. Challenges abound in managing all software development projects!
Project management is the discipline of principles, processes and techniques that a project team uses to drive successful delivery of the software product.
Managing projects in software engineering covers the end-to-end activities that all software engineering students of the MTECH SE course need to know so that the knowledge and skills can be applied to projects they undertake.
Through the use of workshop case studies and discussion, lectures, flipped classroom methods and popup quizzes, students will be given the opportunity to engage in collaborative teamwork and self-learning to maximise their learning and assess their own learning journey.
The 10-day curriculum covers the project management processes and key knowledge areas required to manage the project. This includes identification and management of the project scope, estimating the overall project cost estimate, creation of a project work plan and schedule, execute, monitor and control the project development and management of quality and risks.
All work is achieved through people working in a team, an essential aspect that will also be addressed in the curriculum.
The culmination of the knowledge and skills will be applied through the final capstone project in the MTECH SE programme.
Continuous assessments, final exam and class participation will contribute to the overall assessment.
Pre-requisites: Nil
SG5103 Software Quality Management
The following core topics that ensure the quality of a software are covered in this Module:
a. Software Quality Management System
b. Peer Reviews
c. Software Configuration Management
d. Software Testing
Software Quality Management Systems
The aim of Software Quality Management (SQM) is to manage the quality of software and of its development process. A quality product is one which meets its requirements and satisfies the user. A quality culture is an organisational environment where quality is viewed as everyone's responsibility. CMMI® (Capability Maturity Model® Integration) for Development (CMMI-DEV), which provides a comprehensive integrated set of guidelines for developing products and services will be discussed.
CMMI models are collections of best practices that help organizations to improve their processes. These models are developed by product teams with members from industry, government, and the Carnegie Mellon University (CMU), Software Engineering Institute (SEI), Pittsburgh, PA, USA.
Peer Reviews
The purpose of a peer review is to provide "a disciplined engineering practice for detecting and correcting defects in software artefacts, and preventing their leakage into field operations". This course also describes rules, source documents and kin; the software inspection process, inspection roles and responsibilities; software inspection defect classifications; defect logging and peer review follow-up.
Software Testing
Purpose of testing is to detect software failures so that defects may be discovered and corrected. The scope of software testing often includes examination of code as well as execution of that code in various environments and conditions as well as examining the aspects of code: does it do what it is supposed to do and do what it needs to do. Automated testing techniques and tools will also be discussed in this module.
Software Configuration Management
The purpose of Software Configuration Management is to establish and maintain the integrity of the products of the software project throughout the project's software life cycle. Software Configuration Management involves identifying configuration items for the software project, controlling these configuration items and changes to them, and recording and reporting status and change activity for these configuration item.
Pre-requisites: Nil