Challenge of validation in requirements engineering

Maalem, Sourour; Zarour, Nacer Eddine

doi:10.1016/j.jides.2016.05.001

Cited by 33 publications

(12 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Evaluation of the correctness quality can be performed on the requirement phase [11]. This idea also supported by a few other researchers [12], [13]. A Testdriven approach, which is a use case, has been chosen to validate the functional requirement [14].…”

Section: B Functional Requirement 1) Consistencymentioning

confidence: 99%

Evaluation of Software Requirement Specification Based on IEEE 830 Quality Properties

Stephen

Mit

2020

Int. J. Adv. Sci. Eng. Inf. Technol.

View full text Add to dashboard Cite

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.

show abstract

Section: B Functional Requirement 1) Consistencymentioning

confidence: 99%

Evaluation of Software Requirement Specification Based on IEEE 830 Quality Properties

Stephen

Mit

2020

Int. J. Adv. Sci. Eng. Inf. Technol.

View full text Add to dashboard Cite

show abstract

“…Most of them focus on techniques for a single particular RE/BA area e.g. requirement elicitation [2][39] [41][42], prioritization [38], specification [34] or validation [23] [26], some however include a broader scope and intend to cover all areas [5][21] [24]. The criteria used for RE/BA techniques comparison include: their inherent characteristics (e.g.…”

Section: Related Workmentioning

confidence: 99%

A Survey on Identifying and Addressing Business Analysis Problems

Jarzębowicz

Marciniak²

2017

Foundations of Computing and Decision Sciences

View full text Add to dashboard Cite

Abstract. Despite the growing body of knowledge on requirements engineering and business analysis, these areas of software project are still considered problematic. The paper focuses on problems reported by business analysts and on applicability of available business analysis techniques as solutions to such problems. A unified set of techniques was developed on the basis of 3 industrial standards associated with IIBA, REQB and IREB certification schemes. A group of 8 business analysts was surveyed to list problems they encounter in their work and to assess their frequency. Selected problems were further analyzed and most suitable techniques were proposed to address them. These proposals were validated through follow-up discussions with business analysts. The main results of research reported in this paper are: the comparative analysis of techniques included in IIBA, REQB and IREB standards and the list of problems reported by practitioners associated with techniques suggested as effective solutions.

show abstract

“…A large number of errors occur in the systems due to the poor requirements and several systems fail due to the informal requirements [9]. Requirement validation and specification ensure that all the requirements are correct, complete, consistent, and fulfill the customer needs [10]. For this purpose, requirement models can be created to ensure that all the requirements are correct and satisfy customer needs.…”

Section: Introductionmentioning

confidence: 99%

Requirement Validation for Embedded Systems in Automotive Industry Through Modeling

et al. 2020

View full text Add to dashboard Cite

Requirement validation contributes significantly toward the success of software projects. Validating requirements is also essential to ensure the correctness of embedded systems in the auto industry. The auto industry emphasizes a lot on the verification of car designs and shapes. Invalid or erroneous requirements lead to inappropriate designs and degraded product quality. Considering the required expertise and time for requirement validation, significant attention is not devoted to verification and validation of requirements in the industry. Currently, the failure ratio of software projects is significantly higher and the key reason for that appears to be the inappropriate and invalidated requirements at the early stages in the projects. To that end, we propose a model-based approach that uses the existing V&V model. Through virtual prototyping, the proposed approach eliminates the need to validate the requirements after each stage of the project. Consequently, the model is validated after the design phase and the errors in requirements are detected at the earliest stage. In this research, we performed two different case studies for requirement validation in the auto industry by using a modeling-based approach and formal technique using Petri nets. A benefit of the proposed modeling-based approach is that the projects in the auto industry domain can be completed in less time due to effective requirements validation. Moreover, the modeling-based approach minimizes the development time, cost and increases productivity because the majority of the code is automatically generated using the approach.

show abstract

Challenge of validation in requirements engineering

Cited by 33 publications

References 7 publications

Evaluation of Software Requirement Specification Based on IEEE 830 Quality Properties

Evaluation of Software Requirement Specification Based on IEEE 830 Quality Properties

A Survey on Identifying and Addressing Business Analysis Problems

Requirement Validation for Embedded Systems in Automotive Industry Through Modeling

Contact Info

Product

Resources

About