T3 Intersection Monitoring System
From SoftwarePractice.org
[edit]
T3 Team Members
| Name | Student Number |
| Troy Bellrose | 10447062 |
| Simon Hedge | 10461022 |
| Claudie Cheng | 10012704 |
| Jason Tran | 10041008 |
| Tharsen Santhagunanathan | 01061237 |
| Dhananjay Sinh | 10397697 |
[edit]
Document Overview Milestone 2
This document describes the architecture of the Intersection Monitoring System (IMS). It has been divided into the following sections:
Outlines the overview of the system and gives a top-level view of the system and will lay the foundation for a more in-depth system architecture in the following sections. This section also includes:
- 1.1 System Narrative
- 1.2 Stakeholders
- 1.3 Contextual Factors of the System
- 1.4 Functional and Non-Functional Requirements
- 1.5 System Quality Attributes
Provides domain-level responsibilities for the system. This section was derived form the System Narrative above and includes.
- 2.1 Use of Sterotypes
- 2.2 Discussion of Components and their Responsibilites
- 2.3 Data Models
- 2.4 Behavior derived from Use-case Maps
The Execution Architecture will set out to define the system through "run-time" structures that makes up the system in focus. This section includes.
- 3.1 Concurrent Sub-systems View
- 3.2 Execution Architecture Design
- 3.3 Behaviour
- 3.4 Deployment View
- 3.5 Architecture Feasibility
The Implementation Architecture will set out to define the system through "built-time" structures that makes up the system in focus.
