Iterative criteria-based approach to engineering the requirements of software development methodologies

Software engineering endeavours are typically based on and governed by the requirements of the target software; requirements identification is therefore an integral part of software development methodologies. Similarly, engineering a software development methodology (SDM) involves the identification of the requirements of the target methodology. Methodology engineering approaches pay special attention to this issue; however, they make little use of existing methodologies as sources of insight into methodology requirements. The authors propose an iterative method for eliciting and specifying the requirements of a SDM using existing methodologies as supplementary resources. The method is performed as the analysis phase of a methodology engineering process aimed at the ultimate design and implementation of a target methodology. An initial set of requirements is first identified through analysing the characteristics of the development situation at hand and/or via delineating the general features desirable in the target methodology. These initial requirements are used as evaluation criteria; refined through iterative application to a select set of relevant methodologies. The finalised criteria highlight the qualities that the target methodology is expected to possess, and are therefore used as a basis for de. ning the final set of requirements. In an example, the authors demonstrate how the proposed elicitation process can be used for identifying the requirements of a general object-oriented SDM. Owing to its basis in knowledge gained from existing methodologies and practices, the proposed method can help methodology engineers produce a set of requirements that is not only more complete in span, but also more concrete and rigorous

OpenUP/MDRE: A Model-Driven Requirements Engineering Approach for Health-Care Systems

The domains and problems for which it would be desirable to introduce information systems are currently very complex and the software development process is thus of the same complexity. One of these domains is health-care. Model-Driven Development (MDD) and Service-Oriented Architecture (SOA) are software development approaches that raise to deal with complexity, to reduce time and cost of development, augmenting flexibility and interoperability. However, many techniques and approaches that have been introduced are of little use when not provided under a formalized and well-documented methodological umbrella. A methodology gives the process a well-defined structure that helps in fast and efficient analysis and design, trouble-free implementation, and finally results in the software product improved quality. While MDD and SOA are gaining their momentum toward the adoption in the software industry, there is one critical issue yet to be addressed before its power is fully realized. It is beyond dispute that requirements engineering (RE) has become a critical task within the software development process. Errors made during this process may have negative effects on subsequent development steps, and on the quality of the resulting software. For this reason, the MDD and SOA development approaches should not only be taken into consideration during design and implementation as usually occurs, but also during the RE process. The contribution of this dissertation aims at improving the development process of health-care applications by proposing OpenUP/MDRE methodology. The main goal of this methodology is to enrich the development process of SOA-based health-care systems by focusing on the requirements engineering processes in the model-driven context. I believe that the integration of those two highly important areas of software engineering, gathered in one consistent process, will provide practitioners with many benets. It is noteworthy that the approach presented here was designed for SOA-based health-care applications, however, it also provides means to adapt it to other architectural paradigms or domains. The OpenUP/MDRE approach is an extension of the lightweight OpenUP methodology for iterative, architecture-oriented and model-driven software development. The motivation for this research comes from the experience I gained as a computer science professional working on the health-care systems. This thesis also presents a comprehensive study about: i) the requirements engineering methods and techniques that are being used in the context of the model-driven development, ii) known generic but flexible and extensible methodologies, as well as approaches for service-oriented systems development, iii) requirements engineering techniques used in the health-care industry. Finally, OpenUP/MDRE was applied to a concrete industrial health-care project in order to show the feasibility and accuracy of this methodological approach.Loniewski, G. (2010). OpenUP/MDRE: A Model-Driven Requirements Engineering Approach for Health-Care Systems. http://hdl.handle.net/10251/11652Archivo delegad

Supporting requirement analysis through requirement rationale capture and traceability

Manufacturers of complex engineering systems are increasingly recognising the importance of identifying, understanding and satisfying stakeholders’ needs in order to produce high-quality products. The analysis of these needs into a formal requirement specification is a time consuming and complex process for which little support is offered to design engineers. This can result in requirements being poorly documented and with little or no traceability to their origins. This dissertation reports an investigation to understand the process of requirement analysis and develop computational support for this important phase of the engineering design process. The key argument of this research is that the existing practice of requirement analysis can be improved by providing better support for requirement rationale capture and enabling greater requirement traceability. The research consisted of three main phases. In the first phase, literature related to the requirement analysis was reviewed and led to the creation of a requirement analysis model. In the second phase, the practices of a global engineering organisation were investigated using document analysis as well as interviews with and shadowing of company engineers. The research found that requirement analysis lacks support for requirement rationale capture and traceability. On the basis of this result, a workflow for requirement analysis was proposed. The workflow involves the use of the Decision Rationale editor tool to capture requirement rationale and enable requirement traceability. In the third phase, four studies were undertaken to validate the workflow. These studies investigated: 1) application of the workflow to requirements generated through reverse-engineering a low-complexity consumer product; 2) requirements extracted from documents produced by a graduate engineering team during a twelve-week project; 3) the requirement analysis process undertaken by two graduate engineering teams during twelve-week projects; and 4) requirements for a new aircraft engine development programme. The studies showed that the proposed workflow is feasible, practical, and scalable when applied to engineering projects. Requirement rationales were classified into categories, namely product design and use, pre-existing rationale, and project management. In order to fully support requirement traceability, it was found that it is important to make traceable four types of requirement transformations: newly introduced, copied, updated, and deleted requirements. The research demonstrated that the proposed workflow is a successful proof-of-concept and can lead to improved quality of requirement documentation and requirement traceability.Open Acces

