Search
2017 Volume 32
Article Contents
RESEARCH ARTICLE   Open Access    

Component-based approach for requirements reuse

More Information
  • Abstract: Reusing requirements improves product quality and the productivity of the development process. This paper investigates how the development of new requirements can be made more productive through reuse of the experience gained on similar requirements. This can be facilitated using a component-based reuse approach supported by a framework. Therefore, the central challenge for this research work is double: (1) to define a new concept for the requirement component as the combination of two types of knowledge: reusable knowledge and knowledge of reuse; (2) to define AFR (Analysis For Reuse) that represents the capitalization process by opposition to Analysis By Reuse that represents the process of reuse itself. Finally, we provide a case study related to the requirements of a hotel system to explain how the first process works. Through this approach, we use a framework ‘Requirements Repository Framework (R2F)’ in order to capitalize existing requirements within a repository for future reuse. We present the results of an experiment with three second-level student sections that used R2F in their IS240 course project; as well as with four student groups that used R2F in their respective senior projects. The objective of this experiment is to measure the usability of the proposed AFR process.
  • 加载中
  • Akers D.2008. Real reuse for requirements.Methods & Tools16(1),33–40.

    Google Scholar

    Chernak Y.2012. Requirements reuse: the state of the practice. InProceedings of IEEE International Conference on Software Science, Technology and Engineering (SWSTE), 46–53. https://doi.org/10.1109/SWSTE.2012.12.

    Google Scholar

    Gotel O. & Finkelstein A.1994. An analysis of the requirements traceability problem. InProceedings of the 1st International Conference in Requirements Engineering, 94–101.

    Google Scholar

    Haslhofer B. & Klas W.2010. A survey of techniques for achieving metadata interoperability. ACM Computing Surveys42(2),1–42.

    Google Scholar

    Hauksdottir D., Vermehren A. & Savolainen J.2012. Requirements reuse at Danfoss. In Proceedings of 20th IEEE International on Requirements Engineering Conference (RE), 309–314. https://doi.org/10.1109/RE.2012.6345820.

    Google Scholar

    Husnain M., Waseem M. & Ghayyur S. A. K.2009. An interrogative review of requirement engineering frameworks. International Journal of Reviews in Computing2(1),1–8.

    Google Scholar

    IEEE 1484.12.1-20022002. Draft Standard for Learning Object Metadata. Technical report, IEEE Learning Technology Standards Committee (LTSC).

    Google Scholar

    Lauesen S.2002. Requirements: Styles and Techniques.Addison-Wesley.

    Google Scholar

    Menndez-Domnguez V. H., Zapata A., Prieto-Mendez M. E., Romero C. & Serrano-Guerrero J.2011. A similarity-based approach to enhance learning objects management systems. In Proceedings of 11th International IEEE Conference on Intelligent Systems Design and Applications (ISDA), 996–1001.

    Google Scholar

    Mussbacher G. & Kienzle J.2013. A vision for generic concern-oriented requirements reuse re@21. In Proceedings of 21st IEEE International on Requirements Engineering Conference (RE), 238–249. https://doi.org/10.1109/RE.2013.6636724.

    Google Scholar

    Myklebust T., Lyngby N., Bains R. & Hanssen G. K.2014. CoVeR maintenance and maintainability requirements by using tools. In Proceedings of Annual Symposium on Reliability and Maintainability (RAMS), 1–6. https://doi.org/10.1109/RAMS.2014.6798497.

    Google Scholar

    Niu N., Savolainen J., Niu Z., Jin M. & Cheng J. C.2014. A systems approach to product line requirements reuse. IEEE Systems Journal8(3),827–836, https://doi.org/10.1109/JSYST.2013.2260092.

    Google Scholar

    Pacheco C. L., Garcia I. A., Calvo-Manzano J. A. & Arcilla M.2015. A proposed model for reuse of requirements in requirements catalog. Journal of Software: Evolution and Process27, 1–21.

    Google Scholar

    Palomares C., Quer C. & Franch X.2014. Requirements reuse and patterns: a survey. InRequirements Engineering: Foundation for Software Quality, Lecture Notes in Computer Science 8396, Springer, Cham 301–308.

    Google Scholar

    Palomares C., Quer C., Franch X., Guerlain C. & Renault S.2012. A catalogue of non-technical requirement patterns. InProceedings of IEEE Second International Workshop on Requirements Patterns (RePa), 1–6. https://doi.org/10.1109/RePa.2012.6359969.

    Google Scholar

    Ramesh B. & Jarke M.2001. Towards reference models for requirements traceability. IEEE Transactions in Software Engineering27(1),58–93.

    Google Scholar

    Runeson P. & Hst M.2009. Guidelines for conducting and reporting case study research in software engineering. Empirical Software Engineering14(2), 131164.

    Google Scholar

    Sommerville I.2011. Software Engineering.Pearson Education.

    Google Scholar

    Spanoudakis G. & Zisman A.2005. Software traceability: a roadmap. In Handbook of Software Engineering and Knowledge Engineering, Chang, S. K. (ed.). World Scientific,395–428.

    Google Scholar

    Tastekin S. Y., Erten Y. M. & Bilgen S.2012. Product development time improvement with requirements reuse. In Proceedings of the 7th International Conference on Software Engineering Advances, 394–400.

    Google Scholar

    Toval A., Nicols J., Moros B. & Garca F.2002. Requirements reuse for improving information systems security: a practitioner’s approach.Springer Requirements Engineering Journal6(4),205–219.

    Google Scholar

    Toval A., Moros B., Nicols J. & Lasheras J.2008. Eight key issues for an effective reuse-based requirements process. Computer Systems Science and Engineering23(6),1–20.

    Google Scholar

    Wiegers K. E.2003. Requirements. Microsoft Press.

    Google Scholar

  • Cite this article

    Azeddine Chikh. 2017. Component-based approach for requirements reuse. The Knowledge Engineering Review 32(1), doi: 10.1017/S0269888917000030
    Azeddine Chikh. 2017. Component-based approach for requirements reuse. The Knowledge Engineering Review 32(1), doi: 10.1017/S0269888917000030

