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

Tracing the Scenarios in Scenario-Based Product Design: a study to support scenario generation

Scenario-based design originates from the human-computer interaction and\ud software engineering disciplines, and continues to be adapted for product development. Product development differs from software development in the former’s more varied context of use, broader characteristics of users and more tangible solutions. The possible use of scenarios in product design is therefore broader and more challenging. Existing design methods that involve scenarios can be employed in many different stages of the product design process. However, there is no proficient overview that discusses a\ud scenario-based product design process in its full extent. The purposes of creating scenarios and the evolution of scenarios from their original design data are often not obvious, although the results from using scenarios are clearly visible. Therefore, this paper proposes to classify possible scenario uses with their purpose, characteristics and supporting design methods. The classification makes explicit different types of scenarios and their relation to one another. Furthermore, novel scenario uses can be referred or added to the classification to develop it in parallel with the scenario-based design\ud practice. Eventually, a scenario-based product design process could take inspiration for creating scenarios from the classification because it provides detailed characteristics of the scenario

An introduction to STRIKE : STRuctured Interpretation of the Knowledge Environment

Knowledge forms a critical part of the income generation of the system and the complex environment in which actors participate in the creation of knowledge assets merits robust, eclectic consideration. STRIKE - STRuctured Interpretation of the Knowledge Environment affords an unobtrusive and systematic framework to observe, record, evaluate and articulate concrete and abstract elements of a setting, across internal and external dimensions. Inter-relationships between actor and environment are preserved. STRIKE is supported by underlying techniques to enrich data and enhance the authenticity of its representation. Adoption of photography and videography tools provides illustrative and interpretive benefits and facilitates researcher reflexivity. This structured approach to data analysis and evaluation mitigates criticisms of methodological rigour in observational research and affords standardisation potential, germane for application in a verification or longitudinal capacity. Advancing exploratory validation studies, the method is employed to evaluate the knowledge environments of two enterprises in the UK creative sector. These occupy a critical role in fostering entrepreneurial innovation alongside participant self-efficacy. Access Space in Sheffield and the Bristol Hackspace are committed to open software, open knowledge and open participation; sharing peer learning, creativity and socio-technical aims to address broadly similar community needs. Drawing on Wittgenstein’s Picture Theory of Meaning, the knowledge management perspective is abstracted from the STRIKE assessment. It is argued that the tiered analytical approach which considers a breadth of dimensions enhances representation and interpretation of the knowledge environment and presents a diagnostic and prescriptive capability to actualise change. The paper concludes by evaluating framework effectiveness, findings application and future direction

Un modelo para documentar la elicitación de requisitos

Context: This work proposes a model to document the elicitation of requirements in the field of Requirements Engineering. Method: A systematic review of the literature was conducted to determine the validity and effectiveness of the existing models for documenting requirements elicitation. Results: By analyzing the results of this review, it was concluded that it is possible – and that is required – to take the best documented practices and add principles from logic, abstraction, and formal methods to them in order to structure a semi-formal model for documenting elicitation. Those currently proposed focus on techniques to collect information and pay little attention to documentation. In addition, these models are mainly based on natural language, which makes their interpretation difficult, and they generate re-processing in later stages of the life cycle due to ambiguities. Conclusions: This article describes a structured model, as well as its application and validation, by comparing it against five models found in the review.Contexto: En este trabajo se propone un modelo para documentar la elicitación de requisitos en el área de Ingeniería de Requisitos. Método: Se realizó una revisión sistemática de la literatura para determinar la validez y efectividad de los modelos que existen para documentar la elicitación de requisitos. Resultados: Analizando los resultados de esta revisión, se concluyó que es posible –y así se requiere– tomar las mejores prácticas documentadas y agregarles principios de lógica, abstracción y métodos formales para estructurar un modelo semiformal para documentar la elicitación. Los que se proponen actualmente se centran en las técnicas de recogida de información y prestan poca atención a la documentación. Además, estos modelos se basan principalmente en el lenguaje natural, por lo cual es difícil su interpretación, y generan reprocesos para las etapas posteriores del ciclo de vida debido a las ambigüedades. Conclusiones: En este artículo se describe un modelo estructurado, así como su aplicación y validación mediante la comparación con cinco modelos encontrados en la revisión

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

