Description
- Basics of Architecture Frameworks ( Zachmann / Togaf ) and how to Apply them.
> How to apply these to solving an Enterprise problem and how to scope different architecture concerns.
> How to create a reference Architecture for your organization and benefit from the same.
> How to create an architectural model for your organization
> Create different architecture view points for your stakeholders.
> Understand the ADM and its practical application for as is and legacy application.
> Going from Strategic – Segment-Capability architecture right from vision to execution in Business , Data , Application and Technical architectures.
> Visual representation of your architecture ( modelling and No UML)
> Create an Architecture Content Framework and how to use one for the Organization
> Why business is strategic to EA and how to enforce tight coupling between EA and Business in everything architecture ( data / application / technical architecture )
> How to drive EA to make better decisions and use it for Service Oriented Architecture design / execution and roll out.
> Why TOGAF is agile to the Enterprise and how we can tap its full potential for
delivering value in the turns.
- How to dive deep from Enterprise Architecture to Solution Architecture.
> Vision to reality . From Concept to Cash and how do you plan your solutioning around this and state its importance to the customer. Agile to solution architecture.
> Prioritization of requirements . What should be done first and how can you crowd source solution architecture among your team and showcase value.
> How to use frameworks for NFRs in your project and scope various NFR requirements to service them to satisfaction and cover all of them. How to use
proven frameworks here to get everything covered.
> Architecture Trade Off analysis and how you can do one and arrive at the best architectural approach.
> Bridging the Business technology divide and driving cohesion.
> Explain and design a problem statement ( case study and ) create a RFP/RFC for your proposal and illustrate what is good or bad in the same.
> How to provide team velocity and estimates for work in an agile and iterative fashion. Case study exercise to drive home the point here.
