Business Analysis Concepts

SOLUTION REQUIREMENT

1. the characteristics of a solution that meet business requirements and stakeholder requirements. 2.developed and defined through REQUIREMENT ANALYSIS 3.Two sub parts: >Functional requirement and >Non functional requirement 4.

Different techniques commonly used

1.Acceptance and Evaluation Criteria Definition (9.1) 2.Brainstorming 3.Business Rules Analysis 4.Data Dictionary and Glossary 5.Data Flow Diagrams 6.Data Modeling 7.Decision Analysis 8.Document Analysis 9.Interviews 10.Metrics and Key Performance Indicators 11.Non-functional Requirements Analysis 12.Organization Modeling 13.Problem Tracking 14.Process Modeling 15.Requirements Workshops 16.Scenarios and Use Cases

TRANSITION REQUIREMENT

1.Capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to a desired future state, 2.It Will not be needed once that transition is complete. 3.They will always remain a temporary state. 4.Mandatory to define the existing situation and new solution. 4.They typically cover >data conversion from existing systems, >skill gaps that must be addressed, >and other related changes to reach the desired future state. 5.Developed from Solution assessment and validation

BUSINESS REQUIREMENT

1.higher-level statements of the goals, objectives, or needs of the enterprise. 2.They describe a a)the reasons why a project has been initiated, b)The objectives the project will achieve c)Metrics used for its success. 3.Talks of the needs of the organization as a whole and not individual stakeholders 4.Developed and defined through enterprise analysis.

STAKEHOLDER REQUIREMENT

1.re statements of the needs of a particular stakeholder or class of stakeholders. 2.They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. 3.Bridge between business requirement and solutions requirement 4.developed and defined through REQUIREMENT ANALYSIS

REQUIREMENTS

>A condition or capability needed by a stakeholder to solve a problem or achieve an objective. >A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract, standard, specification, or other formally imposed documents. >A document representation of a condition

FUNCTIONAL SOLUTION REQUIREMENT

>Behavior and information the solution will manage, >Capabilities the system will be able to perform in terms of behavior and operations.

SOLUTION

>Is a set of changes >to the current state of an organization that are made in order >to enable that organization >to meet a business need, >solve a problem, >or take advantage of an opportunity

NON FUNCTIONAL REQUIREMENT

>the environment in which the solution will be effective or qualities the system must have. >indirect behavior > known as quality or supplementary requirements. >include requirements related to capacity, speed,security, availability and the information architecture and presentation of the user interface.

DOMAIN

A domain is the area undergoing analysis. It may correspond to the boundaries of an organization or organizational unit, as well as key stakeholders outside those boundaries and interactions with those stakeholders.

Input

A precondition for a task to perform,Ingredient generated outside of a task generated by a bus9iness analysis task

Different kinds of Underlying competencies

Analytical thinking and problem solving Behavioral characteristics Business Knowledge Communication Skills Interaction Skills Software application

SOLUTION ASSESSMENT AND VALIDATION

Assess proposed solutions to determine which solution best fits the business need, identify gaps and shortcomings in solutions, and determine necessary workarounds or changes to the solution. It also describes how business analysts assess deployed solutions to see how well they met the original need so that the sponsoring organization can assess the performance and effectiveness of the solution

LIST OF KNOWLEDGE AREAS

Business Analysis Planning and Monitoring Elicitation Requirement Management and communication Enterprise Analysis Requirement Analysis Solution Assessment and Validation Underlying Competencies.

Task

Each knowledge area describes the tasks performed by business analysts to accomplish the purpose of that knowledge area.

Task-Characteristics

IT should produce some demonstrable result-that is useful, specific, visible and measureable. Task must be complete Task must be an essential part of the knowledge area with which it is associated.

Techniques

Provide additional information on different ways that a task may be performed or different forms the output of the task may take. A technique must be related to one task atleast.

Task is presented in the following format

Purpose Description Input Element Techniques Stakeholder

what are Underlying competencies

Supporting role for effective performance of the business analysis. The skills knowledge and competencies that help a BA perform the role.

ENTERPRISE ANALYSIS

This knowledge area involves -Problem definition and analysis, -Business case development, -Feasibility studies, and -Definition of solution scope.

KNOWLEDGE AREAS

What a business analyst practitioner must understand What a business analyst practitioner must perform all knowledge areas in rapid succession, iteratively, or simultaneously It is not a methodology to conduct the BA performance.

Task-Purpose

What is the reason for the BA to perform the task and Value that is created by performing it.

REQUIREMENT ANALYSIS

business analysts prioritize and progressively elaborate stakeholder and solution requirements in order to enable the project team to implement a solution that will meet the needs of the sponsoring organization and stakeholders. It involves analyzing stakeholder needs to define solutions that meet those needs, assessing the current state of the business to identify and recommend improvements, and the verification and validation of the resulting requirements.

REQUIREMENTS CLASSIFICATION SCHEME

business requirement stakeholder requirement solution requirement

WHAT DOES BA DO FOR THE SOLUTION

define the optimal solution for their needs, given the set of constraints (including time, budget, regulations, and others) under which that organization operates.

REQUIREMENT MANAGEMENT AND COMMUNICATION

describes 1.How business analysts manage conflicts, issues and changes in order to ensure that stakeholders and the project team remain in agreement on the solution scope. 2.How requirements are communicated to stakeholders, and 3.How knowledge gained by the business analyst is maintained for future use.

UNDERLYING COMPETENCIES

describes the behaviors, knowledge, and other characteristics that support the effective performance of business analysis.

BUSINESS ANALYSIS PLANNING AND MONITORING

how business analysts determine which activities are necessary in order to complete a business analysis effort. It covers the following: 1.Identifying the stakeholders 2.Selction of techniques 3.Process to manage requirements 4.Method to assess progress of work

EXAMPLES OF SOLUTION AND SOLUTION COMPONENTS

software applications, web services, business processes, business rules Governing a process, an information technology application, a revised organizational structure, outsourcing, insourcing, redefining job roles, or any other method of creating a capability needed by an organization.

KEY OBJECTIVE OF BA REGARDS A REQUIREMENT

to be clearly visible and understood by all stakeholders.

ELICITATION

to understand the stakeholders actual needs . how business analysts work with stakeholders to identify and understand their needs and concerns, and understand the environment in which they work. The purpose of elicitation is to ensure that a stakeholder's actual underlying needs are understood, rather than their stated or superficial desires.