Article Metrics

Article views(32) PDF downloads(58)

Other Articles By Authors

RESEARCH ARTICLE   Open Access    

Component-based approach for requirements reuse

Abstract: Abstract: Reusing requirements improves product quality and the productivity of the development process. This paper investigates how the development of new requirements can be made more productive through reuse of the experience gained on similar requirements. This can be facilitated using a component-based reuse approach supported by a framework. Therefore, the central challenge for this research work is double: (1) to define a new concept for the requirement component as the combination of two types of knowledge: reusable knowledge and knowledge of reuse; (2) to define AFR (Analysis For Reuse) that represents the capitalization process by opposition to Analysis By Reuse that represents the process of reuse itself. Finally, we provide a case study related to the requirements of a hotel system to explain how the first process works. Through this approach, we use a framework ‘Requirements Repository Framework (R2F)’ in order to capitalize existing requirements within a repository for future reuse. We present the results of an experiment with three second-level student sections that used R2F in their IS240 course project; as well as with four student groups that used R2F in their respective senior projects. The objective of this experiment is to measure the usability of the proposed AFR process.

    • The author would like to thank senior project students who participated in the experimentation of R2F.

    • © Cambridge University Press, 2017 2017Cambridge University Press
References (23)
  • About this article
    Cite this article
    Azeddine Chikh. 2017. Component-based approach for requirements reuse. The Knowledge Engineering Review 32(1), doi: 10.1017/S0269888917000030
    Azeddine Chikh. 2017. Component-based approach for requirements reuse. The Knowledge Engineering Review 32(1), doi: 10.1017/S0269888917000030
  • Catalog

      /

      DownLoad:  Full-Size Img  PowerPoint
      Return
      Return