177,115 research outputs found
Combining the Continuous Integration Practice and the Model-Driven Engineering Approach
The software development approach called model-driven engineering has become increasingly widespread. The continuous integration practice has also been gaining the importance. Some works have shown that both can improve the software development process. The problem is that the model-driven engineering is still a very active research topic lacking its maturity, what translates into difficulties in optimal incorporation of the continuous integration practice in the process. We present an experience report in which we show the problems we have detected in a real project and how we have solved them. Thus, we increase the productivity of development and the non-technical people are able to modify already deployed applications. Finally, we incorporate an evaluation that shows the benefits of the proposed union
Combining the Continuous Integration Practice and the Model-Driven Engineering Approach
The software development approach called model-driven engineering has become increasingly widespread. The continuous integration practice has also been gaining the importance. Some works have shown that both can improve the software development process. The problem is that the model-driven engineering is still a very active research topic lacking its maturity, what translates into difficulties in optimal incorporation of the continuous integration practice in the process. We present an experience report in which we show the problems we have detected in a real project and how we have solved them. Thus, we increase the productivity of development and the non-technical people are able to modify already deployed applications. Finally, we incorporate an evaluation that shows the benefits of the proposed union
Principles for aerospace manufacturing engineering in integrated new product introduction
This article investigates the value-adding practices of Manufacturing Engineering for integrated New Product Introduction. A model representing how current practices align to support lean integration in Manufacturing Engineering has been defined. The results are used to identify a novel set of guiding principles for integrated Manufacturing Engineering. These are as follows: (1) use a data-driven process, (2) build from core capabilities, (3) develop the standard, (4) deliver through responsive processes and (5) align cross-functional and customer requirements. The investigation used a mixed-method approach. This comprises case studies to identify current practice and a survey to understand implementation in a sample of component development projects within a major aerospace manufacturer. The research contribution is an illustration of aerospace Manufacturing Engineering practices for New Product Introduction. The conclusions will be used to indicate new priorities for New Product Introduction and the cross-functional interactions to support flawless and innovative New Product Introduction. The final principles have been validated through a series of consultations with experts in the sponsoring company to ensure that correct and relevant content has been defined
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
Enterprise Experience into the Integration of Human-Centered Design and Kanban
he integration of Human-Centered Design (HCD) and Agile Software Development (ASD) promises the
development of competitive products comprising a good User Experience (UX). This study has investigated
the integration of HCD and Kanban with the aim to gain industrial experiences in a real world context. A
case study showed that requirements flow into the development process in a structured manner by adding a
design board. To this end, the transparency concerning recurring requirements increased. We contribute to
the body of knowledge of software development by providing practical insights into Human-Centered Agile
Development (HCAD). On one hand, it is shown that the integration of HCD and Kanban leads to a product
with a good UX and makes the development process more human-centered. On the other hand, we conclude
that a cross-functional collaboration speeds up product development.Ministerio de EconomÃa y Competitividad TIN2013-46928-C3-3-RMinisterio de EconomÃa y Competitividad TIN2015-71938-RED
The Need and Requirements to a Strategy Ontology
The importance of strategy and strategy construct is not a new
phenomenon. However as strategy work becomes less tangible, concerns with
understanding, describing, and managing strategies develops into an increasingly
complex subject. Current strategy concepts are dispersed and lack integration.
Moreover, the enablement of modelling practices around strategy concepts
considering the entire strategy lifecycle are also missing. Consequently, this
paper focuses on issues with strategy in theory and practice, why a strategy
ontology is needed and how this can be developed
A Case Study on Artefact-based RE Improvement in Practice
Most requirements engineering (RE) process improvement approaches are
solution-driven and activity-based. They focus on the assessment of the RE of a
company against an external norm of best practices. A consequence is that
practitioners often have to rely on an improvement approach that skips a
profound problem analysis and that results in an RE approach that might be
alien to the organisational needs. In recent years, we have developed an RE
improvement approach (called \emph{ArtREPI}) that guides a holistic RE
improvement against individual goals of a company putting primary attention to
the quality of the artefacts. In this paper, we aim at exploring ArtREPI's
benefits and limitations. We contribute an industrial evaluation of ArtREPI by
relying on a case study research. Our results suggest that ArtREPI is
well-suited for the establishment of an RE that reflects a specific
organisational culture but to some extent at the cost of efficiency resulting
from intensive discussions on a terminology that suits all involved
stakeholders. Our results reveal first benefits and limitations, but we can
also conclude the need of longitudinal and independent investigations for which
we herewith lay the foundation
- …