Identify from the system-wide requirements the non-functional requirements that consumers are likely to impose upon
each service in the service model. Such requirements could include, but are not limited to:
-
Availability (that is, mean time between failure)
-
Operational window (is there ever a time when the service is not expected to be used?)
-
Response time (how quickly does the service need to respond to a request)
-
Peak throughput (how many requests for the service can arrive per unit of time such as per second, per
minute, per hour)
Document any key architectural decisions that are needed to meet these requirements. These decisions also need
to be reflected appropriately within the software architecture document.
The manner in which non-functional requirements are attached to the ServiceInterface is not defined by this guidance. Neither are there bounds set
on what constitutes such a requirement.
|