Requirements Classification and Reuse: Crossing Domain Boundaries

  • Jacob L. Cybulski
  • Karl Reed
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1844)


A serious problem in the classification of software project artefacts for reuse is the natural partitioning of classification terms into many separate domains of discourse. This problem is particularly pronounced when dealing with requirements artefacts that need to be matched with design components in the refinement process. In such a case, requirements can be described with terms drawn from a problem domain (e.g. games), whereas designs with the use of terms characteristic for the solution domain (e.g. implementation). The two domains have not only distinct terminology, but also different semantics and use of their artefacts. This paper describes a method of cross-domain classification of requirements texts with a view to facilitate their reuse and their refinement into reusable design components.


IEEE Computer Society Solution Domain Requirement Engineer Software Reuse Requirement Document 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Agresti, W.W., McGarry, F.E.: The Minnowbrook Workshop on Software Reuse: A summary report. In: Tracz, W. (ed.) Software Reuse: Emerging Technology, pp. 33–40. Computer Society Press, Washington (1988)Google Scholar
  2. 2.
    Aguilera, C., Berry, D.M.: The use of a repeated phrase finder in requirements extraction. Journal of Systems and Software 13(3), 209–230 (1990)CrossRefGoogle Scholar
  3. 3.
    Allen, B.P., Lee, S.D.: A knowledge-based environment for the development of software parts composition systems. In: 11th International Conference on Software Engineering, pp. 104–112. IEEE Computer Society Press, Pittsburgh (1989)CrossRefGoogle Scholar
  4. 4.
    Basili, V.R.: Viewing maintenance as reuse-oriented software development. IEEE Software, 19–25 (1990)Google Scholar
  5. 5.
    Bellinzona, R., Fugini, M.G., Pernici, B.: Reusing specifications in OO applications. IEEE Software 12(2), 65–75 (1995)CrossRefGoogle Scholar
  6. 6.
    Borgida, A., Greenspan, S., Mylopoulos, J.: Knowledge representation as the basis for requirements specifications. IEEE Computer, 82–90 (1985)Google Scholar
  7. 7.
    Bubenko, J., Rolland, C., Loucopoulos, P., DeAntonellis, V.: Facilitating ”Fuzzy to Formal” requirements modelling. In: The First International Conference on Requirements Engineering, pp. 154–157. IEEE Computer Society Press, Colorado Springs (1994)CrossRefGoogle Scholar
  8. 8.
    Castano, S., De Antonellis, V.: The F3 Reuse Environment for Requirements Engineering. ACM SIGSOFT Software Engineering Notes 19(3), 62–65 (1994)CrossRefGoogle Scholar
  9. 9.
    Cybulski, J.: Application of Software Reuse Methods to Requirements Elicitation from Informal Requirements Texts, PhD Thesis Draft, La Trobe University, Bundoora (1999) Google Scholar
  10. 10.
    Cybulski, J.L., Reed, K.: Automating Requirements Refinement with Cross-Domain Requirements Classification. Australian Journal of Information Systems, Special Issue on Requirements Engineering, 131–145 (1999)Google Scholar
  11. 11.
    Davis, A.M.: Predictions and farewells. IEEE Software 15(4), 6–9 (1998)CrossRefGoogle Scholar
  12. 12.
    DoD: Software Reuse Initiative: Technology Roadmap, V2.2, Report, Department of Defense (1995),
  13. 13.
    Fowler, M.: Analysis Patterns: Reusable Object Models. Addison-Wesley, Menlo Park (1997)Google Scholar
  14. 14.
    Frakes, W., Isoda, S.: Success factors of systematic reuse. IEEE Software 11(5), 15–19 (1994)CrossRefGoogle Scholar
  15. 15.
    Frakes, W., Prieto-Diaz, R., Fox, C.: DARE: domain analysis and reuse environment. Annals of Software Engineering 5, 125–141 (1998)CrossRefGoogle Scholar
  16. 16.
    Frakes, W.B., Pole, T.P.: An empirical study of representation methods for reusable software components. IEEE Transactions on Software Engineering 20(8), 617–630 (1994)CrossRefGoogle Scholar
  17. 17.
    Fugini, M.G., Faustle, S.: Retrieval of reusable components in a development information system. In: Ruben, P.-D., William, B.F. (eds.) Advances in Software Reuse: Selected Papers from the Second International Workshop on Software Reusability, pp. 89–98. IEEE Computer Society Press, Los Alamitos (1993)Google Scholar
  18. 18.
    Garg, P.K., Scacchi, W.: Hypertext system to manage software life-cycle documents. IEEE Software 7(3), 90–98 (1990)CrossRefGoogle Scholar
  19. 19.
    Girardi, M.R., Ibrahim, B.: A software reuse system based on natural language specifications. In: 5th Int. Conf. on Computing and Information, Sudbury, Ontario, Canada, pp. 507–511 (1993)Google Scholar
  20. 20.
    Johnson, W.L., Harris, D.R.: Sharing and reuse of requirements knowledge. In: 6th Annual Knowledge-Based Software Engineering Conference, pp. 57–66. IEEE Computer Society Press, New York (1991)CrossRefGoogle Scholar
  21. 21.
    Kaindl, H.: The missing link in requirements engineering. ACM SIGSOFT Software Engineering Notes 18(2), 30–39 (1993)CrossRefGoogle Scholar
  22. 22.
    Kaiya, H., Saeki, M., Ochimizu, K.: Design of a hyper media tool to support requirements elicitation meetings. In: Seventh International Workshop on Computer-Aided Software Engineering, pp. 250–259. IEEE Computer Society Press, Toronto (1995)CrossRefGoogle Scholar
  23. 23.
    Kang, K., Cohen, S., Hess, J., Novak, W., Peterson, S.: Feature-Oriented Domain Analysis (FODA) Feasibility Study, Technical Report CMU/SEI-90-TR-21, Software Engineering Institute, Carnegie-Mello University (1990)Google Scholar
  24. 24.
    Kang, K.C., Cohen, S., Holibaugh, R., Perry, J., Peterson, A.S.: A Reuse-Based Software Development Methodology, Technical Report CMU/SEI-92-SR-4, Software Engineering Institute (1992)Google Scholar
  25. 25.
    Lam, W.: A case study of requirements reuse through product families. Annals of Software Engineering 5, 253–277 (1998)CrossRefGoogle Scholar
  26. 26.
    Lowry, M., Duran, R.: Knowledge-based software engineering. In: Barr, A., Cohen, P.R., Feigenbaum, E.A. (eds.) The Handbook of Artificial Intelligence, pp. 241–322. Addison-Wesley Publishing Company, Inc., Reading (1989)Google Scholar
  27. 27.
    Lubars, M.D.: Wide-spectrum support for software reusability. In: Tracz, W. (ed.) Software Reuse: Emerging Technology, pp. 275–281. Computer Society Press, Washington (1988)Google Scholar
  28. 28.
    Lubars, M.D.: The ROSE-2 strategies for supporting high-level software design reuse. In: Lowry, M.R., McCartney, R.D. (eds.) Automatic Software Design, pp. 93–118. AAAI Press / The MIT Press (1991)Google Scholar
  29. 29.
    Lubars, M.D., Harandi, M.T.: Addressing software reuse through knowledge-based design. In: Biggerstaff, T.J., Perlis, A.J. (eds.) Software Reusability: Concepts and Models, pp. 345–377. ACM Addison Wesley Publishing Company, New York (1989)Google Scholar
  30. 30.
    Maiden, N., Sutcliffe, A.: Analogical matching for specification reuse. In: 6th Annual Knowledge-Based Software Engineering Conference, pp. 108–116. IEEE Computer Society Press, New York (1991)CrossRefGoogle Scholar
  31. 31.
    Matsumoto, Y.: Some experiences in promoting reusable software: presentation in higher abstract levels. In: Biggerstaff, T.J., Perlis, A.J. (eds.) Software Reusability: Concepts and Models, pp. 157–185. ACM Addison Wesley Publishing Company, New York (1989)Google Scholar
  32. 32.
    Mili, H., Ah-Ki, E., Godin, R., Mcheick, H.: Another nail to the coffin of faceted controlled-vocabulary component classification and retrieval. Software Engineering Notes 22(3), 89–98 (1997)CrossRefGoogle Scholar
  33. 33.
    Naka, T.: Pseudo Japanese specification tool. Faset 1, 29–32 (1987)Google Scholar
  34. 34.
    Poulin, J.: Integrated support for software reuse in computer-aided software engineering (CASE). ACM SIGSOFT Software Engineering Notes 18(4), 75–82 (1993)CrossRefGoogle Scholar
  35. 35.
    Prieto-Diaz, R.: Domain analysis for reusability. In: Tracz, W. (ed.) Software Reuse: Emerging Technology, pp. 347–353. IEEE Computer Society Press, Los Alamitos (1988)Google Scholar
  36. 36.
    Prieto-Diaz, R., Freeman, P.: Classifying software for reusability. IEEE Software 4(1), 6–16 (1987)CrossRefGoogle Scholar
  37. 37.
    Puncello, P.P., Torrigiani, P., Pietri, F., Burlon, R., Cardile, B., Conti, M.: ASPIS: a knowledge-based CASE environment. IEEE Software, 58–65 (1988)Google Scholar
  38. 38.
    Salton, G.: Automatic Text Processing: The Transformation, Analysis, and Retrieval of Information by Computer. Addison-Wesley Pub. Co., Reading (1989)Google Scholar
  39. 39.
    Simos, M.: WISR 7 Working Group Report: Domain Model Representations Strategies: Towards a Comparative Framework, Andersen Center, St. Charles, Illinois (1995),
  40. 40.
    Simos, M.A.: The growing of organon: a hybrid knowledge-based technology and methodology for software reuse. In: Prieto-Diaz, R., Arango, G. (eds.) Domain Analysis and Software Systems Modeling, pp. 204–221. IEEE Computer Society Press, Los Alamitos (1991)Google Scholar
  41. 41.
    Tamai, T.: Applying the knowledge engineering approach to software development. In: Matsumoto, Y., Ohno, Y. (eds.) Japanese Perspectives in Software Engineering, pp. 207–227. Addison- Wesley Publishing Company, Singapore (1989)Google Scholar
  42. 42.
    Wirsing, M., Hennicker, R., Stabl, R.: MENU - an example for the systematic reuse of specifications. In: 2nd European Software Engineering Conference, pp. 20–41. Springer, Heidelberg (1989)Google Scholar
  43. 43.
    Yglesias, K.P.: Information reuse parallels software reuse. IBM Systems Journal 32(4), 615–620 (1993)CrossRefGoogle Scholar
  44. 44.
    Zeroual, K.: KBRAS: a knowledge-based requirements acquisition system. In: 6th Annual Knowledge-Based Software Engineering Conference, pp. 38–47. IEEE Computer Society Press, New York (1991)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2000

Authors and Affiliations

  • Jacob L. Cybulski
    • 1
  • Karl Reed
    • 2
  1. 1.Dept of Information SystemsUniversity of MelbourneParkvilleAustralia
  2. 2.School of Computer Science and Computer EngineeringLa Trobe UniversityBundooraAustralia

Personalised recommendations