There are a number of non-functional requirements which need to be taken into account when considering the exchange of ASM data, as they are relevant to any system development. These type of requirements typically are concerned with characteristics such as availability and performance, and can be used as measurements of a system’s efficiency, effectiveness and continued viability when comparing actual performance with expected performance.
In order for these non-functional requirements to be defined as concrete testable requirements, significant analysis of the entire environment would need to be carried out to ascertain the basic nature of the infrastructure and the predicted user activity.
The definition of these non-functional requirements is out of scope of this document.
A non-exhaustive list of some of the features which might directly influence the non-functional aspects is given below.
· Predicted load (typical and extreme)
· Number of concurrent users (typical and extreme)
· Available network bandwidth
· Hardware specifications
· Security policy restrictions
Some of the associated non-functional requirements which need to consequently be considered are described in the following section.