ProjectsCenter Support
|
# Posted: 3 Sep 2006 17:33
Reply
At SWB Consulting, over the years, we have figured out the best structure for software requirements specifications for small and mid-size custom software development projects. Below please find a sample outline of what one of our SRS documents would look like.
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms, Abbreviations and Standards
1.4 References
1.5 Overview
2. The Overall Description
2.1 Product Perspective
2.1.1 System Overview
2.1.2 Memory Constraints
2.1.3 Operations
2.1.4 Site Adaptation Requirements
2.2 User Characteristics
2.2.1 Admin
2.2.2 Public User
2.2.3 Member
2.2.4 Agent
2.2.5 Broker
2.2.6 System
2.3 Constraints
2.4 Assumptions and Dependencies
2.5 Apportioning of Requirements.
3. Specific Requirements
3.1 External Interfaces
3.1.1 System Interfaces
3.1.2 Interfaces
3.1.3 Hardware Interfaces
3.1.4 Software Interfaces
3.1.5 Communications Interfaces
3.2 Functions
3.2.1 Overall
3.2.1.1 Website Design
3.2.2 Admin Functionality
3.2.2.1 Manage Users
3.2.3 Public User Functionality
3.2.3.1 Search for listings (limited)
3.2.3.2 View Results
3.2.3.3 Sign Up
3.2.3.4 Log In
3.2.4 Member Functionality
3.2.4.1 Search for listings (extended)
3.2.4.2 Results List (extended)
3.2.4.3 View Details (extended)
3.2.4.4 Save Listings
3.2.4.5 Manage Saved Items
3.2.4.6 View Reports
3.2.4.7 Send Graph
3.2.4.8 Manage Alerts
3.2.5 Agent Functionality
3.2.5.1 Manage Users
3.2.5.2 Comment on Listing
3.2.5.3 Manage Alerts
3.2.6 Broker Functionality
3.2.6.1 Manage Assignments
3.2.7 System Functionality
3.2.7.1 MLS Scheduler
3.2.7.2 MLS Listener
3.3 Performance Requirements
3.4 Logical Database Requirements
3.5 Design Constraints
3.5.1 Standards Compliance
3.6 Software System Attributes
3.6.1 Reliability
3.6.2 Availability
3.6.3 Security
3.6.4 Maintainability
3.6.5 Portability
4. Change Management Process
5. Document Approvals
6. Supporting Information
|
