SOFTWARE REQUIREMENT SPECIFICATION
1 Introduction
1.1 Purpose
1.2 Project Scope and Product Features
2. Overall Description
2.1 Product respective
2.2 User Classes and Characteristics.
2.2.1 Patron
2.2.2 Canteen staff
2.2.3 Menu Manager
2.2.4 Meal Deliverer
2.3 Operating Environment
2.4 User documentation
2.6 Assumptions and Dependencies
3 System Features
3.1 Order Meals
3.1.1. Description and Priority
3.1.2 Stimulus/Response Sequences
3.1.3 Functional requirements
4. External Interface Requirements
4.1 User Interfaces
4.2 Hardware Interfaces
4.3 Software Interfaces
4.4 Communications Interfaces
5. Other Nonfunctional Requirements
5.1 Performance Requirements
5.2 Safety Requirements
5.3 Security Requirements
5.4 Software Quality Attributes
Appendix A: Data Dictionary
CANTEEN ORDERING SYSTEM AT XYZ COMPANY
1. Introduction
1.1 Purpose
This SRS describes the software functional and nonfunctional requirements for the Canteen Ordering System.
1.2 Project Scope and Product Features
The Canteen Ordering System will permit the employees to order meals from the company canteen on-line to be delivered to specified locations.
2. Overall Description
2.1 Product Perspective
The Canteen Ordering System is a new system that replaces the current manual and telephone processes for ordering and picking up lunches in the XYZ Company’s canteen. The system is expected to provide better service by taking orders online.
2.2 User Classes and Characteristics
2.2.1 Patron
A Patron is an employee at the company, who wishes to order meals to be delivered from the company canteen. There are about 200 potential Patrons, of which an estimated 100 are expected to use the Canteen Ordering System an average of 4 times per week each. Patrons will sometimes order multiple meals for group events or guests. Orders will be placed using the corporate Intranet. All Patrons have Intranet access from their offices. Some Patrons will wish to set up meal subscriptions, either to have the same meal to be delivered every day or to have the day’s meal special delivered automatically. A Patron must be able to override a subscription for a specific day.
2.2.2 Canteen Staff
The XYZ canteen currently employs about 20 Canteen Staff, who will receive orders from the Canteen Ordering System, prepare meals, package them for delivery, print delivery instructions, and request delivery. Most of the Canteen Staff will need to be trained in the use of the computer, the Web browser, and the Canteen Ordering System.
2.2.3 Menu Manager
The Menu Manager is a canteen employee, perhaps the canteen manager, who is responsible for establishing and maintaining daily menus of the meal items available from the canteen and the times of day that each item is available. Some menu items may not be available for delivery. The Menu Manager will also define the canteen’s daily specials. The Menu Manager will need to edit the menus periodically to reflect planned meal items that are not available or price changes.
2.2.4 Meal Deliverer
As the Canteen Staff prepare orders for delivery, they will print delivery instructions and issue delivery requests to the Meal Deliverer, who is another canteen employee. The Meal Deliverer will pick up the meal and delivery instructions for each meal and deliver it to the Patron. The Meal Deliverers’ primary interactions with the system will be to reprint the delivery instructions on occasion and to confirm that a meal was (or was not) delivered.
2.3 Operating Environment
· The Canteen Ordering System shall operate with the following Web browser: Microsoft Internet Explorer versions 5.0 and 6.0
· The Canteen Ordering System shall operate on a server running Window NT Server.
· The Canteen Ordering System shall permit user access from the corporate Intranet.
2.4 User Documentation
The first time a new user accesses the system and on user demand thereafter, the system shall provide an online tutorial to allow users to practice ordering meals using a static tutorial menu. The system shall not store meals ordered using this template in the database or place orders for such meals with the canteen.
2.5 Assumptions and Dependencies
· The canteen is open for breakfast, lunch, and dinner every company business day in which employeesare expected to be on site.
· The operation of the Canteen Order System depends on changes being made in the Canteen Inventor System to update the availability of meal items as Canteen Order System orders are accepted.
3. System Features
3.1 Order Meals
3.1.1 Description and Priority
A canteen Patron whose identity has been verified may order meals either to be delivered to a specified company location or to be picked up in the canteen. A Patron may cancel or change a meal order if it has not yet been prepared.
3.1.2 Stimulus/Response Sequences
Stimulus: Patron requests to place an order for one or more meals.
Response: System queries Patron for details of meal(s), payment, and delivery instructions.
Stimulus: Patron requests to change a meal order.
Response: If status is “Accepted,” system allows user to edit a previous meal order.
Stimulus: Patron requests to cancel a meal order.
Response: If status is “Accepted,”system cancels a meal order.
3.1.3 Functional Requirements
| Order.Place | The system shall let a Patron who is logged into the Canteen Ordering System place an order for one or more meals. |
| Order.Place.Register | The system shall confirm that the Patron is registered for payroll deduction to place an order. |
| Order.Place.Register.No | If the Patron is not registered for payroll deduction, the system shall give the Patron options to register now and continue placing an order, to place an order for pickup in the canteen (not for delivery), or to exit from the system. |
| Order.Place.Date | The system shall prompt the Patron for the meal date |
| Order.Place.Date.Cutoff | If the meal date is the current date and the current time is after the order cutoff time, the system shall inform the patron that it’s too late to place an order for today. The Patron may either change the meal date or cancel the order |
| Order.Deliver.Select | The Patron shall specify whether the order is to be picked up or delivered |
| Order.Deliver.Location | If the order is to be delivered and there are still available delivery times for the meal date, the Patron shall provide a valid delivery location |
| Order.Deliver.Notimes | The system shall notify the Patron if there are no available delivery times for the meal date. The Patron shall either cancel the order or indicate that the Patron will pick up the order in the canteen |
| Order.Deliver.Times | The system shall display the remaining available delivery times for the meal date. The system shall allow the Patron to request one of the delivery times shown, to change the order to be picked up in the canteen, or to cancel the order. |
| Order.Menu.Date | The system shall display a menu for the specified date |
| Order.Menu.Available | The menu for the current date shall display only those meal items for which at least one unit is available in the canteen’s inventory. |
| Order.Units.Meal | The system shall allow the Patron to indicate the number of units of each menu item that he wishes to order |
| Order.Units.Multiple | The system shall permit the user to order multiple identical meals, up to the fewest available units of any menu item in the order. |
| Order.Units.TooMany | If the Patron orders more units of a menu item than are presently in the canteen’s inventory, the system shall inform the Patron of the maximum number of units of that meal item that he can order. |
| Order.Units.Change | If the available inventory cannot fulfill the number of units ordered, the Patron may change the number of units ordered, change the number of identical meals being ordered, or cancel the meal order |
| Order.Confirm.Display | When the Patron indicates that he does not wish to order any more meal items, the system shall display the meal items ordered, the individual meal item prices, and the payment amount, calculated |
| Order.Confirm.Prompt | The system shall prompt the Patron to confirm the meal order |
| Order.Confirm.Not | If the Patron does not confirm the meal order, the Patron may either edit or cancel the order |
| Order.Confirm.More | The system shall let the Patron order additional meals for the same or for different date. BR-3 and BR-4 pertain to multiple meals in a single order |
| Order.Pay.Method | When the Patron indicates that he is done placing orders, the system shall ask the user to select a payment method |
| Order.Pay.Pickup | If the meal is to be picked up in the canteen, the system shall let the Patron choose to pay by payroll deduction or by paying cash at the time of pickup. |
| Order.Pay.Details | The system shall display the meal items ordered, payment amount, payment method, and delivery instructions |
| Order.Pay.Confirm | The Patron shall either confirm the order, request to edit the order, or request to cancel the order |
| Order.Pay.Confirm.Deduct | If the Patron confirmed the order and selected payment by payroll deduction, the system shall issue a payment request to the Payroll System |
| Order.Pay.Confirm.NG | If the payment request is rejected, the system shall display a message with the reason for the rejection. The Patron shall either cancel the order, or change the payment method to cash and request to pick up the order at the canteen. |
| Order.Pay.Confirm.OK | If the payment request is accepted, the system shall display a message confirming acceptance of the order with the payroll deduction transaction number |
| Order.Done | When the Patron has confirmed the order, the system shall do the following as a single transaction |
| Order.Done.Store | Assign the next available meal order number to the meal and store the meal order with an initial status of “Accepted.” |
| Order.Done.Inventory | Send a message to the Canteen Inventory System with the number of units of each meal item in the order |
| Order.Done.Menu | Update the menu for the current order’s order date to reflect any items that are now out of stock in the canteen inventory |
| Order.Done.Times | Update the remaining available delivery times for the date of this order |
| Order.Done.Patron | Send an e-mail message to the Patron with the meal order and meal payment information |
| Order.Done.Canteen | Send an e-mail message to the Canteen Staff with the meal order information |
| Order.Previous.Period | The system shall permit the Patron to view any meals he has ordered within the previous six months. |
| Order.Previous.Reorder | The Patron may reorder any meal he had ordered within the previous six months, provided that all meal items in that order are available on the menu for the meal date |
4. External Interface Requirements
4.1 User Interfaces
- The system shall provide a help link from each displayed HTML page to explain how to use that page.
- The Web pages shall permit complete navigation and meal item selection using the keyboard alone, in addition to using mouse and keyboard combinations.
4.2 Hardware Interfaces
No hardware interfaces have been identified.
4.3 Software Interfaces
Canteen Inventory System
- The Canteen Order System shall transmit the quantities of meal items ordered to the Canteen Inventory System through a programmatic interface.
- The Canteen Order System shall poll the Canteen Inventory System to determine whether a requested meal item is available.
- When the Canteen Inventory System notifies the Canteen Order System that a specific meal item is no longer available, the Canteen Order System shall remove that meal item from the menu for the current date.
Payroll System
The Canteen Order System shall communicate with the Payroll System through a programmatic interface for the following operations:
- To allow a Patron to register for payroll deduction.
- To allow a Patron to unregister for payroll deduction.
- To check whether a patron is registered for payroll deduction.
- To submit a payment request for a purchased meal.
- To reverse all or part of a previous charge because a patron rejected a meal or wasn’t satisfied with it, or because the meal was not delivered per the confirmed delivery instructions.
4.4 Communications Interfaces
· The Canteen Ordering System shall send an e-mail message to the Patron to confirm acceptance of an order, price, and delivery instructions.
· The Canteen Ordering System shall send an e-mail message to the Patron to report any problems with the meal order or delivery after the order is accepted.
5. Other Nonfunctional Requirements
5.1 Performance Requirements
· The system shall accommodate 400 users during the peak usage time, with an estimated average session duration of 10 minutes.
· All Web pages generated by the system shall be fully downloadable in no more than 10 seconds over a 40KBps modem connection.
· Responses to queries shall take no longer than 10 seconds to load onto the screen after the user submits the query.
The system shall display confirmation messages to users within 4 seconds after the user submits information to the system.
5.2 Safety Requirements
No safety requirements have been identified.
5.3 Security Requirements
· Users shall be required to log in to the Canteen Ordering System for all operations except viewing a menu.
· Patrons shall log in according to the restricted computer system access policy.
· The system shall permit only canteen staff members who are on the list of authorized Menu Managers to create or edit menus.
· The system shall permit Patrons to view only their own previously placed orders, not orders placed by other Patrons.
5.4 Software Quality Attributes
Availability: The Canteen Ordering System shall be available to users on the corporate Intranet during working hours.
Robustness: If the connection between the user and the system is broken prior to an order being either confirmed or canceled, the Canteen Ordering System shall enable the user to recover an incomplete order.
Appendix A: Data Dictionary
| delivery instruction | = patron name |
| | + patron phone number |
| | + meal date |
| | + delivery location |
| | + delivery time window |
| delivery location | =* building and room to which an ordered meal is to be delivered * |
| delivery time | =* 15-minute range during which an ordered meal is to be delivered; must begin and end on quarter-hour intervals * |
| employee ID | =* company ID number of the employee who placed a meal order; 6- character numeric string * |
| meal item description | =* text description of a meal item on a menu; maximum 100 characters* |
| meal item price | =* pre-tax cost of a single unit of a menu meal item, in dollars and cents* |
| meal date | =* the date the meal is to be delivered or picked up* |
| meal order | = meal order number |
| | + order date |
| | + meal date |
| | +1:m{ordered meal item} |
| | + delivery instruction |
| | + meal order status |
| meal order number | =* a unique, sequential integer that the system assigns to each accepted meal order* |
| meal order status | =[ incomplete | accepted | prepared | pending delivery | delivered | canceled ] |
| meal payment | = payment amount |
| | + payment method |
| | +(payroll deduction transaction number) |
| menu date | * the date the menu of meal items is available* |
| menu meal item | = meal item description |
| | + meal item price |
| order cutoff time | =* the time of day before which all orders for that date must be placed * |
| order date | =* the date on which a patron placed a meal order* |
| ordered meal item | = menu meal item |
| | + quantity ordered |
| patron | =patron name |
| | + employee ID |
| | + patron phone number |
| | + patron location |
| | + patron mail |
| patron mail | =* e-mail address of the employee who placed a meal order* |
| patron location | =* building and room numbers of the employee who placed a meal order * |
| patron name | =* name of the employee who placed a meal order* |
| patron phone number | =* telephone number of the employee who placed a meal order* |
| payment amount | * total price of an order in rupees and cents* |
| payment method | =[ payroll deduction | cash ] |
| payroll deduction transaction number | * 8-digit sequential integer number that the Payroll System assigns to each payroll deduction transaction that it accepts * |
| quantity ordered | =* the number of units of each meal item that the Patron is ordering * |
SYSTEM REQUIREMENTS SPECIFICATION
Table of Contents
Section1.
Introduction
1.1 Purpose
1.2 Business Context
1.3 Scope
1.4 User Characteristics
Section 2.
General System Description
2.1 System Context
2.2 System Modes and States
2.3Major System Conditions
2.4 Major System Constraints
2.5 Assumptions
2.6 Dependencies
2.7 Operational Scenarios
Section 3.
System Capabilities, Conditions, and Constraints
3.1 Business Requirements
3.2 Functional Requirements
3.3 Physical Requirements
3.4 Logical Data Requirements
3.5 User Requirements
3.6 Information Management Requirements
3.7 Systems Requirements
3.8 Policy and Regulation Requirements
Introduction
System requirements describe what the Canteen system is expected to do; the system’s expected environment, the system’s usage profile, its performance parameters, and its expected quality and effectiveness. The SyRS is a structured collection of information that embodies the requirements of the system. The Canteen SyRS completely describes all inputs, outputs, and required relationships between inputs and outputs.
Documenting system requirements can reduce project risk by reducing uncertainty in implementation of the system. Documentation of detailed and accurate system requirements contributes to the success of IT systems by establishing and communicating expectations for all aspects of the system’s features and performance. In addition, the documented system requirements provide the basis for ensuring that requirements are addressed during system design and testing.
Section 1. Introduction
The canteen ordering system is expected to take orders correctly and allowing employees to modify their commands. If a meal order has been placed, it must have facilities to be updated or cancelled.
1.1 Purpose
The purpose the SyRS is to facilitate communication between both customers and staff of the Canteen Ordering System.
1.2 Business Context
The Canteen Ordering System must be flexible, accountable; it should have a smooth flow between front-end clients and the backend producers that is the staff of the Canteen.
It should be able to deal with the stocks of meals present in the database, show a report of profits or even most preferred meals of the employees.
The organizational objectives of the business unit should be met; the system should be highly interactive.
1.3 Scope
The identity of the system
The Canteen Ordering System allows ordering of meals from the company canteen for being delivered to specified places decided by the employee themselves.
A brief description of the system’s functionality
The Canteen Ordering System accepts orders from the employees, stored it in the database and at the back end the canteen staff can view the orders placed. They processed the orders and delivered the meal at the specific place been told.
An explanation of what the system will and will not do
The system can allow patrons to search for menus or even special menus of the day. They can view its price, the total price of the orders. The orders can also be modified or even cancelled.
The Canteen Ordering System will accept any command unless or until a user is identified and authenticated as a potential user of the system.
A description of the application of the system
This system allows patrons to save time as they do not have to place commands by being personally present in the canteen.
A description of the relevant benefits, objectives, and goals of the system
In the previous Canteen Ordering System manual and telephone processes were used for ordering and picking up lunches in the XYZ Company’s canteen. This system allows time saving by taking orders online.
1.4 User Characteristics
Patron
There are about 200 employees, using the Canteen Ordering System an average of 4 times per week each. Patrons will sometimes order multiple meals for group events or guests. The location of the patrons is within the organization itself, using intranet devices such as their personal computer or laptop connected to the intranet via a router or switch. There may be presence of wireless LAN or Wired LAN, or even numeral types of protocols been used.
Canteen Staff
The XYZ canteen currently employs about 20 Canteen Staff, who will receive orders from the Canteen Ordering System, prepare meals, and package them for delivery, print delivery instructions, and request delivery. Most of the Canteen Staff will need to be trained in the use of the computer, the Web browser, and the Canteen Ordering System.
These users will interact with the system mainly from the canteen itself, their level of education may not be high, thus system must be very interactive, user friendly and allows helps at every phase if there is any problem faced by the staffs. There may be also Accountants in the finance department that needs daily reports of the transactions taking place, money/ product in and out
Menu Manager
The Menu Manager is a canteen employee, responsible for establishing and maintaining daily menus of the meal items available from the canteen and the times of day that each item is available. Some menu items may not be available for delivery. The Menu Manager will also define the canteen’s daily specials. The Menu Manager will need to edit the menus periodically to reflect planned meal items that are not available or price changes.
Meal Deliverer
The meal deliverer may not directly interact with the system, he can be given a hardcopy of the orders, name and address to be delivered
Moreover, many people interact with the system during the operation and maintenance phases of the life cycle of the system. Some are users, operators, and maintenance and systems personnel. Certain characteristics of these people, such as educational level, experience, and technical expertise may impose important constraints on the system's operating environment. There are aspects as if the user is a novice or a person who do not know anything about informatics. All these must be considered to make the system robust and stable.
Section 2. General System Description
2.1 System Context
2.2 System Modes and States
The system’s mode of operation is online system and the environmental condition is the interface between users and system. Any change in the environment will change the database value.
Configuration of the system must be able to detect different versions of Browser used. It should be efficient that is able to display under any version of browser.
Operation of the system under different Operating System must not disturb its function; it should be able to work under any Operating system type.
2.3 Major System Conditions
One major condition to be implemented is that the Canteen system must work under any browser or operating system been used.
2.4 Major System Constraints
Major system constraints limit the scope and functionality of the system including, but not limited to, regulatory policies, infrastructure limitations, resources, and licensing.
2.5 Assumptions
The assumptions that can affect the requirements specified in the SyRS. Assumptions are factors can be end-user characteristics, known technology infrastructure, resource availability, and funding availability.
2.6 Dependencies
Dependencies that can affect the requirements specified in the SyRS are outside of project scope and control and must remain true for the project to succeed. It may be the internet connection or even if ever there is physical damage to the cable, connection may be interrupted. Virus also may cause interruption in communication.
2.7 Operational Scenarios
In the following sub sections, specify all the system requirements to a level of detail sufficient to enable developers to specify and build the system. Every stated requirement should be understandable by users, developers, operators, and external systems staff.
Specify at a minimum the transformation of inputs of the system into outputs of the system product and all functions performed by the system in response to an input or in support of an output. This description may consist of a model of the requirements. For example, the model may contain data flow diagrams, entity relationship diagrams, Product Network Diagram, and a data dictionary.
Requirements should be:
- Correct, unambiguous, complete, consistent, ranked for importance and/or stability, verifiable, modifiable, and traceable
- Cross-referenced to earlier documents that relate
- Uniquely identifiable
- Organized for maximum readability
3.1 Business Requirements
| Order.Place | The system shall let a Patron who is logged into the Canteen Ordering System place an order for one or more meals. |
| Order.Place.Register | The system shall confirm that the Patron is registered for payroll deduction to place an order. |
| Order.Place.Register.No | If the Patron is not registered for payroll deduction, the system shall give the Patron options to register now and continue placing an order, to place an order for pickup in the canteen (not for delivery), or to exit from the system. |
| Order.Place.Date | The system shall prompt the Patron for the meal date |
| Order.Place.Date.Cutoff | If the meal date is the current date and the current time is after the order cutoff time, the system shall inform the patron that it’s too late to place an order for today. The Patron may either change the meal date or cancel the order |
| Order.Deliver.Select | The Patron shall specify whether the order is to be picked up or delivered |
| Order.Deliver.Location | If the order is to be delivered and there are still available delivery times for the meal date, the Patron shall provide a valid delivery location |
| Order.Deliver.Notimes | The system shall notify the Patron if there are no available delivery times for the meal date. The Patron shall either cancel the order or indicate that the Patron will pick up the order in the canteen |
| Order.Deliver.Times | The system shall display the remaining available delivery times for the meal date. The system shall allow the Patron to request one of the delivery times shown, to change the order to be picked up in the canteen, or to cancel the order. |
| Order.Menu.Date | The system shall display a menu for the specified date |
| Order.Menu.Available | The menu for the current date shall display only those meal items for which at least one unit is available in the canteen’s inventory. |
| Order.Units.Meal | The system shall allow the Patron to indicate the number of units of each menu item that he wishes to order |
| Order.Units.Multiple | The system shall permit the user to order multiple identical meals, up to the fewest available units of any menu item in the order. |
| Order.Units.TooMany | If the Patron orders more units of a menu item than are presently in the canteen’s inventory, the system shall inform the Patron of the maximum number of units of that meal item that he can order. |
| Order.Units.Change | If the available inventory cannot fulfill the number of units ordered, the Patron may change the number of units ordered, change the number of identical meals being ordered, or cancel the meal order |
| Order.Confirm.Display | When the Patron indicates that he does not wish to order any more meal items, the system shall display the meal items ordered, the individual meal item prices, and the payment amount, calculated |
| Order.Confirm.Prompt | The system shall prompt the Patron to confirm the meal order |
| Order.Confirm.Not | If the Patron does not confirm the meal order, the Patron may either edit or cancel the order |
| Order.Confirm.More | The system shall let the Patron order additional meals for the same or for different date. BR-3 and BR-4 pertain to multiple meals in a single order |
| Order.Pay.Method | When the Patron indicates that he is done placing orders, the system shall ask the user to select a payment method |
| Order.Pay.Pickup | If the meal is to be picked up in the canteen, the system shall let the Patron choose to pay by payroll deduction or by paying cash at the time of pickup. |
| Order.Pay.Details | The system shall display the meal items ordered, payment amount, payment method, and delivery instructions |
| Order.Pay.Confirm | The Patron shall either confirm the order, request to edit the order, or request to cancel the order |
| Order.Pay.Confirm.Deduct | If the Patron confirmed the order and selected payment by payroll deduction, the system shall issue a payment request to the Payroll System |
| Order.Pay.Confirm.NG | If the payment request is rejected, the system shall display a message with the reason for the rejection. The Patron shall either cancel the order, or change the payment method to cash and request to pick up the order at the canteen. |
| Order.Pay.Confirm.OK | If the payment request is accepted, the system shall display a message confirming acceptance of the order with the payroll deduction transaction number |
| Order.Done | When the Patron has confirmed the order, the system shall do the following as a single transaction |
| Order.Done.Store | Assign the next available meal order number to the meal and store the meal order with an initial status of “Accepted.” |
| Order.Done.Inventory | Send a message to the Canteen Inventory System with the number of units of each meal item in the order |
| Order.Done.Menu | Update the menu for the current order’s order date to reflect any items that are now out of stock in the canteen inventory |
| Order.Done.Times | Update the remaining available delivery times for the date of this order |
| Order.Done.Patron | Send an e-mail message to the Patron with the meal order and meal payment information |
| Order.Done.Canteen | Send an e-mail message to the Canteen Staff with the meal order information |
| Order.Previous.Period | The system shall permit the Patron to view any meals he has ordered within the previous six months. |
| Order.Previous.Reorder | The Patron may reorder any meal he had ordered within the previous six months, provided that all meal items in that order are available on the menu for the meal date |
3.3 Physical Requirements
3.3.1 Construction
The weight limits of the system, dimensional and volume limitations, operator station layout, and access for maintenance should be specified.
3.3.2 Durability
Specify the durability characteristics of the system.
3.3.3 Adaptability
Specify the growth, expansion, capability, and contraction characteristics. For example, if the system will require future network bandwidth, the hardware rack should be specified with extra slots to accommodate new network cards, as demand increases.
3.3.4 Environmental Conditions
Specify the environmental conditions to be encountered by the system. The following subjects should be considered for coverage: natural environment (e.g., wind, rain, and temperature), induced environment (e.g., motion, shock, noise), and electromagnetic signal environment.
3.4 Logical Data Requirements
Describe the logical data requirements for the system. Logical data requirements may include:
• Types of information used by various functions
• Frequency of use
• Accessing capabilities
• Data entities and their relationships
• Integrity constraints
• Data retention requirements
3.5 User Requirements
User requirements capture the intended behavior of the human interface for the application. If the user operates through a display terminal, specify the required screen content, content of any reports or menus, and relative timing of inputs and outputs.
The screens also must be in user friendly with a good graphical interface and colours used should be well chosen.
3.6 Information Management Requirements
Describe the requirements for managing the creation, capture, organization, maintenance, use, protection, and disposition of information in accordance with applicable laws, regulations, policies, and standards.
3.7 Systems Requirements
3.7.1 Performance Requirements
• Movements of the data must be fast, and noise levels must be controlled and decreased to allow better performance of system.
• The number of simultaneous users to be supported will be around 300 users accessing the system concurrently.
• The numbers of transactions and tasks and the amount of data to be processed within certain time periods for both normal and peak workload conditions
• Acceptable performance under atypical stress like disconnection of internet facilities or viruses, but a backup should be frequently done.
95% of the transactions shall be processed in less than one second to allow database integrity.
3.7.2 Quality Requirements
• Correctness – system allows correct data flow through users to the database via the interface
• Efficiency – amount of computing resources and code required to perform function
• Flexibility – effort needed to modify operational program
• Integrity/security – extent to which access to software or data by unauthorized people can be controlled. Security requirements relate to both the facility that houses the system and operational security requirements. Access limitations to the system, such as existence of log-on procedures and passwords, and of data protection and recovery methods. This could include the factors that would protect the system from accidental or malicious access, use, modification, destruction, or disclosure.
• Interoperability – effort needed to couple one system to another
• Maintainability –locating and correct an error during operation, maximum downtime, reaction time, turnaround time, mean and maximum times to repair, mean time between maintenance actions, rate
• Portability –transferring from one hardware or software environment to another
3.8 Policy and Regulation Requirements
Policy and regulation requirements include:
• Multilingual support
• Labor policies
• Protection of personnel information
• Reports to a regulatory agency
• Health and safety criteria, including those basic to the design of the system, with respect to equipment characteristics, methods of operation, and environmental influences
3.9 System Life Cycle Sustainment Requirements
This design attribute established early in the system’s development to provide a basis for planning each incremental development effort. Evolutionary development strategies should address approaches for managing the introduction of new technologies, evolving requirements, or enhancing product capabilities.
The life cycle of the system includes:
• Development
• Testing of the system
• Operation
• Support by an IT techncian
• Training of the staffs
