Conference Paper

Significant Productivity Enhancement through Model Driven Techniques: A Success Story

IKV++, Berlin
DOI: 10.1109/EDOC.2006.53 Conference: Enterprise Distributed Object Computing Conference, 2006. EDOC '06. 10th IEEE International
Source: IEEE Xplore


This paper describes the automation and optimization of a software development process of NTT Data. The target systems of this development process are Web based information systems running on a J2EE platform. The automation and optimization of that process was achieved by the application of model driven techniques, mainly the integration of development tools via a meta object facility (MOF) repository backbone. The internal evaluation of NTT Data pointed out a development effort and time reduction of more than 50%. The main lessons learned form this case include the necessity of model-to-model transformations, the need to preserve advantage of existing development process and tools landscape, the requirements to care about configuration and change management from the beginning and the requirements to support also non modeling tools. Also, we identified a new business role, which is that of a tool and process integrator

Full-text preview

Available from:
  • Source
    • "Automated RE Management [106] Configuration Management System [107] Use Case Models [108] e-R&D [109] ReleasePlanner, which implements a practice called EVOLVE* [110] Test management automation [111] AMEDATO [112] Unnamed Tool [113] "
    [Show abstract] [Hide abstract]
    ABSTRACT: BACKGROUND—Software Process Improvement (SPI) is a systematic approach to increase the efficiency and effectiveness of a software development organization and to enhance software products. OBJECTIVE—This paper aims to identify and characterize evaluation strategies and measurements used to assess the impact of different SPI initiatives. METHOD—The systematic literature review includes 148 papers published between 1991 and 2008. The selected papers were classified according to SPI initiative, applied evaluation strategies, and measurement perspectives. Potential confounding factors interfering with the evaluation of the improvement effort were assessed. RESULTS—Seven distinct evaluation strategies were identified, wherein the most common one, “Pre-Post Comparison,” was applied in 49 percent of the inspected papers. Quality was the most measured attribute (62 percent), followed by Cost (41 percent), and Schedule (18 percent). Looking at measurement perspectives, “Project” represents the majority with 66 percent. CONCLUSION—The evaluation validity of SPI initiatives is challenged by the scarce consideration of potential confounding factors, particularly given that “Pre-Post Comparison” was identified as the most common evaluation strategy, and the inaccurate descriptions of the evaluation context. Measurements to assess the short and mid-term impact of SPI initiatives prevail, whereas long-term measurements in terms of customer satisfaction and return on investment tend to be less used.
    Full-text · Article · Nov 2011 · IEEE Transactions on Software Engineering
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: Model-driven engineering is a software development method to model applications at a high level of abstraction and introduce platform specific details automatically using model transformations. Similarly, models specified in human-readable languages can be mapped automatically onto languages that support the analysis of formal properties. In an industrial context, the transformations that automate such mappings should be able to consume input models from various commercial tools. Unfortunately, such tools tend to store models in slightly different ways, not fully compliant to standards. Additional techniques are necessary to develop transformations in a platform independent manner instead of specific ones for each modeling tool. This paper illustrates such techniques on an example related to the transformation of visual process models (UML activity diagrams) into low-level algebraic (CSP) programs that support formal verification. In turn, the platform independent and human-readable transformation model is translated into code that can transform UML inputs even when these are non-standard.
    Full-text · Conference Paper · May 2008
  • [Show abstract] [Hide abstract]
    ABSTRACT: Almost a decade has passed since the OMG has issued the Model Driven Architecture (MDA) initiative. It soon became obvious that raising the level of abstraction in development and reasoning at the model level would help in asking the right questions at the right time. Based on a concrete problem, we discuss four alternative solutions to a multi-language system design problem. These solutions use a traditional approach, a technique based on modeling, a domain-specific approach, and a mix of modeling and domain-specific techniques, respectively. The solutions depend on the problem, but they are representative for the situations we encounter in practice, therefore giving us a good basis for a larger discussion on the appropriateness of using modeling techniques and on the place of MDA in current software engineering practice and design.
    No preview · Article · Mar 2010 · Innovations in Systems and Software Engineering
Show more