Re: UML Structured class with utility parts?
- From: "H. S. Lahman" <h.lahman@xxxxxxxxxxx>
- Date: Thu, 20 Apr 2006 15:19:43 GMT
Responding to JMF...
I'm trying to sort out what must be a simple situation.
I want to have a "module" of "utilities". The utilities are simply things like stacks, lists, those kinds of things. The idea of the "module" is simply that they are all in one place -- like a library, I suppose.
Then, to build my application, I want to represent application modules as structured classes or components.
These components will make use of the utilities. They'll have stacks inside them, etc.
What I'm trying to sort out in my head is "where things are" and "what actually exists physically."
The short answer is: It depends. B-) It depends upon what sort of problem you are solving.
For example, if your application is something like a code generator, then you would have to model explicitly things like composition of "utilities" into "modules" because that is what the problem is about. That is, the application itself is selecting and collecting things into components in response to external instructions (source model, etc.). However,...
For example, my application module, when actually instantiated in real code, will presumably contain an instantiated stack. Or even two or three of them.
Does that mean that the "module" or "library" where my stack is defined actually contains nothing, only the definition of the stack?
This sounds more like a deployment issue for the software rather than a logical solution issue. That is, you -- as developer -- are selecting the "utilities" needed and are placing them in your OOA/D UML model to be consistent with the solution to the problem in hand. So you will abstract a Stack class in your solution if you need one to solve the problem. But all you are describing is the solution logic, not how that solution will be implemented at the 3GL level.
As a practical matter the classes in the OOA/D model may reside in a library (or some other form) at OOP time when they are actually implemented. At that point the OOP programmer needs to know what the mechanisms are for access, class reuse, etc.. The UML Deployment Diagram is intended to provide that sort of deployment information about where the actual model elements live.
*************
There is nothing wrong with me that could
not be cured by a capful of Drano.
H. S. Lahman
hsl@xxxxxxxxxxxxxxxxx
Pathfinder Solutions -- Put MDA to Work
http://www.pathfindermda.com
blog: http://pathfinderpeople.blogs.com/hslahman
(888)OOA-PATH
.
- References:
- UML Structured class with utility parts?
- From: JMF
- UML Structured class with utility parts?
- Prev by Date: Re: Question on Effective Java Item 27
- Next by Date: Re: UML Structured class with utility parts?
- Previous by thread: UML Structured class with utility parts?
- Next by thread: Re: UML Structured class with utility parts?
- Index(es):
Relevant Pages
|