A Review on Software Requirements Validation and Consistency Management

Kamalrudin, Massila; Sidek, Safiah

doi:10.14257/ijseia.2015.9.10.05

Cited by 19 publications

(11 citation statements)

References 66 publications

(128 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Validation is the procedure of checking key indicators aimed at verifying whether the specifications for the system match the intended purpose. It is meant to check whether the user specifications and requirements are realized [16]. For the developed system, different approaches were used for validation, including unit testing, integration testing, and system testing.…”

Section: B Validationmentioning

confidence: 99%

Development of a Sensor-Based Heartbeat and Body Temperature Monitoring System for Remote Chronic Patients

Obira

Sinde

2021

Eng. Technol. Appl. Sci. Res.

View full text Add to dashboard Cite

The growing number of chronic diseases have stretched the healthcare sector. Globally, more than 36 million deaths per year are attributed to chronic disease complications. This has increased the demand for telemedicine in managing chronic patients as they must be on continuous monitoring for a long time. The involvement of wireless sensor networks and cloud computing technology in the health sector is increasing due to the potential it possesses in remote sensing and monitoring applications. This paper presents a developed system prototype for monitoring the heartbeat rate and body temperature of chronic patients using sensors. The monitored data are sent to a cloud database in real-time via an internet connection using the ESP8266 wireless module. The approach involves connecting a heart pulse sensor, an MLX90614 contactless temperature sensor, and the ESP8266 module to the Arduino development board. The goal of this work is to create a system that interfaces chronic patients and medical personnel in an attempt to avert the effects of insufficient health facilities, especially in rural Africa. The patient’s data in the cloud database can also be retrieved by medical personnel anytime in order to track the patient’s conditions and to advise the patient accordingly. The sensed heartbeat and body temperature readings were processed, sent, and recorded in the cloud database effectively.

show abstract

Section: B Validationmentioning

confidence: 99%

Development of a Sensor-Based Heartbeat and Body Temperature Monitoring System for Remote Chronic Patients

Obira

Sinde

2021

Eng. Technol. Appl. Sci. Res.

View full text Add to dashboard Cite

show abstract

“…is recorded as a phase product. In RCM process, each phase product requires modification as a result of the proposed change, in order to maintain consistency across all artifact documents [73]. The management of SDLC phases product, such as requirement document, design document, source code, and testing document, is crucial, especially if a change occurs in the late phases of SDLC, such as during testing.…”

Section: ) Systematic Literature Review Findings Of Rcm Process In Imentioning

confidence: 99%

Comparative Analysis of Requirement Change Management Challenges Between in-House and Global Software Development: Findings of Literature and Industry Survey

et al. 2019

View full text Add to dashboard Cite

Requirement changes are inevitable, and Requirement Change Management (RCM) is a complex process in software development. In-house software development and Global Software Development (GSD) are two widely used development approaches and there is a need to explore the RCM commonalities and differences in the two development approaches. The primary objective of this study is to identify the challenges that influence RCM in both approaches. First, we have implemented Systematic Literature Review (SLR) and identified 9 challenges that impact the general RCM process and 3 more challenges related to RCM with GSD. Second, we have conducted a questionnaire survey based on SLR results and collected feedback from 69 industry practitioners. The survey result indicates that there are four out of nine challenges, namely impact analysis, requirement traceability, requirement dependency, and system instability having the same impact in both in-house and GSD approaches. On the other hand, cost/time estimation, artifacts documents management, user involvement, requirement consistency, and requirement prioritization need more attention while implemented in GSD paradigm. Furthermore, regarding two important project management structures in GSD, centralized project structure and distributed project structure, the survey results reveal that all challenges have same impact except user involvement and change control board management, which are more important in centralized project structure. Lastly, the result from t-test indicates that both data sets retrieved from SLR and survey are close to each other. This study distinguishes RCM challenges in in-house and GSD approaches and in the context of two prominent project management structures followed in GSD projects. It would assist researchers by providing potential research directions and industry professionals to understand and implement RCM in different context more efficiently. INDEX TERMS Requirement change management (RCM), global software development (GSD), challenges, global project structures, systematic literature review (SLR).

show abstract

“…The existing literature also documents works on consistency management of requirements other than GORE. There has been two directions of research for validation and consistency management of software requirements -heuristic analysis and formal analysis [21]. Heuristic analysis uses heuristic algorithms.…”

Section: State-of-the-artmentioning

confidence: 99%

AFSCR: Annotation of Functional Satisfaction Conditions and their Reconciliation within i* models

Deb¹,

Chaki²

2019

Preprint

View full text Add to dashboard Cite

Context: Researchers, both in industry and academia, are facing the challenge of leveraging the benefits of goal oriented requirements engineering (GORE) techniques to business compliance management. This requires analyzing goal models along with their semantics. However, most prominent goal modeling frameworks have no means of capturing the semantics of goals (except what is trivially conveyed by their nomenclature).Objective: In this paper, we propose the Annotation of Functional Satisfaction Conditions and their Reconciliation (AFSCR) framework for doing the same.The entire framework is presented with respect to i* modeling constructs.Method : This is a semi-automated framework that requires analysts to annotate individual goals with their immediate goal satisfaction conditions. The AFSCR framework can then reconcile these satisfaction conditions for every goal and verify whether the derived set of cumulative satisfaction conditions is in harmony with the intended set of goal satisfaction conditions.Result: If the derived and intended sets of satisfaction conditions are in conflict, the framework raises entailment and/or consistency flags. Whenever a conflict is flagged, the framework also provides alternate solutions and possible workaround strategies to the analysts by refactoring the given i* model. Conclusion:In this paper we present a new framework that uses satisfaction

show abstract

A Review on Software Requirements Validation and Consistency Management

Cited by 19 publications

References 66 publications

Development of a Sensor-Based Heartbeat and Body Temperature Monitoring System for Remote Chronic Patients

Development of a Sensor-Based Heartbeat and Body Temperature Monitoring System for Remote Chronic Patients

Comparative Analysis of Requirement Change Management Challenges Between in-House and Global Software Development: Findings of Literature and Industry Survey

AFSCR: Annotation of Functional Satisfaction Conditions and their Reconciliation within i* models

Contact Info

Product

Resources

About