Defining quality requirements enough is more difficult than defining functional requirements because stakeholders do not state most of quality requirements explicitly. A method to analyze a requirements specification for identifying the amount of quality requirements in the specification has thus already proposed. However, the method requires human decisions a lot because the method depends only on the occurrences of terms in a specification. An analyst sometimes incorrectly analyzes a specification by using this method. We thus propose an improved method by using analyses records of systems similar to a system to be analyzed. We also developed a supporting tool to enact our method. We expect such analyses records help an analyst to make or skip decision during the method, and the result becomes more correct than before. % We applied our method to several requirements specifications, and found our method contribute to making the result more correct than before without a lot of human effort.
['Haruhiko Kaiya', 'Shunichi Suzuki', 'Toru Ogawa', 'Masaaki Tanigawa', 'Masahiro Umemura', 'Kenji Kaijiri']
Spectrum Analysis for Software Quality Requirements Using Analyses Records