 |  |  |  |  |  |  |  |
class diagram/uml
 |
•
•
Join Date: Nov 2004
Posts: 257
Reputation: 
Solved Threads: 1
Posting Whiz in Training
hi,
Now i am really confused, so how would i represent the server side of an application, say i am doing an instant messenger, which is not web based,....
thank you
Now i am really confused, so how would i represent the server side of an application, say i am doing an instant messenger, which is not web based,....
thank you
In the clientside diagram(s), you wouldn't.
You'd only include a highlevel package containing shared classes.
In the serverside(s), you don't include the client and only a highlevel package with those same shared classes.
You'd have a third set containing detailed diagrams of those shared classes.
That immediately forces you to think about the design of your application, cutting it up into distinct (reusable) components.
You'd only include a highlevel package containing shared classes.
In the serverside(s), you don't include the client and only a highlevel package with those same shared classes.
You'd have a third set containing detailed diagrams of those shared classes.
That immediately forces you to think about the design of your application, cutting it up into distinct (reusable) components.
As people are clearly allowed to attack me but I'm not allowed to defend myself, I no longer post to this site.
•
•
Join Date: Nov 2004
Posts: 257
Reputation:
Solved Threads: 1
Posting Whiz in Training
hi,
so what you are saying is that if i have a client and server application i need to model both sides with the class diagram, but seperately.........
thank you
so what you are saying is that if i have a client and server application i need to model both sides with the class diagram, but seperately.........
thank you
yes, they're different applications.
In the real world they'd be different projects or subprojects and should be treated as such.
And the interaction layer is a different project or subproject again.
They'll also have different usecases with quite different actors.
In the real world they'd be different projects or subprojects and should be treated as such.
And the interaction layer is a different project or subproject again.
They'll also have different usecases with quite different actors.
As people are clearly allowed to attack me but I'm not allowed to defend myself, I no longer post to this site.
|
Similar Threads
- Class Diagram (C++)
Other Threads in the Java Forum
- Previous Thread: Noob : Input Stream Trouble
- Next Thread: Javadoc problems
| Thread Tools | Search this Thread |
You need to join our community in order to build your list of favorite forums. You can visit the forum index for a listing of all forums.
Related Forum Features
Latest Java Posts
- Today's Posts
- Unanswered Threads
911 actionlistener addressbook android api append applet application array arrays automation binary block bluetooth character chat class client code component consumer csv database desktop developmenthelp eclipse error fractal ftp game givemetehcodez graphics gui html ide image input integer j2me j2seprojects japplet java javaarraylist javac javaee javaprojects jni jpanel julia lego linked linux list loop loops mac map method methods mobile netbeans newbie number objects online oriented panel printf problem program programming project projects properties recursion replaydirector reporting researchinmotion rotatetext rsa scanner se server set sms sort sql string swing test textfields threads time title tree tutorial-sample ubuntu update windows working
