Business Systems Analysis Midterm

Business Analysis

practice of enabling change in an organizational context, by defining needs and recommending solutions that deliver value to stakeholders.

Supporting expert

draws on expertise concerning h and software and their uses in business.

Consultant

can bring in a fresh perspective that people in an organization do not possess. Will rely heavily on the systematic methods we will learn in this class.

Agent of change

a person who serves as a catalyst for change, develops a plan for change, and works with others in facilitating that change

Enterprise Analysis

describes the business analysis activities necessary to identify a business need, problem, or opportunity, define the nature of a solution that meets that need, and justify the investment necessary to deliver that solution

Systems Analysis and Design

Step-by-step process for developing high-quality information systems

Structured Analysis

-Traditional method for developing systems
-Organized into phases (SDLC)

Object-Oriented Analysis

-More recent method for developing systems
-Objects represent actual people, things, or events

Agile/Adaptive Methods

-Latest trend in software development
-Team-based effort broken down into cycles

Project Planning

Identify all project tasks and estimate the completion time and cost of each

Project Scheduling

Create a specific timetable that shows tasks, task dependencies, and critical tasks that might delay the project

Project Monitoring

Guiding, supervising, and coordinating the project team's workload

Project Reporting

Create regular progress reports to management, users, and the project team itself

Ishikawa (fishbone) diagram

analysis tool that represents the possible causes of a problem as a graphical outline

project scope

defining specific boundaries, or extent, of the project

constraint

requirement or condition that the system must satisfy or an outcome that the system must achieve

International Institution of Business Analysis (IIBA) Vision and Mission

-The World's leading association for Business Analysis professionals
-Develop and Maintain standards for the practice of business analysis and for the certification of its practitioners

BABOK Knowledge Areas

KA1 Business Analysis Planning and Monitoring
KA2 Elicitation
KA3 Requirements Management and Communication
KA4 Enterprise Analysis
KA5 Requirements Analysis
KA6 Solution Assessment and Validation

KA1 Business Analysis Planning and Monitoring

Understand who needs to be engaged & what needs to be done; monitor progress; coordinate with others

KA2 Elicitation

Describes the various techniques used to elicit requirements

KA3 Requirements Management and Communication

Bring stakeholders to a common understanding; formalizes agreement

KA4 Enterprise Analysis

Provides a context and/or foundation on which to evaluate all future issues & challenges

KA5 Requirements Analysis

Transforms the business need into clearly described capabilities

KA6 Solution Assessment and Validation

Evaluate and choose among alternatives; assess tradeoffs and options

Blue

quiet types

Red

bossy, leaders

Green

Order, neat freaks

Yellow

people oriented, the glue that holds groups together

Conflict

disagreement between ideas, principles, or conflicting objectives

Project Management

the process of planning, scheduling, monitoring, and reporting on the development of an information system

Gantt Chart

horizontal bar chart that represents the project schedule with time on the horizontal axis and tasks arranged vertically

PERT/CPM chart

shows the project as a network diagram with tasks connected by arrows

Business Process Modeling

To understand how work that involves multiple roles and departments is performed within an organization

AS-IS Process

Current business process in place

Data flow diagrams (DFDs)

graphically show the movement and transformation of data in the information system

Unified Modeling Language (UML)

uses a set of symbols to represent graphically the various components and relationships within a system

How to effectively Influence?

1. Figure out how to build trust
2. Know what you're talking about
3. Have the courage to recommend the right thing

Systems Development Life Cycle (SDLC)

Series of phases used to plan, analyze, design, implement, and support an information system

SDLC - Planning Phase

1. Brainstorm issues
2. Identify opportunities for org
3. Prioritize and choose projects
4. Set the project scope
5. Develop the project plan

SDLC - Analysis Phase

1. Gather the business requirements for system
2. Define system constraints

SDLC - Design Phase

1. Design technical architecture to support system
2. Design system models

SDLC - Development Phase

1. Build the technical architecture
2. Build the database
3. Build the applications

SDLC - Testing Phase

1. Write the test conditions
2. Perform system testing

SDLC - Implementation Phase

1. Write detailed user documentation
2. Provide training for the system users

