Applying model-driven paradigm: CALIPSOneo experience

Model-Driven Engineering paradigm is being used by the research community in the last years, obtaining suitable results. However, there are few practical experiences in the enterprise field. This paper presents the use of this paradigm in an aeronautical PLM project named CALIPSOneo currently under development in Airbus. In this context, NDT methodology was adapted as methodology in order to be used by the development team. The paper presents this process and the results that we are getting from the project. Besides, some relevant learned lessons from the trenches are concluded.Ministerio de Ciencia e Innovación TIN2010-20057-C03-02Junta de Andalucía TIC-578

Requirements traceability in model-driven development: Applying model and transformation conformance

The variety of design artifacts (models) produced in a model-driven design process results in an intricate relationship between requirements and the various models. This paper proposes a methodological framework that simplifies management of this relationship, which helps in assessing the quality of models, realizations and transformation specifications. Our framework is a basis for understanding requirements traceability in model-driven development, as well as for the design of tools that support requirements traceability in model-driven development processes. We propose a notion of conformance between application models which reduces the effort needed for assessment activities. We discuss how this notion of conformance can be integrated with model transformations

IT Service Management Maturity Model

Yrityksien tietohallinto on toiminnaltaan muuttunut vuosien saatossa vahvasti palveluntuottajan asemaan tarkoituksena tuottaa arvoa yrityksen liiketoimintaan, kuunnellen liiketoiminnan tarpeita. Tämän myötä IT-palveluiden tehokkaista prosesseista, jatkuvasta kehittämisestä ja asiakaslähtöisestä toiminnasta on tullut entistä tärkeämpää IT organisaatiolle. Tähän IT-palveluhallinnan konseptin tukemiseen on aikojen saatossa luotu erilaisia IT-palveluhallintamalleja, joista ITIL on yksi käytetyimmistä menetelmistä. Tämän tutkimuksen tavoitteena on luoda IT-palveluhallinnan tason mittaamiseen sopiva mittaristo suunnittelutiedettä hyödyntäen. Pohjana mittariston luomisessa käytetään vuonna 2019 päivitettyä ITIL versio 4 mallia sekä olemassa olevaa tutkimusmateriaalia IT-palveluhallinnan mittareista. Mittariston tavoitteena on ilmentää yritykselle, miten voidaan IT palveluprosesseja arvioida ITIL versio 4 mukanaan tuomat arvoa tuottavan toiminnan näkökulmat huomioiden. Kirjallisuuskatsaus kattaa IT palveluhallinnan, ITIL mallin kuvauksen, IT- palveluhallinnan kypsyysmittarit sekä katsauksen käytettyyn suunnittelutiede tutkimusmenetelmään. Suunnittelutiedettä mallintaen ITIL versio 4 kanssa yhteensopiva maturiteettimalli luotiin. Pohjana käytettiin kirjallisuuskatsauksen tieteellisiä artikkeleita ja ITIL 4 kirjallisuutta. Tämän kyseisen artefaktin testaamisessa käytettiin kahta eri ITIL 4 palvelunhallintamenetelmää joita testattiin muutaman eri IS palvelun yhteydessä arviointilomakkeen ja haastatteluiden avulla. Tätä kautta kerättiin tuloksia mallin toimivuudesta IT palveluhallinnan mittaamiseen. Tutkimuksen tuotoksena on IT-palveluhallinnan mittaamiseen sopiva maturiteettimalli, kun halutaan käyttää näkökulmana ITIL versio 4 IT palveluhallintamallia. Koska aikaisempia ITIL versio 4 malliin luotuja, tai sitä vasten tehtyjä maturiteettimalleja, saati tutkimuksia ei löytynyt, kerättiin palautetta mallin toimivuudesta ennen kaikkea edellä mainituiden käytännön testaamisten kautta. Malli koettiin toimivaksi ja ennen kaikkea johdon tuki osoittautui tärkeäksi painopisteeksi onnistuneen IT palveluhallinnan arvioinnin mahdollistamisessa. Tutkimuksessa kerättiinkin myös yhteen suosituksia huomioon otettavista asioista ennen kuin IT-palveluhallinnan mittaamista lähdetään toteuttamaan

A CMMI-compliant requirements management and development process