Integration of experience feedback into the product lifecycle: an approach to best respond to the bidding process

Bidding process allows a client to choose a bidder to realize an embodiment of work, supply or service. From the bidder point of view, there are several obvious risks when responding because he bets on a future development that hasn’t been yet realized. We propose to assist the bidder with decision support tools based on past experiences to detect, report and minimize these potential risks. In this paper, we present the definition of a conceptual architecture to integrate experience feedback into the product lifecycle taking into account all stages of product lifecycle to best respond new bidding processes

Supporting Automatic Interoperability in Model-Driven Development Processes

By analyzing the last years of software development evolution, it is possible to observe that the involved technologies are increasingly focused on the definition of models for the specification of the intended software products. This model-centric development schema is the main ingredient for the Model-Driven Development (MDD) paradigm. In general terms, the MDD approaches propose the automatic generation of software products by means of the transformation of the defined models into the final program code. This transformation process is also known as model compilation process. Thus, MDD is oriented to reduce (or even eliminate) the hand-made programming, which is an error-prone and time-consuming task. Hence, models become the main actors of the MDD processes: the models are the new programming code. In this context, the interoperability can be considered a natural trend for the future of model-driven technologies, where different modeling approaches, tools, and standards can be integrated and coordinated to reduce the implementation and learning time of MDD solutions as well as to improve the quality of the final software products. However, there is a lack of approaches that provide a suitable solution to support the interoperability in MDD processes. Moreover, the proposals that define an interoperability framework for MDD processes are still in a theoretical space and are not aligned with current standards, interoperability approaches, and technologies. Thus, the main objective of this doctoral thesis is to develop an approach to achieve the interoperability in MDD processes. This interoperability approach is based on current metamodeling standards, modeling language customization mechanisms, and model-to-model transformation technologies. To achieve this objective, novel approaches have been defined to improve the integration of modeling languages, to obtain a suitable interchange of modeling information, and to perform automatic interoperability verification.Giachetti Herrera, GA. (2011). Supporting Automatic Interoperability in Model-Driven Development Processes [Tesis doctoral no publicada]. Universitat Politècnica de València. https://doi.org/10.4995/Thesis/10251/11108Palanci

Review of Requirement Engineering Approaches for Software Product Lines

The Software Product Lines (SPL) paradigm is one of the most recent topics of interest for the software engineering community. On the one hand, the Software Product Lines is based on a reuse strategy with the aim to reduce the global time-to-market of the software product, to improve the software product quality, and to reduce the cost. On the other hand, traditional Requirement Engineering approaches could not be appropriated to deal with the new challenges that arises the SPL adoption. In the last years, several approaches have been proposed to cover this limitation. This technical report presents an analysis of specific approaches used in the development of SPL to provide solutions to model variability and to deal with the requirements engineering activities. The obtained results show that most of the research in this context is focused on the Domain Engineering, covering mainly the Feature Modeling and the Scenario Modeling. Among the studied approaches, only one of them supported the delta identification; this fact implies that new mechanisms to incorporate new deltas in the Domain specification are needed. Regarding the SPL adoption strategy, most of the approaches support a proactive strategy. However, this strategy is the most expensive and risk-prone. Finally, most of the approaches were based on modeling requirements with feature models giving less support to other important activities in the requirements engineering process such as elicitation, validation, or verification of requirements. The results of this study provide a wide view of the current state of research in requirements engineering for SPL and also highlight possible research gaps that may be of interest for researchers and practitioners.Blanes Domínguez, D.; Insfrán Pelozo, CE. (2011). Review of Requirement Engineering Approaches for Software Product Lines. http://hdl.handle.net/10251/1023