BPMN diagrams are commonly treated as synonyms for process diagrams. This short article will present the last three types of BPMN diagrams (collaboration diagrams, choreography diagrams and conversation diagrams) and the possibilities for their common use.
TOGAF is largely about identifying and documenting architecture requirements... but what is an Architectural Requirement? Frequently we document requirements, not "architecture" requirements! In this blog I explain what we need to do to make requirements architectural.
In this article, we will firstly address how popular BPMN really is, by analyzing some of the existing studies. Secondly, we will define who uses the notation and thirdly, to what end.
Architects sometimes see the ADM as reactive, but EA should never be passive - it needs to respond to concerns, but add architectural thinking and then make a unique contribution to stakeholder needs. This blog explains some of the proactive aspects of ADM that are not so obvious.
BPMN 2.0 is the most comprehensive process modeling standard, with precisely defined notation and an underlying formal meta-model. This paper will present 10 facts, which are defined in the BPMN 2.0 specification, you probably didn’t know.
TOGAF describes three types of architecture role. Two of these types - Enterprise and Solution - are often used in the job title for architects, but it is rare to find someone called a Segment Architect. If you are confused about this missing role... read on, and all will be revealed.
This post presents 10 key BPMN elements, which should be learned prior to creating your first business process diagrams. These 10 key BPMN elements represent a sub-set of the descriptive class of BPMN 2.0 elements.
Sometimes people find it difficult to see the unique contribution of EA. So what is it that makes EA distinctive? Here are five things that the best enterprise architects do, and some tips from TOGAF on how you can follow their example.
With the release of BPMN 2.0.1 in 2013, the Business Process Model and Notation became an ISO/IEC 19510:2013 standard. This blog post explains why this is important.
TOGAF makes a big point of the need for good stakeholder management, devoting the whole of Chapter 24 to the subject, while Step 2 in Phase A: Architecture Vision describes the process to Identify Stakeholders, Concerns, and Business Requirements.