Search Results

While the industry has recognized the value of modeling and code generation, the role of verification has taken a limited second tier role. Model Based Testing (MBT) is typically discussed in the context of automation of testing activities to eliminate the burden of generation and execution of tests. Unfortunately, this objective of effort minimization has skewed solutions away from using quality as a guiding metric. Alternatively, we have identified the simple objective of increasing the quality of testing practices and productivity of developers. In the following paper we introduce the integration of traditional software quality practices of functional, unit, and regression testing with the automated, model-driven world. This approach enables a quantitative approach to model driven software quality. The result is a robust technique that enables confident use of model-based development for production applications.

The value of model-based design has been attempted to be communicated for more than a decade. As methods and tools have appeared and disappeared from a series of different vendors it has become apparent that no single vendor has a solution that meets all users’ needs. Recently standards (UML, MDA, MOF, EMF, etc.) have become a dominant force and an alternative to vendor-specific languages and processes. Where these standards have succeeded and vendors have failed is in the realization that they do not provide the answer, but instead provide the foundation to develop the answer. It is in the utilization of these standards and their capability to be customized that companies have achieved success. Customization has occurred to fit organizations, processes, and architectures that leverage the value of model-driven design.

The past 10 years have created such buzzwords as “model-based development” and “auto-code generation”. Conveniently absent from the tool literature on model-based development are the equally, or more important concepts of Software Architecture and Process. When developing product line software, the process and architecture form a critical foundation to base reusable products and components. The development process can no longer be viewed as “model-based”, but rather as “model-driven”, due to the reliance on the models as the source artifact as opposed to the creators of the source artifacts. A model-driven product line software development process allows capturing of behavior, for commonality across different products, and having a different implementation for a specific product release.