1. Introduction to the Requirements Document
BTS330
Introduction to the Requirements Document

2. Requirements Document
Introduction
Vision
For the software system you are developing
Scope
What are the boundaries of your product. Need to describe what it will and will NOT do.

3. Requirements Document
Sample Vision Statement
For Vitorio, a part owner in Slapshot, who is starting new division named Butterfly to produce specialty goalie sticks for charitable purposes, a software system is needed to manage the production of these goalie sticks. The Butterfly system is a software suite that will manage orders, control and track inventory, secure designs and template, calculate production costs, log orders and track production, maintain shipping and receiving logs, generate invoices. Unlike the current Slapshot system which is not setup to track independent charitable production costs, our product will maintain separate costs, provide accurate costing information and will interface with the existing Slapshot system to maintain an independent business model. This will give Vitorio the information he needs to successfully operate Butterfly.

4. Requirements Document
Introduction
Scope
What are the boundaries of your product. Need to describe what it will and will NOT do.

5. Requirements Document
Sample Scope Statement
The Butterfly system is comprehensive solution to all of Vitorio’s needs. It is comprised of four essential software components: B-Store (Inventory Management), B-Get (Orders Management), B-Paid (Accounting Management) and B-Boss (Administrative Tool). The software suite will allow the Butterfly staff to interface efficiently, yet track independently, the information for the following business areas: Orders, Production, Raw Materials, Shipping/Receiving, Accounting, Purchasing and Finished Goods. With this package Vitorio will be able to easily setup and maintain Butterfly as separate entity from Slapshot.

6. Requirements Document
Sample Scope Statement by Business Area (Orders Department)
For the Orders department who not only need a fast and efficient way to handle all incoming orders, but also need reliability and accuracy of information the B-Get module of the Butterfly System is an ordering solution that provides everything required to successfully maintain and operate all incoming orders. Unlike the existing implementation of ordering software that Slapshot is currently using, our product offers complete integration with every relevant department so all the necessary information is at their fingertips where they need it most.

7. Requirements Document
General Design Constraints
System Boundaries
Presented in a visual form
Show what other systems and users the system interacts with

8. Requirements Document
Sample System Boundaries
Since the Butterfly System is an integrated manufacturing business solution, this software system does not exist in isolation. Different modules interact with other systems and are part of a larger system or environment. This system specifically draws from the existing Slapshot intranet to access databases, product codes and places internal orders for materials. All the departments must have authorization to use the system via access card and be connected to the intranet in order to use the system in the way it was designed. The system needs to operate 24 hrs per day so that the information is always up to date. All the departments will keep their computers in safe locations that are protected from manufacturing debris and other hazards. This section describes the boundaries between the proposed system and its environment.

9. Requirements Document
Sample System Boundaries

10. Requirements Document
General Design Constraints
User Profile
Identify the categories of users (i.e. stakeholder types)

11. Requirements Document
Sample User Profile
Authority
Workplace Safety and Insurance Board are the authorities that define the employees’ rights, as it appeals to safety and it is by law that the rules they pass are kept
Ontario Employment standards which lay out rules for employee hours, breaks, holiday pay and other job rules
Slapshot partners and managers who will need to confirm any transfers or interactions with Butterfly as part of their costing and materials inventory
Government who are require the necessary taxation information and payments as well as records of financial transactions

12. Requirements Document
General Design Constraints
Business Rules
List business rules that impact the performance of a user case
Itemized in a business rules table

13. Requirements Document
Sample Business Rules
Minimum order of 25 goalie sticks.
2 weeks notice prior to shipping date required. During peak seasons 4 weeks notice is required
Packaging and Shipping to be done directly on production floor.
No cancellation upon order confirmation (written from goalie/agent)
Stick designs will be password protected. Only authorized Butterfly employees will have access.
The production floor will be limited to ‘Butterfly employee’ access only during special goalie orders.

14. Requirements Document
Nonfunctional Requirements
Security Requirements
Specify how access is restricted to the system
Are there audit requirements, etc?
Safety Requirements
Workplace Safety and Insurance Board (WSIB)
Workers Hazardous Materials Information System (WHMIS)
etc

15. Requirements Document
Nonfunctional Requirements
Legal

16. Requirements Document
Business Model
Stakeholder Diagram
System Use Cases
Use Case Diagram
Use Case Specifications

17. Stakeholders

18. Definition of a Project
A project is a sequence of unique, complex, and connected activities having one goal or purpose and that must be completed by a specific time, within budget and according to specification.
In IT, a project is usually undertaken to produce an information system that will solve a problem

19. Definition of a Project

20. Operating Environment
Most software systems don’t exist in isolation. They interact with other systems and are part of a larger system or environment.
You must describe the boundaries between the proposed system and its environment.
Any interfaces with existing systems such as database management systems must be described

21. Operating Environment

22. System Boundary vs Automation Boundary

23. Boundaries of the System
The boundaries of a system are defined by the scope section