This step is where a complete definition of the software requirements to be delivered in the current development cycle
is produced so that requirements can be effectively reviewed. All requirements work products are assembled,
and any additional information is supplied.
For less formal projects, this step consists of bundling the relevant reports and hand-generated documentation, with
sufficient supporting material .
On more formal projects, one or more Software Requirements Specifications (SRS) may be produced that
collect and organize all requirements surrounding the project. For example, a separate SRS may describe the complete
software requirements for each feature in a particular release of the product. This may include requirements that are
documented in other requirements work products. In such cases, the SRS may refer to the requirements documented
in the other work products. This allows you to have a formal SRS without having to duplicate the information in
the other work products. Using an appropriate Software Requirements Specification template, assemble the pieces of
the SRS package and supply the remaining information in order to have a complete definition of the software
requirements for this subsystem or feature.