Abstract
The UML specifies that a subsystem is both a package and a classifier. This paper explores what that could possibly mean and explains why that was the right choice. It points out a key to the use of the concept in CASE tools, mentions the historical precedent for that key, and challenges CASE tools to support the flexibility that architects and designers need. Along the way, the paper reviews a method for discovering a good partition of a system into subsystems, describes a scheme for using UML to build a model of a system, and suggests some changes to the UML.
Cite
CITATION STYLE
Miller, J., & Wirfs-Brock, R. (1999). How can a subsystem be both a package and a classifier? In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) (Vol. 1723, pp. 584–597). Springer Verlag. https://doi.org/10.1007/3-540-46852-8_41
Register to see more suggestions
Mendeley helps you to discover research relevant for your work.
