Transition Support

Defining the start, the starting point, boundaries and end condition of the transition in terms of architecture components within its domains and aspects: models and PROSA. When applicable develop concepts that enable the delivery to become more valuable, easy, faster and/or cheaper against better quality results. Deliver the As Is Design and Architecture situation and explain how to progress into the To Be situation. If applicable in several stable platforms including scenarios when and how to chose between the different solutions.

Problems and Solutions

The contemporary approach is challenged with incomplete architecture models, principles, design and development documentation. This leads to tiresome gathering of information to define the Impact and Business Case on the one side, and the Project Start Architecture and Project Initiation Document on the other side. Almost every time a project starts, a new collection of components must be gathered together with high risks of being incomplete and delivering wrong and too optimistic estimates for the transition processes.

Within the Enterprise Architects approach either the necessary information can be collected from the Architecture and Design Continua or the newly defined components can be stored in these Continua for the next transition.

Tools to support Transition

To support the Transition Enterprise Architects offers the following solutions and tools:

AFR/Function Requirement	Defining the PROSA requirements for each Knowledge Function of the solution
APR/PROSA Modeling	Defining the details of Principles, Requirements, design Objectives, Standards & Agreements for the solution
AAM/PSA Generation	Generating the PSA based on the modeling the Product Service Delivery and the Information Service Delivery
APP/PID Generation	Generating the PID based on the PSA
ATS/Transition Support	Supporting the Transition during different phases

The Transition Support tools help architects in aligning the conceptual components with the logical components and the logical components with the physical components. Also, patterns within the Service delivery can be found.

ATS/Product Service Delivery	Support pattern recognition and design of the Product Service Delivery components Actor,LifeEvent, Business Service, Contracts, Business Processes, Knowledge Functions, etc.)
ATS/Information Service Delivery	Support (pattern recognition and) design of the Information Service Delivery components (Knowledge Functions, Application Functions, Technical Services, etc.)
ATS/Interaction Support	Supporting modeling EPICs, User Stories, Interaction Design and Presentation Services – Also see ISE
ATS/Data Support	Supporting Data Management and Information & Data Service Generation – Also see AOM and ISE
ATS/RuleSet Support	Supporting Business Rule Management – Also see ARM
ATS/Knowledge Function Support	Supporting Knowledge Function Management – Also see AFM
ATS/Process and Value Creation	Supporting Value Creation for Process Models
ATS/Competence Support	Supporting Competences for Actor/Role combinations with Process Activities

Advantages of the Enterprise Architects approach

Defining the PROSA requirements for the Knowledge Functions
Defining the PROSA requirements for the complete solution
Generating the PSA
Generating the architectural and design parts of the PID
Supporting the Transition Project or Sprints by
- Support pattern recognition and design of the Product Service Delivery
- Support pattern recognition and design of the Information Service Delivery
- Support of EPIC design, User Stories, Interaction Design and Presentation Service Generation
- Support of Data Management and Service Generation
- Support of Business RuleSet Management
- Support of Knowledge Function Management
- Support of Process Modeling, Value Creation and Competence Management
- The SAFe™ Core Values are safeguarded and improved as follows
  - Alignment
  - Built-in Quality
  - Transparency
  - Program Execution