Question

What sections does your final system requirement document include? What do you believe are the most important sections, and why? Additionally, who is the audience of your final system requirement document? Are there multiple versions of the document to communicate to different audiences?

Answer 1

Define what a final system requirement document is.

The system requirements document will state “what” the software can do. However, it won’t state “how” the software will get it done. What the software is capable of doing is directly perceived by the end users. When the end user completes some type of action, then the software is expected to respond to those actions in an expected way. Similarly, when a request comes from an external system for a particular action then it should get a specific response. The requirements document does not address how the software responds to the particular request.

What sections does your final system requirement document include?

The final system requirement’s document should include the following elements:

• A title page

• Summary

• Glossary

• Use cases, scenarios, and mock-up's

• An overview of the architecture

• Specifications for the modules

• Team specific diagrams

• Deliverables

• Delivery platform

• Terms and authorizations

• Development platform

• Milestones

• Acceptance test plans

• Integration test plans

What do you believe are the most important sections, and why?

For me the important elements are:

1. Summary – A general overview of the project as a whole.

2. Specifications – The details behind the project and its parts.

3. Deliverables – What the users can expect when it is rolled out to all users.

4. Milestones – When users should expect specific segments of the project to be completed, from development to installation and training.

Who is the audience of your final system requirement document?

The team should consist of a diverse cross section of member from within the organization from end users up to leadership. Additionally, the businesses’ customers, a select pilot group, should be included.  

The following is a list of potential members that should be included.

• Development Team Members

• Project Sponsor

• Requirements Analyst

• Business Expert

• QA Specialist

• User Documentation Specialist

• Legacy Support Specialist

• Maintenance Team Member

• Management

• Internal users

• Customers

Are there multiple versions of the document to communicate to different audiences?

A well written requirements document should only need one version available to all stakeholders. One version would prevent any possible confusion to arise, were having multiple version available could produce potential issues. If the wrong audience received the incorrect version they may have many questions if not reject the proposal altogether.