Engineering and Managing Software Requirements
Requirements engineering is the process by which the requirements for software systems are gathered, analyzed, documented, and managed throughout their complete lifecycle. Traditionally it has been concerned with technical goals for, functions of, and constraints on software systems. Aurum and Wohlin, however, argue that it is no longer appropriate for software systems professionals to focus only on functional and non-functional aspects of the intended system and to somehow assume that organizational context and needs are outside their remit. Instead, they call for a broader perspective in order to gain a better understanding of the interdependencies between enterprise stakeholders, processes, and software systems, which would in turn give rise to more appropriate techniques and higher-quality systems.
Following an introductory chapter that provides an exploration of key issues in requirements engineering, the book is organized in three parts. Part 1 presents surveys of state-of-the art requirements engineering process research along with critical assessments of existing models, frameworks and techniques. Part 2 addresses key areas in requirements engineering, such as market-driven requirements engineering, goal modeling, requirements ambiguity, and others. Part 3 concludes the book with articles that present empirical evidence and experiences from practices in industrial projects.
Its broader perspective gives this book its distinct appeal and makes it of interest to both researchers and practitioners, not only in software engineering but also in other disciplines such as business process engineering and management science.
1.5. rezultāts no 5.
Techniques,. Approaches,. and. Tools. Didar Zowghi and Chad Coulin Abstract:
Requirements elicitation is the process of seeking, uncovering, acquiring, and
elaborating requirements for computer based systems. It is generally understood
The intention is to provide an overview of how different techniques and
approaches can be used for each of the requirements elicitation activities, and
which of the commonly used techniques and approaches often employed for
We can see from Table 2.1 above that for each of the requirements elicitation
activities there are a number of suitable techniques and approaches that can be
used. Apart from interviews, domain analysis, and group work, which are generic
the observation of the analyst, the combination of these techniques has the
potential to provide much richer and more detailed requirements information on
both the business processes and the needs of the users. Alternative techniques
Esat sasniedzis šīs grāmatas aplūkošanas reižu limitu.
Lietotāju komentāri - Rakstīt atsauksmi
Specification of Requirements Models
State of the Art and Future
Quality Assurance in Requirements Engineering
The Next Practice in Requirements Engineering 187
MarketDriven Requirements Engineering for Software Products
Requirements Engineering for Agile Methods
Requirements Engineering for WebBased Information Systems
Studies and Industrial Experience
A Case of Developing and Managing
Good Quality Requirements in Unified Process
Studies of Six Companies
An Analysis of Empirical Requirements Engineering Survey
Managing Large Repositories of Natural Language Requirements 219
Understanding Ambiguity in Requirements Engineering
Decision Support in Requirements Engineering
Solutions and Trends