Summary Class notes - Business Analysis

- Business Analysis
- nvt
- 2015 - 2016
- KU Leuven
- Information Management
442 Flashcards & Notes
1 Students
  • This summary

  • +380.000 other summaries

  • A unique study tool

  • A rehearsal system for this summary

  • Studycoaching with videos

Remember faster, study better. Scientifically proven.

PREMIUM summaries are quality controlled, selected summaries prepared for you to help you achieve your study goals faster!

Summary - Class notes - Business Analysis

  • 1451602800 Session 1 - Business Analysis

  • What are the goals of Business Analysis?
    - Essential component of successful organizations
    - Improves efficiency and effectiveness of business processes
    - Improves decision processes
    - Allows the company to stay competitive
    - Enable workgroup collaboration
  • What are the four 'domains' in Business Analysis?
    Vocabulary, rules, processes, and strategy
  • What do you need to understand for doing Business Analysis?
    - How an organization works
    - Why the organization exists
    - What the organization's goals and objectives are
    - How the organization those goals and objectives accomplishes
    - How the organization needs to change to better accomplish those objectives and/or overcome challenges
  • What do you need to define for doing Business Analysis?
    The scope of the solution
  • What is a solution?
    A solution meets a business need by solving problems and/or enabling the organization to take advantage of an opportunity.
  • What is the BABOK?
    The Business Analysis Body of Knowledge, in which a way is described from systems analysis to engineering the business.
  • What are the different steps or phases in developing information system solutions?
    It can be defined in steps:
    Investigate, Analyze, Design, Implement, Maintain
    Or in phases:
    Project planning phase, Analysis phase, Design phase, Implementation phase, Support phase
  • What is a reason for doing Business Analysis?
    Many projects fail due to no undestanding of the organization the system is built for, no incorporation with the business user, or no attention for processes, integration, discipline etc.
  • What is a Business Analyst?
    A business analyst works as a liaison among stakeholders in order to elicit, analyze, communicate, and validate requirements for changes to business processes, policies, and information systems.

    The most important element is the business focus; ensuring business needs are understood and communicated so that the final solution meets the business needs.

    Another definition is:
     A business analyst works as a liaison among stakeholders in order to understand the structure, policies, and operations of an organization, and to recommend solutions that enable the organization to achieve its goals.
  • What are the different kinds of Business Analysts?
    - Business analysts with very strong business skills and understanding of the business domain whose key role is to analyze business processes, procedures, etc. in order to identify problems and determine solutions. (These analysts are more involved in what the IIBA defines as enterprise analysis and are likely to be involved prior to the initiation of an IT project.)
    - IT Business Analyst who is focused on requirements elicitation (finding the problems) and analysis, and solving problems using information technology solutions. This analyst serves as a bridge between business and IT and generally begins work after a project has been initiated. This analyst specifies “what” the system must do.
    - Systems Analyst is an IT business analyst who is more focused on system design and the technical aspects of the solution. This analyst takes the requirements and creates functional specifications regarding “how” a system will do the “what.”
    - Many other titles are used including the Business Systems Analyst which has been described as a combination of the IT Business Analyst and the Systems Analyst.
  • What are the knowledge areas of the BABOK?
    Business Analysis Planning and Monitoring, Enterprise Analysis, Elicitation, Requirements Analyis, Solution Assessment and Validation, Requirements Management and Communication, and Underlying Competencies
  • Tell something about the Enterprise Analysis area of the BABOK.
    - It gives an understanding of the "big picture"
    - In this area you define the business goals the solution must meet
    - Here you integrate the requirements into a larger business architecture
    - Initiatives are supported and a long term planning will be created
    - A strategic planning will be created, a business case will be developed, the Cost Benefit Analysis will be done, and also feasibility studies
    - The question "Why are we doing this?" will be answered
  • Tell something about the Elicitation area of the BABOK.
    - It has a focus on gathering the requirements from various stakeholder groups
    - The tasks, knowledge and techniques for capturing requirements will be identified
    - The question "What do the stakeholders need?" will be answered
  • Mention at least five elicitation techniques.
    Brainstorming, Focus Groups, Interviewing, Observation, Prototyping, Requirements Workshop, Survey/Questionnaire, Document Analysis, Interface Analysis
  • Tell something about the Requirements Analysis area of the BABOK.
    - It focuses on analyzing the data
    - The methods, tools, techniques to structure raw data collected during elicitation are defined
    - It identifies the gaps in requirements
    - The "solution" capabilities are defined and these serve as the foundation for selecting among solution alternatives (the solution can be made when you know the implementations)
    - It answered the question "What must the solution do?"
  • Tell something about the Requirements Management and Communications of the BABOK.
    - Here is a focus on presenting and communicating documented requirements to all stakeholders, including project team members, to bring the group to consensus on project scope
    - The change will be indentified and managed
    - The question "Does everyone understand and agree?" will be answered
  • Tell something about the Solutions Assessment & Validation area of the BABOK.
    - Here is a focus on ensuring that the best approach is chosen, that the solution will meet stakeholder objectives, that the solution is feasible, and that the solution guides "verification"
    - The question "Does the solution do what it is supposed to do?" will be answered
  • Mention at least three of the underlying competencies of a business analyst?
    - Analytical thinking and problem solving
    - Behavioural characteristics: ethics, personal organization, trustworthiness
    - Business knowledge
    - Communication skills
    - Interaction skills: facilitation and negotiation, leadership and influencing, teamwork
    - Software applications
  • What are goals for doing business analysis?
    - To deliver feasible quality solution that meets the business needs: the optimal solution
    - Help prevent scope creep (start small, but when busy you see that the problem is actually bigger), and reduce project risks, including rework
    - Provide traceability to business goals
