TOGAF is the most widely adopted Enterprise architecture framework. It contains detailed methodology for desing and management of the architecture (Architecture Development Method – ADM) and a set of supporting tools and techniques. The framework together with the ArchiMate languege is maintaind by vendor and technology neutral consortium – The Open Group.

TOGAF contains best practise from all The Open Group members and it is continuously being validated and updated. The methodology covers all the architecture lifecycle and is detailed enough to be used used in practise in multiple environments.

TOGAF is intended to be used altogether with other frameworks and methodologies and may be integrated with ITIL, COBIT, PRINCE2 and other methodologies and frameworks. Supporting materials contain document templates, additional guidelines etc.

Implementation of TOGAF requires full understanding of the framework. Our training courses wll provide you with sufficient knowledge for successfull implementation in your organization.

ArchiMate is a comprehensive, open and independent Enterprise architecture modelling language managed by The Open Group. Opposite to other languages like UML and BPMN it focuses on basic architecture building blocks and intentionally does not focus to detail description of components.
With ArchiMate business, application, data, technology, strategy, motivation and implementaion may be described with a very limited and therefore intuitive concepts.

The language is simple, consisting of only few basic concepts but it is strict in creating relationships and viewpoints.
ArchiMate is aligned with TOGAF and supports service orientation.

TOGAF is the most widely adopted Enterprise architecture framework. It contains detailed methodology for desing and management of the architecture (Architecture Development Method – ADM) and a set of supporting tools and techniques. The framework together with the ArchiMate languege is maintaind by vendor and technology neutral consortium – The Open Group.

TOGAF contains best practise from all The Open Group members and it is continuously being validated and updated. The methodology covers all the architecture lifecycle and is detailed enough to be used used in practise in multiple environments.

ArchiMate is a comprehensive, open and independent Enterprise architecture modelling language managed by The Open Group. Opposite to other languages like UML and BPMN it focuses on basic architecture building blocks and intentionally does not focus to detail description of components.
With ArchiMate business, application, data, technology, strategy, motivation and implementaion may be described with a very limited and therefore intuitive concepts.

Combining TOGAF and ArchiMate will move you to higher levels of maturity of your Enterprise Architecture

Enterprise architecture (EA) is a necessity for enterprises of almost all sizes. They are using it for efficient management of the whole enterprise and its assets. It can help you to be prepared for future changes, react quickly as well to optimize its current processes and technology.

Within EA you should focus not only to business and IT aspects but also to financials, legal and other aspects that your enterprise is facing daily.

BIAN is a widely adopted banking standard that focus on banking services (and capabilities). They are generalized and organized within BIAN service landscape which can serve as a reference architecture for almost all banks. They can use the BIAN to get an overview of the banking business and to make informed and strategic decisions.

Besides the service landscape BIAN provides also several how-to guides, metamodel description, supporting definitions and detail description of services and business scenarios.

Currently the BIAN landscape consists of 7 Business Areas, 36 Business Domains, 280 Service Domains, 1960 candidate Service Operation and 178 Business Scenarios.

Agile approach to development is very popular by many companies of all sizes. Following this approach architecture may be perceived as a discipline that slows down the whole environment and is not agile at all. Is it only perception? Is the problem in architecture or its frameworks? Or architects? Do we design architecture in agile way or for agile organizations? Do the popular architecture frameworks support agile approach?

Our Agile architecture training course will help you to find the answers and much more. We will teach you how to seamlessly interconnect the agile development with agile architecture design and gain benefits from this approach. We will extend the basic principles from agile manifesto with architecture principles. We will show you how to use SAFE (Scaled Architecture Framework) that is extending the SCRUM methodology.

We will focus also on agile aspects of architecture frameworks TOGAF and DYA, explain you what is agile organization and how Service oriented architecture (SOA) and cloud computing may evolve your architecture to agile discipline.

Various organizations are facing the complexity for their application portfolios which contain hundreds or thousands of applications. Quick and cheap solutions to reduce the complexity have been already implemented and further rationalizations of such portfolia require more sophisticated approach. Currently, there are several methodologies for managing the application portfolio, they use the same basis and differ only in detailed procedures.

In order to manage the portfolio of applications, it is necessary to analyze it first and then plan for the rationalization. It should rather focus on reducing the overall complexity than reducing the number of applications only.

Well-managed application portfolio can save up to significant portion of entire organization budget.

Service-oriented architecture understands the organization and its environment as a set of interconnected services. Such approach enables a division of complex environments into a relatively isolated parts that are more easy to manage, develop and automate.

Most SOA implementations wrongly focus only on application and technology topics – a look that rarely fulfils the potential of SOA approach. Correct understanding of SOA requires both business and IT perspective to be taken and focus on the service as we know them from outside the organizations.

Integration is a topic that is closely related to SOA. Proper connection of services, their use in business processes, integration to other services and automation. This can be performed in various ways, which might complement each other.