How can a subsystem be both a package and a classifier?

Authors:
Joaquin Miller;Rebecca Wirfs-Brock
Affiliations:
EDS, Minneapolis, MN;Wirfs-Brock Associates, Sherwood, OR
Venue:
UML'99 Proceedings of the 2nd international conference on The unified modeling language: beyond the standard
Year:
1999

Citing 6
Cited 1

Object oriented programming: an evolutionary approach

Object oriented programming: an evolutionary approach
Object identity

OOPLSA '86 Conference proceedings on Object-oriented programming systems, languages and applications
Designing object-oriented software

Designing object-oriented software
Real-time object-oriented modeling

Real-time object-oriented modeling
Software architecture: perspectives on an emerging discipline

Software architecture: perspectives on an emerging discipline
Reliable software through composite design

Reliable software through composite design

Towards a UML profile for software architecture descriptions

UML'00 Proceedings of the 3rd international conference on The unified modeling language: advancing the standard

Quantified Score

Hi-index	0.00

Visualization

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.