Re: UML: Associations between classes and packages

Responding to Kaeppler...

I appreciate your detailed answers, but I'm not very proficient with all the terminology: What does OOA mean? I guess Object Oriented Architecture? And what would OOD and DAO mean?

OOA is Object-Oriented Analysis. It is an abstract solution for just the functional requirements. While executable, an OOA model is independent of the particular computing environment (e.g., Wintel vs. Unix/Spark).

OOD is Object-Oriented Design. It is an elaboration of the OOA solution that addresses nonfunctional requirements within the specific computing environment at a strategic level.

[At the risk of being picky, if you are using UML you really should already know these terms. UML is a notation designed expressly for OOA/D. I would very strongly suggest picking up a couple of books on OOA/D before even attempting to use UML. (The Books category of my blog has some suggestions.)]

OOP is Object-Oriented Programming. It is an elaboration of the OOD solution that addresses nonfunctional requirements tactically at the 3GL (OOPL) level.

DAO is Data Access Object. It is part of Microsoft's layered model for CRUD/USER processing. A DAO is essentially a message data packet that is passed between layers. In the MS view it is a COM object, which allows it to be composed with appropriate architectural infrastructure so that things like distributed layers are transparent.

In your case JFrame, as a language-based infrastructure, would exist almost completely at the OOP level. That's why in UML it can be isolated as an architectural subsystem. Assuming JFrame does support some sort of layered model, then there will probably be some artifact similar to a DAO that might show up at the OOD level.


*************
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



.

Relevant Pages

  • Re: Lets put this to rest
    ... An OOA model is a complete solution specification for functional ... the OOA model does not describe how the application will be implemented in the computing space. ... At the same time, though, that Java program is clearly a concrete implementation of How the OOD specification will be met. ... There is also a useful separation of concerns that supports specialization, which becomes very obvious in translation where the application developer and transformation engine developer essentially belong to different unions. ...
    (comp.object)
  • Re: Lets put this to rest
    ... An OOA model is a complete solution specification for functional requirements. ... In MDA terms an OOA model maps to a Platform Independent Model because it does not depend on the particular computing environment where the application will be implemented. ... OOD is generally regarded as an elaboration of the OOA specification to deal with nonfunctional requirements at a strategic level. ... MDA you are really trying to move from OOA to OOD through "translation" ...
    (comp.object)
  • Re: Lets put this to rest
    ... Abstracting OOA model and intersecting with functional/goal model = ... OOD (more concrete} = {desktop computer, monitor, keyboard, mouse, text ... MDA you are really trying to move from OOA to OOD through "translation" ... what you call OOA/D is not what most people call OOA/D. ...
    (comp.object)
  • Re: Lets put this to rest
    ... An OOA model is a complete solution specification for functional ... MDA methods and techniques. ... OOP is an elaboration of the OOD ... Translation uses that to automate OOD and OOP. ...
    (comp.object)
  • Re: OOA and OOD
    ... Responding to J0mbolar wrote: ... > they understand OOA and OOD. ... I would be cautious about reviews. ...
    (comp.object)