Finding Incorrect and Missing Quality Requirements Definitions Using Requirements Frame

Haruhiko KAIYA  Atsushi OHNISHI  

Publication
IEICE TRANSACTIONS on Information and Systems   Vol.E95-D   No.4   pp.1031-1043
Publication Date: 2012/04/01
Online ISSN: 1745-1361
DOI: 10.1587/transinf.E95.D.1031
Print ISSN: 0916-8532
Type of Manuscript: Special Section PAPER (Special Section on Knowledge-Based Software Engineering)
Category: 
Keyword: 
requirements analysis,  case frame,  quality requirements,  spectrum analysis,  

Full Text: PDF(560.4KB)
>>Buy this Article


Summary: 
Defining quality requirements completely and correctly is more difficult than defining functional requirements because stakeholders do not state most of quality requirements explicitly. We thus propose a method to measure a requirements specification for identifying the amount of quality requirements in the specification. We also propose another method to recommend quality requirements to be defined in such a specification. We expect stakeholders can identify missing and unnecessary quality requirements when measured quality requirements are different from recommended ones. We use a semi-formal language called X-JRDL to represent requirements specifications because it is suitable for analyzing quality requirements. We applied our methods to a requirements specification, and found our methods contribute to defining quality requirements more completely and correctly.