Analytic, Analytical and Analysis Interview Questions And Answers

If someone is analytical then it means the person is always thinking about things - analyzing, pondering, etc. A person who is analytical will have all of the facts about something before doing it.

Analytical is one of the 4 types of people. The other 3 are Promoters, Supporters and Controllers. Most everyone has a portion of every personality trait, but resembles 1-2 for the majority.

You should be able to identify a time where he/she was having difficulty with a work task, found a way to rectify the faults and work more efficiently.

You should mention a time where he/she had to use reason and logic to resolve a problem. Job seeker may have analyzed all the relevant information and created a good, effective solution.

Your answer should show that they are a problem solver, that they can analyze all the information, and come up with a solution.

You should hear answers that show the job seeker has sound analytical skills to solve any problem analyzes problems in great detail to come up with a solution.

You should be able to explain how they can compile facts and figures for preliminary analysis, derive relevant facts and information from the study of this data.

You should have the character to admit mistakes. Also clarify about your work. Were the steps he took correct? More importantly, has he/she learned from this mistake?

SWOT Analysis is a strategic planning technique used to assess the internal and external environment in which a company operates and competes. Internal environmental factors are classified into strengths and weaknesses, while external environmental factors are classified into opportunities and threats.

Use Case modeling is used to diagrammatically depict a system and those people or processes that interact with it. This system can be a business system (a process) or an application system (computer or web based). To understand the scope of the system under consideration a system boundary is used. Anything depicted within the system boundary is part of the system under consideration, while anything outside of it is not. Use cases are then used to define a group of user-system interactions that together deliver value to the user of the system. These users are called actors.

A view organizes diagrams into logical groups to describe a particular aspect of the system. It is the abstraction of the system organized is such a way as to give a perspective of a related set of concerns.

The purpose of using views as a business analyst is to enable the analyst to comprehend very complex systems, and to organize the problem or solution domain around specific areas of expertise. The audience interested in each view may vary based on their roles and experience. A subject matter expert from the business will ask different questions and have different concerns than a developer or system architect. Views help present the information in an easily digestible manner.

Cost Benefit Analysis is a technique used to determine if the financial benefit s of a project outweigh the associated cost of undertaking the project in the first place. For a short term project where the benefit may be an immediate one-time cash windfall this may be as simple as subtracting the total of all the project cost from the total of all of the project benefits. If the total is positive, then the project may be worth completing.

Few analysts are brought on to a project at the very beginning. For those that are, they will often have a hand in creating some of the important documents that other analysts should reference when they first join.

First, get your hands on the project charter. The project charter, while high level, will provide critical information on the project.

It depends, it depends, and it depends!

As for most questions in business analysis, there isn’t only one answer. Whose job is to create a class diagram depends on the purpose of the class diagram.

First of all, the question implies that there is only one class diagram for a given project: “The Class Diagram”. For the most part, this is not the case. On some projects there may be a multitude of class diagrams while in others there may be none.

The Yourdon introductory class on data flow diagramming used to (still does?) teach that 98% of the required work in requirements specification revolved around a single task. What is that task?

For any new piece of work a BA (business analyst) needs to know

1. who are the key stakeholders (i.e. those who can kill the project)

2. what are the key stakeholders specific and measurable measures of success (i.e. their objectives) and what VALUE for each objective MUST be achieved in order for the project to be considered a success (e.g. increase sales per order value by 5%)

3. what are the key stakeholders unmeasured measures of success (i.e. their principles that they would like to see happen but aren't going to measure and so the project cannot be assessed by them - e.g. an intuitive solution)

4. what are the key stakeholders high level requirements (i.e. what capabilities do they expect the solution to deliver - e.g. the ability to offer add-on sales during the order taking process)

5. what is in scope of the work in terms of processes, organization units, locations, data, applications, technology

6. what is the scope of the work in terms of time, money, project resources (people and materials)

7. who will the stakeholders nominate for determining further high level requirements and detailed requirements (e.g. subject or domain experts, middle management of operational teams, etc)

The 4 + 1 View Model is a predefined set of views for organizing the design and architecture of a system. It was developed in 1995 by Philippe Kruchten, formerly the Director of Process Development at Rational Software.

The 4 + 1 View Model gets its name from the 4 primary views and 1 supporting view that are used to capture and communicate different aspects of the system.

The 4 primary views are:

► Logical View: this view describes the functionality of the system in terms of its static structure and dynamic behavior.
► Development View: this view describes the system from a programmer’s perspective and is concerned with the organization of physical code, its main modules, and their dependencies.
► Process View: this view focuses on the runtime behavior of the system and the elements of the system that relate to process performance. It includes aspects important to scalability, throughput, and process response times to name a few.
► Physical View: this view shows the system from a system engineer's point-of-view. It is concerned with the deployment of software components across the physical architecture including computers and devices , as well as communication between these components.

The 1 supporting view is:

► Use Case View: this view describes the functionality of the system from the perspective of external actors.

The flow chart gives a clear graphical representation of an implemented
process. This makes the system simple to understand for all persons involved in the project.

The use case model requires a use case diagram. It describes the business
environment. Its primary goal is to show the series of events and actions within any given process that will be performed by an actor.

► Use case diagram
► Activity diagram
► Collaboration diagram.

A communication diagram or interaction diagram, is an illustration of the relationships and interactions among software objects in the Unified Modeling Language (UML). The concept is more than a decade old although it has been refined as modeling paradigms have evolved.

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.

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.

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 extend is an action that may not necessarily take place.