Tag Archives: Design - Page 2

VDCD510 Objective 1.3 – Determine Risks, Constraints, and Assumptions

This are very common project parts which are not related to VMware or virtualisation. If you are familar with project management this terms should be known.

Requirements are the things that the project must achieve. This could be business or technical requirements. They are the detailed view of the Objectives the Project must deliver. Only a clearly defined list can avoid ambiguities durin the design process. The characteristics of good requirements are: verifiable, traceable, feasible, specific and unambiguous.

  • Must comply with ISO standards
  • The service uptime must be at a minumum of 99,9%
  • Users must be able deploy new virtual machine

Assumptions are factors considered to be true without proof in the planning phase.

  • Equipment will be available at a certain date
  • The organisation has sufficent network bandwidth
  • Stakeholders will make a decistion in the next meeting
  • Server hardware has to be separated between dmz and internal servers

Constraints could be a business policy or a technical limitation that is limiting the design choice.

  • The project has to be finished in 4 month
  • The total cost must not exceed $500.000
  • The hardware vendor has to been xxx

Risks might prevent achieving the project goals. They are a common point within every project as anything can happen during the project. Clearly identify and list every risk that might prevent further progress.

  • User commitment could be a problem in every project
  • Single point of failures in the existing environment
  • The most common risk is that the project being delivered late

VCAP5-DCD Exam Blueprint v1.1

Skills and Abilities

  • Differentiate between the general concepts of a risk, a requirement, a constraint, and an assumption.
  • Given a statement, determine whether it is a risk, requirement, a constraint, or an assumption.
  • Analyze impact of VMware best practices to identified risks, constraints, and assumptions.


VDCD510 Objective 1.2 – Gather and analyze application requirements

This section is really much about best practices and use cases. VMware offers a bunch of documents which are a little bit overkill for the exam, and to complex to memorize. So my advice for the exam is to skim through the documents and memorize the basics. If you have a real world project, this is also a great ressource to gather deep knowledge. The purpose of this section is to give a brief technical overview. Please refer to the resource in the Tools section for more details. A registration is required to download the application kits, but it's free.

The requirements should be documented in the same way as the business requirements.

VCAP5-DCD Exam Blueprint v1.1

Skills and Abilities

  • Given a scenario, gather and analyze application requirements
  • Given a set of applications within a physical environment, determine the requirements for virtualization.
  • Gather information needed in order to identify application dependencies.
  • Given one or more application requirements, determine the impact of the requirements on the design.


VDCD510 Objective 1.1 – Gather and analyze business requirements

Five-Step design process

  1. Initial design meeting
  2. Current-state analysis
  3. Stakeholder and SME training
  4. Design sessions
  5. Design deliverables

Project participants (SMEs / Key Stakeholders)
A design project manager has to determine a list of SMEs and project stakeholders who can provide information about the design requirements. This list typically includes:

  • Network administrators
  • Storage administrators
  • Server hardware administrators
  • Operating system administrators
  • Application administrators
  • Security Officer
  • HR representatives
  • C-Level executives (CEO, CTO, CIO,...)
  • Representatives

It is important to lists the people involved in this project and their contact information. This list should include:

  • Name
  • Title
  • Organisation
  • E-Mail address
  • Phone number
  • Reachability

Having contact information available will help to make progress without unnecessary interruption during the design process.

Stakeholder = A person with an interest in a project
SME = A subject-matter expert is a person who is an expert in a particular area.#

Functional / Non-functional requirements
Functional requirements are tasks or processes that must be performed by the system. For example, a functional requirement of a vSphere platform is "must allow multi tenancy" or "users must be able to create virtual machines".

Non-functional requirements are standards that the system under must have or comply with. For example, a non-functional requirements for a vSphere platform is "must be built for a total cost of $500.000". Non-Functional requirements are also called constraints.

Conceptual design
The conceptual design typically focuses on the business requirements. It is an high level overview which includes only the most important components. Concept design is the first phase of the design process.

Conceptual design from an stretched Cluster

Conceptual design from a webservices platform

Logical design
The logical design specifies the relationship between all components. It is usually stable which means that it will only change if the requierement changes. The logical design does not include physical details such as IP addresses, hostnames or hardware models.

Physical design
The physical design is usually the last and the most specific design. It shows port connections, IP addresses and model description.

Requirement tracking
It is important to document all requirements. This could be done in an excel sheet for example. Every single requirement should contain at least a unique number, desciption, timestap, priority and the originator.

VCAP5-DCD Exam Blueprint v1.1

Skills and Abilities

  • Associate a stakeholder with the information that needs to be collected.
  • Utilize customer inventory and assessment data from a current environment to define a baseline state.
  • Analyze customer interview data to explicitly define customer objectives for a conceptual design.
  • Identify the need for and apply requirements tracking.
  • Given results of a requirements gathering survey, identify requirements for a conceptual design.
  • Categorize requirements by infrastructure qualities to prepare for logical design requirements.