SDLC - Maintenance

1. Build a help desk to support the system users
2. Provide an environment to support system changes

Business Analysis

practice of enabling change in an organizational context, by defining needs and recommending solutions that deliver value to stakeholders.

Supporting expert

draws on expertise concerning h and software and their uses in business.

Consultant

can bring in a fresh perspective that people in an organization do not possess. Will rely heavily on the systematic methods we will learn in this class.

Agent of change

a person who serves as a catalyst for change, develops a plan for change, and works with others in facilitating that change

Enterprise Analysis

describes the business analysis activities necessary to identify a business need, problem, or opportunity, define the nature of a solution that meets that need, and justify the investment necessary to deliver that solution

Systems Analysis and Design

Step-by-step process for developing high-quality information systems

Structured Analysis

#NAME?

Object-Oriented Analysis

#NAME?

Agile/Adaptive Methods

#NAME?

Project Planning

Identify all project tasks and estimate the completion time and cost of each

Project Scheduling

Create a specific timetable that shows tasks, task dependencies, and critical tasks that might delay the project

Project Monitoring

Guiding, supervising, and coordinating the project team's workload

Project Reporting

Create regular progress reports to management, users, and the project team itself

Ishikawa (fishbone) diagram

analysis tool that represents the possible causes of a problem as a graphical outline

project scope

defining specific boundaries, or extent, of the project

constraint

requirement or condition that the system must satisfy or an outcome that the system must achieve

International Institution of Business Analysis (IIBA) Vision and Mission

-The World's leading association for Business Analysis professionals
-Develop and Maintain standards for the practice of business analysis and for the certification of its practitioners

BABOK Knowledge Areas

KA1 Business Analysis Planning and Monitoring
KA2 Elicitation
KA3 Requirements Management and Communication
KA4 Enterprise Analysis
KA5 Requirements Analysis
KA6 Solution Assessment and Validation

KA1 Business Analysis Planning and Monitoring

Understand who needs to be engaged & what needs to be done; monitor progress; coordinate with others

KA2 Elicitation

Describes the various techniques used to elicit requirements

KA3 Requirements Management and Communication

Bring stakeholders to a common understanding; formalizes agreement

KA4 Enterprise Analysis

Provides a context and/or foundation on which to evaluate all future issues & challenges

KA5 Requirements Analysis

Transforms the business need into clearly described capabilities

KA6 Solution Assessment and Validation

Evaluate and choose among alternatives; assess tradeoffs and options

Blue

quiet types

Red

bossy, leaders

Green

Order, neat freaks

Yellow

people oriented, the glue that holds groups together

Conflict

disagreement between ideas, principles, or conflicting objectives

Project Management

the process of planning, scheduling, monitoring, and reporting on the development of an information system

Gantt Chart

horizontal bar chart that represents the project schedule with time on the horizontal axis and tasks arranged vertically

PERT/CPM chart

shows the project as a network diagram with tasks connected by arrows

Business Process Modeling

To understand how work that involves multiple roles and departments is performed within an organization

AS-IS Process

Current business process in place

Data flow diagrams (DFDs)

graphically show the movement and transformation of data in the information system

Unified Modeling Language (UML)

uses a set of symbols to represent graphically the various components and relationships within a system

How to effectively Influence?

1. Figure out how to build trust
2. Know what you're talking about
3. Have the courage to recommend the right thing

Systems Development Life Cycle (SDLC)

Series of phases used to plan, analyze, design, implement, and support an information system

SDLC - Planning Phase

1. Brainstorm issues
2. Identify opportunities for org
3. Prioritize and choose projects
4. Set the project scope
5. Develop the project plan

SDLC - Analysis Phase

1. Gather the business requirements for system
2. Define system constraints

SDLC - Design Phase

1. Design technical architecture to support system
2. Design system models

SDLC - Development Phase

1. Build the technical architecture
2. Build the database
3. Build the applications

SDLC - Testing Phase

1. Write the test conditions
2. Perform system testing

SDLC - Implementation Phase

1. Write detailed user documentation
2. Provide training for the system users

SDLC - Maintenance

1. Build a help desk to support the system users
2. Provide an environment to support system changes