Objectives¶
The primary reasons for creating a Use Case Tree are:
-
Interoperability Achieved
Enable interoperability across the enterprise at high levels of maturity.
-
Business Composability Improved
Making the enterprise adaptive through modular knowledge and reusable capabilities
-
Requirements Captured
Know exactly what the business---the customer or product owner---really needs, short-, mid- and long-term.
-
Knowledge Captured
Enabling a whole new league of use cases.
-
Gaps Bridged
Align business expectations with technology delivery.
-
Expectations Managed
Create an agreed and realistic strategic roadmap aligned to business strategy.
-
Did not boil the ocean
Provide focus, clarity, deliver business value fast, do the right things at the right time. Save money.
-
Disruption Avoided
Make changes gradually with clear interdependencies to avoid disruption across use cases.
-
Quality Increased
Enforce 100% test coverage based on real business scenarios and requirements.
-
Aligned with Strategy
Align strategy of business capability improvement and execution.
-
Delivered
Deliver strategic use cases that cannot realistically be done with other technologies.
-
Modularity Managed
Build with modular, reusable components instead of monolithic systems.
-
Reuse Enabled
Building the foundation for composable, scalable enterprise knowledge