Sunday, August 14, 2011

SRS structure for Web Site/Application


Chapter 1
SRS Document for . . . . . . . . .

1.     Introduction

1.1.Purpose/Problem Definition :

1.2.Scope of the Project :

1.3.References :

2.     Overall Description

2.1.Product perspective :

2.2.Product Functions :

2.2.1.      Customer Module :

2.2.2.      Administrative Module :

2.3.User Classes and Characteristics :

2.3.1.      Administrator :

2.3.2.      Customers :

2.3.3.      Casual Visitors :

2.4.Design and Implementation Constraints :

3.     External Interface Requirements :


3.1.User Interface :

3.2.Hardware Interfaces :

3.3.Software Interfaces :

3.4.Communication Interfaces :

3.5.Communication Protocol :

4.     Product Features :

4.1.Account Creation :

4.2.Buying :

4.3.Others :

5.     Non-Functional Requirements :

5.1.Performance Requirements :

5.2.Software System Attributes (Quality Requirements) :

5.2.1.      Reliability :

5.2.2.      Security :

5.2.3.      Maintainability :

5.2.4.      Availability :

5.2.5.      Recoverability :

6.     Logical Database Requirements :

7.     Other Requirements :


Chapter 2

Analysis

     1.     Preliminary System Study

1.1.Problem Definition:
1.2.Existing System:
1.3.Proposed System:

     2.     Feasibility Report

2.1.Objectives of Feasibility Study :

2.2.Types of Feasibility :

2.2.1.      Technical Feasibility :

1. Is the project possible with current technology?
2. Is the technology available?
3. Is it available locally?
4. Can it be obtained?
5. What technical risk is there?
6. Will it be compatible with other systems?
7. What kind of technology will be used?
8. is the required technology available “in house”?
Conclusion:

2.2.2.      Economic Feasibility :

1. Is the project possible, given the resource constraints?
2. What are the benefits?
3. What are the development and operational costs?
4. Are the benefits worth the costs?
5. How soon will the benefits accrue?
6. Hardware/Software selection?
7. Selection of alternative finance (Rent / Lease / Purchase)
Conclusion:

2.2.3.      Schedule Feasibility :

1. Is it possible to build a solution in time to be useful?
2. What are the consequences of delay?
3. Any constraints on the Schedule?
4. Can these constraints met?
5. Whether training for the required technology will impact the schedule?
6. Given the technical expertise, are the project deadlines reasonable?
7. If there are specific deadlines, are they mandatory or desirable?
8. If the Project overruns, what are the consequences?

2.2.4.      Operational Feasibility :

1. If the system is developed, will it be used?
2. Social acceptability?
3. Legal aspects and government regulations?
4. Does management support the system?
5. How do the end-users feel about their role in the new system?
Conclusion: Operations are feasible.

2.3.System Analysis :
Constraints:
           
Use Case Diagram:
Fig 2.1: Use-Case Diagram

Actors
Description




Table 2.1: Use-Case Diagram Actors Description

Use Case
Description




Table 2.2: Use-Case Diagram Use-Cases Description

Activity Diagram:
Only diagram . . .
Fig. 2.2: Activity Diagram

Class Diagram:
Fig. 2.3: Class Diagram

Class
Description




Table 2.3: Class Diagram Class Description

State Chart Diagram
Fig. 2.4: State Chart Diagram