Requirements Specification Template

Use this as a framework for your requirement specification

1 System Context & Scope

To Integrate the System with a firewall and cache system on one system to take to Belieze. Thsi unit will service an area with mutliple computers sharing a limited bandwidth speed. This part has to do with the packet shaping area. This part of the system has to take 1Mb/s and fairly divide it over many users.

1.1 Scope of the System

Bandwidth Packet Shaping on Priority. Needs Graphing to determin bandwidth flows.

1.2 Workflow Partitioning


1.3 Product Boundary

Must split 1Mb/s over a possible 20-25 users.

1.4 Use Case List

Belieze Schools, Students, Teachers.

2 Functional and Data Requirements

Define the functions of the system.

2.1 Functional Requirements.

Fairly Distribute a single bandwidth over mutliple connections.

2.2 Data Requirements.

1Mb/s Download and Upload Bandwidth. ( User Configurable )

3 Look, Feel and Use Requirements

Define the User Interface

3.1 User Interface Requirements

  1. Ease of Use

  2. Secure

  3. Understandable

  4. Readable

  5. Changeable

3.2 Style Of The Product Requirements


3.3 Ease Of Use Requirements

Must be able to have documentation or ease of use incorporated so that users can monitor and adjust the shaper as time goes on.

3.4 Ease Of Learning Requirements

Networking and Ubuntu Background preferred, but not required.

4 Performance Requirements

Give estimates of the system load, and the needed performace and reliability needs

4.1 Speed Requirements

Look at Previous Documentation

4.2 Safety Critical Requirements


4.3 Precision Requirements


4.4 Reliability and Availability Requirements

Look at Previous Documentation

4.5 Capacity and Scalability Requirements

Look at Previous Documentation

5 Operational Requirements

In what system context will the solution operate. What other systems will interact with this system.

5.1 Expected Technological Environment Requirements

  • Availabel Power

  • Contorlled Enviroment

  • Dust Control

  • Security

  • Dry Enviroment

5.2 Partner Applications & Interfaces Requirements

  • Network WAN COnnection

  • LAN Connection

  • Power

  • User Interfaces

5.3 Supportability Requirements

Need Parts for spares

5.4 Maintainability and Portability Requirements

NA, not needed to be moved.

6 Security Requirements

Specify the required security needs.

6.1 System Confidentiality Requirements

6.2 Data Integrity Requirements

6.3 Audit Requirements

7 Legal Requirements

8 Standards Requirements

9 Off-the-Shelf Solutions Requirements

What are the requirements of existing software that will be used or adpated for this system.

9.1 COTS System Solutions Requirements

9.2 Ready-Made Components Requirements

10 Constraints and Assumptions

10.1 Solution Constraints

10.2 External Factors

10.3 Assumptions

11 Future Requirements


-- JimSkon - 2011-10-04

Topic revision: r3 - 2011-11-13 - KevinAdams
This site is powered by the TWiki collaboration platformCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback