Modelling and engineering the requirements engineering process: An overview of the NATURE approach

This paper presents an overview of the process theory developed in the context of the ESPRIT project NATURE.¹ This theory proposes means for modelling and engineering the requirements engineering (RE) process. The key element of this theory is a situation-and decision-based process meta-model independent of any RE methodology. The process meta-model acts as a shell for defining process models by instantiation. An enactment mechanism implemented in a tool environment has been defined. It allows execution of process models and provides effective guidance to the requirements engineer. Construction of process models is also supported based on generic method knowledge chunks. The formalization of our approach is based on a free algebra.     

A requirements engineering environment within a tightly integrated SDE

This paper describes the outside functionality of an RE environment within an integrated software development environment. Furthermore, an integrator tool for the transition to software system architecture modelling is presented. The tools discussed are editors, analysers, executors, monitors, and integration tools of different characteristics for horizontal integration (within RE) and vertical integration (to architecture modelling). All tools are tightly integrated and work incrementally, therefore allowing different forms of construction and modification processes and giving substantial support.     

Integration of behavioural requirements specification within compositional knowledge engineering

In this paper it is shown how specification of behavioural requirements from informal to formal can be integrated within knowledge engineering. The integration of requirements specification has addressed, in particular: the integration of requirements acquisition and specification with ontology acquisition and specification, the relations between requirements specifications and specifications of task models and problem solving methods, and the relation of requirements specification to verification.     

需求工程的探讨

软件工程被分为需求、设计、实现、测试等几个阶段,其中需求阶段是一个项目的开端,也是项目成功的基石。在软件工程中,需求分析指的是在建立一个新的或改变一个现存的电脑系统时描写新系统的目的、范围、定义和功能时所要做的所有的工作。需求分析是软件工程中的一个关键过程。在这个过程中,系统分析员和软件工程师确定顾客的需要。只有在确定了这些需要后他们才能够分析和寻求新系统的解决方法。在软件工程的历史中,很长时间里人们一直认为需求分析是整个软件工程中最简单的一个步骤,但在过去十年中越来越多的人认识到它是整个过程中最关键的一个过程。假如在需求分析时分析者们未能正确地认识到顾客的需要的话,那么最后的软件实际上不可能达到顾客的需要,或者软件无法在规定的时间里完工。     

CONCENSUS: multi-party negotiation support for conflict resolution in concurrent engineering design

Advances in telematics have led many manufacturing companies in particular to explore the adoption of groupware technology to improve communication between team members. However, complex activities such as conflict resolution are still predominantly facilitated through face-to-face negotiation meetings. Intelligent software agents technology is being applied to support computer-mediated conflict resolution activities, such as information search and retrieval, recording negotiation process history and task allocation – whilst the creative negotiation activities such as generating new solutions, preventing and detecting conflicts are still left to the human experts. This paper describes the development of a framework for the support of multi-party negotiation for multi-agent systems, which will be introduced through a general overview of the requirements of multi-agent negotiation. Finally, the current architecture of the developed prototype for a CONCurrent Engineering Negotiation SUpport System (CONCENSUS) is presented.     

A requirements engineering process for control engineering software

This paper presents a novel approach for the specification of control engineering software. The proposal is based on software engineering techniques which have improved the performance and quality of software processes. Some of the best practices for the building of software products are included. An example of the proposal is given for the requirements specification of the 1992 ACC robust control benchmark.     

Managing the requirements engineering process

Process management is a crucial issue in developing information or computer systems. Theories of software development process management suggest that the process should be supported and managed based on what the process really is. However, our learning from an action research study reveals that the requirements engineering (RE) process differs significantly from that which the current literature tends to describe. The process is not a systematic, smooth and incremental evolution of the requirements model, but involves occasional simplification and restructuring of the requirements model. This revised understanding of the RE process suggests a new challenge to both the academic and industrial communities, demanding new process management approaches. In this paper, we present our understanding of the RE process and its implications for process management.     

Relationship analysis in requirements engineering

