Business Analyst Essentials:
Responsibilities of a Business Analyst
UML(unified modelling language)
SDLC(software development life cycle)
Finance banking knowledge for BA
BA Interview Questions & related:
Imp BA Interview questions set 1
Imp BA Interview questions set 2
Imp BA Interview questions set 3
Imp BA Interview questions set 4
Business analyst Interview questions 1
Business analyst Interview questions 2
Business analyst Interview questions 3
Business analyst Interview questions 4
Business Analyst Health care Related:
SAS (statistical analysis system)
BA Finance Interview questions
Business Analyst Finance domain Interview
What is home equity line of credit (HELOC) ?
What is debt to income ratio &
What are mutual funds ? Interview questions
Trading of Stocks , what are stocks?
Factors that will affect the change in price
What stocks are treated as equity
Business Analyst Tutorials:
Role of a Business Analyst(high level)
RUP (rational unified processing)
Testing skills required
5. Activity and State Diagrams
Previously we have seen how the interaction diagrams demonstrate the behavior of several system objects while executing a single use case. When you want to display the order of events on a broader scale then you should use activity and state diagrams.
Activity Diagram
An activity can be defined as the execution of a task whether it be a physical activity or the simple execution of code. Simply put, the activity diagram depicts the sequence of activities. Like any simple flow chart, activity diagrams have the support for conditional behavior, but also have added support for parallel execution as well.
Start: each activity diagram has only one start (symbol above) at which the sequence of the actions begins.
End: each activity diagram has only one finish at which the sequence of actions ends
Activity: activities are to be connected together by transitions. Transitions are actually directed arrows which are flowing from the previous activity to the next activity. They can be optionally accompanied by a textual label of the form:
[guard] label
The guard is considered to be a conditional expression which when true indicates that the transition has taken place. The label is optional and is represented in free form.
To show conditional behavior you can use a branch and a merge. The top diamond is a branch and can have only one transition flowing into it but any number of mutually exclusive transitions flowing out. So, the guards on the outgoing transitions must resolve themselves in order that only one is followed. The merge is used to finish the conditional behavior. There can be any number of incoming transitions, and only one outgoing transition.
To show the parallel behavior you can use a fork and a join. The fork(placed at top) has only one transition entering and any number of transitions which are exiting, all of which will be taken in action. The join(placed at the bottom) represents the end of the parallel behavior and has any number of transitions entering while there is only one leaving.