Contents
Software requirements
A Software Requirements Specification (SRS) - a requirements specification for a software system - is a complete description of the behavior of a system to be developed. It includes a set of use cases that describe all the interactions the users will have with the software. Use cases are also known as functional requirements. In addition to use cases, the SRS also contains non-functional (or supplementary) requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints).
Physical layer requirements
System features
Interface requirements
User interfaces
Characteristics of each interface between the software and the users.
- sample screen images
- GUI standards or product family style guides that are to be followed
- screen layout constraints
- standard buttons and functions (e.g., help) that will appear on every screen
- keyboard shortcuts
- error message display standards
Hardware interfaces
Logical and physical characteristics of each interface between the software and the hardware components
- supported device types
- the nature of the data and control interactions between the software and the hardware
- communication protocols to be used
Software interfaces
Connections between Freedom Box and other specific software components (name and version)
- databases
- operating systems
- tools
- libraries
- integrated components
- integrated commercial components
- data items or messages coming into the system and going out
- services needed
- nature of communications
- detailed application programming interface protocols
- data that will be shared across software components
- data sharing mechanism
Communications interfaces
- web browser
- network server communications protocols
- electronic forms
- message formatting
- communication standards that will be used: FTP, HTTP, ...
- communication security or encryption issues
- data transfer rates
- synchronization mechanisms
Other Non functional requirements
Performance Requirements
Safety Requirements
- Possible loss, damage, or harm
Security Requirements
- security or privacy issues
- user identity authentication requirements
- Policies or regulations containing security issues that affect Freedom Box
- Security or privacy certifications that must be satisfied
Software Quality Attributes
- adaptability
- availability
- correctness
- flexibility
- interoperability
- maintainability
- portability
- reliability
- reusability
- robustness
- testability
- usability
Communications protocols
- use of distributed network
Error handling
- fault-tolerant
Other requirements
Database requirements
Internationalization requirements
Legal requirements
Reuse objectives for the project
Intro |
Information |
Support |
Contribute |
Reports |
Promote |
|
|
|
|||||
|
|
|
||||
HELP & DISCUSSIONS: Discussion Forum - Mailing List - #freedombox irc.debian.org | CONTACT Foundation | JOIN Project
Next call: Saturday, August 13 at 14:00 UTC
This page is copyright its contributors and is licensed under the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.