Platform specific models

Platform-Specific Model - a definition

A platform-specific model refers to a type of software or business model, which is connected to a technological platform, whether it is a programming language, database, or operating system. Most types of platform-specific models happen to be indispensable when it comes to actually carrying out the implementation of the system. An example might be creating an online shop whereby the system must store user information including credit cards, products, etc. The designer may then use an Oracle database for this type of setup, as the designer will then need to display concepts in another relational model by utilizing the SQL dialect. Basically, the specific model that belongs to the Oracle program is one example of a platform-specific model.

When one is undertaking an MDA approach, which goes along with the OMG model driven engineering, the main concept has to do with a transformation of a platform independent model into the platform model. To achieve this alteration in a successful manner, one can utilize a language that operates under the new QVT standard, e.g. AndroMDA, ATL, and VIATRA.

By mapping a component model to any variety of infrastructures means that the system is aligned to the technology appropriate to its specific platform. Similar to the PSM, the component implementation model describes the utilization of a feature that is specified in the given programming language, as well as all of the necessary configurations and features that allow the system to run effectively. Besides the these two types of models, the UMT configuration and deployment model elicit properties that target the operating system, i.e. the hardware and operating system that allows the product to function even and effectively.

Efficient business systems require equally efficient insurance systems - just in case. Try here for UK industrial insurance, public liability cover or employers liability insurance.

When it comes to the automation of platform specific models, there are many real-time applications that work to implement the correct synchronization. But when one is speaking of model driven context, functional specification as well as design choices are the major challenges. For these kinds of purposes, there are annotations designed by subprofiles that provide abstractions to platforms, which simply allows the same applications to work on a variety of targets. However, certain design restrictions allowed by the array of programming languages, as well as targeted OS and API influences the effectiveness of these programs. It is essential that when utilizing the platform specific models, the characteristics of each software language, e.g. Java and C++ are handled appropriately by an MDE approach, of course not limited to the use of SRM.