This research addresses a major shortcoming in todays requirements analysis techniques—the lack of a rigorous and comprehensive process to explicitly capture the relationship structure of the problem domain. Whereas other analysis techniques lightly address the relationship discovery process, relationship analysis (RA) is a systematic, domain-independent analysis technique focusing exclusively on a domains relationship structure. This paper describes RAs taxonomy of relationship types and corresponding brainstorming questions for eliciting the relationship structure from a domain expert. A preliminary case study analysis of online bookstores using RA as well as a formal experiment have both confirmed RAs effectiveness in helping the analyst produce significantly higher quality requirements. RA should become an invaluable tool for analysts, irrespective of the software engineering approach taken during systems analysis.     

Contextualization as an independent abstraction mechanism for conceptual modeling

The notion of context appears in computer science, as well as in several other disciplines, in various forms. In this paper, we present a general framework for representing the notion of context in information modeling. First, we define a context as a set of objects, within which each object has a set of names and possibly a reference: the reference of the object is another context which “hides” detailed information about the object. Then, we introduce the possibility of structuring the contents of a context through the traditional abstraction mechanisms, i.e., classification, generalization, and attribution. We show that, depending on the application, our notion of context can be used as an independent abstraction mechanism, either in an alternative or a complementary capacity with respect to the traditional abstraction mechanisms. We also study the interactions between contextualization and the traditional abstraction mechanisms, as well as the constraints that govern such interactions. Finally, we present a theory for contextualized information bases. The theory includes a set of validity constraints, a model theory, as well as a set of sound and complete inference rules. We show that our core theory can be easily extended to support embedding of particular information models in our contextualization framework.     

Qualitative design support for engineering and architecture

Conventional design support software tools cannot effectively manage the complex, heterogeneous information used in engineering and architecture (EA) tasks. Crucially, despite uncertainty being an inherent quality of EA information particularly in the early stages of a design project, current tools solely rely on numerical approaches which do not support such incomplete and vague information. In this paper, we establish a complete framework for developing qualitative support tools that directly address these shortcomings. Our framework is application oriented and addresses the broader issues surrounding the actual use of qualitative methods. It provides design principles and strategies that allow a software engineer to develop custom qualitative software tools according to their specific EA task specifications. Our framework also provides the engineer with practical theory and guidelines for implementing their custom qualitative model and validating their system using context specific test data. We demonstrate the validity of our framework by presenting a case study in architectural lighting in which a prototype qualitative reasoning engine successfully automates qualitative logic about the subjective impressions of a lighting installation.     

Agile requirements engineering via paraconsistent reasoning

Innovative companies need an agile approach towards product and service requirements, to rapidly respond to and exploit changing conditions. The agile approach to requirements must nonetheless be systematic, especially with respect to accommodating legal and non-functional requirements. This paper examines how to support lightweight, agile requirements processes which can still be systematically modeled, analyzed and changed. We propose a framework, RE-KOMBINE, which is based on a propositional language for requirements modeling called Techne. We define operations on Techne models which tolerate the presence of inconsistencies. This paraconsistent reasoning is vital for supporting delayed commitment to particular design solutions. We evaluate these operations with an industry case study using two well-known formal analysis tools. Our evaluations show that the proposed framework scales to industry-sized requirements model, while still retaining (via propositional logic) the informality that is so useful during early requirements analysis.     

Complexity classification in qualitative temporal constraint reasoning

We study the computational complexity of the qualitative algebra which is a temporal constraint formalism that combines the point algebra, the point-interval algebra and Allen's interval algebra. We identify all tractable fragments and show that every other fragment is NP-complete.     

A conceptual framework for requirements engineering

A framework for assessing research and practice in requirements engineering is proposed. The framework is used to survey state of the art research contributions and practice. The framework considers a task activity view of requirements, and elaborates different views of requirements engineering (RE) depending on the starting point of a system development. Another perspective is to analyse RE from different conceptions of products and their properties. RE research is examined within this framework and then placed in the context of how it extends current system development methods and systems analysis techniques.     

