Unified modeling language UML tutorial part 8


Training & Tutorials:

*Roles and Responsibilities of a

 Business Analyst

*What is System Analyst

*What is SDLC and different

 Phases of it?

*What is usecase diagram?

 & its Importance.

*How to draw flowchart? And

 its uses?

*What is RUP? Explain in detail.

*What is UML explain in detail?

*Business Analyst Tutorials

*Business Analyst Interview


*Testing (QA) knowledge Required

 for BA

*Business Analyst Healthcare

 domain Tutorials

*Business Analyst Finance

 Domain Tutorials

*Rational Rose Tools Interview


*Diagrams for Business Analyst

*Resumes for Business Analyst

*Jobs for Business Analyst

*Interviews Tips



BA Interview Questions

*BA Interview questions set 1

*BA Interview questions set 2

*BA Interview questions set 3

*BA Interview questions set 4

*BA Interview questions set 5

*Business analyst Interview

 questions 6

*Business analyst Interview

 questions 7

*Business analyst Interview

 questions 8

*Resume writing tips for BA 9

*General business analyst interview

  questions 10

*Mortgage related interview questions

  for BA 11


Business Analyst Tutorials

*Responsibilities of a Business Analyst

*What is Business Analysis

*Sequence diagram Explained

*Class diagram explained

*RUP explained

*UML(unified modelling language)

*SDLC(systems development life cycle)

*Insurance knowledge for BA

*Health care knowledge for BA

*Finance banking knowledge for BA

*Role of a Business Analyst(high level)

*Use case diagram step by step

*Class Diagrams UML

*Responsibilities of BA

*What is RUP ?

*RUP in SDLC process


*Bug Life cycle

*BA Faq

*Business Users of the system

*Class diagrams

*CMM levels

*Collaboration diagram

*Data Mapping & Data modeling

*Data model in data base

*Deliverables in SDLC

*Tools used by BA

*Q-Gate (quality gate)

*RUP (rational unified processing)

*Sequence diagrams

*Deliverables in RUP

*UML (unified modeling language)

*Use case diagram

*Use case examples

*Use case template examples

*what are JAD sessions?

*What is GAP analysis ?

*What is User acceptance testing (

*Daily duties of a BA

*What is System analyst ?

*UML Tutorial Part 1

*UML Tutorial Part 2

*UML Tutorial Part 3

*UML Tutorial Part 4

*UML Tutorial Part 5

*UML Tutorial Part 6

*UML Tutorial Part 7

*UML Tutorial Part 8


Testing Knowledge

*Testing processes

*QTP recording flow

*Break points in qtp

*Split actions in qtp


*Check Points in QTP

*Integrated testing

*What is QTP ?

*Loadrunner step by step


Business Analyst Finance

*Business Analyst Finance domain

 Interview questions set 1

*What is Fixed rate Loan?

*What is home equity line of credit

  (HELOC) ?

*What is Loan to value ratio ?

*What is debt to income  ratio &

*What is lien Lien holder ?

*What are mutual funds ? Interview


*Trading of Stocks , what are stocks?

*New york Stock exchange

*What is NASDAQ ?

*Stock exchanges in USA

*Factors that will affect the change in

 price of STOCKS

*How to buy a STOCK ?

*What stocks are treated as equity

 while bonds as debt ?

*Some more Finance related interview

  questions for Business analyst

*Imp finance related interview

 questions for BA

*What is SWAP and types of swaps

*What are  Options & Bonds and types

Bonds in finance

*what are Options in finance

*what is a derivative and how it functions

*Who is a broker dealer

*Commercial bank in brokerage industry

*Who is a market maker?

*who is a specialist ?

*What are bond and types of bonds

*Steps for writing use case diagram

*What is SOX (Sarbanes Oxley act)

*CMM Capability maturity model


Business Analyst Health care :

*BA Health Care Claims

*SAS (statistical analysis system)

*Clinical Trials

*What are FACETS

*Health care fraud detection

*What is HIPAA

*Medicare Procedures and policies

*Health care Interview questions for BA


Share on Facebook









6. Implementation Diagrams - Component and Deployment


So far, we've seen how the tasks which the system will perform can be diagrammed along with the details of the system classes, and the system dynamic behavior. But what about the big picture? There are two types of implementation diagrams which strive to provide the solution. With the deployment diagram, you can depict how the system components are physically related, and with the component diagram, you can display the components in the system which are organized.

You can combine the two diagrams if you wish:

Above, the nodes are given in green and the components in maroon. The nodes represent something upon which a component can run, and components are units of software.

On the diagram, nodes are connected with connections which displays the physical path of information with in the system. Components are connected with directed dashed lines which represent the communication between components. You can also use lollipop interfaces on components to depict which of the communication is actually through an interface.

Putting it all Together

The physical diagrams will help with the overall structure and distribution of the system. The component and deployment diagrams can be drawn separately or combined as you choose to do. Also, the components within the nodes need not be displayed as given above, although it will help in the overall understanding of what is being executed where.

Visual Case Tool - UML Tutorial

7. Summary & Further Reading

Now that you have the basics of each kind of UML diagrams, you're ready to begin. You can now Download the trial version of the Visual Case Tool and try some of the simple designs.

You should but remember what each UML diagram is and what each is used for:

Use Case diagrams help to specify the user goals that the system has to carry out.

Class diagrams depict the physical structure of the system objects and their static relationships.

Sequence and collaboration diagrams give the dynamic interactions between instances which are used to carry out a single use case.

State charts diagram depict an instance over time and the events that cause it to change.

Activity diagrams are good for giving details on  high level processes that require conditional and parallel processing.

Physical diagrams give you an overview of the structure, distribution and implementation of your system.

Putting it all Together

You should not be overwhelmed with the semantics and detail.  UML is a very rich and detailed language and you should remember that there is no need to master each and every bit of information at first. You should first strive to get comfortable with the basics.

Also, you should keep your diagrams very simple. Each of the UML diagram should have only one key concept or design feature which you're striving to explain. Further, that key concept or feature should be interesting enough. You don't need to design the very obvious features as you should not be redundant. You should express what needs to be expressed and move forward.

Finally, all of the diagrams in this tutorial have been created with Visual Case, so you should Download the trial and get started with your own system designs.

In order to get Further Information!!

You can browse the web for various resources such as message forums, other tutorials and more examples.

A good and very accessible book which should get you started is: UML Distilled Second Edition - A Brief Guide to the Standard Object Modeling Language

Author: Martin Fowler with Kendall Scott. Published: 2000 Addison-Wesley (