How to compile software requirement specifications (7)

Address: http://www.microtoolsinc.com/Howsrs.php

How to Write a software requirements specification

How to compile software requirement specifications

By Robert japenga

__________________________________________________________________________________________

 

Is this do-able? Won't we miss our deadlines if we take the time to do this?

Is it operable? Will the project be extended because it takes too much time on software requirements?

This is a great question. there is no question that there is balance in this process. we have seen companies and individuals go overboard on documenting software that does not need to be writable ented, such as a temporary utility. we have also
Seen customers kill good products by spending too much time specifying it.

This problem is very good. There is no doubt that this is a process that requires balance. We can see that some companies and individuals spend too much effort on software without documentation, such as temporary utilities. We have also seen customers spend too much time on the specifications, but they have killed a good product.

However, the bigger problem is at the other end of the spectrum. we have found that taking the time up front pays dividends down stream. if you do not have time to specify it up front, you probably do not have the time to do the project.

However, the bigger problem is that we found that less and less time is spent on the specification book. If you didn't have time to write the specification book at the beginning, you may not have time to develop projects.

Here are some of our guidelines:

• Spend time specifying and documenting well software that you plan to keep.
• Keep documentation to a minimum when the software will only be used for a short time or has a limited number of users.
• Have separate individuals write the specifications (not the individual who will write the code ).
• The person to write the specification shoshould have good communication skills.
• Pretty diagrams can help but often tables and charts are easier to maintain and can communicate the same requirements.
• Take your time with complicated requirements. Vagueness in those areas will come back to bite you later.
• Conversely, watch out for over-documenting those functions that are well understood by province people but for which you can create some great requirements.
• Keep the SRS up to date as you make changes.
• Approximately 20-25% of the project time shocould be allocated to requirements definition.
• Keep 5% of the project time for updating the requirements after the design has begun.
• Test the requirements document by using it as the basis for writing the test plan.

Here are some guiding suggestions:

• When the software is used for a short period of time, or the number of users is small, the document should be as short as possible.
• Someone should be assigned to write the specifications (rather than the code writer)
• The person who writes the specifications needs good communication skills.
• Beautiful digraphs are helpful, but tables and charts are usually easier to maintain and can be used as a medium for communication.
• Pay attention to complicated requirements. Ambiguity of these requirements will lead to subsequent rework.
• On the contrary, do not describe too many requirements that most people can understand. Focus on other important demands.
• Ensure that SRS is updated in a timely manner
• Requirement definition accounts for almost 20-20 of the entire project process ~ 25% of the time
• After entering the design stage, ensure that 5% of the project time is required to be updated
• Test Requirement documents by writing test plans based on Requirement documents

How to compile software requirement specifications (1)

How to compile software requirement specifications (2)

How to compile software requirement specifications (3)

How to compile software requirement specifications (4)

How to compile software requirement specifications (5)

How to compile software requirement specifications (6)

How to compile software requirement specifications (7)