Software Architecture, Process, and Management (Level 10) (U02937)

? Credit Points : 10 ? SCQF Level : 10 ? Acronym : INF-4-SAPM

The aim of this module is to introduce you to key concepts in the design and implementation of large scale, long lived software systems. The course gives students some practical experience of working in a team faced with planning a long-term project for developing a large software system. It helps them to be aware of common threats to such projects and how to address them. It also gives students a repertoire of high-level design and architectural patterns and guides students in applying them.

Entry Requirements

? Pre-requisites : Successful completion of Year 3 of an Informatics Single or Combined Honours Degree, or equivalent by permission of the School.

? Co-requisites : Software Engineering with Objects & Components is a worthwhile companion course, although not required.

? Prohibited combinations : Software Architecture, Process, and Management (Level 11)

Subject Areas

Home subject area

Software Engineering, (School of Informatics, Schedule O)

Delivery Information

? Normal year taken : 4th year

? Delivery Period : Semester 2 (Blocks 3-4)

? Contact Teaching Time : 2 hour(s) per week for 10 weeks

All of the following classes

Type	Day	Start	End	Area
Lecture	Tuesday	15:00	15:50	Central
Lecture	Friday	15:00	15:50	Central

Summary of Intended Learning Outcomes

It is anticipated that students who complete the course will be able to:
* Select and apply an appropriate design pattern.
* Select and apply appropriate existing architectures for large-scale, long-lived systems.
* Explain how refactoring can be used to preserve good design as programs are modified
* Explain why software reuse is difficult, and some approaches for increasing software reuse
* Summarize and apply approaches for maintaining and replacing legacy code
* Compare lightweight ("agile") and heavyweight design processes, and know how to apply at least one example of both to a new project.
* Analyze the significant sources of risk for particular projects and suggest ways to reduce the risks.
* Describe and be able to use tools for automating large-scale, long-term development, such as configuration, build, test, and project management tools
* Integrate one's work with that of others in a team faced with the high-level design of a large software system.