Sample SRS Template

Sample System Requirement Specification Document

1. Background
2. Scope
.
3. Software Requirement Specification
3.1. System scope
3.2. Definitions, Acronyms, Abbreviations
4. Assumptions and Dependencies
5. Non-Functional Requirements
5.1. Environmental Requirements
5.2. System Performance Requirements
5.3. Security
5.4. Design and Implementation Constraints
5.5. Standards

6. Evisioned Future Enhancements / Open Issues

Description Person Responsible Resolution Date Complete

7. References

Learn Internet Protocols

Students,

If you want to learn about Internet,Ecommerce,Internet Protocols please check our question bank

Knowledge acquisition:Concepts

Knowledge acquisition includes the elicitation, collection, analysis, modeling and validation of knowledge for knowledge engineering and knowledge management projects.

Issues in Knowledge Acquisition

Some of the most important issues in knowledge acquisition are as follows:
• Most knowledge is in the heads of experts
• Experts have vast amounts of knowledge
• Experts have a lot of tacit knowledge
o They don't know all that they know and use
o Tacit knowledge is hard (impossible) to describe
• Experts are very busy and valuable people
• Each expert doesn't know everything
• Knowledge has a "shelf life"
Requirements for KA Techniques
Because of these issues, techniques are required which:
• Take experts off the job for short time periods
• Allow non-experts to understand the knowledge
• Focus on the essential knowledge
• Can capture tacit knowledge
• Allow knowledge to be collated from different experts
• Allow knowledge to be validated and maintained

Software Requirements Specification:How to Write

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.......

Coming Soon

People in Programming,

Want to know tips and tricks on Project Management.Soon i will be posting on How to manage short-term projects.Projects which are not longer then 6-8 months.I will explain how to built proposals,SRS,Project management plan,Work Break Down structure and Effort estimation sheet.How to use various bug tracking tool and visual source.So keep waiting...for some time...

Cheers
Admin

About FindThing4u

Friends,

On this blog you will lots of information about cool gadgets,cool softwares,Shopping,Education,c,c++,Free ISO templates,SRS,Project Management Plans,Jobs,Flash games and lots of other cool stuff.

Please join this blog and also give your valuable suggestions.Also visit our main site

cheers
Admin