Skip to content

Latest commit

 

History

History
101 lines (94 loc) · 6.41 KB

phase-5-E-opportunities-and-solutions.md

File metadata and controls

101 lines (94 loc) · 6.41 KB
Raw

Opportunities and Solutions

image

Purpose (Objectives)

  1. generate the Initial Architecture Roadmap
  2. Identify if Transition Architectures are required
    • Now maybe you can get from where you are to where you want to go with a single project, with some single deployment
    • Or maybe you need what are called transition architectures that will get you partway there and then you can do one or more transition architectures before finally getting to the architecture.
  3. Define Solution Building Blocks (SBBs)
    • reusable components
    • identify things in our architecture that can be generalized and reused in other places?

Inputs

  1. External Reference Materials
  2. Product Information
  3. Request for Architecture Work (Preliminary Phase)
  4. Organization Capability Assessment (from Phase A)
  5. Communication Plan (from Phase A)
  6. Planning Methodologies
  7. Organization Model for Enterprise Architecture (from Preliminary Phase)
  8. Governance models and frameworks
    • governance models has to do with corporate business planning, your frameworks for these types of things
    • any kind of project management framework
    • are you following the Agile methodology or following some other type of known methods?
  9. Tailored Architecture Framework (Preliminary Phase)
  10. Approved Statement of Architecture Work (from Phase A)
  11. Architecture Vision (from Phase A)
  12. Architecture Repository (from Preliminary Phase)
  13. Draft Architecture Documents and draft Requirements (BDAT)
  14. Change requests for existing business programs and projects
    • ormal requests for modifications or enhancements in current business programs or projects.
    • These could span from minor adjustments to major upgrades or feature implementations.
    • Such change requests are typically fueled by evolving business needs, emerging technologies, user feedback or a change in organizational strategy.
    • The purpose is to ensure that the existing projects or programs continue to align with the organization's goals and continue to meet, or ideally exceed, user needs and expectations.
  15. Candidate Architecture Roadmap Components
    • Components you get analyzed your gaps

Steps

So we're no longer defining our business architectures or our architectures we are now planning.
Interesting thing, because at the end of this you really just coming up with a draft strategy, your your strategy and your plans and your roadmaps.

  • We really haven't put the teams together.
  • We really haven't introduced this plan into other people yet.
  • You're just doing the planning part before you get into bringing in other people.
  1. Determine key corporate change attributes
  2. Determine business constraints for implementation
    • So what are what is coming up that is going to constrain you?
    • "extremely busy holiday season, which is in the United States is November and December, therefore in October is a cut off for doing deployments."
    • And so understanding what your business constraints are that are around implementation
  3. Review and consolidate gap analysis for Phase B to D
    • review your gap analysis from phases B, C and D and you consolidate them.
  4. Review consolidated requirements across business functions
    • review your requirements that you've been coming together, consolidate them
  5. Consolidate and reconcile interoperability requirements
    • if you've got existing implementations, existing contracts, you've got what kind of coordination you need to do between departments.
  6. Refine and Validate Dependencies
    • Maybe there is projects that are underway that are going to be impacted.
    • So understanding various dependencies.
  7. Confirm readiness and risk for business transformation
    • So there is a business transformation readiness assessment that was conducted in Phase A,
    • and you have basically already identified what are the risks for your business in doing large changes
    • Now, maybe your business doesn't handle very large changes very well and things have to be done very slowly
    • So you go back to your business transformation for readiness assessment and look at your impact on your architecture roadmap and your implementation strategy.
  8. Formulate implementation and migration strategy
    • So you go back to your business transformation for readiness assessment
    • and look at your impact on your architecture roadmap and your implementation strategy.
    • If you have to purchase things, do you have to hire consultants?
    • You're going to have to kick off projects?
    • Who's going to do what?
    • What is achievable?
    • What is going to be a challenge?
  9. Indentify and group major work packages
    • put stuff into work packages
    • So let's say you've decided you've got to do transfer to transition architectures and you have to do these four things in the first phase, these three things in the second phase. And finally the last phase can do the rest.
    • This is also when you put your transition architectures together.
  10. Identify Transition Architectures
  • So documenting what is your architecture going to look like at the end of the first phase of implementation while you still have a lot of work to do?
  1. Create the architecture roadmap & implementation and migration plan
  • So you're consolidating your work packages, your transition architectures.
  • That becomes your draft architecture roadmap.
  • That's going to be the timeline of going from a baseline architecture to a target architecture.
  • And this is basically a draft document that you've come up with to say what is basically the migration phase.

Outputs

  1. Refined Phase A deliverables
  2. Draft Architecture Definition document
    • including baseline and target BDAT architectures, approved version
    • including transition architectures if needed
    • architecture views
  3. Draft Architecture Requirements Specification
    • including gap analysis
  4. Organization Capability assessments
  5. Architecture Roadmap
    • including work package portfolio
  6. Implementation and migration plan, draft version

Artifacts

Very few artifacts on this phase.
Now phase does combine into phase F (Migration Planning), which is the migration plan formally, and that's when you do start working with third parties, other people in your company and getting them to prepare to start projects.

Diagrams: Product context diagram, benefits diagram