Requirements Engineering has been acknowledged an essential discipline for Software Quality. Poorly-defined processes for eliciting, analyzing, specifying and validating requirements can lead to unclear issues or misunderstandings on business needs and project’s scope. These typically result in customers’ non-satisfaction with either the products’ quality or the increase of the project’s budget and duration. Maturity models allow an organization to measure the quality of its processes and improve them according to an evolutionary path based on levels. The Capability Maturity Model Integration (CMMI) addresses the aforementioned Requirements Engineering issues. CMMI defines a set of best practices for process improvement that are divided into several process areas. Requirements Management and Requirements Development are the process areas concerned with Requirements Engineering maturity. Altran Portugal is a consulting company concerned with the quality of its software. In 2012, the Solution Center department has developed and applied successfully a set of processes aligned with CMMI-DEV v1.3, what granted them a Level 2 maturity certification. For 2015, they defined an organizational goal of addressing CMMI-DEV maturity level 3. This MSc dissertation is part of this organization effort. In particular, it is concerned with the required process areas that address the activities of Requirements Engineering. Our main goal is to contribute for the development of Altran’s internal engineering processes to conform to the guidelines of the Requirements Development process area. Throughout this dissertation, we started with an evaluation method based on CMMI and conducted a compliance assessment of Altran’s current processes. This allowed demonstrating their alignment with the CMMI Requirements Management process area and to highlight the improvements needed to conform to the Requirements Development process area. Based on the study of alternative solutions for the gaps found, we proposed a new Requirements Management and Development process that was later validated using three different approaches. The main contribution of this dissertation is the new process developed for Altran Portugal. However, given that studies on these topics are not abundant in the literature, we also expect to contribute with useful evidences to the existing body of knowledge with a survey on CMMI and requirements engineering trends. Most importantly, we hope that the implementation of the proposed processes’ improvements will minimize the risks of mishandled requirements, increasing Altran’s performance and taking them one step further to the desired maturity level

A maturity model for DevOps

Nowadays, businesses aim to respond to customer needs at unprecedented speed. Thus, many companies are rushing to the DevOps movement. DevOps is the combination of Development and Operations and a new way of thinking in the software engineering domain. However, no common understanding of what it means has yet been achieved. Also, no adoption models or fine-grained maturity models to assist DevOps maturation and implementation were identified. Therefore, this research attempt to fill these gaps. A systematic literature review is performed to identify the determining factors contributing to the implementation of DevOps, including the main capabilities and areas with which it evolves. Then, two sets of interviews with DevOps experts were performed and their experience used to build the DevOps Maturity Model. The DevOps maturity model was then developed grounded on scientific and professional viewpoints. Once developed the Maturity Model was demonstrated in a real organisation.info:eu-repo/semantics/acceptedVersio

Applying Model-Driven Paradigm for the Improvement of Web Requirement Validation

This paper proposes an approach for Web requirements validation by applying the model-driven paradigm in classical requirements validation techniques. In particular, we present how the Navigational Development Techniques (NDT) approach exploits the model-driven paradigm to improve its requirements validation task by exploring tool cases that systematize or even automate the application of requirements validation techniques. Our solution is validated by applying it in a real industrial environment. The results and the learned lessons are presented accordingly

Maturity model for DevOps

Businesses today need to respond to customer needs at unprecedented speed. Driven by this need for speed, many companies are rushing to the DevOps movement. DevOps, the combination of Development and Operations, is a new way of thinking in the software engineering domain that recently received much attention. Since DevOps has recently been introduced as a new term and novel concept, no common understanding of what it means has yet been achieved. Therefore, the definitions of DevOps often are only a part relevant to the concept. When further observing DevOps, it could be seen as a movement, but is still young and not yet formally defined. Also, no adoption models or fine-grained maturity models showing what to consider to adopt DevOps and how to mature it were identified. As a consequence, this research attempted to fill these gaps and consequently brought forward a Systematic Literature Review to identify the determining factors contributing to the implementation of DevOps, including the main capabilities and areas with which it evolves. This resulted in a list of practices per area and capability that was used in the interviews with DevOps practitioners that, with their experience, contributed to define the maturity of those DevOps practices. This combination of factors was used to construct a DevOps maturity model showing the areas and capabilities to be taken into account in the adoption and maturation of DevOps.Hoje em dia, as empresas precisam de responder às necessidades dos clientes a uma velocidade sem precedentes. Impulsionadas por esta necessidade de velocidade, muitas empresas apressam-se para o movimento DevOps. O DevOps, a combinação de Desenvolvimento e Operações, é uma nova maneira de pensar no domínio da engenharia de software que recentemente recebeu muita atenção. Desde que o DevOps foi introduzido como um novo termo e um novo conceito, ainda não foi alcançado um entendimento comum do que significa. Portanto, as definições do DevOps geralmente são apenas uma parte relevante para o conceito. Ao observar o DevOps, o fenómeno aborda questões culturais e técnicas para obter uma produção mais rápida de software, tem um âmbito amplo e pode ser visto como um movimento, mas ainda é jovem e ainda não está formalmente definido. Além disso, não foram identificados modelos de adoção ou modelos de maturidade refinados que mostrem o que considerar para adotar o DevOps e como fazê-lo crescer. Como consequência, esta pesquisa tentou preencher essas lacunas e, consequentemente, apresentou uma Revisão sistemática da literatura para identificar os fatores determinantes que contribuem para a implementação de DevOps, incluindo os principais recursos e áreas com os quais ele evolui. Isto resultou numa lista de práticas por área e por capacidade, que foi utilizado como base nas entrevistas realizadas com peritos em DevOps que, com a sua experiência, ajudaram a atribuir níveis de maturidade a cada prática. Esta combinação de fatores foi usada para construir um modelo de maturidade de DevOps mostrando as áreas e as capacidades a serem levados em consideração na sua adoção e maturação