Chapter 4 Traceability in the Co-evolution of Architectural Requirements and Design

Abstract Requirements and architectural design specifications can be conflicting and inconsistent, especially during the design period when requirements and architectural design are co-evolving. One reason is that stakeholders do not have up-to-date knowledge of each other’s work to fully understand potential conflicts and inconsistencies. Specifications are often documented in a natural language, which also makes it difficult for tracing related information automatically. In this chapter, we introduce a general-purpose ontology that we have developed to address this problem. We demonstrate an implementation of semantic wiki that supports traceability of co-evolving requirements specifications and architecture design. Let us begin by considering a typical software architecting scenario: A team of business analysts and users work on a new software system in an organization. The business analysts and users document the business goals, use-case scenarios, system and data requirements in a requirements document. The team of software and system architects studie

Identifying capabilities and constraints in utilizing blockchain technology in hospitality and tourism

PurposeThe purpose of this study synthesises the body of research revolving around blockchain technology (BCT) whilst drawing on the technology-organization-environment framework, resource-based theory and theory of constraints, to conceptualize capabilities (enablers) and constraints (barriers) of BCT in the hospitality and tourism (H&T) industry.Design/methodology/approachA systematic literature review of BCT in the hotel and tourism industry has been achieved through two databases, i.e. Scopus and Web of Science. From 544 articles selected between the years 2008 and 2023 (first quarter), a sample of 49 articles was used to structure existing research on this subject.FindingsThe findings of this systematic literature review of BCT in the H&T literature establish a solid groundwork for assessing the evolution of this research area over time. Findings are classified into two groups: capabilities (enablers) and constraints (barriers) of BCT based on publication year, different research methods, theoretical underpinnings and applicable contexts.Originality/valueTo the best of the authors’ knowledge, this is one of the first attempts to synthesize studies related to BCT in H&T research by combining three theoretical approaches. It serves as a foundation to evaluate the development of BCT studies in this field

Hybrid semantic-document models

This thesis presents the concept of hybrid semantic-document models to aid information management when using standards for complex technical domains such as military data communication. These standards are traditionally text based documents for human interpretation, but prose sections can often be ambiguous and can lead to discrepancies and subsequent implementation problems. Many organisations produce semantic representations of the material to ensure common understanding and to exploit computer aided development. In developing these semantic representations, no relationship is maintained to the original prose. Maintaining relationships between the original prose and the semantic model has key benefits, including assessing conformance at a semantic level, and enabling original content authors to explicitly define their intentions, thus reducing ambiguity and facilitating computer aided functionality. Through the use of a case study method based on the military standard MIL-STD-6016C, a framework of relationships is proposed. These relationships can integrate with common document modelling techniques and provide the necessary functionality to allow semantic content to be mapped into document views. These relationships are then generalised for applicability to a wider context. Additionally, this framework is coupled with a templating approach which, for repeating sections, can improve consistency and further enhance quality. A reflective approach to model driven web rendering is presented and evaluated. This reflective approach uses self-inspection at runtime to read directly from the model, thus eliminating the need for any generative processes which result in data duplication across source used for different purpose

Engineering Blockchain Based Software Systems: Foundations, Survey, and Future Directions

Many scientific and practical areas have shown increasing interest in reaping the benefits of blockchain technology to empower software systems. However, the unique characteristics and requirements associated with Blockchain Based Software (BBS) systems raise new challenges across the development lifecycle that entail an extensive improvement of conventional software engineering. This article presents a systematic literature review of the state-of-the-art in BBS engineering research from a software engineering perspective. We characterize BBS engineering from the theoretical foundations, processes, models, and roles and discuss a rich repertoire of key development activities, principles, challenges, and techniques. The focus and depth of this survey not only gives software engineering practitioners and researchers a consolidated body of knowledge about current BBS development but also underpins a starting point for further research in this field

Cost optimization in requirements management for space systems

2021 Spring.Includes bibliographical references.When producing complex space systems, the transformation of customer needs into a realized system includes the development of product requirements. The ability to generate and manage the requirements can either enable the overall system development or drive significant cost and schedule impacts. Assessing practices in the industry and publications, it is observed that there is a substantial amount of documented approaches to address requirement development and product verification, but only a limited amount of documented approaches for requirements management. A complex system can have tens of thousands of requirements across multiple levels of development which, if not well managed, can lead to hidden costs associated with missed requirements and product rework. With current space system projects being developed at a rapid pace using more cost constrained approaches such as fixed budgets, an investigation into more efficient processes, such as requirements management, can yield methods to enable successful, cost effective system development. To address the optimal approach of managing requirements for complex space systems, this dissertation assesses current practices for requirements management, evaluates various contributing factors towards optimization of project costs associated with this activity, and proposes an optimized requirements management process to utilize during the development of space systems. Four key areas of process control are identified for requirements management optimization on a project, including utilization of a data focused requirements management approach, development (and review) of requirements using a collaborative software application, ensuring the requirement set is a consolidated with an appropriate amount of requirements for the project, and evaluating when to officially levy requirements on the product developers based on requirement maturation stability. Multiple case studies are presented to evaluate if the proposed requirements management process yields improvement over traditional approaches, including a simulation of the current state and proposed requirements management approaches. Ultimately, usage of the proposed optimized set of processes is demonstrated to be a cost effective approach when compared against traditional processes that may adversely impact the development of new space systems