Use Cases for IMM
The following outlines how IMM may be used across (potentially) many different tools. Please note this is a vision and not a statement of requirements. Communication between the tools may be by exchanging XMI® files, access to a common repository, or use of APIs.
- A data analyst creates an Entity Relationship diagram. It is possible to trace the Entities to the formal definitions of the corresponding terms in an existing Business Vocabulary (either in the ER tool or a separate trace mapping tool)
- A relational database expert loads the Relational data model and uses a relational database tool to optimize it based on the documented needs of the intended use. The latter are outside the scope of IMM but could come from a Requirements model, UML system design. But it should be possible to trace from design decisions in the relational design to the requirements influencing the decision. This will result in a new version of the relational model (compared to that automatically generated)
- The relational model is loaded into a UML tool used by the application designer, who uses the UML Profile representation of the model to incorporate database access based on the correct table definition, and then generates the Java code for the system. (The system modeling and generation is outside scope of IMM but IMM provides the access to the correct data model in that environment)
- A model-to-text generation tool generates SQL text from the relational model. This is scheduled for deployment on the actual relational database software in conjunction with the deployment of the (new version) of the application
- The relational model is read by a data-warehousing tool, which is used to design an Extract to be run every night for a data mart. The data mart cube and underlying relational design is recorded as an IMM model
- The cube structure is loaded into a business-reporting tool and used by a business analyst to generate end user reports and queries. The traceability information can also be accessed and incorporated (from relational model back to ER model back to business vocabulary) in order to present the reports to the users using the business terms they are familiar with. Links are automatically created allowing the user to click a link to access the full definition of the term though dynamic access to the original business vocabulary model/repository