UML Operator Blog

 In our UML Operator Channel , we are publishing a series on Business Process Modeling Notation (BPMN) . As I move through Business Process Modeling content, I want to reiterate the purpose of some elements, their roles, and attributes relevant to each. BPMN is extended from the Unified Modeling Language (UML) and in Sparx EA, we can blend UML and BPMN to support more effective delivery. Another struggler that modelers have in "delivery", is the elicitation, development, and specification of "Requirements". We cannot solve a problem if we do not understand the problem, and problems are defined using different types of "Requirements". Reminder: BPMN (Business Process Model and Notation) is a standard for representing business processes in a graphical notation. It uses a set of elements to define the flow of activities and the relationships between them. In this article I will BPMN and differences with UML, various requirement types. Here's...

BPMN (Business Process Model and Notation) is a graphical representation language for specifying business processes in a visual and standardized manner. BPMN provides a set of graphical elements and symbols that allow users to create diagrams to represent various aspects of business processes, including their activities, flows, events, gateways, and artifacts. So why ask this question today? One answer may be, "How are we going to reference our Business Processes so that others understand them?". While BPMN was not released until around 2004, we in business, were drawing (modeling, diagraming) our business processes for decades before. However, during the computing boom of the 80's and internet boom of the 90's, business were not aligned on how to convey their business processes, methods, and procedures. While I was using Computer Aided Design (CAD) software to draw, or draft, my design visions, no one was really using computing capabilities to draw/draft their busine...

The purpose of this post is to set up a conversation around Business Process Modeling (BPM), specifically Business Process Modeling Notation (BPMN) and Business Process Execution Language (BPEL). As we develop content for the UML Operator Channel related to Model-Driven-Architecture (MDA) and delivering Systems and Software, BPM is critical to understand and defining Project Delivery. So let's start with some history and then move into some nuances. The Business Process Model and Notation (BPMN) specification was first released in the year 2004. BPMN is a graphical modeling language specifically designed for representing business processes and workflows in a standardized manner. The initial version, BPMN 1.0, was developed by the Business Process Management Initiative (BPMI) and released in 2004. It provided a comprehensive set of symbols, rules, and semantics for modeling business processes, allowing organizations to visually represent and communicate their processes effectively....

Over the past month, we have been working on a series on UML Operator YouTube Channel pertaining to Business Process Engineering (BPE) and Business Process Modeling (BPM), including BPMN and other approaches. I have been surprised by the enthusiasm around this subject and received a great deal of feedback. As time permits, we will keep publishing content relevant to BPM in 2024. The current content is part of two playlists: "Business Process Engineering" and "System Architecture Delivery". As we progress, in the UMLO Channel, we will focus on System Architecture Delivery while trying to keep our content in specific "interests" playlists. The Business Process Engineering series (playlist) includes: Introduction to BPMN Part 1 (e37) - This is the start of a new multi-part series on BPM modeling. In this session we will introduce Business Process Modeling Notation (BPMN) as an alternative to just Activity Diagrams. BPMN, released in 2004, is a graphical mod...

We are starting a series on Business Process Modeling Notation (BPMN) and Business Process Execution Language (BPEL) as it meshes with Unified Modeling Language (UML). You can follow this series on the UML Operator Channel . My focus is on Model-Driven-Architecture (MDA) which I have been practicing for over 30 years.  The Evolution With Artificial Intelligence (AI) getting more attention as a subject these days, our world is in for a bigger change since the DOTCOM boom. As Personal Computing became a hot subject in the 70s, we heard people in fear of losing their jobs, but history proved them wrong. The same applies to AI today. Computers made us smarter, mobile devices keep us aware 24x7, and AI will augment our lives. Computer Aided Software Engineering (CASE), Computer Aided Design (CAD), and MDA will become an import launchpads for success in everything we do. The Revolution We are already seeing disruptive changes and a fundamental shift. For some, this transformation is NOT...