VOLATILE REQUIREMENT IDENTIFICATION: AN IMPLEMENTATION OF PERSPECTIVE BASED INSPECTION TECHNIQUES
Main Article Content
Abstract
Inspection is a best known way of detecting defects in SRS [1]. Software Inspection was initially created for source code. However, it was later extended to be used for the various software life cycle products such as design design & requirements specification. The key characteristics of a software project are requirements. Requirements keep on changing throughout the life cycle of a project [2]. These changing requirements are popularly known as volatile requirements. If not resolved these volatile requirements can be very dangerous. They should be  detected in earlier phases of software development life cycle. In this paper an inspection technique is proposed that uses perspective based reading [3] for detecting these volatile requirements.
Â
Downloads
Article Details
COPYRIGHT
Submission of a manuscript implies: that the work described has not been published before, that it is not under consideration for publication elsewhere; that if and when the manuscript is accepted for publication, the authors agree to automatic transfer of the copyright to the publisher.
Authors who publish with this journal agree to the following terms:
- Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution License that allows others to share the work with an acknowledgment of the work's authorship and initial publication in this journal.
- Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgment of its initial publication in this journal.
- Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work
- The journal allows the author(s) to retain publishing rights without restrictions.
- The journal allows the author(s) to hold the copyright without restrictions.
References
M. Fagan, “Advances in Software Inspections,†IEEE Trans. Software Eng., July 1986, pp. 744-751.
K. E. Wiegers, “Software requirementsâ€, Microsoft press 1999.
Forrest Shull Ioana Rus, Victor Basili “How Perspective-Based Reading Can Improve Requirements Inspections†0018-9162/00/ 2000 IEEE
R. Glass, The software research crisis, IEEE Software 11 (6) (1994) 42-47
Porter A. A. Votta & Basili V.R. 1995, Comparing detection methods for software requirement inspection: A replicated experiment, IEEE Trans. Soft. Eng 2(6): 563-575
Fagan M.E. 1976 Design and code inspection to reduce errors in program development IBM systems Journal 15(3) 182-211
Harker, S.D.P.; Eason, K.D. “The change and evolution of requirements as a challenge to the practice of software engineering†Proceedings of IEEE International Symposium on Requirements Engineering, 1993
S. Nayak, R. Khan and R.Beg “Evaluation of Requirement Defects: An Implementation of Identification Technique†ICIET2012, Journal of Procedia Technology
Victor Basili, Scott Green, Oliver Laitenberger, Fillipo Lanubile, Forrest Shull, Sivert Sorumgard, and Marvin V. Zelkowitz, The Empirical Investigation of Perspective-Based Reading, Journal of Empirical Software Engineering, vol. 2, no. 1, pp. 133-164, 1996.
Bee Bee Chua and June Verner “Examining Requirements Change Rework Effort: A Study†International Journal of Software Engineering & Applications (IJSEA), Vol.1, No.3, July 2010 DOI : 10.5121/ijsea.2010.1304 48
Md. Faisal, R Beg, H Sadia “A proficient Model for Requirement Volatility Managementâ€, I CIET 2012, Journal of Procedia Technology.