*Roles and Responsibilities of a
& its Importance.
*What is RUP? Explain in detail.
*What is UML explain in detail?
*Testing (QA) knowledge Required
*Rational Rose Tools Interview
Questions
*Diagrams for Business Analyst
BA Interview Questions
*General business analyst interview
*Mortgage related interview questions
Business Analyst Tutorials
*Responsibilities of a Business Analyst
*UML(unified modelling language)
*SDLC(systems development life cycle)
*Finance banking knowledge for BA
*Role of a Business Analyst(high level)
*Use case diagram step by step
*SDLC
*RUP (rational unified processing)
*UML (unified modeling language)
*What is User acceptance
testing (
UAT)?
Testing Knowledge
Business Analyst Finance
*Business Analyst Finance domain
*What is home equity line of credit
*What is Loan to value ratio ?
*What is debt to income ratio &
*What are mutual funds ? Interview
*Trading of Stocks , what are stocks?
*Factors that will affect the change in
*What stocks are treated as equity
*Some more Finance related interview
questions for Business analyst
*Imp finance related interview
*What is SWAP and types of swaps
*What are Options & Bonds and types
*what is a derivative and how it functions
*Commercial bank in brokerage industry
*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 :
*SAS (statistical analysis system)
*Medicare Procedures and policies
*Health care Interview questions for BA
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.
photo