Must i use the Business architect to create conceptual data model?

I would prefer to use the ER Data Architect. How are people using the ER DA for creating conceptual, logical and physical data models. At the moment, there are just the placeholders for the Logical and Physical Data model can be generated off the Logical. Is there a way to rename the Logical to Conceptual below?

  • I guess something to the effect below would serve as a placeholder for ideating and conceptualizing. Whereas the remaining submodels fill in the attribution for the overall conceptual model.  Does anyone see issues with the approach below?

     

     

  • Hello! ER/Studio Data Architect is meant for working with logical and physical models. You can use Business Data Objects to consolidate entities into higher-level objects if that's helpful. But for true conceptual modeling, you may want to consider using ER/Studio Business Architect, which is designed for conceptual models and business process models. You can create conceptual models in ERBA then export them to a file that can be imported directly into ERDA as the basis for your logical model design, and you can also move models from ERDA to ERBA in a similar manner. Check out more on ERBA on our website: https://www.idera.com/er-studio-business-architect-software

    Let us know if you have any other questions. Thanks!

  • The conceptual modeling is in the ER/Studio Business Architect tool so that high level conceptual models can be created by personas such as business analysts and business architects, staying in the same tool that they use to create business process models.  The conceptual models in the Business architect tool also use the Barker notation, which can be easier for those users to work with.  Anything created in a business architect conceptual model can be brought over to a data architect logical model for further elaboration.  (Side note:  information can also be updated back to the conceptual model if desired).

    That said, it is perfectly fine to use the logical modeling capability in data architect to create conceptual models.  Rather than have a separate top level sub-model called conceptual, it is often more practical to set up your top level submodels to represent functional business areas.  ER/Studio has a much more flexible (and powerful) architecture that allows you to create a submodel hierarchy (nested submodels) as many levels deep as you would like to represent a true business decomposition.  Therefore, you could create sub-models within your business areas to separate the  conceptual and logical perspectives, showing a lower degree of detail in the conceptual perspective than the logical, by applying different submodel display options.  For instance, in the conceptual perspective you may wish to show entities only or entities with definitions but show full attribution and other characteristics in the logical view.  By having them linked in the same branch of the hierarchy, you can also set submodel options so that updates made in the lower level (such as adding entities, etc.) can be automatically propagated to the parent level.

    ER/Studio Data Architect also includes a construct called Business Data Objects (BDO)which can be used to group entities (or tables in a physical model) that comprise a business object.  The BDO can also be collapsed visually to hide underlying details, which offers a more summarized view that is more appropriate for some audiences.  For example, you may have a business data object called "Sales Order" which contains entities like "Sales Order Header. Sales Order Detail".