An Architecture of Business concept defines and utilises a connotation of business capability to deliver, to do something in the continuously changing market, i.e., tomorrow and then after. The architecture of a successful corporation hooks into the future because current knowledge and skills can become obsolete by the EOD. The article defines the Capability benefits via business functionality and information; just data without business meaning is useless.
Tag Archives: architecture
Architecture of Business and IT Enterprise Architecture: an architecture from the Business perspectives
While an Architecture of business organisation includes an Intrinsic Architecture and a Practice of Architecture, the Enterprise and even Business Archtiectures, defined by TOG, are predominantly a practice or implementation of an undefined architecture at the enterprise (rather than an IT) level. From the IT viewpoint, the enterprise is constituted by the corporate-wide technology; from the corporate-wide business viewpoint, technology and its architectural practice (EA) are just types of resources Business Capabilities may utilise to reach the strategic objectives of the business.
How BUSINESS CAPABILITY may be built
Describes a process of bulding Business Capabilities for the Architecture of Business organisation. The Business Capabilities are abilities of the business to deliver a certain result by a given time in a defined execution context. IT and EA are just resources for this delivery.
Putting value delivery chains at the heart of an organic Target Operating Model
Value delivery chains are quite simply the steps that need to be done by an organisation to deliver its intended proposition to each beneficiary group. Mapping the value delivery chain for any organisation – existing or envisioned, for- or not-for-profit, government or private – justifies the Target Operating Models. The latter are delivered via Business Capabilities in the Architecture of Business concept.
Minefield of IT’s Capability Mapping Method
One of the major problems that separate corporate business from corporate technology is not only in the functions they have and represent in the corporate structure but also in the languages these two realms use. Mimicking the term names leads rather to misinformation because the semantics of similarly sounding terms may be basically different.
Steps of Transition to an Organic Business
The first time published on MAY 27 – JUNE 8, 2018 Understanding the Subject: Part 1 Introduction In our previous articles “The Major Principles of the Organic Business Design” and “Results of Applying Principles of Organic Business Design” we discussed how an Organic Business organisation looks like from inside. This article aims to explain how to …
Continue reading “Steps of Transition to an Organic Business”
#Sib #Pattern for #Microservice #Fault #Tolerance
Fault tolerance requirement was known for a long time before Microservices were defined. This requirement has surfaced again because when working with relatively small applications or components like Microservices, it is much easier to observe fault tolerance and it replicates at a higher scale than when working with monolith applications. There are no any special …
Continue reading “#Sib #Pattern for #Microservice #Fault #Tolerance”
How TO: #Microservices and #Eventholder – what is what for
For people who are in the IT industry for years, the comparison of SOA to EDA and vice versa is not news. For the new generation, their fundamental difference may be not that obvious, especially, when the architecture implementation relates to Microservices. The basis of SOA is a client-server/service model. Yes, it is the old …
Continue reading “How TO: #Microservices and #Eventholder – what is what for”
⌗ARCHIMATE TRANSFORMES ITSELF INTO LOREM IPSUM
For the last 2.5 decades IT architects used Unified Modelling Language (UML) notation. This graphical notation and the concept supporting it was created by Grady Booch, Ivar Jacobson, and James Rumbaugh while working at Rational software. In 1997, the Object Management Group (TOG) adopted UML as a standard for its members,. Later on, UML became a …
Continue reading “⌗ARCHIMATE TRANSFORMES ITSELF INTO LOREM IPSUM”
DOES #ENTERPRISE #ARCHITECTURE NEED #PROTECTION IN A #DIGITAL WORLD?
Not long time ago, hashtag#McKinsey & Company decided to advise Enterprise Architects on how they have to change themselves to survive in the digital revolution. Well, it might be a noble mission if such a “business case” was strong. McKensey – the trusted advisor to the world’s leading businesses, governments, and institutions – had identified …
Continue reading “DOES #ENTERPRISE #ARCHITECTURE NEED #PROTECTION IN A #DIGITAL WORLD?”
A short-term tactical solution may be good only if you have the long-term solution observed/understood already
During a recession, every company faces a dilemma – where to put its management attention and funds – in the short-term surviving projects/products or the long-term ones as well. IMHO, if you are concerned about survival only, you will lose immediately after the recession ends even if you survive it. My advice is to put …
Optimising a Target Operating Model through an Architecture of Business
by Michael Poulin & Kirill Derevenski Abstract This paper describes a comprehensive – and revolutionary – approach to effective organisational adaptation to change in a dynamic market environment. Disruption is all around and even the most established players are no longer guaranteed relevance. Business and operating models are in constant change and in order to …
Continue reading “Optimising a Target Operating Model through an Architecture of Business”
Architecture of Business: Architectural Governance
Part 1. Architectural Governance: What and Why A concept of an Architecture of Business organisation (AoB) includes four fundamental artefacts, one of which is an Architectural Governance (AG). The Architecture of Business’s AG is defined as a set of principles, policies and procedures or activities, by which The AG is designed in compliance with existing …
Continue reading “Architecture of Business: Architectural Governance”
Extending Zachman Framework™ for new Market Realities
Architecture of Business/Enterprise requires extension of Zachman Framework/Ontology to add contextual and ‘by whom’ dimensions
Ontology-based View on Architecture of Business Organisation
Ontology of the Architecture of Business/Enterprise with description (Organic Organisation Model supplement)
Recent ARTICLES published in #LinkedIn
Are Clouds now heading to a Thunderstorm? by Michael Poulin, 2022. Does #Enterprise #Architecture need #protection in a #digital world? by Michael Poulin, 2022. If experts still define EA differently, what is EA actually? by Michael Poulin, 2022. This is the article #100; 12,184 Impressions. Shared Services in a Nutshell by Michael Poulin, 2022. Risks of …
Split and Join of #Functional and #Informational #Microservices
Article defines Functional Microservices using gRPC interface versus Informational Microservices accessible via RESTful interface. The Functional Microservices are validated against distortionless criteria. The code example of Interface definition for Functional Microservice is provided together with options allowing passing data together with function invocation.
TOG Open Business Architecture standard is, actually, about IT transformation
Business Architecture”(BA) is not about an architecture of business organisation but about a very specific view that IT departments can take on the business of their own companies, bottom-up. The name of the standard includes “Open” to point to the standard creator – “The Open Group” that locked it to the trusted close Business Architecture Guild for mainly. As usual, this “open business” standard is for IT, not for the business of an enterprise.
HOW to ARCHITECT for DEVELOPERS 