► Describe a time when you had to facilitate a requirements gathering activity where your stakeholders were not located in the same city. If you haven't done this before, describe to us how you will deal with this type of situation?
► Describe a situation where you used business analysis techniques to gather business requirements from stakeholders. Which techniques did you use and why did you choose those techniques?
► Describe a time when you were responsible to plan and facilitate a requirements workshop. How did you go about it?
► Describe a time when you had to win a difficult stakeholder over to accept the project change that will affect his/her department. How did you do it?
► Describe a time when you were in a project where change happened constantly without any change control to requirements. How did you deal with this situation and how did you overcome the associated challenges?
► Describe a time when you had to deal with stakeholders at all levels of the organisation. How was the message different?
► Describe a time when you had to deal with a stakeholder that just didn't want to participate in one of your requirements workshops and tried to sabotage it. What did you do?
► Describe a situation when you were unable to deliver one of your requirements documents on time. What did you do?
► Tell us about a time when you needed to gain approval for one of your business requirements documents but a stakeholder kept on delaying or postponing meeting with you?
► As a business analyst, describe your ideal project environment?
► Describe a time when you introduced a new idea or process into a project or department and how it improved the process or situation.
► Describe a situation where you had to mentor a colleague on any tool or concept. How did you approach this?
► 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?
► 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?
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.
The business analyst must understand IT and also has to understand the stakeholder's needs.
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 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 most important responsibilities of a business systems analysts are as a communication conduit between the stakeholders and the team.
There are 2 documents:
► FRD (functional requirement document)
► SDD (system design document) which can also be called TRS (Technical