Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Business Models
Requirements |
Use Cases |
BPMN |
Decision Models
|
Mind Mapping |
Create, Model and manage requirements directly in line with your other project tasks. Trace from high level requirements to deployment artifacts.
|
Describe the functional requirements of the system the the manner in which outside things (Actors) interact at the system boundary and the response of the system. |
Capture the behavior and the information flows within an organization or system |
Define decisions with models and tables using the decision trees or decision tables |
Capture high level ideas and concepts and trace them in with down stream actions. |
|
|
|||
Business Rules
|
BPEL |
SPEM |
ArchiMate
|
Eriksson-Penker Extensions
|
Identify and store business rules within your model while integrating them in with downstream processes. |
Generate Business Process Execution Language (BPEL) from processes described using BPMN. |
A process engineering meta-model as well as conceptual framework, which provides the necessary concepts for modeling, documenting, presenting, managing, interchanging, and enacting development methods and processes |
Define your business capability with ArchiMate, an open-standard enterprise architecture language |
A framework for UML business processing model extensions |
|
|
|
|
|
A Business Process model describes both the behavior and the information flows within an organization or system. As a model of business activity, it captures the significant events, inputs, resources, processing and outputs associated with relevant business processes.
Enterprise Architect provides specific modeling tools for a range of Business Modeling types.
Topic |
Detail |
See also |
|---|---|---|
Requirements |
Enterprise Architect is one of the few UML tools that integrate Requirements Management with other software development disciplines in the core product, by defining requirements within the model.
|
|
Business Modeling |
Modeling the business process is an essential part of any software development process, enabling the analyst to capture the broad outline and procedures that govern what it is a business does.
|
|
Business Rules |
Business Rule modeling captures the rules that govern a business, and their relationships with the entities and specific tasks within the organization or system.
|
|
BPMN |
The Business Process Modeling Notation is specifically targeted at the business modeling community and has a direct mapping to UML through BPMN Profiles; these profiles enable you to develop BPMN diagrams quickly and simply.
|
|
BPEL |
Business Process Execution Language is an executable language for specifying interactions with Web Services. Enterprise Architect uses the BPMN profile as a graphical front-end to capture BPEL Process descriptions.
|
|
SPEM |
The Software and Systems Process Engineering Meta-model (SPEM) is a conceptual framework for modeling, documenting, presenting, managing, interchanging, and enacting development methods and processes. SPEM 2.0 focuses on providing the additional information structures that you require for processes modeled with UML 2 Activities or BPMN/BPDM.
|
|
ArchiMate |
ArchiMate is an open-standard enterprise architecture language based on the IEEE 1471 standard, providing a common language for describing the construction and operation of business processes, organizational structures, information flows, IT systems and technical infrastructure. It enables Enterprise Architects to clearly describe, analyse and visualize the relationships among business domains.
|
|
Eriksson-Penker Extensions |
Eriksson-Penker extensions provide a framework for UML business processing model extensions, to which an Enterprise Architect can add stereotypes and properties appropriate to their business. In Enterprise Architect, the Eriksson-Penker profile provides, through a set of stereotypes, a unique and powerful means of visualizing and communicating business processes and the necessary flow of information within an organization.
|
