We already had a detailed discussion about VCAP6 - DCV Design exam, where we discussed about the Path we need to follow and what are the objectives that we need to take care, If in case you missed it here is the link for your reference Kick Start Your Journey Towards VCAP6-DCV Design.
We have also had a detailed discussion about the VCAP6-DCV Design Objective 1.1 and VCAP6-DCV Design Objective 1.2 in which we discussed about Business and Application Requirements here is the link for your reference VCAP6-DCV Design Objective 1.1,
Let's proceed further and understand VCAP6-DCV Design Objective 1.3 in this article will see what are the Skills and Abilities required to prepare for this objective and what are various tools/ Urls we can refer while doing the preparation.
Objective 1.3 – Determine Risks, Requirements, Constraints and Assumptions
Skills and Abilities
- Differentiate between the concepts of risks, requirements, constraints, and assumptions.
- Given a statement, determine whether it is a risk, requirement, constraint, or an assumption.
- Analyze impact of VMware best practices to identified risks, constraints, and assumptions.
- Developing Your Virtualization Strategy and Deployment Plan
- Constraints, Assumptions (Risk, Requirements) & Dependencies
I have already highlighted about Assumptions ,Risks and Constraints in one of the old article which i dedicated towards Design Qualifiers here is the link for your reference VMware vSphere Design Qualifiers let's have a look on these one by one again.
Assumptions
Assumptions are the expectations about the implementation of a project which are believed to be true and cannot be confirmed during the assessment and design stage.
For example one common assumption is that the support staff are trained on the Virtualization technologies or the Client will provide all the License required for the implementation of the Project, or could be that Application team will help with all the test plans necessary for the implementation of the project.
Assumptions are acting as a helping hand for providing guidance within the Design and if not met those Design areas are at Risk.
RISKS
Situation/Event which has a direct impact on the Design and need to be properly documented during the Design process, and stakeholders should respond to the Risks highlighted with a Plan of Action.
For Example Having vMotion and Data traffic on the same physical network can lead to network disruptions if not designed carefully can lead the Design at High Risks and need to be documented properly.
When working towards the Design the Design Architect has to document each and every Risks and make the stakeholders aware about those Risks so as they can prepare a plan of action in terms of reducing those risks, and also reducing the overall impact of that Risks.
When dealing with the Plan of action it could be related to Prevention of the Risks, Reduction of the Risks or it could also be Transference of the Risks depending on the type of Risks we are dealing with the Stakeholders may come with the any of these approach Constraints, Assumptions (Risk, Requirements) & Dependencies explains the same and other alternatives that can be considered when dealing with Risks.
Constraints
Constraints are the boundaries within which the Design should be laid, it could be an Organization Policy or could be a Budget Restriction.
For Example when working towards the Design, Stakeholders specified that we have to make use of the existing hardware and existing Storage arrays, now this is definitely a Constraint because when preparing the Design the Design Architect has to work within these boundaries because he need to find out some ways where he can make use of the Existing Hardware and Existing Storage Arrays.
 |
| Image Source -VMware |
Assumptions are the expectations about the implementation of a project which are believed to be true and cannot be confirmed during the assessment and design stage.
For example one common assumption is that the support staff are trained on the Virtualization technologies or the Client will provide all the License required for the implementation of the Project, or could be that Application team will help with all the test plans necessary for the implementation of the project.
Assumptions are acting as a helping hand for providing guidance within the Design and if not met those Design areas are at Risk.
RISKS
Situation/Event which has a direct impact on the Design and need to be properly documented during the Design process, and stakeholders should respond to the Risks highlighted with a Plan of Action.
For Example Having vMotion and Data traffic on the same physical network can lead to network disruptions if not designed carefully can lead the Design at High Risks and need to be documented properly.
When working towards the Design the Design Architect has to document each and every Risks and make the stakeholders aware about those Risks so as they can prepare a plan of action in terms of reducing those risks, and also reducing the overall impact of that Risks.
When dealing with the Plan of action it could be related to Prevention of the Risks, Reduction of the Risks or it could also be Transference of the Risks depending on the type of Risks we are dealing with the Stakeholders may come with the any of these approach Constraints, Assumptions (Risk, Requirements) & Dependencies explains the same and other alternatives that can be considered when dealing with Risks.
Constraints
Constraints are the boundaries within which the Design should be laid, it could be an Organization Policy or could be a Budget Restriction.
For Example when working towards the Design, Stakeholders specified that we have to make use of the existing hardware and existing Storage arrays, now this is definitely a Constraint because when preparing the Design the Design Architect has to work within these boundaries because he need to find out some ways where he can make use of the Existing Hardware and Existing Storage Arrays.
No comments:
Post a Comment