Sunday, May 16, 2010

SRSD

Ahhhh! At last we prepared SRSD and we delivered the document for approval. After approval the deliverable will be mailed to our client.


When our client explained about ALS (Aircraft Landing Scheduler), I taught the project is simple, and we started to write the code. I did not know that we should prepare a SRSD before coding. As the day passed I came to know that we should prepare few documents before coding, i.e. SRSD, HLD-high level design document, DDD-detail design document etc.
That day I went home and started to browse internet and I came to know about SRSD, HLD, DDD.It took me whole night to know about these documents. That night I realized before preparing SRSD we should know so many things about the domain and also we should capture requirements from the client. Now I have an idea about SRSD.I also learnt, what and all should be included in SRSD.
The outline of SRSD that we have prepared in our project.
TABLE OF CONTENTS
Revision History
1.Introduction
1.1.Product Overview
1.2.Purpose
1.3.Scope
1.4.Reference
1.5.Definitions and Abbreviations
2.Overall Description
2.1.Product Purpose
2.2.Product Functions
2.3.User Characteristics
2.4.General Constraints
2.5.Assumptions and Dependency
3. Specific Requirements
3.1.External Interface Requirements
3.1.1.User interface
3.1.2.Hardware Interface
3.1.3.SoftwareInterface
3.1.4 Operations
3.2 Software System Attributes
3.2.1 Reliability
3.2.2 Availability
3.2.3 Security
3.2.4 Maintainability
3.2.5 Portability
3.2.6 Performance
3.4 Database Requirements
3.5 Risk Analysis
I learnt many things while preparing SRSD.I learnt how an aircraft lifts takes place, naming the runways, basic aerodynamics. I learnt how does communication takes place between pilot and ATC (Air Traffic Controller).Day by day my confidence level is increasing by learning all these.

In SRSD we included use cases, which are inputs for test cases when we proceed for testing.

We also did Risk analysis to make the project proceed smoothly without any problems.
Risk analysis contains two parts:
1. Risk of the system
2. Risk of the project

No comments:

Post a Comment