Please enable JavaScript.
Coggle requires JavaScript to display documents.
Chapter 3 - Business Analysis - Coggle Diagram
Chapter 3 - Business Analysis
Business Analysis
Definition: "An internal consultancy role which has the responsibility for investigating business situations, identifying and evaluating options for improving business systems, defining requirements and ensuring the effective use of information systems in meeting the needs of the business."
IIBA Definition: Business analysis is the practice of enabling change in an organisation context, by defining needs and recommending solutions that deliver value to stakeholders
Need For Business Analysis
Role started in the 1990's
Users where unsatisfied by the IT systems being developed due to the lack of understanding of client and business requirements
With the IT growing systems where being needed to fit business requirements
Rationale for business
Initially being used to translate business needs and facilitate communications between the business and staff
Evolved to focus on addressing business problems and opportunities, looking at potential future issues
Proactivity - the needs of a business needed to be fully understood, so did the problem we're trying to fix
POPIT
"Used to classify the different elements that form z business system and to support 'Holistic' analysis by ensuring that all of these elements - and their interactions - are considered."
People, Organisation, Process, Information-Technology
People: Do they have the skills for the job?
Organisation: Is there a supportive management approach
Process: Are they well defined and communicated
Information technology (IT): Are the information needs of the business being met? Does the technology support the business process
Business Analysis in the SDLC
Feasibility Study: Investigating a Businesses Situation, Identifying and evaluating possible options to solve the business pain points. Vital to determine the best approach to move forward in the project
Business analysis process model
Feasibility factors: Is it finically worthwhile, is there a financial return?
Business Feasibility: Seeing if a solution will 'fit' a businesses architecture, culture and management style
Technical Feasibility: Ensuring current technology can support the proposed solutions and any new technology fits the business and meets the needs of the business
Define Requirements: Business requirements need to be defined in sufficient detail, so do technical requirements to ensure all further work is developed to target the organisations needs.
Deliver Solution: During the design, development and test, any changes that the requirements are analysed and assessed for impacts
Outcomes from Business Analysis
IT change
Identifying the type of change, a complete IT overhaul or a simple update or new version of a existing system
Business analysis need to ensure the new It systems meet business requirements and is a improvement operationally, tactically and strategically to an organisations IT systems
Process Change
A business process may need to change in order to use the new technology effectively
Certain tasks may no longer need to be performed
Documentation and clear communication is needed to ensure the business, know clearly, how to use the IT system effectively
People Change
A review into the skills needed to use the new It system and how the staff will adapt, communicate and manage with the new system
Organisation Change
Job roles may need to be redefined, resulting in a job redefinition being needed to define the new responsibilities of new roles.
Possibles roles could be made redundant
Teams could merge
A new management layout could be required
Communications between teams may need to be redefined.