- Associate a stakeholder with the information that needs to be collected.
Before a design can begin the correct information needs to be collected, this information needs to be collected and associated with particular stakeholders.
GATHER (information) – DEFINE (requirements) – IDENTIFY(constraints, risks and assumptions)
Stakeholder = A person with a big interest in the project
SME = Expert in a given area.
Either an SME and or Stakeholder should be assigned to the below categories so they can provide the right information required for the design:
- Network administrators
- Storage administrators
- Server hardware administrators
- Operating system administrators
- Application administrators
- Security Officer
- HR representatives
- executives (CEO, CTO, CIO,…)
- Capacity Management
- Utilize customer inventory and assessment data from a current environment to define a baseline state.
What does the environment looks like now? what does the client already have? This is what it is asking here.
- Perform current state analysis with tools like VMware Capacity Planner
- Review the current environment documentation
- Collected information from stakeholders and SMEs
- Analyze customer interview data to explicitly define customer objectives for a conceptual design.
From the interviews you need to determine:
- Goals (why are we doing this and what is the time frame)
- Scope (Whats included, whats not included)
- Business (cost savings, work force reductions)
- Technical ( Uptime, consolidation, DR)
- Legislative ( compliance, security)
- Assumptions ( sufficient cooling for hardware in datacenter)
- Constraints (Must be done – re-use of existing servers or must be HP branded)
- Risks ( could prevent the project from happening like budget not yet approved or a dependency on another project)
- Identify the need for and apply requirements tracking.
All requirements must be documented so none are missed when doing a design, Its a good idea to use project management software but excel would do and track if a requirements has been met by the design. and keep notes etc.
- Given results of a requirements gathering survey, identify requirements for a conceptual design.
Once you have gathered all the information from all the sources, Its now time to define the requirements as stated by the client. Once the requirements are defined you can now analyse them to determine risks and constraints. This is basically inline wit the above heading with customer objectives.
- Categorize requirements by infrastructure qualities to prepare for logical design requirements.
What is a logical design? its a:
- High Level design without a great level of detail
- Focuses on satisfying the design factors (requirements, risks, assumptions and constraints)
- Doesn’t explain how it satisfies design factors
- Doesn’t include specific solutions or products
- can be graphical and or textual.
This objective is asking you to sort out your requirements by infrastructure like storage compute, networks, Guest OSes etc ready for the Logical Design