chapter
We hope this will be a panel discussion with a difference. Each of our panel members has been given a scenario description of the world in 2020, significantly different from our own.
chapter
Complex goal oriented information models such as i* and the non functional requirements framework bring up the need to model relationships between goals. In particular when dealing with non-functional goals, also known as softgoals, the modeler faces the problem of how to elicit the complex web of intertwined relationships that exist between them. We tackle this problem by using the personal construct...
chapter
This poster outlines a set of rules to systematically identify crosscutting concerns present in i* models, and modularizing them using aspects. The result is the reduction of the complexity of those models
chapter
Over the past 25 years, user interface designers and usability engineers have studied and refined human-computer interaction techniques with the goal of improving people's productivity and experience. One result is an increasing number of tools designed to help end users build or customize software solutions for a variety of everyday problems - from email filters, to spreadsheet simulations, to interactive...
chapter
The challenges to requirements from linguistic factors are well-known. This work concerns an approach to communicating requirements with greater fidelity among stakeholders through accommodation of cognitive habits and limits. To instantiate this approach, we synthesized linguistic principles into a method to generate high-quality representations of domain concepts to form the base of a project lexicon...
chapter
Summary form only given. The last fifteen years have seen the rise of a new phase in software development which is concerned with the acquisition, modelling and analysis of stakeholder purposes ("goals") in order to derive functional and nonfunctional requirements. The history of ideas and research results for this new phase was reviewed in a RE'04 keynote presentation by Axel van Lamsweerde...
chapter
This paper introduces an information retrieval based approach for automating the detection and classification of non-functional requirements (NFRs). Early detection of NFRs is useful because it enables system level constraints to be considered and incorporated into early architectural designs as opposed to being refactored in at a later time. Candidate NFRs can be detected in both structured and unstructured...
chapter
This paper describes the experiences of the first author in leadership requirements engineering (RE) roles in the developments of two consecutive versions of one software product in one company. The two developments differed in the amounts and the quality of their upfront RE and in their final results. The paper notes a correlation between the quantity and quality of RE and the quality of the final...
chapter
Use case modeling is an effective technique used to capture functional requirements. Use case models are mainly composed of textual descriptions written in natural language and simple diagrams that adhere to a few syntactic rules. This simplicity can be deceptive as many modelers create use case models that are incorrect, inconsistent, and ambiguous and contain restrictive design decisions. In this...
chapter
Feature diagrams (FD) are a family of popular modelling languages used for engineering requirements in software product lines. FD were first introduced by Kang as part of the FODA (feature oriented domain analysis) method back in 1990, Since then, various extensions of FODA FD were devised to compensate for a purported ambiguity and lack of precision and expressiveness. However, they never received...
chapter
In goal-oriented requirements engineering (GORE), one usually proceeds from a goal analysis to a requirements specification, usually of IT systems. In contrast, we consider the use of GORE for the design of IT-enabled value constellations, which are collections of enterprises that jointly satisfy a consumer need using information technology. The requirements analysis needed to do such a cross-organizational...
chapter
We introduce a variability-intensive approach to goal decomposition that is tailored to support requirements identification for highly customizable software. The approach is based on the semantic characterization of OR-decompositions of goals. We first show that each high-level goal can be associated with a set of concerns, in response to which, alternative refinements of the goal can be introduced...
chapter
Aspect-oriented concepts are currently introduced in all phases of the software development life cycle. However, the complexity of interactions among different aspects and between aspects and base entities may reduce the value of aspect-oriented separation of cross-cutting concerns. Some interactions may be intended or may be emerging behavior, while others are the source of unexpected inconsistencies...
chapter
Informal requirements stated in a natural language often suffer from ambiguity, inconsistency, and incompleteness. For these reasons, the trend over the last decade has been towards the development of alternate approaches for specifying requirements such as use cases and requirement modeling languages. However, the growing popularity of model-based development and the increasing power of formal verification...
chapter
Summary form only given. Dr. Young describes how, as "process owner" for the requirements process at Northrop Grumman Information Technology Defense Group, he has advocated for the practices he recommends in his most recent book, Project Requirements: A Guide to Best Practices (Management Concepts, 2006). Dr. Young is frequently asked to provide "initial requirements briefings"...
chapter
The objective of this paper is to report on the challenges and experiences gained during a three years multidisciplinary software development project in the insurance domain, focusing on the employed requirements process. Although, there has been consensus on an agile development process among the project partners, this approach stands in some contrast to the traditional (standardized or regulated)...
chapter
chapter
The following topics were dealt with: requirements engineering; goal-oriented requirements; knowledge-based system; model-based systems; software engineering; and software tools
chapter
Cross-organizational information systems projects, such as ERP, imply an expensive requirements engineering (RE) cycle. Little is known yet about how to carry it out with more predictable alignment results and chances for success. We propose an approach that allows incremental, systematic improvement of cross-organizational RE. It builds on organizational network research, coordination theory, ERP...
chapter
In the last decade, software product management has received much practical attention, though research in this area is still scattered. In this paper, we present a reference framework for software product management, in which the key process areas, namely portfolio management, product roadmapping, release planning and requirements management, are identified, as well as the stakeholders and their relations...
