Reference no: EM133730387
Systems Analysis and Design
Fire Management System
Objective of the system
The main objective is to develop an online management system for IFS that will control the hub of the fire management system. The local building FIPs are produced by other companies, but the hub needs to be able to communicate with them using their published addressable interface (IP address on the fibre FMS).
The manager needs all information at their fingertips to make decisions.
Safety is a critical aspect of this system, as failure could result in loss of life where a fire occurs.
The manager requires multiple types of reports, periodic each month, on-demand, and after-action reports (automatically generated after a major alarm state has been resolved).
Records must be kept secure, only accessed by authorised staff.
The system must be able to receive and report on equipment and sensor data as it comes in, that
is, it must be ‘live' 24/7, with reliability and uptime a priority.
The system should be online, so that, for example, IFS staff can issue commands from a mobile app outside a building in an emergency, instead of having to run to an accessible computer and login, although this should also be possible.
Tasks
The system definition above will be used for the two assignments for this course. For this assignment, you will partially design and propose an implementation strategy for the system. You should identify system components and realize system requirements. In this assignment you will design the system according to the requirements identified in part A, map business rules to your design and construct a model of the system in UML. Specifically, you will develop sequence diagrams, interface storyboards, test plans, risk mitigation plans, and map out a class diagram for the solution domain.There are no limits to how far the design and implementation might go. However, complexity, coverage and correctness of the elements will be taken into account in the assessment of the submitted work.
The main deliverable of this assignment is a report and Gantt Chart to be submitted via Canvas,
Note, your academic may also ask for a hard copy of the report and for your team to show your Gantt file in class.
For the report, you need to submit a Word or PDF document and a Gantt file in one compressed (zip) file
containing the following:
Report cover sheet containing the
Default is 5 Team members (first and last name and student numbers)
Lab Day
Lab Room,
Lab Time and
Lab academic (first name only)
Introduction to the report
What is in the report?
Who is the intended audience of this report?
What are the objectives of this report?
How does each element of this report contribute to achieving the report objectives?
Business Rules
Refine business rules which you have already identified in Assignment 1 Part A. You may add on/ update your business rules as you discover more detailed requirements (as you perform iterative modelling). Your final list of business rules cannot be smaller than the requirements for part A.
Explain how each business rule is captured (enforced) by your team design. This is an important part of testing your design. Remember some business rule may only be captured by human business processes. So is a business rule captured by an interface, by class data or a method etc?
System Design
The complete subsystem specification for the system.
You will need to identify the subsystems, and describe the services they each provide. (see Brugge and Dutoit Chap 6 Fig 6-29): Discussed in lecture 8 (see week 8 lab notes page 3: Fig 6-29)
Illustrate the relationships between each subsystem: Discussed in lecture 8 (see week 8 lab notes)
A class diagram with all classes to be implemented (including the Boundary classes,
Controller classes and Entity classes) and appropriate relationships between them.
All attributes for each class. Include access modifiers i.e. private, public and protected for each attribute of the classes that are required for each Use Case: Discussed in lecture 7
All operations/ methods, include access modifiers i.e. private, public and protected for each. You should also include input parameters and return types for each method.
Your class diagram should follow principles of good system and object design as taught in lectures. Include a description explaining your design and the decisions you made.
Use Case Mapping to Sequence Diagram
Each team member will revise their Use Case description from assignment Part A (unless otherwise assigned by your academic) e.g. cannot use the logon use case.
Each team member will create a subset of the class diagram (section 4) that shows only the part of the system required to implement their Use Case description: Discussed in lecture 7
Each team member will create a sequence diagram (for the Use Case) that shows the relevant Boundary, Controller and Entity classes from your class diagram in section 5b.
Give a short description for each diagram to briefly explain the interactions among the models to perform the use case.
User Interface
Each team member will develop a user interfaces (i.e. screen design) using your use case description, subset of the class diagram and sequence diagram (section 5) as the basis of your interface (The logon interface is not to be modeled).
Use the storyboarding technique (eg Powerpoint) to illustrate each screen required by your use case, including alternate flows, and exceptions.
Each interface (team style) must be consistent in appearance and visual style.
Consider each user of your interface, considering accessibility and ease of use.
Test Plan
You are required to propose a testing strategy for the system, as well as any future modifications to the system. Your strategy should include different levels of tests:
Unit tests, Integration tests, System tests, and User Acceptance tests.
For each level provide two example of white-box and two example of black-box testing (aside from User Acceptance tests, which will only have black-box tests).
Your test plan requires test cases, sample inputs, and expected outputs. Provide examples of possible defects to illustrate how your proposed testing strategy could identify a variety of faults.
Risk Assessment
Identify a list and ranking of major and minor risks for the project.
Rate the likelihood and impact of each risk to determine their severity.
Risks with a high severity should include a mitigation strategy, and an updated rating before/after the strategy is implemented.
To help with this you might like to consider questions such as:
What is a risk matrix?
What use cases involve risk?
Are there any ethical considerations that will need to be considered - If so, what are they?
Are there any special privacy or security conditions expected by the client?
The risks will include the project and your team (e.g. cost and schedule overruns).
Deployment
What is your team proposing for a deployment strategy?
How will you address issues in data migration from the old system to the new system?
How will you handle user training?
How does your chosen strategy address the potential for system faults and bugs?
Will you use a direct, pilot, parallel, or phased deployment (or a hybrid approach)?
Justify your choice in comparison to the alternatives.
What are some potential disadvantages to your choice and how will these be mitigated?
Have a look at the 14-2-Deployment.mp4 video link.
Give an example (with inline citations and references) of a real-world situation where a similar strategy was used to support your argument.
Team Management
Meeting notes for at least 5 meetings and MS teams activity report
Gantt Chart (MS Project)
Your team will continue to refine your existing chart and show who has done what and the percentage completed for each task
This part of your assessment will be utilised if there is any issue with team management of production and team submission. Makes sure you keep copies of your individual work
Self and Peer-Assessment process using TeamMates
Conclusion
What was completed
What was not completed and why
How did each section of the report achieve the report objectives?
What are your recommendations for the client?