Professional Documents
Culture Documents
The term
'business model' is thus used for informal and formal descriptions to represent core aspects of a business.
The plan for implementing functional requirements is detailed in the system design and defines what a system is
supposed to do.
The hierarchy of functional requirements is: user/stakeholder request -> feature -> use case -> business rule.
The plan for implementing non-functional requirements is detailed in the system architecture and defines how a system
is supposed to be.
Can be divided into two main categories:
1. Execution qualities, such as security and usability, which are observable at run time.
2. Evolution qualities, such as testability, maintainability, extensibility and scalability, which are static structure of the
software system