T3: Conceptual Architecture
From SoftwarePractice.org
Contents |
Conceptual Architecture
Provides domain-level responsibilities for the system. This section was derived form the System Narrative in section 1 and includes.
2.1 Use of Stereotypes
| Icon | Stereotypes |
 | User Presentation |
 | Real-time Response |
 | Persistent Storage |
2.2 Discussion of Components and their Responsibilities
2.2.1 Components
2.2.2 Component Map
Explanatory text :-
The A/V Processing System(AVPS) gets sound and video data from the microphone and the camera. This data is recorded continuously. The AVPS also gets location and time information from a GPS/Time system which is superimposed on the video data. It is assumed that the camera covers the entire intersection.
The Incident Monitoring System(IMS) constantly monitors the the audio & the video data. The video data is used to identify different vehicle types and forward this information to the report system which formulated various reports based on this data. The IMS also gets information from the traffic lights system regarding when different lights at the intersection turn red and uses this information and the streaming video data to identify cars that violate the red light. The IMS continuously analyses the sound data for sound/s that meet the prior defined criteria of an accident. If an accident is detected then the IMS send the sound and video data 20 seconds prior and following the detection of the accident to the reporting system and alerts the Central Monitoring unit(CMU) of an accident.
The CMU is the user interface to the entire system. A user shall be able to see the various incidents reported to the CMU from multiple intersections. The user shall be able to view(query) various reports via the reporting system.
The Error Diagnosing System(EDS) monitors the entire system for any outage/malfunction. In case of a malfunction the EDS sends the details to the reports database directly and alerts the CMU accordingly.
2.3 Data Models
2.4 Run-time and Life-cycle Events
2.5 Behavior derived from Use-case Maps
Car Accident
Description:
- The Microphone picks up a certain sound
- The A/V Processing System then finds that the sound is above a certain decibel level and sets a flag
- The data is stored in the A/V Data
- The Incident Analysis System monitors the A/V Data looking for the flag
- Once a flag is found it then goes to the reports system
- The reports system then stores the report
- Then the Central Monitoring Point is notified of an accident.
Car Goes By
Description:
- The Video is recorded when cars go by
- The A/V Processing System then senses the movement and finds the size of the vehicle
- The data is stored in the A/V Data
- The Incident Analysis System monitors the A/V Data looking at how many vehicles go by
- As each car goes by a small report is creating with an accumulative number of all the vehicles gone by
- The reports system then stores the report
- Then the Central Monitoring Point is notified of the current number of cars passing through the intersection.
Query
Description:
- The Central monitoring point looks at all the stored reports that have been created
- The necessary reports are sent back to the Central Monitoring Point.
Red Light Camera
Description:
- The Camera records Vehicles going through the intersection and is then stored
- The Traffic lights send a signal that shows that it has changed to a red light.
- The Incident Analysis System then locates any data of vehicles passing through the intersection
- A Report is then created showing the vehicle going through the intersection and the report is stored.
- The Central Monitoring point is then Notified that someone has gone through a red light.
Fault at Central
Description of all faults down the page.
Fault in the Camera
Description of all faults down the page.
Fault in the Microphone
Description of all faults down the page.
Fault in the A/V Processing System
Description of all faults down the page.
Fault in the A/V Processing System
Description of all faults down the page.
Fault in the Reports System
Description of all faults down the page.
Fault in the Reports Data System
Description of all faults down the page.
Fault in the Time Source
Description of all faults down the page.
Fault in the Traffic Lights
Description of all faults:
- A Fault has occurred in a component of the system
- The Error Diagnosing system finds that something is wrong with the system.
- A report of the Fault is then created and stored.
- The central Monitoring Point is then notified of the Fault that has occured
