SOMF™ defines the term “service” as a holistic entity that may encapsulate business requirements and, from a technological perspective, is identified with a software component. The value of a service resides in addressing either business or technology needs. The focus in this paper is on the business side, specifically mapping service functionality expressed in SOMF™ to business process constructs modeled using BPMN™ which is the current industry standard for modeling enterprise business processes. The document demonstrates the crafting of a modeling environment in which both business processes and service definitions are captured and interrelated.
This document presents an overview of the modeling notation introduced by Michael Bell in his seminal book Service-Oriented Modeling – Service Analysis, Design and Architecture. This notation is available in the base version of the Enterprise Architect modeling tool from Sparx Systems. SOMF™ provides a formal method of defining services at different levels of abstraction, along with a set of disciplines to guide practicing modelers. This overview does not cover the process related aspects of the book, such as the extensive guidelines for service discovery. Instead it focuses on the modeling facets, including meta-model concepts and notation, using sample diagrams for illustration.
This tutorial is part of the MDA® white paper series. It serves as a practical guide for using Enterprise Architect (EA) to implement the Model Driven Architecture® approach. The tutorial first takes an under-the-covers look at the tool’s model driven development features, then it uses a concrete example to take you through the transformation process step by step.
If you are evaluating MDA® tools, this paper is for you. As part of a series of white papers addressing the pragmatic aspects of MDA®, this is a practical guide for organizations evaluating tools for their model driven environment. Specifically, it measures the model driven development features of the Enterprise Architect (EA) tool to MDA® concepts. Find out what specific criteria you can use in modeling tool selection and how you can sort through the hype and promises of tool vendors.
A foundational and practical guide for software architects pursuing model driven practices.
This white paper is a first in a series intended to provide a foundational and practical guide for software architects wanting to work within a model driven environment. It is intended to help both architect and manager navigate through the concepts of Model Driven Architecture® (MDA®) in order to understand its fundamental departure from traditional software development.
True value is ‘ready’ process data reported comprehensively and in perspective to primary stakeholders!
Business process models can be very complex, spanning multiple levels of definition, represented by many inter-related diagrams. A key challenge that this client faced was the ability to produce a role-focused process report, meaning a report of all of the process steps that a role in the modeled organization is responsible for. Enterprise Architect’s built-in RTF templates and custom report generation capabilities are geared towards reporting on the structural properties of model elements. This particular client’s situation required the ability to traverse relationships at the model element and at the diagram levels.
This case study presents the solution that Cephas developed for this client to enable them to traverse and report on any number of loosely associated business process models. The models use a combination of EA Analysis and UML® Sequence diagrams. The purpose is to collect information about a given process role, and to structure the resulting data in a Word document format defined by the client.
Freely download and use any of the following white papers which cover a variety of topics including case studies, Model Driven Architecture (MDA), Service Oriented Architecture (SOA), Business Process Modeling (BPM), and other software development and systems engineering related subjects.
Find out how you can use modeling to specify software applications and systems architectures prior to committing to construction, and raise the level of abstraction when reasoning about and designing systems. Explore uncommon and standard concerns for methodology strategies and technology adoption considerations.