Analysis

The activity diagram is important because it gives an outline of the work

flow within the business as well as the activities and action completed.

For instance with a company, there is likely to be more than one department. In such a case each department, will have different access levels to the system.

So if there's a Medical, HR and Accounts team they will only have access to screens that relate to each.

The activity diagram will highlight the differences within the departments which will be very helpful for developers when they are designing and coding.

UML in full means Unified Modeling Language. It is the industry standard

language for constructing, visualizing and documenting the different components within a system.

There are 2 documents:

► FRD (functional requirement document)

► SDD (system design document) which can also be called TRS (Technical

requirements specifications).

This is a flow that accounts for an unexpected or unusual result within

the application process. The exception will be handled according to its designed flow.

An include is where a specific action has to take place.

An extend is an action that may not necessarily take place.

This is the flow that will come into action, when there is a failure in the

use case system where the expected results haven't come to fruition.

The most important responsibilities of a business systems analysts are as a communication conduit between the stakeholders and the team.

The common tools that can be used by a business analyst are MS office, MS word, MS Excel, Power point, Quality center/test director MS Project. There may be tools that are client specific also, but these will be supplied the client.

The use case diagram defines the role of each actor that is associated to a particular role or system. A use diagram is also a behavioral diagram and a part of UML.

An example of this is an "Order Management" as the main function, in such a case the person that is given the order is an actor.

Download the questions and answers here right click save as. You can read them on your tablet, mobile phone, e-reader device or anything else that can read PDF documents.

The business analyst must understand IT and also has to understand the stakeholder's needs.

A systems analyst has the ability to look at a program or utility and see the code. They can go in and pinpoint where changes need to be made.

► What is the purpose of the Business Analyst within an organisation?

► What do you believe are good attributes of a Business Analyst?

► What is the difference between a functional requirement and a non-functional requirement?

► What are the attributes of a good business requirement?

► What is the purpose of requirements trace-ability?

► When do you use a RACI or RASCI model?

► How do you ensure your business requirements are of a high quality?

► What is contained within a typical Requirements Management Plan?

► Describe the phases of the SDLC. Which phases have you worked in?

► Describe the difference between a Waterfall based methodology and an Agile methodology?

► What is a user story in an Agile context and how is it used?

► What is a use case and when would you use it as a Business Analyst?

► What is the difference between a functional specification and a business requirements document? How are they related?

► Describe an effective way to manage change to requirements within a project?