![Quality Assurance in Requirement Engineering
Uzma Noorin α
& Mehreen Sirshar σ
Abstract- Requirement engineering is the most important
process in software development life cycle. Quality assurance
in requirement engineering has a great impact on the product
quality. It checks whether the requirements meet the desired
quality attributes i.e. adequacy, completeness, consistency
etc. Quality Assurance of the requirement is important
because the cost of requirements failure is very high. The
proposed research is based on the survey of the quality
assurance in requirement engineering. The major focus of this
research paper is to analyze the quality parameters which
assure the overcome of the issues related to the requirements.
The research papers include brief overview of those
parameters.
Keywords: requirement engineering, quality assurance,
models, artifact -based requirements, TSLA, laquso.
I. Introduction
uality Assurance ensures that the product
manufactured is without defects. For this, the
quality of the requirements should be fulfilled.
Quality Assurance must be done in requirement engine-
ering process, so that the most valuable requirements
should be added. The Quality Assurance of Require-
ments is much important, as it is said by Boehm and
Basili;
“Finding and fixing a software problem after
delivery is often 100 times more expensive than finding
and fixing it during the requirements and design phase.”
This research work is based on a survey related
to the quality assurance in requirement engineering. The
analysis of different on the perspective of different rese-
arch paper is done using different parameters like qua-
lity, feasibility, maintainability, understanding, reusability
etc. Each research paper has its own perspective to
verify the quality of requirements. The evaluation criteria
are given in the TABLE 1, for comparing effects of differ-
rent parameters that are discuss in analysis. Brief sum-
aries of each survey papers are also mentioned below.
II. Experiences on Analysis of
Requirements Quality [1]
Requirement engineering is the most important
and critical process in the software development life
cycle. The quality of the system depends on the quality
of requirements that are difficult to recognize in require-
ments development phase but it has a great impact on
the product quality. This paper proposed a method
known as LaQuSo Software Product Certification Model
for certifying the quality of requirements specification.
This method explains three different certification criteria
for all product areas; Completeness of the required
elements, Uniformity of the product area should be with
respect to standards, Conformance of the elements
should be according to the property that is subject of
the certification. These all criteria focus on the
verification of the requirements.
III. Assessing the Quality of Software
Requirement Specification [2]
In the initial stage it is difficult to determine whe-
ther the SRS will provide the final product. So, a quality
model is needed known as Goal-Question-Matric (GQM)
method. This paper gives the outline of researchers plan
related to GQM, their findings, and finally proves that
their quality assessment helps in the project success.
IV. Improvement of Quality of Software
Requirements with Requirements
Ontology [3]
Requirements elicitation is the most difficult task
in requirement engineering. The quality and the quantity
of elicit requirements depend on both analysts ability
and his domain knowledge of the target system. This
paper helps in the improvement of quality and quantity
of the elicit requirements using requirements ontology
model. This paper checks the correctness, complete-
ness and quality of the requirements.
V. Applying Case-based Reasoning to
Software Requirements Specifications
Quality Analysis System [4]
This paper focuses on the quality of the prepare
software requirement specification. The technique used
is Software Quality Assurance audit to check whether
the required standards and procedures within this phase
are followed or not. This technique checks whether the
requirements are complete, modifiable, consistent, ran-
ked, correct, unambiguous, understandbleandtraceable.
The case-based Reasoning technique is used to check
the quality of requirements with respect to the previous
quality based cases.
Q
Global
Journal
of
Computer
Science
and
Technology
Volume
XVII
Issue
I
Version
I
1
Year
2017
(
)
C
Author α σ: Software Engineering Department. Fatima Jinnah Women
University, Rawalpindi. e-mails: Uzmakhattak63@yahoo.com,
msirshar@gmail.com
© 2017 Global Journals Inc. (US)](https://image.slidesharecdn.com/lecturew7aqainre-210418071442/85/QA-in-RE-2-320.jpg)
![Requirement engineering process is volatile.
This paper developed a model that support the new
artifact based philosophy. This approach helps in the
improvements in syntactic and the semantic quality of
created artifacts. This approach defines the reference
model of the artifacts for development process. This
paper also showed the increase in the completeness
and consistency of artifact and also their flexibility.
VII. What you Need is What you Get! the
Vision of View-based Requirements
Specifications [6]
This paper worked on the improvement of high
quality SRS that fit the particular requests for progre-
ssive record stakeholders. For the quality of require-
ments, its data and the system function and interaction,
viewpoints of architectural experts, goals description
and technical requirements are most important arte-
facts.
VIII. Defects in Natural Language
Requirement Specifications at
Mercedes-Benz: an Investigation
using Acombination of Legacy Data
and Expert Opinion [7]
This paper works on the study of natural
language of Software Requirement Specification. With
respect to the quality model, the results obtained are:
defect in natural language of SRS in automotive domain;
for defect extremity, the associations of quality para-
meters; signs on the handling quality parameters; time
needed information for defect association on the basis
of quality parameters. The results ensure that the impor-
tant quality parameters in investigated NL parameters
are completeness, consistency and correctness.
IX. Foreword Quality in Agile Methods
[8]
This paper worked on many different methods
and views related to the quality of agile methods. The
discoveries of these investigations assist developers,
researchers and managers, in this agile method field.
The discoveries are made to understand how to reduce
the issues of quality while working on this method.
X. A Framework of Software
Requirements Quality Analysis System
using Case-based Reasoning and Neural
Network [9]
This paper worked in the improvement of quality
analysis process of Software Requirement Specification.
It ensures that the Software Requirement Specification
document must have some standards. Further, the
analysis of SRS qualityis done by using Neural Network
(ANN) and CBR techniques.CBR works in the impro-
vement of quality by the reference of past experiences.
ANN also works with CBR.
XI. A Process Improvement in
Requirement Verification and
Validation using Ontology [10]
After developing the system, the verification and
validation is always done but still there are issues of
stakeholders in different domains. The problem arises in
the verification and validation of requirement which are
difficult activities in requirement engineering. This paper
works on removing the conflicts of requirements, their
consistencies and recognizing the failure due to
requirements. These goals are achieved by ontology
which is also used for the verification and validation of
requirements.
XII. It’s the Activities, Stupid! a New
Perspective on Re Quality [11]
Requirement engineering is the important pro-
cess in System Development. Its Quality must be ensu-
red for testing, development and other software active-
ties. This paper introduces a context-specific Require-
ment Engineering artifacts Quality and explain how the
quality parameters of RE artefacts affect the activities of
development.
XIII. Software Quality Control Via exit
Criteria Methodology: An Industrial
Experience Report [12]
This paper introduces the Exit Criteria Metho-
dology. This methodology helps in vast financial
systems to improve the quality of the system from the
beginning of a SCRUM sprint to the end. As a whole-
process control of quality, the methodology is executed
from the quality plan to the quality review.
XIV. Quality Assessment Method for
Software Requirements Specifications
based on Document characteristics
and Its Structure [13]
In this research it is presented that in software
development process quality of SRS should be main-
tained. For this process different assessment methods
are used by keeping in mind the three characteristics of
SRS unambiguous variable and modifiable because it is
necessary to satisfy the customers.
VI. A Case Study on The Application of
An Artefact-based Requirements
Engineering Approach [5]
Global
Journal
of
Computer
Science
and
Technology
Volume
XVII
Issue
I
Version
I
2
Year
2017
(
)
C
© 2017 Global Journals Inc. (US)
1
Quality Assurance in Requirement Engineering](https://image.slidesharecdn.com/lecturew7aqainre-210418071442/85/QA-in-RE-3-320.jpg)
![XV. Security Assurance Requirements
Engineering (stare) for Trustworthy
Service level Agreements [14]
In this research through two case studies it is
discussed that how STARE is effective in real world by
evaluating that STARE from different techniques and
easement criteria and how TSLA can be used to achieve
TSLA can be used to achieve the trust worthless service.
XVI. Does Quality of Requirements
Specifications Matter? Combined
Results of Two Empirical Studies [15]
Quality of SRS depends on efficient and effecti-
veness of quality assurance and by two correlations it is
proved that SRS is less used for communication beca-
use of it defects. In future it is necessary to document
SRS on certain degree.
XVII. Naming the Pain in Requirements
Engineering [16]
This paper explains that for better quality
requirements, human interaction is important for
elicitation regardless of project type and company size.
For this standard process models and certifiable impro-
vement standards are used. There is not necessary to
use agile or non-agile methods for better quality. It is
actually the way to solve the problems. The problem
itself manifest in different ways.
XVIII. Quality Assurance of Component
based Software Systems [17]
On this latest technology our software’s and
web based applications are more complicated and with
complex coding. Quality Assurance also maintains and
reduces more work effort and also helps organization to
develop application in the right path from the initial
stage to the ending point.
XIX. Assessing the Quality of Software
Requirements Specifications for
Automotive Software Systems [18]
In this paper we conclude that SRS can be
depend on the software or application we need to
develop. There some types of SRS std. IEEE 830 to
1998. Several standards organizations including the
IEEE have identified some points during designing and
writing an SRS; Interfaces, Functional Capabilities,
Performance Levels, Data Structures/Elements, Safety,
Reliability, Security/Privacy, Quality, Constraints and
Limitations.
ding to experts Q. A reduce 50% effort in final stage. It
also helps developers and also help to track any bug.
By applying all Q.A methodology you can also improve
your application efficiency.
XXI. How Artifacts Support and Impede
Requirements Communication [20]
In this we collect information from different
recourses that artificial mapping is not suitable for all
types of project because in some cases it will be costly
according to other, it should be suitable for linking
bases modules.
XXII. Analysis of Quality Parameters for
Requirements
a) Feasibility
The requirements must be feasible in
perspective of the financial plan, timetable, and
innovation limitations
b) Comprehensibility
The definition of requirements must be
intelligible by the general population who need to utilize
them.
c) Good Structuring
The document of the requirements ought to be
composed as it were that highlights the auxiliary
connections among its components
d) Modifiability
It ought to be conceivable to change, adjust,
develop, or contract the document of the requirements
through adjustments that are as nearby as could
reasonably be expected
e) Traceability
The setting in which a thing of the requirements
archive was made, adjusted, or utilized ought to be
anything but difficult to recover. Such setting ought to
incorporate the method of reasoning for creation,
adjustment, or utilize.
f) Efficiency
The requirements should be efficient that is they
must fulfill the functionality and they also help in
increasing the performance of the product.
g) Correctness
The requirements that are going to be
implemented must be correct. They must be related to
the functionality of the product.
Global
Journal
of
Computer
Science
and
Technology
Volume
XVII
Issue
I
Version
I
3
Year
2017
(
)
C
XX. A Quality Assurance Model for
Analysis Phase [19]
According to my opinion Q.A is most important
part it plays as a back bone of any application. Accor
h) Completeness
The requirements that are going to
implemented must be complete.
XXIII. Conclusion
The paper discusses different factors to
improve the quality of the product from the initial stage
Quality Assurance in Requirement Engineering
© 2017 Global Journals Inc. (US)](https://image.slidesharecdn.com/lecturew7aqainre-210418071442/85/QA-in-RE-4-320.jpg)
QA in RE
- 1. Uzma Noorin & Mehreen Sirshar. This is a research/review paper, distributed under the terms of the Creative Commons Attribution-Noncommercial 3.0 Unported License http://creativecommons.org/licenses/by-nc/3.0/), permitting all non-commercial use, distribution, and reproduction inany medium, provided the original work is properly cited. Quality Assurance in Requirement Engineering By Uzma Noorin & Mehreen Sirshar Fatima Jinnah Women University Abstract- Requirement engineering is the most important process in software development life cycle. Quality assurance in requirement engineering has a great impact on the product quality. It checks whether the requirements meet the desired quality attributes i.e. adequacy, completeness, consistency etc. Quality Assurance of the requirement is important because the cost of requirements failure is very high. The proposed research is based on the survey of the quality assurance in requirement engineering. The major focus of this research paper is to analyze the quality parameters which assure the overcome of the issues related to the requirements. The research papers include brief overview of those parameters. Keywords: requirement engineering, quality assurance, models, artifact -based requirements, TSLA, laquso. GJCST-C Classification: B.8.1, D.2.5 QualityAssuranceinRequirementEngineering Strictly as per the compliance and regulations of: Online ISSN: 0975-4172 & Print ISSN: 0975-4350 Publisher: Global Journals Inc. (USA) Type: Double Blind Peer Reviewed International Research Journal Volume 17 Issue 1 Version 1.0 Year 2017 Software & Data Engineering Global Journal of Computer Science and Technology: C © 2017.
- 2. Quality Assurance in Requirement Engineering Uzma Noorin α & Mehreen Sirshar σ Abstract- Requirement engineering is the most important process in software development life cycle. Quality assurance in requirement engineering has a great impact on the product quality. It checks whether the requirements meet the desired quality attributes i.e. adequacy, completeness, consistency etc. Quality Assurance of the requirement is important because the cost of requirements failure is very high. The proposed research is based on the survey of the quality assurance in requirement engineering. The major focus of this research paper is to analyze the quality parameters which assure the overcome of the issues related to the requirements. The research papers include brief overview of those parameters. Keywords: requirement engineering, quality assurance, models, artifact -based requirements, TSLA, laquso. I. Introduction uality Assurance ensures that the product manufactured is without defects. For this, the quality of the requirements should be fulfilled. Quality Assurance must be done in requirement engine- ering process, so that the most valuable requirements should be added. The Quality Assurance of Require- ments is much important, as it is said by Boehm and Basili; “Finding and fixing a software problem after delivery is often 100 times more expensive than finding and fixing it during the requirements and design phase.” This research work is based on a survey related to the quality assurance in requirement engineering. The analysis of different on the perspective of different rese- arch paper is done using different parameters like qua- lity, feasibility, maintainability, understanding, reusability etc. Each research paper has its own perspective to verify the quality of requirements. The evaluation criteria are given in the TABLE 1, for comparing effects of differ- rent parameters that are discuss in analysis. Brief sum- aries of each survey papers are also mentioned below. II. Experiences on Analysis of Requirements Quality [1] Requirement engineering is the most important and critical process in the software development life cycle. The quality of the system depends on the quality of requirements that are difficult to recognize in require- ments development phase but it has a great impact on the product quality. This paper proposed a method known as LaQuSo Software Product Certification Model for certifying the quality of requirements specification. This method explains three different certification criteria for all product areas; Completeness of the required elements, Uniformity of the product area should be with respect to standards, Conformance of the elements should be according to the property that is subject of the certification. These all criteria focus on the verification of the requirements. III. Assessing the Quality of Software Requirement Specification [2] In the initial stage it is difficult to determine whe- ther the SRS will provide the final product. So, a quality model is needed known as Goal-Question-Matric (GQM) method. This paper gives the outline of researchers plan related to GQM, their findings, and finally proves that their quality assessment helps in the project success. IV. Improvement of Quality of Software Requirements with Requirements Ontology [3] Requirements elicitation is the most difficult task in requirement engineering. The quality and the quantity of elicit requirements depend on both analysts ability and his domain knowledge of the target system. This paper helps in the improvement of quality and quantity of the elicit requirements using requirements ontology model. This paper checks the correctness, complete- ness and quality of the requirements. V. Applying Case-based Reasoning to Software Requirements Specifications Quality Analysis System [4] This paper focuses on the quality of the prepare software requirement specification. The technique used is Software Quality Assurance audit to check whether the required standards and procedures within this phase are followed or not. This technique checks whether the requirements are complete, modifiable, consistent, ran- ked, correct, unambiguous, understandbleandtraceable. The case-based Reasoning technique is used to check the quality of requirements with respect to the previous quality based cases. Q Global Journal of Computer Science and Technology Volume XVII Issue I Version I 1 Year 2017 ( ) C Author α σ: Software Engineering Department. Fatima Jinnah Women University, Rawalpindi. e-mails: Uzmakhattak63@yahoo.com, msirshar@gmail.com © 2017 Global Journals Inc. (US)
- 3. Requirement engineering process is volatile. This paper developed a model that support the new artifact based philosophy. This approach helps in the improvements in syntactic and the semantic quality of created artifacts. This approach defines the reference model of the artifacts for development process. This paper also showed the increase in the completeness and consistency of artifact and also their flexibility. VII. What you Need is What you Get! the Vision of View-based Requirements Specifications [6] This paper worked on the improvement of high quality SRS that fit the particular requests for progre- ssive record stakeholders. For the quality of require- ments, its data and the system function and interaction, viewpoints of architectural experts, goals description and technical requirements are most important arte- facts. VIII. Defects in Natural Language Requirement Specifications at Mercedes-Benz: an Investigation using Acombination of Legacy Data and Expert Opinion [7] This paper works on the study of natural language of Software Requirement Specification. With respect to the quality model, the results obtained are: defect in natural language of SRS in automotive domain; for defect extremity, the associations of quality para- meters; signs on the handling quality parameters; time needed information for defect association on the basis of quality parameters. The results ensure that the impor- tant quality parameters in investigated NL parameters are completeness, consistency and correctness. IX. Foreword Quality in Agile Methods [8] This paper worked on many different methods and views related to the quality of agile methods. The discoveries of these investigations assist developers, researchers and managers, in this agile method field. The discoveries are made to understand how to reduce the issues of quality while working on this method. X. A Framework of Software Requirements Quality Analysis System using Case-based Reasoning and Neural Network [9] This paper worked in the improvement of quality analysis process of Software Requirement Specification. It ensures that the Software Requirement Specification document must have some standards. Further, the analysis of SRS qualityis done by using Neural Network (ANN) and CBR techniques.CBR works in the impro- vement of quality by the reference of past experiences. ANN also works with CBR. XI. A Process Improvement in Requirement Verification and Validation using Ontology [10] After developing the system, the verification and validation is always done but still there are issues of stakeholders in different domains. The problem arises in the verification and validation of requirement which are difficult activities in requirement engineering. This paper works on removing the conflicts of requirements, their consistencies and recognizing the failure due to requirements. These goals are achieved by ontology which is also used for the verification and validation of requirements. XII. It’s the Activities, Stupid! a New Perspective on Re Quality [11] Requirement engineering is the important pro- cess in System Development. Its Quality must be ensu- red for testing, development and other software active- ties. This paper introduces a context-specific Require- ment Engineering artifacts Quality and explain how the quality parameters of RE artefacts affect the activities of development. XIII. Software Quality Control Via exit Criteria Methodology: An Industrial Experience Report [12] This paper introduces the Exit Criteria Metho- dology. This methodology helps in vast financial systems to improve the quality of the system from the beginning of a SCRUM sprint to the end. As a whole- process control of quality, the methodology is executed from the quality plan to the quality review. XIV. Quality Assessment Method for Software Requirements Specifications based on Document characteristics and Its Structure [13] In this research it is presented that in software development process quality of SRS should be main- tained. For this process different assessment methods are used by keeping in mind the three characteristics of SRS unambiguous variable and modifiable because it is necessary to satisfy the customers. VI. A Case Study on The Application of An Artefact-based Requirements Engineering Approach [5] Global Journal of Computer Science and Technology Volume XVII Issue I Version I 2 Year 2017 ( ) C © 2017 Global Journals Inc. (US) 1 Quality Assurance in Requirement Engineering
- 4. XV. Security Assurance Requirements Engineering (stare) for Trustworthy Service level Agreements [14] In this research through two case studies it is discussed that how STARE is effective in real world by evaluating that STARE from different techniques and easement criteria and how TSLA can be used to achieve TSLA can be used to achieve the trust worthless service. XVI. Does Quality of Requirements Specifications Matter? Combined Results of Two Empirical Studies [15] Quality of SRS depends on efficient and effecti- veness of quality assurance and by two correlations it is proved that SRS is less used for communication beca- use of it defects. In future it is necessary to document SRS on certain degree. XVII. Naming the Pain in Requirements Engineering [16] This paper explains that for better quality requirements, human interaction is important for elicitation regardless of project type and company size. For this standard process models and certifiable impro- vement standards are used. There is not necessary to use agile or non-agile methods for better quality. It is actually the way to solve the problems. The problem itself manifest in different ways. XVIII. Quality Assurance of Component based Software Systems [17] On this latest technology our software’s and web based applications are more complicated and with complex coding. Quality Assurance also maintains and reduces more work effort and also helps organization to develop application in the right path from the initial stage to the ending point. XIX. Assessing the Quality of Software Requirements Specifications for Automotive Software Systems [18] In this paper we conclude that SRS can be depend on the software or application we need to develop. There some types of SRS std. IEEE 830 to 1998. Several standards organizations including the IEEE have identified some points during designing and writing an SRS; Interfaces, Functional Capabilities, Performance Levels, Data Structures/Elements, Safety, Reliability, Security/Privacy, Quality, Constraints and Limitations. ding to experts Q. A reduce 50% effort in final stage. It also helps developers and also help to track any bug. By applying all Q.A methodology you can also improve your application efficiency. XXI. How Artifacts Support and Impede Requirements Communication [20] In this we collect information from different recourses that artificial mapping is not suitable for all types of project because in some cases it will be costly according to other, it should be suitable for linking bases modules. XXII. Analysis of Quality Parameters for Requirements a) Feasibility The requirements must be feasible in perspective of the financial plan, timetable, and innovation limitations b) Comprehensibility The definition of requirements must be intelligible by the general population who need to utilize them. c) Good Structuring The document of the requirements ought to be composed as it were that highlights the auxiliary connections among its components d) Modifiability It ought to be conceivable to change, adjust, develop, or contract the document of the requirements through adjustments that are as nearby as could reasonably be expected e) Traceability The setting in which a thing of the requirements archive was made, adjusted, or utilized ought to be anything but difficult to recover. Such setting ought to incorporate the method of reasoning for creation, adjustment, or utilize. f) Efficiency The requirements should be efficient that is they must fulfill the functionality and they also help in increasing the performance of the product. g) Correctness The requirements that are going to be implemented must be correct. They must be related to the functionality of the product. Global Journal of Computer Science and Technology Volume XVII Issue I Version I 3 Year 2017 ( ) C XX. A Quality Assurance Model for Analysis Phase [19] According to my opinion Q.A is most important part it plays as a back bone of any application. Accor h) Completeness The requirements that are going to implemented must be complete. XXIII. Conclusion The paper discusses different factors to improve the quality of the product from the initial stage Quality Assurance in Requirement Engineering © 2017 Global Journals Inc. (US)
- 5. that is requirement engineering. Different models like LaQuSo, ANN, CBR and many more are introduced for checking different quality parameters including correct- ness, completeness etc. The feasibility, comprehends- bility, Modifiability, good structuring, completeness etc. are the parameters that effect quality of requirements and by analyzing them a better quality of requirements can be achieved. For better quality product, the requirements must be of better quality. XXIV. Acknowledgement I thank to my department of Software Engine- ering and my teacher, Ma’am MehreenSirshar, who have contributed towards the development of this research paper. References Références Referencias 1. Petra Heck, PäiviParviainen, Experiences on Ana- lysis of Requirements Quality, 2008 IEEE The Third International Conference on Software Engineering Advances. 2. Eric Knauss, Christian El Boustani, Assessing the Quality of Software Requirements Specifications, 2008 16th IEEE International Requirements Engine- ering Conference 3. Dang Viet Dzung, Atsushi Ohnishi, Improvement of Quality of Software Requirements with Require- ments Ontology, 2009 Ninth International Confe- rence on Quality Software 4. Hajar Mat Jani,Applying Case-Based Reasoning to Software Requirements Specifications Quality Analy- sis System, 5. Daniel M´endezFern´andez, Klaus Lochmann, Birgit Penzenstadler, Stefan Wagner, A Case Study on the Application of an Artefact-Based Requirements Engineering Approach, 2011 6. Anne Gross, JoergDoerr, What You Need Is What You Get! The Vision of View-Based Requirements Specifications, 2012 7. Daniel Ott, Defects in Natural Language Require- ment Specifications at Mercedes-Benz: AnInvesti- gation Using a Combination of Legacy Data and Expert Opinion, 2012 8. Panagiotis Sfetsos, ForewordQuality in Agile Methods, 9. Hajar Mat Jani, ABM Tariqul Islam, A Framework of Software Requirements Quality Analysis System using Case-Based Reasoning and Neural Network, 10. Sana Nazir, Yasir Hafeez Motla, Tahir Abbas, Asma Khatoon, JavariaJabeen, MehwishIqr,KhushBakhat, A Process Improvement in RequirementVerification and Validation using Ontology, 11. Henning Femmer, JakobMund, Daniel M´endez Fern´andez, It’s the Activities, Stupid!A New Pers- pective on RE Quality, 2015 IEEE/ACM 2nd Interna- tional Workshop on Requirements Engineering and Testing 12. Xiaoqiong Zhao, Xiao Xuan, Aoyu Wangy , Dong Liuz,Lingyun Zheng, Software Quality Control via Exit Criteria Methodology: An Industrial Experience Report, 2014 21st Asia-Pacific Software Engineering Conference 13. Patra Thitisathienkul, NakornthipPrompoon, Quality Assessment Method for SoftwareRequirements Specifications based on Document Characteristics and its Structure, 2015 2nd International Conference on Trustworthy Systems and Their Applications 14. Yudhistira Nugraha, Security Assurance Require- ments Engineering(STARE) for Trustworthy Service Level Agreements, 2015 15. Jakob Mund, Henning Femmer, Daniel M´endez Fern´andez, Jonas Eckhardt, Does Quality of Req- uirements Specifications matter? Combined Results of Two Empirical Studies, 2015 16. Daniel Méndez Fernández, Stefan Wagner, Marcos Kalinowski, André Schekelmann, Ahmet Tuzcu, Tay- ana Conte, Rodrigo Spinola, and Rafael Prikladnicki, Naming the Painin Requirements Engineering, 2015 17. Ravi Kumar Sharma, Parul Gandhi, Quality Assura- nce of Component Based Software Systems, 2016 18. AkiyukiTakoshima, Mikio Aoyama, Assessing the Quality of Software Requirements Specifications for Automotive Software Systems, 2015 19. RehamEjaz,MubinaNazmeen, Maryam Zafar, A Quality Assurance Model for Analysis Phase, Oct 4th , 2010 20. Olga Liskin, How Artifacts Support and Impede- Requirements Communication, January 2011. Global Journal of Computer Science and Technology Volume XVII Issue I Version I 4 Year 2017 ( ) © 2017 Global Journals Inc. (US) 1 C Quality Assurance in Requirement Engineering
- 6. Table 1: Evaluation Criteria for Copiler Optimization Table 2: Evaluations Of Parameters For Compiler Optimization No. Parameters Description Value 1. Feasibility Requirements are easy to use Yes, No 2. Comprehensibility Requirements are understandable to other people Yes, No 3. Good Structuring Requirements are well structured and have links among its elements Yes, No 4. Modifiability Requirements are revisable and adaptable. Yes, No 5. Traceability Easy to trace the requirements Yes, No 6. Efficiency Requirements fulfill the functionality. Yes, No 7. Correctness Checks whether the requirements are correct. Yes, No 8. Completeness Checks whether the requirements are complete. Yes/No Global Journal of Computer Science and Technology Volume XVII Issue I Version I 5 Year 2017 ( ) C Quality Assurance in Requirement Engineering S # Reasearch Paper’s Auther Feasib- ility Compre hensibili ty Good Structurin g Modifi- ability Trace- ability Effici ency Correct- ness Comple te-ness 1 P. Heck, P. Parviainen Yes Yes No No Yes Yes Yes Yes 2 E. Knauss, C. E.Boustani Yes Yes Yes Yes Yes Yes Yes Yes 3 D. V. Dzung, A. Ohnishi Yes Yes Yes Yes Yes Yes Yes Yes 4 H. M. Jani Yes Yes Yes No Yes Yes Yes Yes 5 D. M. Fern´andez, K. Lochmann, B. Penzenstadler, S. Wagner Yes No No No No No Yes Yes 6 A. Gross, J. Doerr Yes Yes Yes No Yes No Yes Yes 7 D. Ott Yes Yes Yes Yes Yes Yes Yes Yes 8 P. Sfetsos Yes Yes Yes Yes No Yes Yes Yes 9 H. M. Jani, A. T. Islam No Yes Yes No Yes No Yes No 1 0 S. Nazir, Y. H. Motla, T. Abbas, A. Khatoon, J. Jabeen, M. Iqr, K.Bakhat Yes No Yes No Yes No Yes Yes 1 1 H. Femmer, J.Mund, D. M. Fern´andez Yes No Yes Yes Yes Yes Yes Yes 1 2 X. Zhao, X. Xuan, A.Wangy, D. Liuz, L. Zheng Yes Yes Yes Yes Yes Yes Yes Yes 1 3 P.Thitisathienkul, N.Prompoon No Yes Yes Yes Yes Yes Yes Yes 1 4 Y. Nugraha Yes Yes Yes Yes Yes Yes Yes Yes 1 5 J. Mund, H. Femmer, D. M. Fern´andez, J. Eckhardt Yes Yes Yes Yes Yes Yes Yes Yes 1 6 D. M. Fernández, S. Wagner, M. Kalinowski, A. Schekelmann, A. Tuzcu, T. Conte, R. Spinola, R.Prikladnick No No No No No Yes Yes Yes 1 7 R. K. Sharma, P. Gandhi Yes No Yes No Yes Yes Yes Yes © 2017 Global Journals Inc. (US)
- 7. Global Journal of Computer Science and Technology Volume XVII Issue I Version I 6 Year 2017 ( ) © 2017 Global Journals Inc. (US) 1 C Quality Assurance in Requirement Engineering 1 8 A. Takoshima, M. Aoyama Yes Yes Yes Yes Yes Yes Yes Yes 1 9 R. Ejaz, M. Nazmeen, M. Zafar Yes Yes Yes Yes Yes Yes Yes Yes 2 0 O.Liskin No Yes No No Yes Yes Yes Yes