Developing future state involves documenting the expected state of the system/ solution and is useful for:
Supporting the ROI + Go/No Go decision (Stop Loss)
Supporting Architects with more information
Helping the business units understand the technical aspects
Ensuring that technology and the stakeholders have the same vision of the future state
Steps
Review current state documents
Get a comprehensive understanding of the current state by reviewing the current state diagram/process flow/document.
Review business requirements
Using the current state of the system/solution as a baseline, review the business requirements thoroughly and identify the
areas needing improvement or modification.
Document the future state
Based on the outcome of the business requirements review step above, document the future state. Areas/systems needing
improvements or modification must be clearly identified.
Alternatives
To document the future state in a descriptive manner
Version and Release
Unified Life Cycle (ULC): 5.1, November 3, 2014
Phase Gates: 1.1, May 27, 2014
Process Engineering Process (PEP): 1.1, May 27, 2014