COMPGS01 - Requirements Engineering and Software Architecture
This database contains 2016-17 versions of the syllabuses. For current versions please see here.
|Code||COMPGS01 (Also taught as: COMPM014)|
|Prerequisites||Knowledge and practical experience of software engineering at least equivalent to undergraduate third year study.|
|Taught By||Emmanuel Letier (100%)|
|Aims||The course will train students in the fundamental principles and latest techniques in systems requirements engineering and software architecture.|
|Learning Outcomes||Students will learn how to discover, model, analyse and communicate requirements for software intensive systems and how to design, evaluate and communicate software architecture that meet these requirements. The emphasis will be on developing the students' modelling skills and their ability to communicate requirements and architectures with clarity and precision to business stakeholders and software developers.|
System Requirements Engineering
Goal-oriented requirements engineering, requirements engineering in agile projects.
Architecture modelling, architectural styles, quality requirements.
Method of Instruction:
Each week the students will be given a concrete problem to solve and materials to read to help them solve the problem. The problem solutions and reading materials will be discussed in class followed by additional lectures summarizing fundamental principles discovered while solving the problems. The second part of the module will require students to work in groups to solve a case study and present their work to experienced IT consultants.
The course has the following assessment components:
- Written Examination (2.5 hours, 75%)
- Coursework Section (2 pieces, 25%)
To pass this module, students must:
- Obtain an overall pass mark of 50% for all components combined.
Lecture notes and readings will be given during the course.
The main references are the following:
Alex van Lamsweerde, Requirements Engineering: From System Goals to UML Models to Software Specifications, Wiley, 2009.
Gojko Adzic, Impact Mapping: Making a big impact with software products and projects, 2012.
Nick Rozanski and Eoin Woods. Software Systems Architecture: working with stakeholders using viewpoints and perspectives. Addison-Wesley Professional, 2011.