French

Why consider the "Goal & Data Driven Alignment" for your Digital Enterprise Architectures ?

Introduction to Goal and Data Driven Business and IT Alignment Process for an Agile Enterprise

Well-organized business process models produce the actual value of the enterprise and puts it into the hands of customers.

However, these process models do not always respond intelligently to market changes, as they do not "timely" consider digital disruptions that need to be captured to align strategies, tactics and capabilities with desired results.

As a consequence, underlying applications are unable to offer required digital services with the right service levels expected for your digital survival model.

 

Read more last updated 8.05.2017

 

Aligning IT with the Digital Business Model on the basis of your Digital Landscape

An Overview on the "Digital Business Model Alignment " process until Agile Software Development

This section provides a brief insight on the links that CxOs should check up from the business vision, goals and strategies impacted by the disrupting competitive landscape to align IT.

It illustrates, using Enterprise Architect (EA), how to bridge the resulting digital business model to run IT according to your changing business strategies, tactics and directives.

 

Read more last updated 8.05.2017

 

Enterprise Architectures : From TOGAF 9 and the Business Motivation Model (BMM) toward SOA applications

Bridging Goals, Capabilities and Business Processes Toward IT Level SOA Components

In the light of TOGAF's governance links to align SOA service components with changing strategies, the BMM - SOA bridge offers a Goal-Driven Architecture framework that helps companies to increase their competitiveness by synchronizing IT systems with evolutions of their goals and also capitalizing on their business capabilities.

In this context, the framework provides links to establish between your business vision, goals, strategies, tactics as well as business rules and processes according to BMM, then presents bridges from these business specifications toward components of the Service Oriented Architecture (SOA) in order to align IT system components to your goals and directives...

 

Read more last updated 25.07.2013

 

 

How to align SOA based Architectures to Changing Strategies ?

Steps for increasing business agility by aligning IT to changes on your "Business Architecture"

IT systems that are developed only using use-case driven and object-oriented methodologies do not provide companies with good levels of agility in face of changes. This is because such methodologies structure systems only focusing on actor/system interactions hiding business requirements.

The resulting systems are difficult to align to change, since IT components are not designed on the basis of "business capabilities" (DNA of the organizations) able to focus on goals and changing requirements that have to be propagated to impact system components in coherence.

Introduction : Why Use Cases are unable to align IT systems to changes ?

Step 1 - Describe strategies and capabilities on the basis of business goals

Step 2 - Model business processes that realize business capabilities

Step 3 - Discover use cases that invoke services

Step 4 - Draft the backbone of the "Goal-Driven SOA"

Step 5 and 6 - Describe use case and service behaviours that have to be plugged into the SOA backbone

Read more last updated 25.07.2013

 

 

 

Agile Enterprise Architectures : Six Patterns for Aligning IT with Changing Business Objectives

Patterns for succeeding with the Business / IT System Agility using TOGAF's ADM

Estimated to finish end of July 2017

Along the enterprise architecture transformation processes such as TOGAF's ADM, in order to prevent agility issues while adapting IT to changes, business and IT structures of the Enterprise Architecture Framework are to be rendered flexible as well as traceable in order to guarantee a coherent evolution in face of changes of the business requirements.

Two groups of patterns may help to achieve these objectives.

 

The first group patterns confer flexibility to business and IT service specifications. They ensure identification, traceability and executability of business services.

 

The second group patterns configure services to closing the gap between the business and application layers in order to confer to the overall system a coherent evolution in face of changes.

 

last updated 01.02.2015

 

TOGAF 9.1 and Archimate 2 for Aligning SOA with Business Strategies and Capabilities (from EAUG 2013 - Extended Version)

Goal-Driven and Capability-Based Development using Archimate 2.0 within TOGAF ADM phases

This animated presentation is about the Open Group's TOGAF 9.1 and ArchiMate 2.0 standards. It illustrates on a short case study how to use the ArchiMate ® 2.0 throughout TOGAF®  9’ ADM phases in order to align SOA backbone components with changing business strategies and capabilities using Sparx EA.

 

Read more last updated 30.12.2013

 

 

 

Animated : Increasing Business Agility by aligning IT with your Business Architecture

An overview on how to align IT with the Business Architecture Views using the OMG's BMM, MDA and SoaML standards

This animated version of the "Goal-Driven Service Oriented Architecture" process illustrates on a short case study useful steps that allow companies to capitalize on their business capabilities and react coherently to changes.

Thanks to its reusable goal-driven business capability components - easily adaptable to changing strategies, the "Goal-Driven SOA" process aims at allowing companies to control execution of their business processes and underlying SOA services then adapt them efficiently to targeted situations...

 

Read more last updated 12.01.2012

 

Agile Modeling to deal with Changing Requirements

Introduction to the Goal-Driven Agile and Smart Modeling to succeed with Agile Methods

Since a few years, companies try to customize Agile Methods ( Scrum, XP,...) in order to enhance delivery of their software products on time and budget. One of the serious obstacles they meet using such methods is due to informal and untraceable requirement gathering process that causes extra costs when dealing with changes !

Indeed, requirement gathering on the basis of user stories (or use case scenarios) is not sufficient alone to ensure coherent impact analysis in face of changes. This animated short case study presentation illustrates how requirements can be efficiently gathered, structured and assigned to system functions till the software architecture level components in order to better deal with changes.

Read more last updated 16.01.2015

 

 

 

Google search
WWW www.goobiz.com