Skip to main content

2017 | Buch

Requirements Engineering

verfasst von: Jeremy Dick, BSc (Eng), ACGI, DPhil, DIC, MA, Elizabeth Hull, BSc, PhD, CITP, FBCS, Ken Jackson, BSc, MSc, MBCS

Verlag: Springer International Publishing

insite
SUCHEN

Über dieses Buch

Updated with new developments, ideas and thinking, as well as new tool descriptions, the fourth edition of this popular book is driven by practical experience from industry. It provides invaluable information on how to write and structure requirements, whilst explaining the importance of Systems Engineering and the creation of effective solutions to problems.

This edition contains an expanded discussion of “design agnosticism” as an important principle in Requirements Engineering, and new insights regarding the validation and verification process in the context of the Systems Engineering “V” model. Further new elements include a discussion of SysML in the chapter on modelling techniques, and the use of SysML diagrams to present the generic process. Readers will also discover the latest thinking on requirements flow-down and rich traceability and an update to the chapter on tools to present DOORS Next Generation.

Requirements Engineering is written by practitioners for practitioners and students who want to develop their knowledge of the subject area.

Inhaltsverzeichnis

Frontmatter
Chapter 1. Introduction
Abstract
This chapter provides an overview of the scope of requirements engineering, including a definition of the key terms.  It describes how requirements engineering fits into the wider discipline of systems engineering, and introduces the central concept of traceability.
Jeremy Dick, Elizabeth Hull, Ken Jackson
Chapter 2. A Generic Process for Requirements Engineering
Abstract
This chapter introduces the concept of a process for the development of systems. It starts by examining the way in which systems are developed. This leads to the identification of a development pattern that can be used in many different contexts. This development pattern is expressed as a generic process and is explained in some detail. Subsequent chapters indicate how the generic process can be instantiated for specific purposes. The relationship between process models and information models is also explored and an information model for the generic process is developed.
Jeremy Dick, Elizabeth Hull, Ken Jackson
Chapter 3. System Modelling for Requirements Engineering
Abstract
This chapter introduces system modelling as an important complement to requirements management. System modelling supports the analysis and design process by introducing a degree of formality into the way systems are defined. During system development it is often the case that pictures are used to help visualize some aspects of the development. Modelling provides a way of formalising these representations, through diagrams, by not only defining a standard syntax, but also providing a medium for understanding and communicating the ideas associated with system development.
Jeremy Dick, Elizabeth Hull, Ken Jackson
Chapter 4. Writing and Reviewing Requirements
Abstract
This chapter addresses the discipline of writing requirement statements. Requirements are technical data items, and should be written as such, using concise, uniform language that minimises ambiguity. Where appropriate, the statements should be design agnostic and quantified. How that is achieved is discussed, including the concept of statement-level requirement templates.
Jeremy Dick, Elizabeth Hull, Ken Jackson
Chapter 5. Requirements Engineering in the Problem Domain
Abstract
This chapter addresses requirements in the problem domain – the domain in which a system is going to be used. There is a material difference in the way requirement statements at this level are expressed. The subject of the requirements differs, and the statements are expected to be design-agnostic.
Jeremy Dick, Elizabeth Hull, Ken Jackson
Chapter 6. Requirements Engineering in the Solution Domain
Abstract
This chapter discusses requirements in the solution domain – the domain in which engineers use their ingenuity to solve problems. The primary characteristic that differentiates the solution domain from the problem domain is that, invariably requirements engineering in the solution domain starts with a given set of requirements. In the problem domain requirements engineering starts with a vague objective or wish list. The extent to which the input requirements for the solution domain are “well formed” depends upon the quality of the people within the customer organisation that developed them. In an ideal world, all the requirements would be clearly articulated, individual test able requirements.
Jeremy Dick, Elizabeth Hull, Ken Jackson
Chapter 7. Advanced Traceability
Abstract
This chapter addresses some advanced topics surrounding traceability, in particular the conept of “rich traceability”, where design intent is captured as rationale or narrative. Metrics associated with traceability are also discussed.
Jeremy Dick, Elizabeth Hull, Ken Jackson
Chapter 8. DOORS: A Tool to Manage Requirements
Abstract
This chapter presents a widely used requirements management tool as representative of the features of such tools in general. The nature of requirements management is such that tool support quickly becomes essential, especially in managing, reporting and analysing traceability.
Jeremy Dick, Elizabeth Hull, Ken Jackson
Chapter 9. Management Aspects of Requirements Engineering
Abstract
This chapter addresses the management aspects of requirements engineering, the sorts of activities that have to be persued, the dependences between them, and how to put the theory of requirements engineering into practice.
Jeremy Dick, Elizabeth Hull, Ken Jackson
Erratum to: Requirements Engineering
Jeremy Dick, Elizabeth Hull, Ken Jackson
Backmatter
Metadaten
Titel
Requirements Engineering
verfasst von
Jeremy Dick, BSc (Eng), ACGI, DPhil, DIC, MA
Elizabeth Hull, BSc, PhD, CITP, FBCS
Ken Jackson, BSc, MSc, MBCS
Copyright-Jahr
2017
Verlag
Springer International Publishing
Electronic ISBN
978-3-319-61073-3
Print ISBN
978-3-319-61072-6
DOI
https://doi.org/10.1007/978-3-319-61073-3