This post will attempt to document all of the important terminology required to understand in the VCAP6-DCV Design certification exam. This is going to assume you have some general IT knowledge. This isn’t meant in anyway to be a complete dictionary. Because ain’t nobody got time for that.
- Design Components:
- Vision – Whole reason for the project.
- Scope – Quantitative statement of what is/isn’t in a project.
- Requirements – Attribute that must be achieved.
- Functional – A definable and detailed project item that describes the purpose of a component. (ex. PCI, SOX compliance)
- Non-Functional – Describes the quality of a solution or service. (ex. application should be available 24/7)
- Constraints – Attribute that may limit design choice. Technical or business driven.
- Assumptions – Attribute that has been decided to be true but never tested or proved.
- Risks – Attribute that could prevent or change the completion of the project considerably
- MTBF – Mean Time Between Failure – Time between component failures.
- MTTR – Mean Time to Recovery – Time to recover after a component failure.
- Business Continuity – Plan that addresses resilience, recovery, & contingency.
- Fault Tolerance – If a failure happens & operations continue to function.
- High Availability – If a failure happens & operations recover quickly.
- Recovery – If a failure happens, how to recover as quickly as possible.
- Disaster Recovery – A subset of Business Continuity to address a disaster typically focused on critical business functions.
- Current State Analysis – Project starting point.
- Gap State Analysis – Review of items or tasks required to progress to the projects vision.
- RPO – Recovery Point Objective – Point in time which a service/system needs to be restored too following a failure.
- RTO – Recovery Time Objective – Amount of time it takes to restore a service after a failure.
1 thought on “VCAP6-DCV Design: Definitions”