Read the full summary
This summary. +380.000 other summaries. A unique study tool. A rehearsal system for this summary. Studycoaching with videos.

Latest added flashcards

What are important elements of project management?
Time, budget, documentation of the activities, organization of the project, and the quality of the final solution
What things do you check for the quality control in each phase?
Inception: scope and stakeholders
Analysis: what, user involvement, solving the right problem?, communication, expectations
Design: user participation, team quality, critical path, implementation environment
Programming and testing: test time, business participation, error discovery and handling
What are design criteria in de structured design phase?
Module coupling: a measure for the degree of dependency between the modules of a system

Module cohesion: a measure for the degree to which individual modules perform a single, well-defined function (the content should be clear)

Fan-in: the number of modules that call the specified model (manage the incoming flows)

Fan-out: the number of modules called by the specified module: span of control (best is 7, outgoing flows)
How does the market influence the social context and processes of companies?
There is a market, which is dynamic, turbulent and competitive. This leads to constant change in the companies. So they change processes and social context. The challenge is to understand and enable the change.
What are traditional approaches/techniques in process mining?
Workshops, interviews, observations, document analysis, walkthroughs, transaction sampling.
How do event logs emerge?
Data from systems will be generated in event logs. Data is for example, time users etc.
Which different versions of project management exist? Explain.
Pro-active project management
Reactive project management: Reactive management refers to a situation in which you can't – or don't – plan ahead for problems or opportunities. Instead, you react to them as they happen. As a result, you're always a step behind. You don't have time to look ahead to pre-empt problems, so they seem to happen "out of the blue."
What do the business and the ICT guys do in every step of the ICT-project's lifecycle?
Idea phase: Business --> Getting acquainted to the problem domain, talk to people and decide whether a (ICT) project is needed. ICT --> Answering some (very) high-level questions

Prestudy: Business --> Provide detailed input (requirements) to ICT ,based on elaborate discussions with stakeholders. ICT --> Analyse and document the requirements and propose a solution  

Contracting: Business --> Get solution validated by stakeholders and find budget. ICT --> Define and formalize planning, scope, budget, etc. in contract.

Execution & Testing: Business --> Provide extra input, user acceptance testing and decide on GO or NO-GO. ICT --> Develop solution and conduct first ICT-side tests.

Roll-out: Business --> Training, make sure everyone knows about the change & the impact on them (including customers). ICT --> Get approval by ICT management, launch solution 'in production'

Closure: Business --> Lessons learned, closely follow-up usage and possible problems, re-training where needed. ICT --> Hand-over from project team to operational team.
What if the model can generate the trace?
Than the fitness of the model is good.
There are different event types and different activity instances. What means it when they overlap?
Examples form activity instances:
- Schedule-assign-start-complete
- Schedule-assign-reassign-start-suspend-resume-complete
- Start-suspend-resume-suspend-abort activity
- Start-complete
- Complete

The last one happens the most.     

Note: there can be overlapping activity instances in event logs, then you do not know which start and end point is related to each other.