Examples needed...

[raidolinja]

Hallo.
I'm very confused.
Is it possible to find .eap project files as examples of models? I'm trying to map an organization system, but newbie in using UML tools?

[mikewhit]

If you are completely new to UML as well, I suggest you first of all get one (or more) of the tutorial books on the subject and at least familiarise yourself with the diagrams and concepts.

A modelling tool is no good if you don't understand what it's trying to do.

A couple that do a straightforward job are:
UML Weekend Crash Course (Pender)  Wiley Publishing ISBN 0-7645-4910-3 [not UML 2]

Teach Yourself UML (Schmuller) Sams Publishing ISBN 0-672-32640-X [includes UML 2]


If you're trying to capture an existing system implementation, have a look at the EAExample.eap file, in the Component Model of the Messenger example - there you can see how the subsystems and interconnections are represented.

You could then start by representing your existing application's components. As you discover more detail about each component, you can create and link in another diagram to show it, eventually including Class diagrams if you have the source code.

But by mapping an existing system you will only be using the structural parts of UML (showing what is there) - to include any behaviour you will need to understand and describe its operation !

[thomaskilian]

raidolinja,
use search "examples" in this board. There are some useful discussions about it...

[raidolinja]

Well, I am familiar with UML basics (Fowlers "UML Distilled"+ea_help) and know for what diagrams are and for what to use them. But it is still very hard to map something - giving overview of the infosystem and typical processes and to bound them as whole project.  That is why I am looking for examples. I think that eaexample.eap is not for me, aren't there anything else?


Excuse my english.
Raidolinja

[thomaskilian]

Raidolinja,
AFAIK there are no public sources for EAP files. I suggest you start from a scratch file and extend this basis in time. My project files look like this:  
Root Level :"my companies name"
- View (use any icon you like): "project name"
- - Project Definition
- - - Project organization
- - - Stakeholders
- - - Requirements (split up as needed; fuctional/non-func/etc.)
- - Business Process Modell (not always there)
- - Use Case Model
- - - Actors
- - - further packaging
- - Domain Model (incl. Use Case Realizations)
- - Design Model
- - - M: Data Model
- - - V: Human Interface
- - - C: Control Model
- - - Technical Architecture Model
- - - - Component Model
- - - - Deployment
- - - - Environment
- - - - Interfaces
- V: Common (things common to all projects)

This is just a sample structure which fits for my purposes. You are encouraged to find out a structure for yourself. The one above was derived by an article someone posted in this board.