Home > Archive > Software Engineering > October 2007 > Desktop Application Class Diagram
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Desktop Application Class Diagram
|
|
| Manuel 2007-10-06, 8:04 am |
| hi to all,
I need to make a class diagram of a desktop application(plugin of
another app), is common pratice make object like "UserInterface" with
button and textfield attributes?
| |
| H. S. Lahman 2007-10-06, 7:07 pm |
| Responding to Manuel...
> I need to make a class diagram of a desktop application(plugin of
> another app), is common pratice make object like "UserInterface" with
> button and textfield attributes?
Usually the UI paradigm is encapsulated within a subsystem. That allows
the UI paradigm to be substituted transparently for the application. It
also allows one to abstract the invariants of the specific UI paradigm
within the subsystem. Thus the dominant objects for a GUI would be
Window and Control while the dominant objects for a browser UI would be
Page and Section. Thus a button or textbox in a GUI would be
specializations of a standalone Control object.
However, if your software is a plugin to another application, that other
application may already handle the UI and you simply need surrogate
objects to represent whatever mechanisms that application provides for
accessing its UI. How one would abstract that depends very much on what
sorts of mechanisms the application provides (i.e., what interface /it/
presents to plugins).
If those mechanisms are very simple, then it is conceivable that a
single Interface object in your software could be the surrogate for
those mechanisms as you describe it.
--
*************
There is nothing wrong with me that could
not be cured by a capful of Drano.
H. S. Lahman
hsl@pathfindermda.com
Pathfinder Solutions
http://www.pathfindermda.com
blog: http://pathfinderpeople.blogs.com/hslahman
"Model-Based Translation: The Next Step in Agile Development". Email
info@pathfindermda.com for your copy.
Pathfinder is hiring:
http://www.pathfindermda.com/about_us/careers_pos3.php.
(888)OOA-PATH
| |
|
| Manuel wrote:
> I need to make a class diagram of a desktop application(plugin of another
> app), is common pratice make object like "UserInterface" with button and
> textfield attributes?
Why do you need to draw this diagram? Who will read it, and what will they
do with it?
What's common practice is to answer a question, like "how is this module
designed to accept upgrades?", or "what happens when we click that button?"
Then you only put in the diagram the details which answer that question. Not
all the extraneous details, like all the buttons on a window, or the details
of your library's String class...
--
Phlip
|
|
|
|
|