Advertisement

Using Hierarchies to Adapt Domain Analysis to Software Development

  • Marko J. Forsell

Abstract

Software development strives toward increasing the amount and quality of the software and at the same time decreasing the costs and development time. One approach to achieve these diverse goals is the systematic software reuse (Biggerstaff and Richter, 1987). In the reuse-oriented software development the key success factor is domain analysis (DA) (Arango, 1989; Lam and McDermid, 1997; Prieto-Díaz, 1994). DA is a process through which information used in software development is identified, captured, and organized with the purpose of making it reusable when creating new systems (Prieto-Díaz, 1990). While the traditional development methods (e.g., Jaaksi et al.,1999; Jacobson et al., 1999) focus on one application, DA focuses on classes of applications (Arango, 1994).

Keywords

Software Development Unify Modeling Language Domain Expert Domain Analysis Software Architecture 
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.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Arango, G. “Domain analysis-From Art Form to Engineering Discipline,” Proceedings of the 5 th International Workshop on Software Specifications and Designs, 1989, pp. 152–159.Google Scholar
  2. Arango, G. “Domain analysis methods,” in (eds.) Schäfer, W., Prieto-Díaz, R., and Matsumoto, M. Software Reusability, Ellis Horwood Ltd., 1994, pp. 17–49.Google Scholar
  3. Arango, G. and Prieto-Díaz, R. “Domain Analysis Concepts and Research Directions,” in (eds.) Prieto-Díaz, R. and Arango, G. Domain Analysis and Software Systems Modeling. IEEE Computer Society Press Tutorial, 1991, pp. 9–32.Google Scholar
  4. Bayer, J., Flege, O., Knauber, P., Lagua, R., Muthig, D., Schmid, K., Widen, T., and DeBaud, J.-M. “PuLSE: A Methodology to Develop Software Product Lines,” Proceedings of the 1999 Symposium on Software Reusability, pp. 122–131.CrossRefGoogle Scholar
  5. Biggerstaff, T. and Richter, C. “Reusability Framework, Assessment, and Directions,” IEEE Software, March 1987, pp. 41–49.Google Scholar
  6. Booch, G., Rumbaugh, J., and Jacobson, I. The Unified Modeling Language User Guide, Addison Wesley Longman Inc., 1999.Google Scholar
  7. Clements, P. and Northrop, L. “Software Architecture: An Executive Overview,” Technical Report, CMU/SEI-96-TR-003, Software Engineering Institute, Carnegie Mellon University, 1996.Google Scholar
  8. Codenie, W., De Hondt, K., Steyaert, P., and Vercammen, A. d“dFrom Custom Applications to Domain-Specific Frameworks,” Communications of the ACM, Vol. 40, No. 10, October 1997, pp. 70–77.Google Scholar
  9. D'Souza, D. and Wills, A. Objects, Components, and Frameworks with UML: The Catalysis Approach, Addison-Wesley, 1999.Google Scholar
  10. Forsell, M., Halttunen, V., and Ahonen, J. “Use and Identification of Components in Component-based Software Development Methods,” To appear in the Proceedings of the Sixth International Conference on the Software Reusability, Vienna, Austria, June 27–29, 2000.Google Scholar
  11. Freeman, P. “Reusable Software Engineering: Concepts and Research Directions,” ITT Proceedings of the Workshop on reusability in Programming, 1983, pp. 129–137.Google Scholar
  12. Horowitz, E. and Munson, J. “An Expansive View of Reusable Software,” IEEE Transactions on Software Engineering, Vol. 10, No. 5 September 1984, pp. 477–487.Google Scholar
  13. Jaaksi, A., Aalto, J.-M., Aalto, A., and Vättö, K. Tried & True Object Development: Industry-Proven Approaches with UML, Cambridge University Press, Cambridge, 1999.Google Scholar
  14. Jacobson, I., Griss, M., and Jonsson, P. Software Reuse: Architecture, Process and Organization for Business Success, ACM Press, New York, 1997.Google Scholar
  15. Jacobson, I., Booch, G., and Rumbaugh, J. The Unified Software Development Process, Addison Wesley Longman, Inc., 1999.Google Scholar
  16. Jackson, M. “Problems, Methods and Specialisation,” Software Engineering Journal, Vol. 9, No. 6, November 1994, pp. 249–255.Google Scholar
  17. Jarzabek, S. “Modeling Multiple Domains in Software Reuse,” Proceedings of the 1997 Symposium on Software Reusability, 1997, pp. 65–74.CrossRefGoogle Scholar
  18. Karlsson, E. (ed.) Software Reuse: A Holistic Approach, John Wiley & Sons Ltd., Chichester, 1995.Google Scholar
  19. Krueger, C.“Software Reuse,” ACM Computing Surveys, Vol. 24, No. 2, June 1992, pp. 131–183.Google Scholar
  20. Kruchten, P.“The 4 + 1 View Model of Architecture,” IEEE Software, Vol. 12, No. 6, November 1995, pp. 42–50.Google Scholar
  21. Lam, W. and McDermid, J.“A Summary of Domain Analysis Experience by Way of Heuristics,” Proceedings of the 1997 Symposium on Software Reusability, 1997, pp. 54–64.CrossRefGoogle Scholar
  22. McCain, R. “Reusable Software Component Construction: A Product-Oriented Paradigm,” Proceedings of the 5th AIAA/ACM/NASA/IEEE Computers in Aerospace, 1985, pp. 125–135.Google Scholar
  23. Mclllroy, M. “Mass-produced Software Components,” in (eds.) Buxton, J.M., Naur, P., and Randell, B. Software Engineering Concepts and Techniques, 1968 NATO conference on Software Engineering, Petroce1li/Charter, Belgium, 1976, pp. 88–89.Google Scholar
  24. Mintzberg, H. Structure in Fives: Designing Effective Organizations, Prentice-Hall, Inc., Englewood Cliffs, N.J., 1983.Google Scholar
  25. Mintzberg, H. “A Typology of Organizational Structure,” in Miller, D. and Friesen, P. Organizations A Quantum View, Prentice-Hall Inc., 1984, pp. 68–86.Google Scholar
  26. Moore, J. and Bailin, S.“Domain Analysis: Framework for Reuse,” in (eds.) Prieto-Díaz, R. and Arango, G. Domain Analysis and Software Systems Modeling, IEEE Computer Society Press, 1991, pp. 179–203.Google Scholar
  27. Neighbors, J. “Software Construction Using Components,” Ph.D. Thesis, Department of Information and Computer Science, University of California, Irvine, 1980.Google Scholar
  28. Neighbors, J.“DRACO: A Method for Engineering Reusable Software Systems,” in (eds.) Biggerstaff, T. and Perlis, A. Software Reusability, Volume I, Concepts and Models, ACM Pressl989, pp. 295–319.Google Scholar
  29. Parnas, D.“On the Design and Development of Program Families,” IEEE Transactions on Software Engineering, Vol. SE-2, No. 1, March 1976, pp. 1–9.Google Scholar
  30. Prieto-Díaz, R.“Domain Analysis for Reuse,” Proceedings of COMPSAC '87, 1987, pp. 23–29.Google Scholar
  31. Prieto-Díaz, R. “Domain Analysis: An Introduction,” Software Engineering Notes, Vol. 15, No. 2, April 1990, pp. 47–54.Google Scholar
  32. Prieto-Díaz, R. and Arango, G. (eds.) Domain Analysis and Software Systems Modeling. IEEE Computer Society Press Tutorial, 1991.Google Scholar
  33. Prieto-Díaz, R.“Historical Overview,” in (eds.) Schäfer, W., Prieto-Díaz, R., and Matsumoto, M. Software Reusability, Ellis Horwood Limited, 1994, pp. 1–16.Google Scholar
  34. Shaw, M. and Garlan, D. Software Architecture: Perspectives on an Emerging Discipline, Prentice-Hall Inc., New Jersey, 1996.MATHGoogle Scholar
  35. Simos, M. “Organization Domain Modeling (ODM) Guidebook, Version 2.0,” Informal Technical Report for Software Technology for Adaptable, Reliable Systems (STARS), STARS-VC-A025/001/00, June 14, 1996.Google Scholar
  36. Tracz, W. Confessions of a Used Program Salesman: Institutionalizing Software Reuse, Addison-Wesley Publishing Company, 1995.Google Scholar
  37. Villarreal, E. and Batory, D. “Rosetta: A Generator of Data Language Compilers,” Proceedings of the 1997 Symposium on Software Reusability, Boston, United States, May 17–20 1997, pp. 146–156CrossRefGoogle Scholar
  38. Wartik, S. and Prieto-Díaz, R.“Criteria for Comparing Reuse-Oriented Domain Analysis Approaches,” International Journal of Software Engineering and Knowledge Engineering, Vol. 2, No. 3, September 1992, pp. 403–433.Google Scholar
  39. Wegner, P.“Varieties of Reusability,” ITT Proceedings of the Workshop on Reusability in Programming, 1983, pp. 30–44.Google Scholar
  40. Whittle, B.“Reusing requirement specifications: Lessons Learnt,” Proceedings of the 7th Annual Workshop on Software Reuse, Andersen Consulting Center in St. Charles, Illinois, August 28–30 1995.Google Scholar

Copyright information

© Springer Science+Business Media New York 2001

Authors and Affiliations

  • Marko J. Forsell
    • 1
  1. 1.Department of Information Technology Research InstituteUniversity of JyväskyläFinland

Personalised recommendations