Evaluate Software Architecture Assignment
Table of Contents
1 About This Sprint
This sprint reviews how to describe a non-trivial software system in the form of a software architecture.
In particular, the sprint focuses on evaluating your software architecture.
2 User Stories covered in this Sprint
- As a software designer I want to be able to divide my design into manageable chunks so that I can get a better overview.
- As a software designer I want to address the quality requirements of the software system early on so that they are not missed.
- As a software designer I want to address the quality requirements of the software system in the most appropriate way to facilitate the rest of the development project.
3 Learning Material
Please review the sprints on:
4 Experiential Learning
4.1 Assignment: Evaluate Initial Software Architecture
Evaluate your software architecture based on your initial list of quality attrbutes.
Tasks:
- For each quality attribute, how can you evaluate your architecture to see whether you meet your requirements or not?
- For each quality attribute, evaluate your architecture according to what you just decided.
- For each quality attribute and evaluation, reason about how you can improve your architecture to further meet your quality goals.
Document Structure:
The title for this Assignment Document is: Evaluation of Initial Software Architecture for System <system name>
.
The assignment document shall contain the following items:
- Title Page, according to the Title Page Instructions (Link)
System Description
A brief description (2-3 paragraphs) of your interpretation of what the goal of the system is.
- Quality Attributes
- Create one section for each quality attribute
- Describe how you plan on evaluating your architecture with respect to the quality attribute, and why this is a sufficient evaluation strategy.
- Evaluate your architecture, using relevant viewpoints, according to your evaluation strategy.
- Summarise your evaluation and any bottlenecks you find.
- Reason about how your architecture can be improved to remove the identified bottlenecks.
Commit and push this document to your project repository.
Conditions of Satisfaction: When marking this part of the assignment we are looking for the following:
- Does the title page contain a table with authors and author contribution?
- Size of assignment: Is the architecture evaluated from the perspective of 3-5 quality attrbutes?
- For each quality attribute, is the chosen evaluation strategy motivated?
- For each quality attribute, is the chosen evaluation strategy sufficient?
- For each quality attribute, is the architecture sufficiently evaluated using the described evaluation strategy?
- For each quality attribute, are the findings from the evaluation summarised?
- For each quality attribute, is there a sufficient reasoning about how to improve the architecture?
5 Sprint Acceptance Tests
You are done with this sprint when:
- You have evaluated your initial software architecture.
- You have committed/pushed the created documents to your project repository
You may also have
- Improved your initial software architecture based on your evaluation.
- Updated your Sprint Test Plan
- Updated your Course Backlog