3.3 Performance Requirements This subsection should specify both the static and the dynamic numerical requirements placed on
the software or on human interaction with the software as a whole. Static numerical requirements
may include the following:
a)
The number of terminals to be supported
b)
The number of simultaneous users to be supported
c)
Amount and type of information to be handled
Static numerical requirements are sometimes identified under a separate section entitled Capacity
Dynamic numerical requirements may include, for example, the numbers of transactions and tasks
and the amount of data to be processed within certain time periods for both normal and peak
workload conditions.
Note: All of these requirements should be stated in measurable terms.
Example 95% of the transactions shall be processed in less than 1 s. rather than, An operator shall not have to wait for the transaction to complete. NOTE: Numerical limits applied to one specific function are normally specified as part of the
processing subparagraph description of that function.
3.4 Logical Database Requirements This should specify the logical requirements for any information that is to be placed into a database.
This may include the following:
a)
Types of information used by various functions
(e.g. integer, varchar. etc.) b)
Frequency of use
(e.g. Stored information is used how many time- for posts, messages, check-in information etc.) c)
Accessing capabilities
d)
Data entities and their relationships
(e.g. ER Diagram given below shows the relationship) e)
Integrity constraints: Integrity constraints ensure that the data insertion, updating, and
other processes have to be performed in such a way that data integrity is not affected, so
should the diagram represent
f)
Data Retention Requirement: Describe the length of time the data must be retained
(e.g. Information about an application for naturalization shall be retained in immediately accessible form for 3 years after receipt of the application.)