Skills and Abilities
- Differentiate between general concepts of a risk, requirement, constraint, and assumption
- Given a statement, determine whether it is a risk, requirement, a constraint, or an assumption
- Analyze impact of VMware best practices to identify risks, constraints, and assumptions
Differentiate between general concepts of a risk, requirement, constraint, and assumption
These are the main factors that we have to understand well and define for every design. Let’s cover these factors in a bit more detail.
Risks – Risks are potential issues that we might encounter during the scope of the project. In other words, it’s something that might impact deployment so it’s important that we identify the risks as quick as possible.
Requirements – Requirements are the reason why a project is started. A requirement is something that we absolutely must meet in order to have a successful deployment.
Constraints – Constraints typically limit our design. For example, we might be tied to a specific vendor and that vendor might not support a certain feature. Constraints also don’t have to be related to technology, constraints could be related to business as well
Assumptions – Assumptions are consideration that we make, however further testing or validating is still required. Typically an assumption will be influenced based on certain factors that we have not had the opportunity to verify.
Given a statement, determine whether it is a risk, requirement, a constraint, or an assumption
We’ve covered this section already, please see above… but I will also link other posts I’ve done that talks about this here.
Analyze impact of VMware best practices to identify risks, constraints, and assumptions
The title of this objective says a lot actually, the key phrase here being “Analyze Impact of VMware best practices“. We definitely have to consider the best practices, but remember, the best practices don’t always meet the business requirements so it’s not the only solution. For me, best practices are away of analyzing a product, but tweaking the design in order to meet the customers needs. Now, of course we need to make sure that whatever solution we propose, will be supported.
The vBrownbag has some great examples of design criteria which you can take look at here.