Collaborative requirements review

  • Authors

    • Azlin Nordin
    • Nadzurah Zainal Abidin
    • Sara Hanum Mohd Zaini
    2018-04-06
    https://doi.org/10.14419/ijet.v7i2.14.11158
  • Requirements Review, Requirements Validation, Collaborative Review.

  • Requirements review is a formal review conducted to ensure that system requirements have been completely and clearly identified. In the conventional requirements review technique, reviewers are required to physically attend the review session and give their review feedback during the session. In such a situation, there are potential problems of scheduling the review session based on the availability of the reviewers and issues with having to physically attend the entire review session. Furthermore, the review session needs to be manually organized by the review leader and the outcome of the session need to be manually compiled. In some occasions, more than one sessions are required to be organized. Hence, the objectives of this project are to: (1) create means for the reviewers to perform review anytime and anywhere; (2) facilitate collaborative review session; (3) support checklist management for the review guidance; and (4) allow compilation of the review feedback to be generated.  As a case study, a web application for collaborative requirements review has been developed and tested. Finally, the features of the application are tested and issues are documented.

     

     

  • References

    1. [1] I. Sommerville, Software Engineering, 10th ed. Boston: Pearson, 2015.

      [2] G. Kotonya and I. Sommerville, Requirement Engineering: Process and Techniques. John Wiley & Son, 1998.

      [3] “IEEE Recommended Practice for Software Requirements Specifications,†IEEE Std 830-1998, pp. 1–40, Oct. 1998.

      [4] N. Condori-Fernandez, S. España, K. Sikkel, M. Daneva, and A. González, “Analyzing the Effect of the Collaborative Interactions on Performance of Requirements Validation,†in Proceedings of the 20th International Working Conference on Requirements Engineering: Foundation for Software Quality - Volume 8396, New York, NY, USA, 2014, pp. 216–231.

      [5] “IEEE Standard for Software Reviews and Audits,†IEEE Std 1028-2008, pp. 1–52, Aug. 2008.

      [6] L. Sulehri, Comparative Selection of Requirements Validation Techniques Based on Industrial Survey. 2010.

      [7] K. Pohl, Requirements Engineering: Fundamentals, Principles, and Techniques, 1st ed. Springer Publishing Company, Incorporated, 2010.

      [8] “Project Management White Papers | Project Smart.†[Online]. Available: https://www.projectsmart.co.uk/white-papers/chaos-report.pdf. [Accessed: 18-Aug-2017].

      [9] S. O. Mokhtar, R. Nordin, Z. A. Aziz, and R. M. Rawi, “Issues and Challenges of Requirements Review in the Industry,†Indian J. Sci. Technol., vol. 10, no. 3, Jan. 2017.

      [10] K. Wiegers and J. Beatty, Software Requirements, 3rd ed. Redmond, Washington: Microsoft Press, 2013.

      [11] S. B. Saqi and S. Ahmed, Requirements Validation Techniques practiced in industry : Studies of six companies. 2008.

      [12] K. Wiegers, More About Software Requirements: Thorny Issues and Practical Advice. Microsoft Press, 2005.

      [13] Y. K. Lee, H. P. In, and R. Kazman, “Customer Requirements Validation Method Based on Mental Models,†in 2014 21st Asia-Pacific Software Engineering Conference, 2014, vol. 1, pp. 199–206.

      [14] “PleaseReview: collaborative document review, editing and co-authoring.†[Online]. Available: http://www.pleasetech.com/ pleasereview.aspx. [Accessed: 02-May-2017].

      [15] “Online Proofing Software Tools | Review & Approval ProofHQ.†[Online]. Available: https://www.proofhq.com/. [Accessed: 02-May-2017].

      [16] “About Frontiers | Academic Journals and Research Community.†[Online]. Available: http://home.frontiersin.org/about/review-system. [Accessed: 02-May-2017].

  • Downloads

  • How to Cite

    Nordin, A., Zainal Abidin, N., & Hanum Mohd Zaini, S. (2018). Collaborative requirements review. International Journal of Engineering & Technology, 7(2.14), 66-69. https://doi.org/10.14419/ijet.v7i2.14.11158