Extending the Model Driven Architecture with a preCIM level

Whilst the successful alignment of business strategy and IT development is an important topic, there are still few ways that this is possible. The Model Driven Architecture (MDA) shows promise as an approach but is focussed firmly in the IT domain at the level of the Platform Independent and Platform Specific Models. The Computation Independent Model (CIM) is targetted at business users, but this paper argues that the complexity of the CIM level disenfranchises them. The concept of a preCIM level could provide much richness to the MDA process and give the domain user greater ownership of the IT development that supports their processes

A methodology for CIM modelling and its transformation to PIM

Developing with Model Driven Architecture is nowadays widely used starting with a CIM that can be transformed to models of low abstraction (PIM, PSM) that can be used to generate the code. The CIM represents the highest level of abstraction of the approach which allowing modeling system’s requirement. However, there is no standard method to build this type of model or how to transform it to lower level of abstraction (PIM) which is considered the final objective of building such model. This paper provides an approach to build the CIM that can be transformed (semi-) automatically later to lower levels of abstraction in PIMs.  Thereby, the proposed architecture represents both the static and dynamic view of the system based on the business process model. Meanwhile, the PIM level is represented by the Domain Diagram class and Sequence Diagram of Systems External behavior. Thus, the proposal helps bridging the gap between those that are experts about the domain and its requirements, and those that are experts of the system design and development. Keywords: CIM to PIM transformation; MDA; software process

PROPOSED FRAMEWORK FOR TAILORING AGILE-BASED SOFTWARE DEVELOPMENT PROCESSES FOR SMALL AND MEDIUM SIZED COMPANIES

High risks are involved as well as a large number of resources are required to construct the software development processes from scratch. Most of the software development companies follow ad-hoc approaches in informal ways to tailor an existing software development process according to their requirements. Instead of devising new tailoring strategies, these approaches describe and compare the similar tailoring operations at very superficial level and mainly focus on the large sized software development companies

Model and use case driven software development process.

У докторској дисертацији је разматран проблем интеграције случајева коришћења у моделом вођени развој софтвера и предложена оригиналана Silab- UCMDDM метода. Предложена Silab-UCMDDM метода истиче важност и неопходност коришћења 3 међусобно конзистентна и комплементарна модела: а) моделa случајева коришћења, б) доменскoг моделa и ц) моделa прелаза стања. У дисертацији је идентификована директна веза између ова три модела која се пре свега огледа у томе да спецификација акција случаја коришћења треба да се ослања на доменски модел, док се предуслови и постуслови за извршење случајева коришћења дефинишу у моделу прелаза стања. Silab-UCMDM метода користи две стратегије у развоју софтвера: а) стратегију засновану на случајевима коришћења (Use Case Driven Development) и б) стратегију засновану на MDD (Model Driven Development) приступу. Спецификација захтева у оквиру Silab-UCMDM методе омогућена је преко сопственог доменски специфичног језика (UCDSL). Имплементација предложеног UCDSL језика извршена је преко JetBrains MPS алата за метапрограмирање (JetBrains MPS metaprogramming system). UCDSL језик је интегрисан у оквиру SILAB-MDDTOOLSET алата који се може користити као додатак (plugin) за окружења као што су MPS и IntelliJ IDEA...The thesis discusses the problem of integration of the Use Cases in the Model driven software development and proposes an original Silab-UCMDDM method. The Silab-UCMDDM method emphasizes the importance and necessity of using 3 mutually consistent and complementary models: a) the use case model, b) the domain model and c) the state machine model. The thesis identifies a direct link between these three models which are primarily reflected in the fact that the specification of use case actions should be based on the domain model, while the preconditions and postconditions for executing use cases should be defined in the state machine model. This model state machine model is used for a clear and precise definition of use cases. The Silab-UCMDM method uses two strategies in software development: a) a strategy based on the use cases (Use Case Driven Development) and b) a strategy based on MDD (Model Driven Development) approach. Requirements specification within Silab- UCMDM method is enabled via its own domain specific language (UCDSL). The proposed UCDSL language was performed using the JetBrains MPS tool for metaprogramming (metaprogramming system JetBrains MPS). UCDSL language is integrated within the SILAB-MDDTOOLSET tool that can be used as an add-on (plugin) for environments such as MPS and IntelliJ IDEA. The proposed Silab-UCMDD method was evaluated in three different ways: 1) By performing the comparative analysis of the proposed method and other existing methods. 2) By presenting and analyzing the case study that has been developed using proposed method. 3) By analyzing the results of the testing with students who evaluated the proposed method and UCDSL language for requirements specification and validation. The Silab-UCMDDM method is a part of a comprehensive Silab-MDD approach. Silab-MDD approach defines the way of integration of the Structured System Analysis method, which describes the functionalities of the business system. In addition Silab-MDD defines the phases of requirements gathering and analysis in the software development lifecycle. Therefore, the Silab-MDD approach contains its own domain specific languages for specifying the Data Flow diagrams (DFDDSL) and the Data Dictionary (DataDDSL)..

PROPOSED FRAMEWORK FOR TAILORING AGILE-BASED SOFTWARE DEVELOPMENT PROCESSES FOR SMALL AND MEDIUM SIZED COMPANIES

High risks are involved as well as a large number of resources are required to construct the software development processes from scratch. Most of the software development companies follow ad-hoc approaches in informal ways to tailor an existing software development process according to their requirements. Instead of devising new tailoring strategies, these approaches describe and compare the similar tailoring operations at very superficial level and mainly focus on the large sized software development companies