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)..

Detecting Functional Requirements Inconsistencies within Multi-teams Projects Framed into a Model-based Web Methodology

One of the most essential processes within the software project life cycle is the REP (Requirements Engineering Process) because it allows specifying the software product requirements. This specification should be as consistent as possible because it allows estimating in a suitable manner the effort required to obtain the final product. REP is complex in itself, but this complexity is greatly increased in big, distributed and heterogeneous projects with multiple analyst teams and high integration between functional modules. This paper presents an approach for the systematic conciliation of functional requirements in big projects dealing with a web model-based approach and how this approach may be implemented in the context of the NDT (Navigational Development Techniques): a web methodology. This paper also describes the empirical evaluation in the CALIPSOneo project by analyzing the improvements obtained with our approach.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-RMinisterio de Economía y Competitividad TIN2015-71938-RED

Agile Requirements Engineering: A systematic literature review

Nowadays, Agile Software Development (ASD) is used to cope with increasing complexity in system development. Hybrid development models, with the integration of User-Centered Design (UCD), are applied with the aim to deliver competitive products with a suitable User Experience (UX). Therefore, stakeholder and user involvement during Requirements Engineering (RE) are essential in order to establish a collaborative environment with constant feedback loops. The aim of this study is to capture the current state of the art of the literature related to Agile RE with focus on stakeholder and user involvement. In particular, we investigate what approaches exist to involve stakeholder in the process, which methodologies are commonly used to present the user perspective and how requirements management is been carried out. We conduct a Systematic Literature Review (SLR) with an extensive quality assessment of the included studies. We identified 27 relevant papers. After analyzing them in detail, we derive deep insights to the following aspects of Agile RE: stakeholder and user involvement, data gathering, user perspective, integrated methodologies, shared understanding, artifacts, documentation and Non-Functional Requirements (NFR). Agile RE is a complex research field with cross-functional influences. This study will contribute to the software development body of knowledge by assessing the involvement of stakeholder and user in Agile RE, providing methodologies that make ASD more human-centric and giving an overview of requirements management in ASD.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-RMinisterio de Economía y Competitividad TIN2015-71938-RED

Mapping Big Data into Knowledge Space with Cognitive Cyber-Infrastructure

Big data research has attracted great attention in science, technology, industry and society. It is developing with the evolving scientific paradigm, the fourth industrial revolution, and the transformational innovation of technologies. However, its nature and fundamental challenge have not been recognized, and its own methodology has not been formed. This paper explores and answers the following questions: What is big data? What are the basic methods for representing, managing and analyzing big data? What is the relationship between big data and knowledge? Can we find a mapping from big data into knowledge space? What kind of infrastructure is required to support not only big data management and analysis but also knowledge discovery, sharing and management? What is the relationship between big data and science paradigm? What is the nature and fundamental challenge of big data computing? A multi-dimensional perspective is presented toward a methodology of big data computing.Comment: 59 page

Incorporating Agile with MDA Case Study: Online Polling System

Nowadays agile software development is used in greater extend but for small organizations only, whereas MDA is suitable for large organizations but yet not standardized. In this paper the pros and cons of Model Driven Architecture (MDA) and Extreme programming have been discussed. As both of them have some limitations and cannot be used in both large scale and small scale organizations a new architecture has been proposed. In this model it is tried to opt the advantages and important values to overcome the limitations of both the software development procedures. In support to the proposed architecture the implementation of it on Online Polling System has been discussed and all the phases of software development have been explained.Comment: 14 pages,1 Figure,1 Tabl

On Modeling and Analyzing Cost Factors in Information Systems Engineering

Introducing enterprise information systems (EIS) is usually associated with high costs. It is therefore crucial to understand those factors that determine or influence these costs. Though software cost estimation has received considerable attention during the last decades, it is difficult to apply existing approaches to EIS. This difficulty particularly stems from the inability of these methods to deal with the dynamic interactions of the many technological, organizational and projectdriven cost factors which specifically arise in the context of EIS. Picking up this problem, we introduce the EcoPOST framework to investigate the complex cost structures of EIS engineering projects through qualitative cost evaluation models. This paper extends previously described concepts and introduces design rules and guidelines for cost evaluation models in order to enhance the development of meaningful and useful EcoPOST cost evaluation models. A case study illustrates the benefits of our approach. Most important, our EcoPOST framework is an important tool supporting EIS engineers in gaining a better understanding of the critical factors determining the costs of EIS engineering projects

Using Ontologies for the Design of Data Warehouses

Obtaining an implementation of a data warehouse is a complex task that forces designers to acquire wide knowledge of the domain, thus requiring a high level of expertise and becoming it a prone-to-fail task. Based on our experience, we have detected a set of situations we have faced up with in real-world projects in which we believe that the use of ontologies will improve several aspects of the design of data warehouses. The aim of this article is to describe several shortcomings of current data warehouse design approaches and discuss the benefit of using ontologies to overcome them. This work is a starting point for discussing the convenience of using ontologies in data warehouse design.Comment: 15 pages, 2 figure

Model the System from Adversary Viewpoint: Threats Identification and Modeling

Security attacks are hard to understand, often expressed with unfriendly and limited details, making it difficult for security experts and for security analysts to create intelligible security specifications. For instance, to explain Why (attack objective), What (i.e., system assets, goals, etc.), and How (attack method), adversary achieved his attack goals. We introduce in this paper a security attack meta-model for our SysML-Sec framework, developed to improve the threat identification and modeling through the explicit representation of security concerns with knowledge representation techniques. Our proposed meta-model enables the specification of these concerns through ontological concepts which define the semantics of the security artifacts and introduced using SysML-Sec diagrams. This meta-model also enables representing the relationships that tie several such concepts together. This representation is then used for reasoning about the knowledge introduced by system designers as well as security experts through the graphical environment of the SysML-Sec framework.Comment: In Proceedings AIDP 2014, arXiv:1410.322

The uses of process modeling : a framework for understanding modeling formalisms

There is wide-spread recognition of the urgent need to improve software processes in order to improve the performance of software organizations. Process models are essential in achieving understanding and visibility of processes and are important for other uses including the analysis of processes for improvement. It has been increasingly difficult to compare and evaluate the variety of process modeling formalisms that have appeared in recent years without a clear understanding of precisely for what they will be used. The contribution of this paper is to provide an understanding and a fairly comprehensive catalog of the applications of process modeling for which formalisms may be used. The primary mechanism for doing this is a guided tour of the literature on process modeling supplemented by recent industrial experience. In the paper, basic definitions concerning processes, process descriptions and process modeling are reviewed and then uses of process modeling are surveyed under the following headings: communication among process participants, construction of new processes, control of processes, process· analysis, and process support by automation. Comments are offered on paradigms for process modeling formalisms and directions for future work to permit evolution of a discipline of process engineering are given