Cite Article

Evaluation of Software Requirement Specification Based on IEEE 830 Quality Properties

Choose citation format

BibTeX

@article{IJASEIT10186,
   author = {E. Stephen and E. Mit},
   title = {Evaluation of Software Requirement Specification Based on IEEE 830 Quality Properties},
   journal = {International Journal on Advanced Science, Engineering and Information Technology},
   volume = {10},
   number = {4},
   year = {2020},
   pages = {1396--1402},
   keywords = {quality properties; quantitative approach; requirement engineering; software requirement specification.},
   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.

},    issn = {2088-5334},    publisher = {INSIGHT - Indonesian Society for Knowledge and Human Development},    url = {http://ijaseit.insightsociety.org/index.php?option=com_content&view=article&id=9&Itemid=1&article_id=10186},    doi = {10.18517/ijaseit.10.4.10186} }

EndNote

%A Stephen, E.
%A Mit, E.
%D 2020
%T Evaluation of Software Requirement Specification Based on IEEE 830 Quality Properties
%B 2020
%9 quality properties; quantitative approach; requirement engineering; software requirement specification.
%! Evaluation of Software Requirement Specification Based on IEEE 830 Quality Properties
%K quality properties; quantitative approach; requirement engineering; software requirement specification.
%X 

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.

%U http://ijaseit.insightsociety.org/index.php?option=com_content&view=article&id=9&Itemid=1&article_id=10186 %R doi:10.18517/ijaseit.10.4.10186 %J International Journal on Advanced Science, Engineering and Information Technology %V 10 %N 4 %@ 2088-5334

IEEE

E. Stephen and E. Mit,"Evaluation of Software Requirement Specification Based on IEEE 830 Quality Properties," International Journal on Advanced Science, Engineering and Information Technology, vol. 10, no. 4, pp. 1396-1402, 2020. [Online]. Available: http://dx.doi.org/10.18517/ijaseit.10.4.10186.

RefMan/ProCite (RIS)

TY  - JOUR
AU  - Stephen, E.
AU  - Mit, E.
PY  - 2020
TI  - Evaluation of Software Requirement Specification Based on IEEE 830 Quality Properties
JF  - International Journal on Advanced Science, Engineering and Information Technology; Vol. 10 (2020) No. 4
Y2  - 2020
SP  - 1396
EP  - 1402
SN  - 2088-5334
PB  - INSIGHT - Indonesian Society for Knowledge and Human Development
KW  - quality properties; quantitative approach; requirement engineering; software requirement specification.
N2  - 

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.

UR - http://ijaseit.insightsociety.org/index.php?option=com_content&view=article&id=9&Itemid=1&article_id=10186 DO - 10.18517/ijaseit.10.4.10186

RefWorks

RT Journal Article
ID 10186
A1 Stephen, E.
A1 Mit, E.
T1 Evaluation of Software Requirement Specification Based on IEEE 830 Quality Properties
JF International Journal on Advanced Science, Engineering and Information Technology
VO 10
IS 4
YR 2020
SP 1396
OP 1402
SN 2088-5334
PB INSIGHT - Indonesian Society for Knowledge and Human Development
K1 quality properties; quantitative approach; requirement engineering; software requirement specification.
AB 

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.

LK http://ijaseit.insightsociety.org/index.php?option=com_content&view=article&id=9&Itemid=1&article_id=10186 DO - 10.18517/ijaseit.10.4.10186