VCAP DCD Study – Home Lab Design Part 10

Section 4 – Implementation Planning

Objective 4.1 – Create an Execute a Validation Plan

Recall standard functional test areas for design and operational verification.

Covered this in earlier sections but a recap!

Functional Requirements The official definition for a functional requirement specifies what the system should do: “A requirement specifies a function that a system or component must be able to perform.” Functional requirements specify specific behavior or functions, for example: “Display the heart rate, blood pressure and temperature of a patient connected to the patient monitor.”

Typical functional requirements are:

  • Business Rules
  • Transaction corrections, adjustments, cancellations
  • Administrative functions
  • Authentication
  • Authorization –functions user is delegated to perform
  • Audit Tracking
  • External Interfaces
  • Certification Requirements
  • Reporting Requirements
  • Historical Data
  • Legal or Regulatory Requirements

Non-Functional Requirements The official definition for a non-functional requirement specifies how the system should behave: “A non-functional requirement is a statement of how a system must behave, it is a constraint upon the systems behavior.”

Non-functional requirements specify all the remaining requirements not covered by the functional requirements. They specify criteria that judge the operation of a system, rather than specific behaviors, for example: “Display of the patient’s vital signs must respond to a change in the patient’s status within 2 seconds.”

Typical non-functional requirements are:

  • Performance – Response Time, Throughput, Utilization, Static Volumetric
  • Scalability
  • Capacity
  • Availability
  • Reliability
  • Recoverability
  • Maintainability
  • Serviceability
  • Security
  • Regulatory
  • Manageability
  • Environmental
  • Data Integrity
  • Usability
  • Interoperability

Non-functional requirements specify the system’s ‘quality characteristics’ or ‘quality attributes’. Potentially many different stakeholders have an interest in getting the non-functional requirements right. This is because for many large systems the people buying the system are completely different from those who are going to use it (customers and users)


Differentiate between operational testing and design verification.

Good operational testing examples can be found here..

From Brownbag notes…

Operational Testing is testing pieces of the virtual infrastructure in general

Design Verification means implementing a business goal or requirement and verifying
its accuracy with the business, that the design item(s) perform as expected and, if so, a
ccepted by the business (i.e. meeting a Compliance requirement); this may or may not be
outside of standard implementation criteria.


Skills and Abilities

From an existing template, choose the appropriate test areas.

Example of a test template here..

Test vSphere features (i.e. vMotion, HA, DRS) under certain workloads to see how apps

Identify expected results

Document the results from the test plans and compare them to the current state analysis done at the start of the project.

Demonstrate an ability to track results in an organized fashion

Use health check scripts and rvtools and document and present the results.

Compare validation plan metrics to demonstrate traceability to business objectives

Compare the results to the business objectives and requirements for validation.


Objective 4.2 – Create an Implementation Plan

Skills and Abilities

Based on key phases of enterprise vSphere 5.x implementations, map customer development needs to a standard implementation plan template.

VMware provide a plan and design kit to partners, basically they are saying that although it is a useful tool we shouldn’t stick to it to the letter, take in to account your own business requirements and make sure the design fits them.

Evaluate customer implementation requirements and provide a customized implementation plan.

Not really sure what to say here but create an implementation that meets the customers needs.

Incorporate customer objectives into a phased implementation schedule.

Phased implementation focus areas:
Early ROI workloads
Low risk/high visibility

Match customer skills and abilities to implementation resource requirements.

The key roles for the team are listed below.

  • Relationship Manager – Act as primary interface between application owners and infrastructure groups.
  • IT Analyst – Identify impacted operational areas and recommend changes.
  • IT Infrastructure Architect – Translate requirements into architectural designs.
  • IT Infrastructure Engineer – Provide specific technical design for virtualized solutions.

The size of the team will vary depending on the scope and size of deployments, but it can be as small as three people or larger where multiple people are acting in each role. These positions should be viewed as relatively senior positions for highly regarded and skilled employees. Suitable candidates can often be found in the current organization (for example, in relationship management, IT infrastructure architecture, or server engineering groups). Once the team is in place, the team members play a central role in the deployment of projects in a virtualized environment.

Identify and correct implementation plan gaps.

Basically provide the finer detail of the implementation plans e.g. configure vswitch security settings.

Objective 4.3 – Create an Installation Guide


Identify standard resources required to construct an installation guide.

Use the official VMware documentation to construct the installation guides, also refer to the VMware community.
Skills and Abilities
Consider multiple product installation dependencies to create a validated configuration.

Ensure the installation guide follows a logical flow so that components are installed in the correct order.
Recognize opportunities to utilize automated procedures to optimize installation.

Auto-deploy springs to mind, nothing stopping you from using good old linux based kickstart to do a scripted installation.
Create installation documentation specific to the design.

Create a step by step installation doc, use screenshots to assist the engineer installing the components.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s