SRS:How to Write
A Software Requirements Specification (SRS) is a complete description of the behavior of the system to be developed.It also acts as an agrement between customer and client.Great way to freeze the requirements.Its always better to get SRS approved from customer first and then start working.It's important to note that an SRS contains functional and nonfunctional requirements only; it doesn't offer design suggestions, possible solutions to technology or business issues.
Keep In Mind : 1) The development team should try to be very precise while writing srs.
2)The team should keep in mind the requirements of client,timeline and budget of the project.In most cases project is taken by business team and given to development team so this should be kept in mind
3) It should not be too technical.Try to make it simple to understand even for a layman.
Advatages of SRS
* Reduce the development effort.
* Provide a basis for estimating costs and schedules(if project is not awarded yet).
* Provide a baseline for validation and verification.
* Serve as a basis for enhancement.
I have 3 + years of experience in project management.I have some very simple but effective templates that you can use to write SRS.If you have any questions or you want any guidance in writing SRS.please free to ask.I will be posting some Software Requirements Specifications (SRS) Templates soon...so keep looking.......
Posts
2 comments:
it will be great if you can post some templates
its really nice. i am also team leader at some company and like to learn PM concepts. I hope this blog will provide some gr8 stuff for that.
Post a Comment