lesson 8 Flashcards
describe the characteristics of the final deliverable in ordinary non-technical language.
Functional requirements
specify criteria that can be used to judge the final product or service that your project delivers.
Non-functional requirements
restrictions or constraints to be placed on the deliverable and how to build it.
Non-functional requirements
Their purpose is to restrict the number of solutions that will meet a set of requirements.
Non-functional requirements
Three types of general non-functional development constraints?
- Time
- Resource
- Quality
When a deliverable should be delivered
time
How much money is available to develop the deliverable
Resource
Any standards that are used to develop the deliverable, development methods, etc.
Quality
emerge from the functional requirements to answer the
questions: how will the problem be solved this time and will it be solved technologically and/or procedurally?
Technical Requirements
are the needs of the sponsoring organization, always from a management perspective.
Business requirements
are usually expressed in broad outcomes, satisfying the business needs, rather than specific functions the system must perform.
Business requirements
These requirements grow out of the vision for the product that, in turn, is driven by mission (or business) goals and objectives
Business requirements
requirements describe what the users need to do with the system or product.
User Requirements
can be internal or external and are usually non-negotiable.
Regulatory requirements
They are the restrictions, licenses, and laws applicable to a product or business that are imposed by the government.
Regulatory requirements