5. Define Design Option Flashcards
Purpose
To define the solution approach,
Identify opportunities to improve the biz,
Allocate reqs across solution component
Represent design options that achieve the desired future state
Description
When design a solution maybe one or more design options identified
Design option exist at a lower level than the strategy, tactical rather than strategy
Tactical trade-offs may need to be made among design alternatives
Inputs
Change strategy
Reqs(validated, prioritized)
Reqs architecture: full set of reqs and their relationship is important for defining design option that can address the holistic set of reqs
Elements 1
- Define solution approaches
- Create: solution components are assembled, constructed, or developed by expert as a direct response to a set of reqs. Includes modifying an existing solution. The r&d option enough detail to make a decision which solution to construct
- Purchase: select from a set of offerings that fulfill the reqs. The r&d option enough detail to make a recommendation.
Combination of both
Elements 2
- Identify improvement opportunities
- Increase efficiencies: automate or simply the work people perform by re-engineering or sharing process, changing responsibility, or outsourcing
- Improve access to information: provide greater amounts of infor to staff, thereby reducing need for specialists
- Identify additional capabilities: highlight capabilities that have the potential to provide future value and can be support by the solution
Elements 3
- Reqs allocation
Is the process of assigning reqs to solution component and releases to best achieve the objectives
Reqs may be allocated between org unit, job function, solution component or release of solution
Begin when a solution approach has been determined, continues until all valid reqs are allocated. Allocation typically continues through design and implementation of the solution
Elements 4
- Describe design options
A design option consists many design components, each describe by a design element
Design element may describe:
Biz policies and biz rule
Biz process to be perform and managed
People operate and maintain the solution
Operational biz decisions to be made
Software application
Org structure, interaction in org and cust, supplier
Guidelines and tools
Existing solution
Future state description
Reqs(traced)
Solution scope
Techniques
Benchmarking and market analysis
Brainstorming
Document analysis
Interviews
Lesson learned
Mind mapping
Root cause analysis
Survey
Vendor assessment
Workshops
Stakeholders
Domain sme: provide input, feedback to solution alternative, potential benefit of solution
Implementation sme: provide input, feedback to constraints of a solution and cost
Operational support
Project manager: plan and manage
Supplier: provide info, particular of design option
Output
Design options