Analysis of Real-Time System
Learning Outcomes
The following course learning outcomes are assessed by completing this assessment:
Analyse and apply complex decision making to determine the appropriate methodology to apply to different development situations
Develop a good understanding of processes to ensure quality in the engineering of large software systems
Develop a good understanding of the principles of commonly used Software Engineering Methodologies
Develop a good understanding of the artefacts that can be created to control and support quality assurance, risk management and communication in large software development projects
Critically analyse and use complex decision making to research and determine the appropriate Software Engineering tools and methodologies to utilize in a given situation
Apply professional communication skills to support and manage the engineering of a large software system
Review, critically analyse and develop artefacts to define processes for quality assurance, risk management and communication in large software development projects
Analysis of a large system development problem to decide upon the best methodological approach
Requirements:
Demonstrate an understanding of particular concepts covered in lectures, tutorials, laboratories and reading to provide the specification requested. This may require further reading and research beyond the material discussed in class.
Assessable Tasks/Requirements
Your task is to complete a Real-Time Structured Analysis Specification for the AMAC. You analysis should include the following components:
1. An External Entity-Relationship Diagram (ERD) indicating relationships of the AMAC and the other external entities in the system. You do not need to include attributes of the entities on the ERD, just the relationships and their cardinality and modality.
2. Data and Control Flow Diagrams (DFD/CFDs) – to sufficient detail that only a single task is carried out by each process at the lowest level. You should show the control events that occur on the same diagrams. Use the real-time extensions for control flows etc shown in the lecture notes on slide 17 from week 3. You need to determine when and where events will occur. For example, whenever a piece of data becomes available it may need a control event to let the system know that it is available. These events must be clearly shown in these DFD/CFD diagrams and then handled in the CSPEC.
3. Process specifications (PSPECs) – a pseudo-code or similar design language specification is required for each process at the lowest level. A narrative description alone will not be considered sufficient.
4. Control Specifications (CSPECs) – use combinational or sequential FSMs as required, presented in an appropriate format. The idea is that the CSPEC will completely describe how each and every event or control flow is handled in the system. You need to provide both “Process Activation Table” and “State Machine Diagram”.
5. A Data Dictionary is required to adequately describe each name or special term used in the analysis. This includes process names, data flow names, control flow names etc.
You should include sufficient detail to allow the system to handle all the monitoring and control aspects specified in the Detailed Description section of this document (and any further aspects you consider essential).
