Specifies functionalities that:
- are common across several US/UC;
- are not related to US/UC, namely: Audit, Reporting and Security.
(fill in here)
Evaluates the user interface. It has several subcategories, among them: error prevention; interface aesthetics and design; help and documentation; consistency and standards.
(fill in here )
Refers to the integrity, compliance and interoperability of the software. The requirements to be considered are: frequency and severity of failure, possibility of recovery, possibility of prediction, accuracy, average time between failures.
(fill in here )
Evaluates the performance requirements of the software, namely: response time, start-up time, recovery time, memory consumption, CPU usage, load capacity and application availability.
(fill in here )
The supportability requirements gathers several characteristics, such as: testability, adaptability, maintainability, compatibility, configurability, installability, scalability and more.
(fill in here )
Specifies or constraints the system design process. Examples may include: programming languages, software process, mandatory standards/patterns, use of development tools, class library, etc.
(fill in here )
Specifies or constraints the code or construction of a system such such as: mandatory standards/patterns, implementation languages, database integrity, resource limits, operating system.
(fill in here )
Specifies or constraints the features inherent to the interaction of the system being developed with other external systems.
(fill in here )
Specifies a limitation or physical requirement regarding the hardware used to house the system, as for example: material, shape, size or weight.
(fill in here )