skip to main content
10.5555/783106.783140dlproceedingsArticle/Chapter ViewAbstractPublication Pagesaus-cscConference Proceedingsconference-collections
Article
Free Access

Refactoring use case models: the metamodel

Authors Info & Claims
Published:01 February 2003Publication History

ABSTRACT

This paper describes how refactoring as a concept can be broadened to apply to use case models. A metamodel for use case modeling is described in detail, which represents our perspective on use case formalization. This metamodel allows us to define several categories of use case refactorings that help us discover and organize use case refactorings. A list of current refactorings is given. Finally, we illustrate the concept of use case refactorings with a simple example.

References

  1. Anton, A. I. (1997), Goal identification and refinement in the specification of software-based information systems, Ph.D.thesis, Georgia Institute of Technology. Google ScholarGoogle ScholarDigital LibraryDigital Library
  2. Anton, A. I. & McCracken, W. M. & Potts, C. (1994), Goal decomposition and scenario analysis in business process reengineering, advanced information systems engineering, 6th International Conference Proceedings (CaiSE'94), pp.94-104. Google ScholarGoogle ScholarDigital LibraryDigital Library
  3. Beck, K. (1999), Extreme Programming Explained: Embrace Change, Addison-Wesley. Google ScholarGoogle ScholarDigital LibraryDigital Library
  4. Buhr, R. J. A. (1998), Use Case Maps as Architectural Entities for Complex Systems. Transactions on Software Engineering, IEEE, Vol. 24, No. 12, pp. 1131-1155. Google ScholarGoogle ScholarDigital LibraryDigital Library
  5. Butler, G. & Xu, L. (2001), Cascaded refactoring for framework evolution, Proceedings of 2001 Symposium on Software Reusability, ACM Press, pp. 51-57. Google ScholarGoogle ScholarDigital LibraryDigital Library
  6. Cockburn, A. (1997), Structuring use cases with goals, JOOP/ROAD 10(5) and 10(7).Google ScholarGoogle Scholar
  7. Constantine, L. L. & Lockwood, L. A. D. (2001), Structure and style in use cases for user interface design, In Mark Van Harmelen, editor, Object Modeling and User Interface Design, Addison-Wesley. Google ScholarGoogle ScholarDigital LibraryDigital Library
  8. Dardenne, A. & Van Lamsweerde, A. & Fickas, S. (1993), Goal-directed requirements acquisition, Science of Computer Programming, 20, 3-50. Google ScholarGoogle ScholarDigital LibraryDigital Library
  9. Firesmith, D. G. & Henderson-Sellers, B. & Graham, I. (1997), OPEN Modeling Language (OML) Reference Manual, SIGS, New York. Google ScholarGoogle ScholarDigital LibraryDigital Library
  10. Fowler, M. (1999), Refactoring: Improving the Design of Existing Code, Addison-Wesley. Google ScholarGoogle ScholarDigital LibraryDigital Library
  11. Graham, I. (1994), Migrating to Object Technology, Addison-Wesley. Google ScholarGoogle ScholarDigital LibraryDigital Library
  12. Henderson-Sellers, B. & Firesmith, D.G. (1997), Choosing between UML and OPEN, American Programmer, 10(3), 15-23.Google ScholarGoogle Scholar
  13. Henderson-Sellers, B. & Firesmith, D. G. & Graham, I. (1997), OML Metamodel: Relationships and State Modeling, JOOP 10, 1, March/April.Google ScholarGoogle Scholar
  14. Jacobson, I. & Booch, G. & Jonsson, P. & Overgaard, G. (1992), Object-Oriented Software Engineering: A Use-Case Driven Approach, Addison-Wesley. Google ScholarGoogle ScholarDigital LibraryDigital Library
  15. Jacobson, I. & Booch, G. & Rumbaugh, J. (1999), The Unified Software Development Process, Addison Wesley. Google ScholarGoogle ScholarDigital LibraryDigital Library
  16. Jacobson, I. & Ericsson, M. & Jacobson, A. (1994), The Object Advantage: Business Process Reengineering with Object Technology, ACM Press. Google ScholarGoogle ScholarDigital LibraryDigital Library
  17. Lewis, C. (1990), A research agenda for the nineties in human-computer interaction, Human-Computer Interaction, 5, 125-143.Google ScholarGoogle ScholarDigital LibraryDigital Library
  18. Miller, G. G. & McGregor, J.D. & Major, M. L. (1999), Capture framework requirements, In M. E. Fayad, D. C. Schmidt, and R. E. Johnson, editors, Building Application Frameworks: Object-Oriented Foundations of Framework Design . Wiley.Google ScholarGoogle Scholar
  19. Nielsen, J. (1994), Goal composition: extending task analysis to predict things people may want to do, http://www.useit.com/papers/goalcomposition.htmlGoogle ScholarGoogle Scholar
  20. Opdyke, W. F. (1992), Refactoring object-oriented frameworks, Ph.D. thesis, University of Illinois. Google ScholarGoogle ScholarDigital LibraryDigital Library
  21. Rational Corporation, (1997), UML Summary, Semantics, Notation Guide, Version 1.1, Rational Software Corporation.Google ScholarGoogle Scholar
  22. Regnell, B. (1999), Requirements engineering with use cases -- a basis for software development, Ph.D. thesis, Lund University.Google ScholarGoogle Scholar
  23. Roberts, D. B. (1999), Practical analysis for refactoring , Ph.D. thesis, University of Illinois. Google ScholarGoogle ScholarDigital LibraryDigital Library
  24. Rumbaugh, J. & Jacobson, I. & Booch, G. (1999), The Unified Modeling Language Reference Manual , Addison-Wesley. Google ScholarGoogle ScholarDigital LibraryDigital Library
  25. Schach,, S. R. (1999), Software Engineering with JAVA, McGraw-Hill. Google ScholarGoogle ScholarDigital LibraryDigital Library
  26. Tokuda, L. (1999), Evolving object-oriented designs with refactorings, Ph.D. thesis, University of Texas at Austin. Google ScholarGoogle ScholarDigital LibraryDigital Library

Index Terms

  1. Refactoring use case models: the metamodel

          Recommendations

          Comments

          Login options

          Check if you have access through your login credentials or your institution to get full access on this article.

          Sign in

          PDF Format

          View or Download as a PDF file.

          PDF

          eReader

          View online with eReader.

          eReader