Technology Strategy
Definitions
- Technology Strategy
- the architecture
document
produced during business engineering that documents the
customer organization’s
strategy for using appropriate technologies on its current and future
systems and
applications
As illustrated in the preceding figure, Technology Strategy is part of the following inheritance hierarchy:
- Type: Concrete
- Superclass: Document
- Subclasses:
The typical responsibilities of the Technology Strategy are to:
- Document the customer organization’s strategy for using appropriate technologies
on its current and future systems and applications.
- Enable the customer organization to:
- Have a consistent approach to new technologies.
- Maximize its benefits from using these technologies.
The typical contents of the Technology Strategy are:
- Overview:
- For each Technology X:
- Description
- Benefits (value proposition)
- Risks
- Trends
- Vendors
- Recommendations
- Conclusion
- Appendices:
- Major Issues
- TBDs
- Assumptions
The typical stakeholders of the Technology Strategy are:
- Producers:
- Evaluators:
- Approvers:
- Maintainers:
- Users:
- Business engineering architecture team,
which uses the technology strategy during the rearchitecting of the customer organization’s business.
The Technology Strategy typically can be started if the following preconditions hold:
The typical inputs to the Technology Strategy include:
- Work Products:
- Stakeholders:
- This is a living document that is developed incrementally and iteratively in parallel with other documents.
Technology Strategy is typically constrained by the following conventions:
- Work Flow
- Content and Format Standard
- MS Word Template
- XML Template
- Inspection Checklist
- Example Technology Strategy