CS 411:
Software
Architecture
Design

Instructor:
Dr. Bedir Tekinerdoğan
bedir@cs.bilkent.edu.tr

Final Project

The final project report will be an improved and extended version of the midterm project report. The improvements should consider the peer reviews and the evaluations of the instructor. The extensions will include a section on applying architectural patterns, evaluating software architecture based on scenario-based analysis approach and mapping architecture to object-oriented design.

The following points (most of the sections are reused from the midterm project report) need at least to be addressed:

Introductory Pages
These should include the title page and a table of contents.

Introduction - Update
Describes the context and the introduction of the project. The introduction briefly sets the context of the project, describes shortly the problem statement,  the adopted approach, and provides outline of the structure of the rest of the report.

Case Description - Update
Describe your case shortly. What kind of problem will you address? What is the goal of the project?  

The software architecture design process - Update
Describes the steps followed in designing the software architecture. These are essentially based on the synthesis-based software architecture design approach as discussed in the classes. Also explain the adoption of views and beyond approach for modeling the architecture and the SAAM approach for architectural evaluation.  

Requirements Analysis - Update
Describes the stakeholders, the textual requirements, use cases, (architectural) scenarios, prototype(s), state transition diagrams (if necessary).  

Technical Problem Analysis - Update
Describes the basic technical problems/concerns that need to be solved by the software architecture.  

Domain Analysis - Update
Describes the identified domains, the knowledge sources, the evaluation of knowledge sources, the derived concepts, the structure and description of concepts.

Top-Level Context Diagram
Describes the top-level context diagram of the system  

Module Views
- Uses View, Decomposition View, Generalization View, Layers View, Aspects View, and Data Model View.  
- Context diagrams for decomposition view, uses view and layers view

Component and Connector Views
Select at least three styles from the C&C styles

Allocation Views
- Deployment View, Install View, Work allocation view
- Context diagram for deployment view

Evaluation of software architecture
- Apply Scenario-based Architectural Analysis (SAAM) process to evaluate architecture
- Define a utility tree (ATAM) 

Conclusion - Updated/Extended
The conclusions should discuss the project, process and product. It should summarize how successful you were in achieving the original project objectives, what obstacles arose in the course of the project, the lessons learned, and how your work could be developed in future to enhance its utility.  

References