Evaluation of Software Requirement Specification Based on IEEE 830 Quality Properties

Abstract

Software requirement specification (SRS) documented an essential requirement of software and its external interface. Many studies found the quality of SRS, but lack of the informality organizing of document and representation of functional requirement. This paper aims to evaluate the quality properties of the software requirement specification (SRS). There are four quality properties to be assessed, which are completeness, correctness, preciseness, and consistency. Completeness quality is used to evaluate the structure of the SRS document; meanwhile, the other three qualities used to evaluate the functional requirement. The measurement for each quality properties has been proposed in the previous study. The evaluation process involves a few stages. In short, the prototype would extract text through the provided document, do a calculation, and came out with the result in the form of a similarity percentage. The prototype designs in such ways it minimizes the user interference. Those resulted in reducing human error. Corpus contains libraries of term and topic are expected to increase the reliability of detection. The corpus includes topics extracted from IEEE 830 standard, vague word, terms represent Create, Read, Update, and Delete (CRUD) operation, and terms denote possible datatype. The extracted functional requirement would be refined based on the Requirement Boilerplate (RB) template. RB adopted in the study to ensure the consistency of functional refinement requirements. The percentage of similarity is determined based on comparison with IEEE 830 standard. The rate of the result of each quality properties reflects the quality of the software requirement specification.

Software Requirement Specification for Learning Man-agement System Design

“…SRS is a formal document that specifies what developers must include in the software they create. SRS will be very beneficial in testing since it can locate documents relevant to user requirements and software controls [12] [13]. The use of SRS has been widely used in previous research, one of which was done by Susilowati et al The goal of this research is to understand the requirements for developing a citizen database information system, which will be accomplished by creating an SRS for a citizen database information system based on ISO/IEC/IEEE 29148-2011 [14].…”