T3: Conceptual Architecture v2
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
The A/V Processing System (AVPS) captures sound and video data from the microphone and the camera into raw sound and images, which are recorded continuously. The AVPS also gets its 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 audio & video data. The video data is used to identify different vehicle types and forward this information to the report system which formulated various traffic analysis 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 sounds that meet the prior defined criteria of an accident. When an accident is detected, the IMS sends 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 occurring at this specific intersection.
The CMU is the user interface to the entire system. A user shall be able to monitor various incidents reported to the CMU from multiple intersections. The user shall be able to view/query various traffic 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.3.1 System Model
The following data model has been updated and improved to ensure that events are monitored in realtime so that there is no delay in processing.
The IMS interface is the central monitoring point for the system and therefore communicates with all internal systems. The incident analysis system (IAS) queries the simulator GUI for unusual events, traffic signal changes and vehicles that pass through the intersection. The IAS then signals the IMS interface that a new event has occurred and sends the details to the reports system.
The error diagnostic system operates in a similar manner to the incident analysis system by querying the simulator GUI for hardware errors. If an error is found it signals the IMS and sends the details to the reports system.
The reports system formats the data provided by the incident analysis system and the error diagnostic system with details of events and errors to be viewed by the IMS.
2.3.2 Vehicle Identifier
The vehicle identification system is used to distinguish between different makes and models of vehicles that pass through the intersection. It uses a visual recognition system that then matches a car to it's make and model through the vehicle database.
2.3.3 Incident Analysis
The incident analysis system determines the type of event recorded and sends the information on to the report system. The event information can then be accessed by the IMS interface.
2.3.4 Error Diagnostic
The error diagnostic component is responsible for signaling the IMS when a error is detected in the audio visual system. Details of the error are also sent to the reporting system.
2.3.5 Report System
The reporting system gathers events and errors and formats them for viewing via the IMS interface. The reports contain the event or error classification, the type of vehicle involved, date and time stamps.
2.4 Behavior derived from Use-case Maps
Car Accident
Description:
- The Microphone picks up a certain sound
- The A/V Processing System processes all the A/V data and sends it to the Incident Analysis System.
- The Incident Analysis System monitors the inbound A/V data from the A/V Proccessing System and Sends a message to the Central Monitoring Point. It Also send a report to the Report System.
- The Central Monitoring Point Displays the Message.
- The Reports System Stores the Report.
Car Goes By
Description:
- The Video is recorded when cars go by
- The A/V Processing System then senses the movement and sends the A/V data to the Incident Analysis System.
- The Incident Analysis System receives the A/V data and processes it determining that a car has passed through the intersection.
- As each car goes by a small report is creating with an accumulative number of all the vehicles gone by.
- The Central Monitoring Point then receives a message that a car has gone through the intersection.
- The Reports Systems stores the report of the car driving through the intersection.
Query
Description:
- The Central monitoring point sends a request to the Reports System.
- The necessary reports are sent back to the Central Monitoring Point.
Red Light Camera
Description:
- The Camera records Vehicles going through the intersection.
- The A/V Proccessing System processes the data and sends it to the Incident Analysis System.
- The Traffic lights send a signal to the Incident Analysis System that shows that it has changed to a red light.
- The Incident Analysis System then locates any data of vehicles passing through the intersection
- The Central Monitoring Point is Notified of the Red Light Violation.
A report is sent to the Reports System and is stored.
Faults
- A Fault has occurred in one component of the system
- The Error Diagnosing system finds that something is wrong with the system.
- The central Monitoring Point is then notified of the Fault that has occurred.
- A report of the Fault is then created and stored.
(This use case map has all the Faults in one use case map)
