Last modified: 22 May 2019 17:07
Students will develop large commercial and industrial software systems as a team-based effort that puts technical quality at centre stage. The module will focus on the early stage of software development, encompassing team building, requirements specification, architectural and detailed design, and software construction. Group work (where each team of students will develop a system selected using a business planning exercise) will guide the software engineering learning process. Teams will be encouraged to have an active, agile approach to problem solving through the guided study, evaluation and integration of practically relevant software engineering concepts, methods, and tools.
|Session||First Sub Session||Credit Points||15 credits (7.5 ECTS credits)|
|Campus||Old Aberdeen||Sustained Study||No|
Principles of software engineering aims at providing students with both an in-width and an in-depth understanding of disciplined approaches to the software development process, which facilitates the further in-depth understanding gained during the subsequent practice-based sibling course in term two.
Teamwork-based practicals focusing on the preliminary stage of a software development project chosen by students aims at complementing the learning process.
Main Learning Outcomes
Project management issues: Team organisation, time and cost estimation, risk analysis.
Software analysis and design issues: Requirements elicitation, developing a system specification through use cases, architectural design, detailed design, design patterns.
Software implementation and quality issues: Testing strategies and methods; quality assurance and management; software verification and validation; software documentation and maintenance.
This is the total time spent in lectures, tutorials and other class teaching.
1 two hour written examination (75%);
continuous assessment (25%).
Continuous assessment includes 1 teamwork project white paper (10 pages); 1 teamwork project initial technical report (10 pages); 1 proof-of concept software release.
1 two hour written examination (75%).
As it is not possible to resit the teamwork-based coursework, an alternative individual equivalent task will be assigned to the student in case of resit of the coursework component.
Collective verbal team discussion with groupwork project guides (every fortnights) and with course organiser (every month or so). Individual MyAberdeen-based technical assignments(every two weeks) with team leader reporting.
Due to the groupwork-based nature of most assignments, feedback is provided by team guides (and by the course organiser) during the appropriate meetings (see above). Feedback for individual tasks is verbally provided as part of the team strength discussion between the course organiser and the team leaders.