CAR SHOWROOM MANAGEMENT SYSTEM
Format of the System Requirement Specification (SRS)
1. Introduction
1.1
1.2
1.3
1.4
1.5
1.6
1.7
Purpose of SRS
Methodology used
Terms of Reference
Structure of this document
Definitions and acronyms
Key persons involved
List of persons with designation and Offices, from the clients end, involved in the development of Software
Important Dates
Dates of Delivery, phase deliveries, tests, etc
2. Overview of Requirements (for each system)
2.1
Technical Rationale
2.1.1 Problems
• Description of the manual process
2.1.2 Current Practice
• Flow diagram of the Manual System
• Description of work to be undertaken at each stage • Business Logic involved
2.1.3 Proposed Solution Overview
• Description of the proposed solution
• Detailed explanation of the whole process and the module 2.1.3.1 For Each module
• Degree of atomization achieved by this module • Explain if BPR required
• Dependency with other modules
• Designation of person using this module
• Proposed process flow diagram
• Input and Output Specification
2.2 Business Rationale
2.3
2.4
2.5
3.
Integration of the existing Applications/websites/modules with new suggested system. List all the proposed modules covering following points
• Priority of development
• Dependency of the module on other module
• Specification for Alert & Escalation mechanism
Proposed
Hardware,
Software
and
Network
Specification
• Network Diagram of the proposed system including suggested nodes, dependent clients, servers, printers etc. Also specify where GSWAN connectivity is applicable and where dial up or Lease Line required.
Architecture
3.1
3.2
3.3
3.4
3.5
System Architecture
User Interface layer
Application layer
Utility layer
Core layer
4. General Requirements
4.1
4.2
4.3
4.4
4.5
Audit Trails
• Application driven & managed Audit trails are a must. • Platform driven/ managed audit trails may be used to complement the application
1. Introduction
1.1
1.2
1.3
1.4
1.5
1.6
1.7
Purpose of SRS
Methodology used
Terms of Reference
Structure of this document
Definitions and acronyms
Key persons involved
List of persons with designation and Offices, from the clients end, involved in the development of Software
Important Dates
Dates of Delivery, phase deliveries, tests, etc
2. Overview of Requirements (for each system)
2.1
Technical Rationale
2.1.1 Problems
• Description of the manual process
2.1.2 Current Practice
• Flow diagram of the Manual System
• Description of work to be undertaken at each stage • Business Logic involved
2.1.3 Proposed Solution Overview
• Description of the proposed solution
• Detailed explanation of the whole process and the module 2.1.3.1 For Each module
• Degree of atomization achieved by this module • Explain if BPR required
• Dependency with other modules
• Designation of person using this module
• Proposed process flow diagram
• Input and Output Specification
2.2 Business Rationale
2.3
2.4
2.5
3.
Integration of the existing Applications/websites/modules with new suggested system. List all the proposed modules covering following points
• Priority of development
• Dependency of the module on other module
• Specification for Alert & Escalation mechanism
Proposed
Hardware,
Software
and
Network
Specification
• Network Diagram of the proposed system including suggested nodes, dependent clients, servers, printers etc. Also specify where GSWAN connectivity is applicable and where dial up or Lease Line required.
Architecture
3.1
3.2
3.3
3.4
3.5
System Architecture
User Interface layer
Application layer
Utility layer
Core layer
4. General Requirements
4.1
4.2
4.3
4.4
4.5
Audit Trails
• Application driven & managed Audit trails are a must. • Platform driven/ managed audit trails may be used to complement the application