
Requirements Engineering: Foundation for Software Quality
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
More details
Other editions
Additional editions

Content
- Title
- Preface
- Conference Organization
- Table of Contents
- Session 1: Contractual Requirements
- Why the Electronic Land Registry Failed
- Background
- Project History
- Method
- What Caused the Overload?
- Usability and User Interface Requirements
- Architecture and SOA Integration
- Risk Analysis
- Discussion and Conclusion
- References
- Answering a Request for Proposal - Challenges and Proposed Solutions
- Introduction
- Related Work
- Being a Supplier in a Tender Process
- Roles
- Information Responsibilities
- Challenges
- The Workshop
- Proposed Solutions for the Challenges
- Risk Assessment Checklist
- Documentation of the Existing System
- Documentation of the RFP Knowledge
- Conclusion
- References
- Impediments to Requirements-Compliance
- Introduction and Overview of Related Work
- Study Overview
- Impediments to Requirements-Compliance
- Size and Nature of Regulatory Text
- Contractual Complexity
- 'Large-Scale' System
- Conclusions, Implications and Future Work
- References
- Session 2: Quality Requirements
- How Architects See Non-Functional Requirements: Beware of Modifiability
- Introduction
- Conceptual Model
- Survey Description
- Constructs
- Analysis
- Non-Functional Requirements and Project Success
- Approaches and Project Success
- Discussion and Related Work
- Availability Most Business Critical
- Non-Functional Requirements and Project Success
- Approaches and Project Success
- Threats to Validity and Opportunities for Further Research
- Conclusions
- References
- Research Preview: Prioritizing Quality Requirements Based on Software Architecture Evaluation Feedback
- Introduction
- Related Work
- Quality Requirements in Software Architecture Evaluation
- Quality Requirements Prioritization in Research
- Prioritization by Architecture Feedback
- Conclusion
- References
- A Simulation Approach for Impact Analysis of Requirement Volatility Considering Dependency Change
- Introduction
- The DepRVSim Approach
- Requirements Dependency/Traceability Relationship
- Requirements Change Event Generator
- Requirements Change Event Routines
- Case Study
- Project Introduction
- Simulation Scenario and Impact Analysis
- Evaluation of DepRVSim
- Threats to Validity
- Related Work
- Conclusions and Future Work
- References
- Session 3: Collaboration, Complexity and Creativity
- Collaborative Resolution of Requirements Mismatches When Adopting Open Source Components
- Introduction
- Research Background
- Requirements-Components Matching Processes
- Requirements-Components Mismatches Resolution Process
- Research Approach
- Research Questions
- Data Collection and Analysis
- Results
- Projects Description
- RQ1: What Are the General Practices of Requirements Elicitation and OSS Component Selection in OSS Adoption Software Projects?
- RQ2: How Are the Functional Mismatches Between Requirements and OSS Components Collaboratively Managed in OSS Adoption Software Projects?
- RQ3: How Are Non-functional Requirements Fulfilled by Using OSS Components in OSS Adoption Software Projects?
- Discussion
- Threats to Validity
- Summary and Future Works
- References
- High-Level Requirements Management and Complexity Costs in Automotive Development Projects: A Problem Statement
- Today's Requirements Management in Automotive Practice
- Requirements and Costs
- Example
- Extending Traceability
- References
- Choose Your Creativity: Why and How Creativity in Requirements Engineering Means Different Things to Different People
- Introduction
- Method
- Related Work
- A Brief History of Creativity in the Social Sciences
- A Review of Creativity Definitions in RE Literature
- Why and How the Meaning of Creativity Changes
- Contextual Factors
- Dimensions
- Using the Framework
- Discussion
- Conclusion
- References
- Session 4: Requirements Analysis
- Supporting Failure Mode and Effect Analysis: A Case Study with Failure Sequence Diagrams
- Introduction
- Background
- Method
- Research Questions
- Choice of Research Method
- The ANSP Case
- Procedure for Conducting the Case Study
- Data Collection during the Sessions
- Data Collection through Interviews
- Using FSD for Supporting FMEA
- First Session
- Second Session
- Third Session
- Results
- Can FSD Support FMEA?
- How Should the Two Techniques Be Used Together?
- Can FSD Cover the Weakness of FMEA?
- Analysis of the Interview
- Threats to Validity and Reliability
- Discussion
- Sequence Diagrams and Failure Notation
- The System Assessed and Decomposition
- Tool Support
- Conclusion and Further Work
- References
- Aligning Mal-activity Diagrams and Security Risk Management for Security Requirements Definitions
- Introduction
- The ISSRM Domain Model
- Alignment of MAD to ISSRM
- Running Example
- MAD and the ISSRM Domain Model
- Lessons Learnt
- References
- Towards a More Semantically Transparent i* Visual Syntax
- Introduction
- Experiment Plan
- Experiment 1: Production of Drawings
- Experiment 2: Population Stereotype
- Experiment 3: Population Prototype
- Conclusion and Future Work
- References
- Session 5: Templates and Heuristics
- Providing Software Product Line Knowledge to Requirements Engineers - A Template for Elicitation Instructions
- Motivation
- Related Work
- Research Approach
- A Template for Elicitation Instructions
- Requirements on Elicitation Instructions
- Basic Structure
- Single Instructions and Hints
- Implemented Elicitation Strategy
- Evaluation
- Results
- Threats to Validity and Outlook on Controlled Experiment
- Conclusion and Future Work
- References
- Supporting Learning Organisations in Writing Better Requirements Documents Based on Heuristic Critiques
- Introduction
- Related Work
- Experience Based Tools and Learning
- Study: Encoding of New Experience
- Discussion and Outlook
- References
- Managing Implicit Requirements Using Semantic Case-Based Reasoning Research Preview
- Introduction and Motivation
- Related Work
- Semantic CBR for Implicit Requirements
- Model for Implicit Requirement Reuse
- E-Banking Application Example
- Approach Overview
- Discussion and Conclusion
- References
- Session 6: Requirements Traceability
- Trace Queries for Safety Requirements in High Assurance Systems
- Introduction
- Traceability in a Safety Critical Environment
- Illustrative Example
- Fault Tree
- Safety-Related Software Requirements
- Safety Analysis
- Visual Trace Modeling Language (VTML)
- Safety-Related Trace Queries
- Requirement Coverage of all Common Cause Failures
- Integrating Formal Method Results
- Assumptions
- Prototype
- Related Work
- Conclusions
- References
- Which Traceability Visualization Is Suitable in This Context? A Comparative Study
- Introduction
- Foundation
- Traceability Information: What to Visualize
- Visualization Technique: How to Visualize
- Task Context: When to Visualize
- Research Design
- Research Questions
- Research Method
- Research Setup
- Quantitative Results
- Qualitative Results
- Which Visualization Is Suitable in a Particular Task Context?
- What Information Should Be Visualized and How?
- Discussion
- Limitations
- Conclusion
- References
- Session 7: Tools and Quality
- The Case for Dumb Requirements Engineering Tools
- Introduction
- Categories of NL RE Tools
- Scenarios of Tool Use and Their Implications
- Future Research Agenda
- Conclusion
- References
- Automatic Analysis of Multimodal Requirements: A Research Preview
- Introduction
- Background
- Automatic Analysis of Multimodal Requirements
- Discussion and Conclusions
- References
- 10 Myths of Software Quality
- Introduction
- Myths by Category
- Myths about the Relevance of Software Quality
- Myths about Software Quality as an Inconvenience
- Myths about the Notion of Software Quality
- The Myths at a Glance
- Untitled
- References
- Empirical Analysis of the Impact of Requirements Engineering on Software Quality
- Introduction
- Research Approach
- Results
- Threats to Validity
- Conclusions and Future Work
- References
- Session 8: Services and Clouds
- A Systematic Literature Review on Service Description Methods
- Introduction
- Background: Service Description
- Review Methodology
- Defining the Research Questions
- Search and Selection Process
- Study Quality Assessment and Data Collection
- Review Results
- RQ1: Service Description Methods
- RQ2: Problem Faced in Describing Services
- RQ3: Strengths and Weakness of Current Service Description Methods
- Limitations of This Review
- Conclusions and Future Work
- References
- A Pattern-Based Methodf or Identifying and Analyzing Laws
- Introduction
- Pattern-Based Law Analysis
- Structure of Laws, Sections and Dictates of Justice
- A Process for Identifying Relevant Laws
- Related Work
- Conclusions
- References
- Session 9: Self-adaptivity
- Towards a Requirements Modeling Language for Self-Adaptive Systems
- Introduction
- Modeling the Requirements of iComp
- Requirements Modeling with i*
- Requirements Modeling with Adaptive RML
- Definition of Adaptive RML
- Concepts and Relations
- Adaptive RML Visual Notations
- Modeling in Adaptive RML
- Towards Detailed Specification Analysis
- Detailed Specification at Runtime
- Discussion and Related Work
- Conclusion and Future Work
- References
- Requirements Monitoring for Adaptive Service-Based Applications
- Introduction
- Related Work and Baseline
- Requirements Monitoring Framework
- Scenario
- The Framework at Design-Time
- The Framework at Run-Time
- Conclusions and Future Work
- References
- Session 10: Industrial Case Studies
- Release Planning with Feature Trees: Industrial Case
- Introduction
- Background and Motivation
- Feature Trees for Release Planning
- Industrial Case Study
- Study Definition, Planning, and Operation
- Threats to Validity
- Use of Feature Trees for Release Planning
- Discussion and Conclusions
- References
- Goal-Oriented Requirements Engineering and Enterprise Architecture: Two Case Studies and Some Lessons Learned
- Introduction
- Related Work
- Research Methodology
- Definition of ARMOR
- Case Study 1
- Case Description and Research Design
- Observations and Explanations
- Answers to Research Questions
- Validity
- Redesign
- Case Study 2
- Case Description and Research Design
- Observations and Explanations
- Answers to Research Questions
- Validity
- Lessons Learned and Further Work
- References
- Author Index
System requirements
File format: PDF
Copy protection: Watermark-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Use the free software Adobe Reader, Adobe Digital Editions, or any other PDF viewer of your choice (see eBook Help).
- Tablet/Smartphone (Android; iOS): Install the free app Adobe Digital Editions or another reading app for eBooks, e.g., PocketBook (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (only limited: Kindle).
The file format PDF always displays a book page identically on any hardware. This makes PDF suitable for complex layouts such as those used in textbooks and reference books (images, tables, columns, footnotes). Unfortunately, on the small screens of e-readers or smartphones, PDFs are rather annoying, requiring too much scrolling.
This eBook uses Watermark-DRM, a „soft” copy protection. This means that there are no technical restrictions to prevent illegal distribution. However, there is a personalised watermark embedded in the eBook that can be used to identify the purchaser of the eBook in the event of misuse and to provide evidence for legal purposes.
For more information, see our eBook Help page.