Journal of information and communication convergence engineering

The Korea Institute of Information and Commucation Engineering (한국정보통신학회)
권호 표지
DOI QR코드

DOI QR Code

A Model for Reusing Requirements Using Examples from Open Source Software

  • Received : 2012.05.31
  • Accepted : 2012.06.25
  • Published : 2012.09.30
Download PDF
⟨ Previous Next ⟩

Abstract

The quality of requirements is one of the key factors in the success of a project. One of the studies on successful projects is the reuse of requirements. However, the rate of failed projects is about 70%, and these projects often fail because of improper requirements. The current techniques for software reuse may not perform requirement engineering appropriately or develop requirements having good characteristics. In order to improve this situation, we propose a model for reusing requirements. We expect that our model will contribute toward increasing project productivity using requirement reuse in existing projects, and reusing requirements that have good quality.

Keywords

References

  1. G. Kotonya and I. Sommerville, "Requirements engineering with viewpoints," Software Engineering Journal, vol. 11, no. 1, pp. 5-18, 1996. https://doi.org/10.1049/sej.1996.0002
  2. A. M. Davis, Just Enough Requirements Management: Where Software Development Meets Marketing, New York: Dorset House Pub., 2005.
  3. M. Davis and D. Zowghi, "Good requirements practices are neither necessary nor sufficient," Requirements Engineering, vol. 11, no. 1, pp. 1-3, 2005.
  4. D. T. Ross, "Structured analysis (SA): a language for communicating ideas," IEEE Transactions on Software Engineering, vol. 3, no. 1, pp. 16-34, 1977. https://doi.org/10.1109/TSE.1977.229900
  5. D. Zimmermann and L. Grotzbach, "A requirement engineering approach to user centered design," Proceedings of the 12th International Conference on Human-Computer Interaction, Beijing, China, pp. 360-369, 2007.
  6. I. F. Hooks and K. A. Farry, Customer-Centered Products: Creating Successful Products through Smart Requirements Management, New York: American Management Association, 2000.
  7. J. M. DeBaud and K. Schmid, "A systematic approach to derive the scope of software product lines," Proceedings of the 21st International Conference on Software Engineering, Los Angeles, CA, pp. 34-43, 1999.
  8. K. C. Kang, S. G. Cohen, J. A. Hess, W. E. Novak, and A. S. Peterson, "Feature-oriented domain analysis (FODA) feasibility study," Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, Technical Report CMU/SEI-90-TR-21, 1990.
  9. K. Lee, K. C. Kang, and J. Lee, "Concepts and guidelines of feature modeling for product line software engineering," Proceedings of the 7th International Conference on Software Reuse, Austin, TX, pp. 62-77, 2002.
  10. J. Kuusela and J. Savolainen, "Requirements engineering for product families," Proceedings of the 22nd International Conference on Software Engineering, Limerick, Ireland, pp. 61-69, 2000.
  11. M. Moon and K. Yeom, "An approach to develop requirement as a core asset in product line," Software Reuse: Methods, Techniques, and Tools, Lecture Notes in Computer Science, vol. 3107, pp. 23-34, 2004.
  12. M. Moon, K. Yeom, and H. S. Chae, "An approach to developing domain requirements as a core asset based on commonality and variability analysis in a product line," IEEE Transactions on Software Engineering, vol. 31, no. 7, pp. 551-569, 2005. https://doi.org/10.1109/TSE.2005.76
  13. M. Simos, D. Creps, C. Klingler, L. Levine, and D. Allemang, "Organization domain modeling (ODM) guidebook version 2.0," Lockheed Martin Tactical Defence Systems, Manassas: VA, Technical Report STARS-VC-A025/001/00, 1996.
  14. R. R. Holibaugh, "Joint integrated avionics working group (JIAWG) object-oriented domain analysis method (JODA)," Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, Special Report CMU/SEI-92-SR-003, 1992.
  15. R. Prieto-Diaz, "Domain analysis: an introduction," ACM SIGSOFT Software Engineering Notes, vol. 15, no. 2, pp. 47-54, 1990. https://doi.org/10.1145/382296.382703
  16. T. Gorschek and C. Wohlin, "Requirements abstraction model," Requirements Engineering, vol. 11, no. 1, pp. 79-101, 2005.
  17. T. Gorschek and A. M. Davis, "Requirements engineering: In search of the dependent variables," Information and Software Technology, vol. 50, no. 1-2, pp. 67-75, 2008. https://doi.org/10.1016/j.infsof.2007.10.003
  18. W. Frakes, R. Prieto-Diaz, and C. Fox, "DARE: Domain analysis and reuse environment," Annals of Software Engineering, vol. 5, pp. 125-141, 1998. https://doi.org/10.1023/A:1018972323770
  19. W. Lam and J. A. McDermid, "A summary of domain analysis experience by way of heuristics," ACM SIGSOFT Software Engineering Notes, vol. 22, no. 3, pp. 54-64, 1997.
  20. The Standish Group, CHAOS Summary 2009, Boston: The Standish Group International, 2009.
  21. S. Buhne and K. Pohl, "Domain requirements engineering," in Software Product Line Engineering, Heidelberg: Springer, pp. 193-216, 2005.
  22. A. G. Sutcliffe and N. A. M. Maiden, "Domain modeling for reuse," Proceedings of the 3rd International Conference on Software Reuse, Rio de Janeiro, Brazil, pp. 169-177, 1994.
  23. J. Coplien, D. Hoffman, and D. Weiss, "Commonality and variability in software engineering," IEEE Software, vol. 15, no. 6, pp. 37-45, 1998.
  24. M. Harsu, "A survey on domain engineering," Tampere University of Technology, Tampere, Finland, Technical Report 31, 2002.
  25. J. M. Acken, "Logic level modeling," in Encyclopedia of Computer Science and Technology Vol 36, New York: Marcel Dekker Inc., pp. 281-306, 1997.

Cited by

  1. 오픈소스 모바일 UI컴포넌트 선정 절차 프레임워크 vol.18, pp.11, 2012, https://doi.org/10.6109/jkiice.2014.18.11.2593