VMware End-User Computing: Design — Lesson 1: Business drivers, user personas, workload characteristics, application portfolios, endpoint diversity, connectivity patterns, service levels, constraints, and design assumptions

Learning Objectives

• Break down the prerequisites, components, roles, and decision points involved in Business drivers, user personas, workload characteristics, application portfolios, endpoint diversity, connectivity patterns, service levels, constraints, and design assumptions.
• Complete a controlled activity for Business drivers, user personas, workload characteristics, application portfolios, endpoint diversity, connectivity patterns, service levels, constraints, and design assumptions and capture persona-to-service requirements matrix and assumption register.
• Challenge the result with a design optimized for office users failing remote workers with intermittent connectivity, then justify the corrective action.

Detailed Topics

• Business drivers
• User personas
• Workload characteristics
• Application portfolios
• Endpoint diversity
• Connectivity patterns
• Service levels
• Constraints
• And design assumptions
• Decision ownership, prerequisites, and acceptance evidence for Business drivers, user personas, workload characteristics, application portfolios, endpoint diversity, connectivity patterns, service levels, constraints, and design assumptions
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

The instructor builds a representative scenario for Business drivers, user personas, workload characteristics, application portfolios, endpoint diversity, connectivity patterns, service levels, constraints, and design assumptions, narrating each decision and showing how it contributes to an end-user computing design that aligns personas, application delivery, desktop architecture, security, availability, capacity, and operational support with measurable user experience. The demonstration records persona-to-service requirements matrix and assumption register so learners can compare design intent with observable behavior.

Hands-On Exercise

Build or execute Business drivers, user personas, workload characteristics, application portfolios, endpoint diversity, connectivity patterns, service levels, constraints, and design assumptions for a defined scenario. Introduce the condition “a design optimized for office users failing remote workers with intermittent connectivity,” inspect the evidence, correct the cause without discarding the audit trail, and document the accepted state in persona-to-service requirements matrix and assumption register.

1. Record the starting state, assumptions, identities, topology, and expected outcome.
2. Execute the planned workflow and collect evidence at each material checkpoint.
3. Test one valid path, one boundary condition, and the stated failure scenario.
4. Document the correction, retest result, rollback option, and follow-up owner.

Scenario Analysis

• Clarify the service trigger, affected components and roles, prerequisites, and acceptable result for Business drivers, user personas, workload characteristics, application portfolios, endpoint diversity, connectivity patterns, service levels, constraints, and design assumptions.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how persona-to-service requirements matrix and assumption register should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

When Business drivers, user personas, workload characteristics, application portfolios, endpoint diversity, connectivity patterns, service levels, constraints, and design assumptions produces an unexpected result, reproduce the issue with the same scope, identity, workload, and time context. Inspect persona-to-service requirements matrix and assumption register, test whether “a design optimized for office users failing remote workers with intermittent connectivity” explains the evidence, apply the smallest reversible correction, and retest an unaffected path for regression.

Validation Checklist

• The requirement for Business drivers, user personas, workload characteristics, application portfolios, endpoint diversity, connectivity patterns, service levels, constraints, and design assumptions is linked to an owner and observable acceptance condition.
• Persona-to-service requirements matrix and assumption register contains enough detail for another practitioner to repeat the check.
• Normal operation, one boundary condition, and the identified failure path have been tested.
• Access, security, downstream impact, rollback, monitoring, and support ownership are recorded.

Lesson Outcome

Learners can apply Business drivers, user personas, workload characteristics, application portfolios, endpoint diversity, connectivity patterns, service levels, constraints, and design assumptions, explain the decisions made, and defend the result with persona-to-service requirements matrix and assumption register.