Welcome to ER/Studio Business Architect

From ER/Studio Business Architect
Jump to: navigation, search

Go Up to Main Page

ER/Studio Business Architect (previously known as EA/Studio) applies two different types of modeling: Business Process Modeling Notation (BPMN), and Conceptual Modeling. These modeling processes allow you to integrate roles from various constituencies to collaborate, agree, create, and enable executable processes.

The Business Process Modeling portion of ER/Studio Business Architect (ER/Studio BA) is a visual modeling application that focuses on business process modeling and its relationship to related enterprise and data artifacts. Business processes do not exist in a vacuum within the organization, so ER/Studio BA allows you to link key business process information to data, organization, rules, etc. to get a broad view of the organization and show how processes and data impact one another.

The Conceptual Modeling portion allows Data Modelers to create high-level designs of core business concepts to gain acceptance and requirements from the business. These high-level Conceptual models can be forward engineered to create detailed Logical Data Models in ER/Studio. You can relate data objects to business process information and create Usage (CRUD) and Impact Analysis reports. In addition to process-specific information, related business information can also be linked to data objects such as business rules, business elements, business units, and stewards.

Through robust reporting, modeling, and graphical impact analysis, users are able to provide relevant information to various stakeholders within the organization in a format that makes sense to them. For example, a data analyst may wish to see a Usage (CRUD) report showing what data is used by a given process for compliance. A business user may want to see a list of relevant business rules in a spreadsheet. A process modeler needs to see a semantically-rich process model. ER/Studio BA allows each stakeholder to see a different “slice” of information—all from the same data source and metadata model.