Scenario advisor tool for requirements engineering

This study investigates the usefulness of a scenario advisor tool which was built to help requirements engineers to generate sufficient sets of scenarios in the domain of socio-technical systems. The tool provides traceability between scenario models and requirements and helps to generate new scenarios and scenario variations. Through two series of evaluation sessions, we found that the scenario advisor tool helped users to write more sound scenarios without any domain knowledge, and to generate more variations on existing scenarios by providing specific scenario-generation hints for each scenario component. The tool should improve the reliability of requirements elicitation and validation.     

MOQARE: misuse-oriented quality requirements engineering

This work presents MOQARE (misuse-oriented quality requirements engineering), a method to explore quality requirements. The aim of MOQARE is to support intuitive and systematic identification of quality requirements. It was developed by integrating and adapting concepts from other methods (like Misuse Cases). It provides a general conceptual model of quality requirements, and a checklist-based process for deriving them in a top-down fashion. This derivation starts from business goals and vague quality requirements and delivers detailed requirements. MOQARE applies to requirements on the system to be developed requirements, but also derives requirements on the development process, including administration and maintenance. It considers normal and extreme use. The relationships among these requirements are modeled in a Misuse Tree. MOQARE has shown its merits in several case studies, one of which is presented here.     

Immersive stereo displays,intuitive reasoning,and cognitive engineering

Abstract— Stereoscopic displays have generated great interest in the display community in recent years. Despite this interest, there can be a problem with their use when such displays contain high‐level cue conflict, which refers to multiple cues conveying different depths to a viewer, creating “eye” strain and discomfort. It can be argued that the basis for this discomfort is to be found in the mental processes of human reasoning. Specifically, immersive stereo displays that depict real‐world scenes primarily engage an intuitive reasoning system, which attempts (and fails) to make reasoned sense out of conflicting perceptual information. Because not all displays have the potential to create this problem, it is proposed that information displays be subdivided into two types: analytical reasoning‐inducing displays and intuitive reasoning‐inducing displays. All information displays, even stereo displays, involve issues of cognitive engineering.     

Human software requirements engineering for computer-controlled manufacturing systems

Computers as integral systems components determine the quality of work of operators in industrial production. This paper contributes to improving the design of man-machine systems by proposing a formal aid to human software requirements definition and design. First, the need for considering human requirements is stressed. Since technology is to be considered as ‘non-deterministic’, the designer is faced with a degree of freedom in his design decisions which can be and should be utilized for raising the quality of work of people operating computer-controlled man-machine systems. Then, a hierarchy of human quality criteria applicable for ergonomic judgement of work design measures is derived. Following the principle of prospective work design, these criteria must be considered as design goals just like technical and economic requirements. As a formal aid for making design decisions meeting these comprehensive requirements, the Requirements/Quality Criteria Matrix is proposed. Finally, this method of considering human requirements is illustrated by designing some man-machine interface features for operators of a hypothetical flexible manufacturing system.     

A requirements engineering framework for cross-organizational ERP systems

The development of cross-organizational enterprise resource planning (ERP) solutions is becoming increasingly critical to the business strategy of many networked companies. The major function of cross-organizational ERP solutions is to coordinate work in two or more organizations. However, how to align ERP application components and business requirements for coordination and cooperation is hardly known. This paper reports on the outcomes of applying a coordination theory perspective to an analysis of the ERP misalignment problem. We present a conceptual framework for analyzing coordination and cooperation requirements in inter-organizational ERP projects. The framework makes explicit the undocumented built-in assumptions for coordination and cooperation that may have significant implications for the ERP adopters and incorporates a library of existing coordination mechanisms supported by modern ERP systems. We use it to develop a proposal for how to achieve a better alignment between ERP implementations and supported business coordination processes in inter-organizational settings. We report on some early assessments of the implications of our framework for practicing requirements engineers. Both our framework and library rest on a literature survey and the first author’s experience with ERP implementation. In future empirical research, we will further validate and refine our framework.