scispace - formally typeset
Open AccessBook

Requirements Engineering: Processes and Techniques

Reads0
Chats0
TLDR
Tried and tested techniques such as data-flow and object-oriented models are covered as well as some promising new ones and are all based on real systems descriptions to demonstrate the applicability of the approach.
Abstract
Requirements Engineering Processes and Techniques Why this book was written The value of introducing requirements engineering to trainee software engineers is to equip them for the real world of software and systems development. What is involved in Requirements Engineering? As a discipline, newly emerging from software engineering, there are a range of views on where requirements engineering starts and finishes and what it should encompass. This book offers the most comprehensive coverage of the requirements engineering process to date - from initial requirements elicitation through to requirements validation. How and Which methods and techniques should you use? As there is no one catch-all technique applicable to all types of system, requirements engineers need to know about a range of different techniques. Tried and tested techniques such as data-flow and object-oriented models are covered as well as some promising new ones. They are all based on real systems descriptions to demonstrate the applicability of the approach. Who should read it? Principally written for senior undergraduate and graduate students studying computer science, software engineering or systems engineering, this text will also be helpful for those in industry new to requirements engineering. Accompanying Website: http: //www.comp.lancs.ac.uk/computing/resources/re Visit our Website: http://www.wiley.com/college/wws

read more

Citations
More filters
Proceedings ArticleDOI

On Non-Functional Requirements

TL;DR: The existing definitions of the term 'non-functional requirement' are surveyed, the problems with the current definitions are discussed, and concepts for overcoming these problems are contributed.
Journal ArticleDOI

Eliciting security requirements with misuse cases

TL;DR: In this article, a systematic approach to eliciting security requirements based on use cases, with emphasis on description and method guidelines, is presented, which extends traditional use cases to also cover misuse, and is potentially useful for several other types of extra-functional requirements beyond security.
Journal ArticleDOI

Security Requirements Engineering: A Framework for Representation and Analysis

TL;DR: The framework is based on constructing a context for the system, representing security requirements as constraints, and developing satisfaction arguments for the security requirements, and is evaluated by applying it to a security requirements analysis within an air traffic control technology evaluation project.
Book ChapterDOI

Requirements Elicitation: A Survey of Techniques, Approaches, and Tools

Didar Zowghi, +1 more
TL;DR: The objectives of this chapter are to present a comprehensive survey of important aspects of the techniques, approaches, and tools for requirements elicitation, and examine the current issues, trends, and challenges faced by researchers and practitioners in this field.
Journal ArticleDOI

Understanding the requirements for developing open source software systems

TL;DR: Eight kinds of software informalisms are found to play a critical role in the elicitation, analysis, specification, validation and management of requirements for developing open software systems, and this focus enables the consideration of a reformulation of the requirements engineering process and its associated artefacts, or (in)formalisms, to better account for the requirements for developed open source software systems.