Model-Driven Architecture (MDA™) is a software design approach that its sponsor, the Object Management Group (OMG), officially launched in 2001. MDA supports model-driven engineering of software systems. MDA provides a set of guidelines for structuring specifications expressed as models.
The MDA approach defines system functionality using a platform-independent model (PIM) using an appropriate Domain Specific Language. Then, given a Platform Definition Model (PDM) corresponding to CORBA, DotNet, the Web, etc., the PIM is translated to one or more platform-specific models (PSMs) that computers can run, using different Domain Specific Languages, or a General Purpose Language like Java, C#, Python, etc.
One of the main aims of the MDA is to separate design from architecture. As the concepts and technologies used to realize designs and the concepts and technologies used to realize architectures have changed at their own pace, decoupling them allows system developers to choose from the best and most fitting in both domains.
The design addresses the functional (use case) requirements while architecture provides the infrastructure through which non-functional requirements like scalability, reliability and performance are realized. MDA envisages that the platform independent model (PIM), which represents a conceptual design realizing the functional requirements, will survive changes in realization technologies and software architectures.
The Casewise reference model kick start your project with pre defined templates. It gives you guidance and enables you to communicate your design results as HTML, Word document or you can maintain the data (create, delete, update) via the Web Portal, which provides you also Dashboard views for communicating the metrics (performance metric, critical success factors, compliance status,…)
All requirements were visualized and can be used throughout the Corporate Modeler toolset and can be easily customized to your organizational environment. Because of our extensibility you are free to add your own Audit question and controls and cross reference them with the modeled requirements, with your own processes or you can use the pre defined ITIL process model and get the cross references out of the box.
As part of our Casewise tool set you will be able to schedule audit questions and controls in order to perform internal checks/audits or just performed simple assessments. Based on this data you will be able to communicate the results via our HTML Portal within different Dashboard or list views. This data can also be maintained (create, delete, update) via the Portal (web front end).