Mapping my Process to EA, UCases -> Activities

[SamJolly]

Dear All,

I am new to EA, UML and Processes that use UML like Iconix and RUP. However I have my own home cooked process for working out requirements which usually start with a pice of A3 and a pencil!!

Basically what I do is:

a) Do a Overview Business Process - standard Process mapping to get the process right.
b) From a) Identify the Use Case Models for each role, and Use cases for each model.
c) Process map each Use Case - Happy path to start with, carefully identifying Verbs and Nouns to indentify Methods and Classes.
d) Create Class diagram for ERD for RDMS design.

With EA I want to make this more efficient. I believe in 'divide and conquer' and would hope a tool such as EA would enable me to create Activity diagrams for each USe Case with links. Can you choose to create a Activity diagram for a Use Case, or do you have to create an Activity diagram and then link it back to a Use Case.

I work, as a freelancer on small projects using web app technology such as ASP/COM/XSLT/JS. What I need is a method and tools to enable me to be create requirements and designs quickly - must not be overweight. Also interested in any recommended training materials. I have had a little look at ICONIX, and have their introductory CDROM.  

Any ideas to the above are hugely appreciated.

Many thanks,

Sam

[thomaskilian]

Hi Sam,
by coincidence http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.cgi?board=UMLPRO;action=display;num=1089917358 ran in parallel with your question.

Regarding the requirements: EA is a very powerful tool to capture and sort out requirement. First you need to have som good project structure (see http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.cgi?board=general;action=display;num=1033756093;start=2#2)
Having that, you can capture your requirements in one package/diagram, note who stated which by adding associations to the appropriate stakeholder (actor) and then sort out the requirement (function, non-functional like extensibility, performance a.s.o.) After that you will be able to construct use case etc. The ICONIX way is quite applicable but you need a bit practice.