2.5 Assumptions and Dependencies This subsection of the SRS should list each of the factors that affect the requirements stated in the
SRS. These factors are not design constraints on the software but are, rather, any changes to them
that can affect the requirements in the SRS.
Example An assumption may be that a specific operating system will be available on the hardware designated for the software product. If, in fact, the operating system is not available, the SRS would then have to change accordingly. 2.6 Apportioning of Requirements This subsection of the SRS should identify requirements that may be delayed until future versions of
the system. This section divides the requirements into different sections for development and
delivery
Use Case ID Use Case Name Primary Actor Priority Use Case
identified by its
unique id
The Name of the Use
Case. It Usually Starts
With a Verb
Mention the name of the
primary actor who is
responsible for the use
case
priority can be
identified as
1,2,3,4,5….etc
1 being the top most
priority.
Illustration Use Case ID Use Case Name Primary Actor Priority UC001
Place a Bid
Buyer
1
UC004
Ship an Item
Seller
2
UC182
Add a Warehouse
Admin
-
3 Specific Requirements This section of the SRS should contain all of the software requirements to a level of detail sufficient
to enable designers to design a system to satisfy those requirements, and testers to test that the
