This week's book giveaways are in the Cloud/Virtualization and Go forums. We're giving away four copies each of Cloud Native Transformation: Practical Patterns for Innovation and The Go Workshop and have the authors on-line! See this thread and this one for details.
I am new to Java and this forum as well. I heard a lot about the book "Head first Java" and am gonna start reading it from Monday. The book's gonna come only on Monday .I've noticed that one of the same authors moderates this forum so I've joined it and this is my first post in this forum.
Coming to my question,
I am trying to do high level documentation for a client-server ftp application and I was wondering if the class/sequence diagrams should be just one or should it be two. One for the client and one for the server? Also, any comments on how to build some nice diagrams and using which tools are welcome.
First, a bit of business: you may not have read our naming policy on the way in. It requires that you use a full, real (sounding) first and last name for your display name. Nicknames and "handles" don't cut it here. You can change your display name here. Thanks!
I am trying to do high level documentation for a client-server ftp application and I was wondering if the class/sequence diagrams should be just one or should it be two. One for the client and one for the server?
Do what is necessary to communicate your "message". If the issue is to illustrate events on the either the server or the client then only stay in that context otherwise show both. I suspect that you will need at least one diagram that shows the exchange between the client and the server without any "object details". If you need to go to a lower level of detail you are looking at two more diagrams one for the server and one for the client that may show the object level where the high-level exchanges are modeled as external events. Using only two diagrams without the higher-level mapping may make things more difficult for your audience than it needs to be.