Convincing Features
Assignment Type
Subject
Uploaded by Malaysia Assignment Help
Date
This section introduces the requirement specification document that specifies all system requirements that will govern the development and implementation of [system name]. It provides the purpose and scope of the system as well as the definition of terms specific to the system.
[Specify what your system is intended to do and how it will go about doing what it is intended to do.]
Example:
This Ambulance Dispatch System (ADS) is needed to help ensure that the ambulance dispatching company meets all federal mandates about the speed at which an ambulance is dispatched. In order to make this possible, the system greatly decreases the amount of paperwork that must be filed. This system should also help the company ensure that they are providing an adequate amount of ambulance for each of their service areas by enabling the management to track the status of each ambulance and a log of ambulance activity.
[Specify in more detail what your system shall do and shall not do.]
Example:
The ADS shall assist the operators and dispatchers in quickly and efficiently dispatching ambulance to 911-incident call. This system shall reduce the paperwork that is currently filed for each call, which shall in turn help the company meets the federal mandates. This reduction of paperwork will allow the company to keep cost low. (The federal mandates state that an ambulance must be dispatched within an average of 3 minutes of a 911-incident call. The ambulance must arrive at the scene of the incident within an average of 11 minutes of its dispatch). The ADS shall allow operators to input the 911 call information, assist operators in determining the uniqueness of calls and assist the dispatcher in locating a nearby ambulance, prioritize calls and allow the dispatcher to update the status of each ambulance. All 911 call information, ambulance dispatches, and ambulance status shall be logged and stored in a central computer database.
The ADS shall not replace the way in which dispatchers contact ambulances and ambulances contact dispatchers, through hand-held radios. The system shall not take into account congested roads and areas of high traffic. The dispatchers should be aware of traffic conditions when an ambulance is dispatched. An interface among ambulances and hospitals shall not be implemented in this system. Regarding hospitals, ambulance should continue the way in which they currently operate. The system shall not determine if a 911-incident call is a duplicate of a currently pending claim; however, the system shall provide an interface to assist the operator in making this decision. The system shall not decide what ambulance to dispatch; this remains the dispatcher’s decision.
[List all specific/domain terms used in this document.]
Example:
| ADS – | Ambulance Dispatch System |
| C#.NET – | A computer language designed for the Microsoft .NET framework used for creating Microsoft Windows applications |
| Dispatcher – | The person who decide what ambulance to dispatch. The dispatcher also contacts the ambulance drivers as well as updates the status of each ambulance. |
This section provides a high-level description of [system name], identifies the users involved and their roles, and specifies the general constraints, assumptions and dependencies (if any).
[Specify the functions of your system.]
Example:
The ADS ensures ambulances are dispatched quickly and efficiently in order to reduce the costs for the ambulance providers and increase their ability to save more lives. To facilitate these needs,……
[Specify users of your system and their roles.]
Example:
Three groups of users will use this system, i.e. system administrator, the management team, and operators and dispatchers. System administrators are concerned with data integrity and system stability. This group possesses good computer skill and is capable of supporting computer network. Their interaction with the system is very limited, and is only necessary for backing up and archiving data from the database or to provide basic computer support to the other users of the system.
The management team ……
The operators and dispatchers ……
[Specify the software and hardware limitation.]
Example:
Software limitation:
Hardware limitation:
[Specify any assumption and dependency.]
Example:
Assumption:
Dependencies:
This section contains the listing of all functional and non-functional requirements for [system name], the use case(s) model, analysis object model as well as dynamic model. An initial interface prototype is also included at the end of this section.
Both functional and non-functional requirements are as shown in Table 1 and 2 respectively. Each requirement is either a mandatory (M) or desirable (D) or an optional (O).
M – Requirement that the system must do
D – Requirement that the system preferably do
O – Requirement that the system may do
Example:
TABLE 1 Functional Requirement List
| No. | Requirement | Priority | |
| 1. | To record details of Agate’s clients and the advertising campaigns for those clients. | ||
| 1.1 | To record names, address and contact details for each client | M | |
| 1.2 | To record the details for each campaign … | M | |
| 1.3 | O | ||
| 1.4 | … | ||
| 2. | To provide …. | ||
| 2.1 | To allow … | … | |
| [see A1.4 on p. 94] | |||
TABLE 2 Non-functional Requirement List
| No. | Requirement | Priority | |
| 1. | …… | ||
| 1.1 | …… | M | |
| 1.2 | …… | M | |
| 2. | …… | ||
| 2.1 | …… | … | |
The above requirements are gathered using the following techniques:
[List the techniques you used to gather the requirement.]
[List the basic flow of how the system will operate.]
Example:
Table 3 shows the list of use case(s) associated to each requirement, and their ID.
Example:
TABLE 3 Use Case List
| No. | Requirement | Use Case(s) | Use Case ID | |
| 1 | To record names, address and contact details for each client | Add new client | AG_01_01 | |
| 2 | To record details for each campaign … | Add new campaign | … | |
| … | …… | … | … | |
| … | …… | … | … | |
| [see A2.2 on p. 160] | ||||
[Include the system’s main use case diagram]
[Followed by sub-system’s use cases]
Example:
[see Figure A2.1 on p. 162]
TABLE 4 Use Case Descriptions
| Use Case | Descriptions |
| Add new staff | … [For each use case, do not just describe what it does. Specify input to this use case, processing as well as output] …. |
| … | … |
| [see Use Case Description on p. 163 – description can be in one table for all use cases or separate table for different sub-systems] | |
[Insert sequence diagram for the system]
[Insert class diagram for the system]
Declaration
I hereby declare that this submission is my own work and to the best of my knowledge it contains no materials previously published or written by another.
| Student’s Signature | Date |
| Supervisor’s Approval | ||
| Project Supervisor’s Signature & Stamp | Date |
| Lecturer’s Approval |
| Approve without modification | |
| Approve with modification | |
| Reject |
Many UUM students struggle to complete the STZK3993 Academic Project 1 – Assignment 2: Project Design due to limited time, unclear instructions, or difficulty understanding system requirements and use case modelling. But you don’t need to stress—Malaysia Assignment Help provides expert-made, 100% human-written, plagiarism-free project assignment help tailored to UUM standards. Before ordering, you can check our STZK3993 sample to see the quality we deliver. Get custom-written system requirements, functional & non-functional requirements, use case diagrams, and models prepared exclusively for you. Order now and secure high marks with ease.
