Imperfect requirements in software development

Authors:
Joost Noppen;Pim Van Den Broek;Mehmet Aksit
Affiliations:
TRESE Software Engineering, Dept. of Computer Science, University of Twente, Enschede, The Netherlands;TRESE Software Engineering, Dept. of Computer Science, University of Twente, Enschede, The Netherlands;TRESE Software Engineering, Dept. of Computer Science, University of Twente, Enschede, The Netherlands
Venue:
REFSQ'07 Proceedings of the 13th international working conference on Requirements engineering: foundation for software quality
Year:
2007

Citing 6
Cited 2

Software requirements: analysis and specification

Software requirements: analysis and specification
The missing link in requirements engineering

ACM SIGSOFT Software Engineering Notes
A bi-level language for software process modeling

Configuration management
The road to the unified software development process

The road to the unified software development process
Structured Design: Fundamentals of a Discipline of Computer Program and Systems Design

Structured Design: Fundamentals of a Discipline of Computer Program and Systems Design
A decision tree solution considering the decision maker's attitude

Fuzzy Sets and Systems

Semantics of trace relations in requirements models for consistency checking and inferencing

Software and Systems Modeling (SoSyM)
Improving efficiency of change impact assessment using graphical requirement specifications: an experiment

PROFES'10 Proceedings of the 11th international conference on Product-Focused Software Process Improvement

Quantified Score

Hi-index	0.00

Visualization

Abstract

Requirement Specifications are very difficult to define. Due to lack of information and differences in interpretation, software engineers are faced with the necessity to redesign and iterate. This imperfection in software requirement specifications is commonly addressed by incremental design. In this paper, we advocate an approach where the imperfect requirements in requirement specifications are modeled by fuzzy sets. By supporting this approach with a requirement tracing and an optimization approach, the necessity for design iteration can be reduced.