Key Design Terminology Flashcards
Name the 4 design requirements
Requirements
Risk
Assumptions
Constraints
Meaning of CAPEX and OPEX
Capital Expenditure
Operational Expenditure
What is a - Functional Requirement
WHAT
A functional requirement is what the design must DO.
“A requirement specifies a function that a system or component must be able to perform.”
“The design must cater for 10% growth in storage capacity used by Engineering, and 30% compute growth, within the next 12 months” – This is a functional requirement. In other words the design must deliver on 10% growth in storage (something the design must DO or ACHIEVE).
What is a - Non-Functional Requirement
HOW
A non-functional requirement typically describes HOW is does it.
“A non-functional requirement is a statement of how a system must behave, it is a constraint upon the systems behavior.”
“The design must incorporate storage from the existing EMC VNX storage array” – This is a non-functional requirement, but also a constraint. The vSphere design must use existing storage, but this introduces a constraint.
Describe the meaning of - Conceptually
conceptually what you are trying to produce …
Describe the meaning of - Logically
logically how it would be designed …
Describe the meaning of - Physically
physically how you intend to build it.
Describe a Requirement
What the design MUST satisfy.
A condition the must be satisfied by a functional or non-functional requirement.
RTO
Recovery Time Objective
The duration of time and a service level within which a business process must be restored after a disaster (or disruption) in order to avoid unacceptable consequences associated with a break in business continuity.
RPO
Recovery Point Objective
It is the maximum tolerable period in which data might be lost from an IT service due to a major incident.
