Application Strategy is the
architecture work
product produced during the
business architecting
activity that documents the
customer organization’s strategy for producing future
applications.
The typical objectives of the application strategy are to
document the customer organization’s business in terms of
its:
The typical benefits of the application strategy are:
- It enables the customer organization to plan and
prioritize its future applications.
The typical contents of the application strategy are:
- Overview:
- For each Application X:
- Description
- Goals
- Application Success Criteria
- Planned Benefits (value proposition)
- Stakeholders
- Cost/Benefit Analysis (by reference)
- Priority
- Conclusion
- Appendices:
- Major Issues
- TBDs
- Assumptions
The typical stakeholders of the application strategy
are:
- Producers:
- Evaluators:
- Approvers:
- Maintainer:
Architecture Team
- Users:
- Business engineering
architecture team, which uses the application
strategy during the rearchitecting of the customer
organization's business.
- Application development
requirements team, which uses the application
strategy to develop the application vision
statement.
Preconditions
The application strategy typically can be started if the
following preconditions hold:
The typical inputs to the application strategy include:
- Work Products:
- Stakeholders:
- This is a living document that is developed incrementally
and iteratively in parallel with other documents.
The application strategy is typically constrained by the
following conventions:
-
Work Flow
-
Content and Format Standard
-
MS Word Template
-
XML Template
-
Inspection Checklist
-
Example Application Business
Case