Chapter 1 Flashcards
organization dedicated to the business analysis profession and establish common standards of knowledge within the BA profession
International Institute of Business Analysis (IIBA)
tasks, knowledge, and techniques required to identify business needs and determine solutions to business problems.
Business Analysis
systems development component, but may also consist of process improvement or organizational change
Solutions
key skill that needs to be retained within organizations operating an outsourcing arrangement.
business systems thinking
liaison among stakeholders in order to elicit, analyze, communicate and validate requirements for changes to business processes, policies & information systems.
Business Analyst
Three factors need to be present for IT systems to deliver competitive advantage
- needs of the business must drive the development of the IT systems
- implementation of an IT system must be accompanied by the necessary business changes
- requirements for IT systems must be defined with rigor and accuracy
- must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally-imposed documents
- needed by a stakeholder to solve a problem or achieve an objective
- documented representation of a condition or capability
Requirement
- higher level statements of the goals, objectives, or needs of the enterprise.
Business Requirements
- the needs that a given stakeholder has and how that stakeholder will interact with a solution.
User Requirements
- also known as non-functional requirements.
- conditions that do not directly relate to the behavior or functionality of the solution
- describe environmental conditions under which the solution must remain effective
Quality of Service Requirements
- capabilities the system will be able to perform in terms of behaviors or operations
Functional Requirements
- limits or impacts the design of the solution.
Assumptions and Constraints
- resources and tasks associated with the planning and management of requirements gathering activities
Requirements Planning and Management
the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state.
Implementation Requirements
- elicits, analyses, documents and reviews the requirements for accuracy.
Business Analyst
- overall responsibility for the project at the management level
Executive Sponsor
- manages the day-to-day activities of the project ensuring that the requirement-related tasks are delivered on time, within budget, and within scope.
Project Manager
- ensures the quality standards are adhered
Quality Assurance Analyst
- technical direction of the project and the overall structure of the solution.
Application Architect
- technical resources assigned to a project, and may include many technical roles
Developer
- all technical aspects related to designing, creating and maintaining project databases.
Database Analyst
- develops user training materials and delivering training to end-users
Trainer
- designs the overall hardware and software infrastructure
Infrastructure Analyst
- defines and approves the project scope
Solution Owner
- assesses the overall data requirements of an information system project
Information Architect
- defining, approving and using the functional requirements for the project.
Subject Matter Expert
- tool useful to illustrate usual responsibilities of the roles involved in planning & managing requirements
The RACI Matrix
- group of people in the organization (and often external to it also) who will actually interact directly with the software application
End-user
- anyone materially affected by the outcome of the project
Stakeholders
