uml - UMLet Diagrams like Use Case, Class, Activity, etc -

can please me find detailed tutorial on topics:

1. uml
2. behavior diagrams
   1. use case diagrams
   2. activity diagrams
3. structure diagrams
   1. class diagram
4. interaction diagrams
   1. sequence diagram
   2. communication diagram

i'm newbie , want know ideas in using uml diagrams, there differences, , tools (like umlet) ideal novices me.

first , let me discuss uml , use cases.

uml graphical way of describing software systems. there 2 types of uml namely:

1. uml sketching - here want communicate idea , go through different alternative approaches. it's not specific gives basic ideas.
2. uml blueprint - detailed type of modeling in laid out , there definite time of completion.

next uml development process.

1. waterfall model - development process must follow analysis, design, coding, , testing process strictly. meaning can't coding without design, , on. must start analysis, design, coding , testing (adct) process. overlapping within processes not allowed.
2. iterative (most common) - iterative way kinda different waterfall model in sense more flexible. can divide system pieces , run adct process on each piece. meaning not analysis once, make system flexible changes. no wonder more common type of approach.

then there's uml planning process

1. predictive planning - outcome known whole duration of project , should run smoothly stakeholders involve, 'on same page'. if can list requirements , pretty sure not change, use predictive planning.

2. adaptive planning (agile development) - here developer continually works user possible changes. act 'adaptor' -- changes. it's flexibility makes better option predictive planning.

finally use case diagrams. use case diagrams define how program solve problems or provide functionality.

here's example:

use case diagrams deals interaction of actors human, or external system. use cases represented elipses "insert card".

the line actor towards use cases called communication lines.

the 'include' part means 2 or more use case try access single use case. whereas 'extend' part when use case try access optional use case.

the 'select amount' use case general use case while under 2 specific use cases.

after use case description. description of use case. " user enters card , inputs pin. system security check if card active or not stolen and/or if inputted pin correct", etc. wrapped saying system (security) provide funds , receipt.

another thing note

1. triggers (machine receives card/user enters pin)

2. actors

3. preconditions (e.g., bank has sufficient funds)
4. goals (e.g., successful conclusions being able provide user funds).
5. list failed conclusion (ex: invalid card)
6. extensions (ex: if pin invalid after 3 3 tries)
7. steps of execution (ex: customer inserts card ejection of card)

activity diagrams

activity diagrams describes actions occurred achieve ultimate goal. if familiar flow charts, easier understand concepts behind activity diagrams.

initial nodes starting point of activity diagram symbolize shaded circle.the purple colored notes describes different components of activity diagram.

class diagrams

classes describes types of objects program use while class diagrams describe classes , how relate.

i upload slide shows make tutorial faster:

sequence diagrams

sequence diagrams model interactions in program , provide logical way layout system. showing order of interactions between parts of program.

in making sequence diagrams, describe interactions triggered , when. focus in on order of events in interactions.

again, here sequence diagrams of tutorial:

communication diagrams

communication diagrams used show links between participants. focus in on interactions triggered , when. describe order of events in interactions.

these ideas video tutorials of derek banas

here list of uml tools. free. :)