8 of
18 b)
Specify the site or mission-related features that should be modified to adapt the software to
a particular installation.
Example If any modifications to the customer’s work area would be required by your system, then document that here. For instance, “A 100Kw backup generator and 10000 BTU air conditioning systems must be installed at the user site prior to software installation”. This could also be software-specific like, “New data tables created for this system must be installed on the company’s existing DB server and populated prior to system activation.” Any equipment the customer would need to buy or any software setup that needs to be done so that your system will install and operate correctly should be documented here. 2.2 Product Functions This subsection of the SRS should provide a summary of the major functions that the software will
perform.
(e.g., an SRS for an accounting program may use this part to address customer account maintenance, customer statement, and invoice preparation without mentioning the vast amount of detail that each of those functions requires.) .
Sometimes the function summary that is necessary for this part can be taken directly from the
section of the higher-level specification (if one exists) that allocates particular functions to the
software product. Note that for the sake of clarity
a)
The functions should be organized in a way that makes the list of functions understandable
to the customer or to anyone else reading the document for the first time.
b) Textual or graphical methods can be used to show the different functions and their
relationships. Such a diagram is not intended to show a design of a product, but simply
shows the logical relationships among variables
. (e.g. Use Case diagrams and description shown below)
