Glossary Flashcards
Activity sampling
An investigation technique carried out to determine the amount of time individuals spend on different aspects of their work. Activity sampling is a form of observation and involves the collection of data that may be used for statistical analysis
Agile
An approach to software development based upon the Agile Manifesto and using evolutionary development and incremental delivery approaches
Actor
A role that performs areas of work within a business system. Actors are modelled on swim-lane diagrams and use case diagrams. Actors are usually user roles and show the individual or group of individuals responsible for carrying out the work or interacting with a system. An actor may also be an IT system or time.
APM
The Association for Project Management; aims to develop and promote project management
Balanced Business Scorecard
A Balaence Business Scorecard supports a strategic management system by capturing both financial and non-financial measures of performance. There are usually four quadrants - financial, customer, process, learning and growth. The balanced business scorecard was developed by R. S. Kaplan, and D. P. Norton
BCS, The Chartered Institute for IT
BCS is the leading international professional body for the IT industry with over 70,000 members. BCS is responsible for setting standards for the IT profession and advises and informs industry and government on successful IT implementation
Benefits management
A process that is concerned with the delivery of the predicted business benefits defined in the business case. This process includes managing projects such that they are able to deliver the predicted benefits and, after the project has been implemented, checking progress on the achievement of these benefits and taking any actions required to enable their delivery.
Boston Box
A technique used to analyse the market potential of the products and services provided by an organisation. The technique was defined by the Boston Consulting Group.
Business actor
Someone who has an interest in a project, either because they have commissioned it, they work within the business system being studied or they will be the users of a proposed new IT system. See Stakeholder.
Business analysis
An advisory role which has the responsibility for investigating and analysing business situations, identifying and evaluating options for improving business systems, elaborating and defining requirements, and ensuring the effective implementation and use of information systems in line with the needs of the business.
Business Analysis Process Model
A framework for business analysis assignments that incorporates the business context and has six stages – investigate situation, consider perspectives, analyse needs, evaluate options, define requirements and deliver changes. The framework places standard modelling techniques in context to help analysts determine the most appropriate technique for individual business situations.
Business architecture
A set of artefacts that define several views of an organisation.
Business Activity Model (BAM)
A conceptual model that shows the set of business activities that would be expected to be in place given the stakeholder perspective from which it has been developed. There are five types of business activity represented on a business activity model. These are: planning, enabling, doing, monitoring and controlling activities. See Business perspective.
Business case
A document that describes the findings from a business analysis study and presents a recommended course of action for senior management to consider. A business case would normally include an introduction, management summary, description of the current situation, options considered, analysis of costs and benefits, impact assessment, risk assessment, recommendations, plus appendices that provide detailed supporting information.
Business event
A business event triggers the business system to do something. Typically this is to initiate the business process that forms the business system response to the event. In effect, the business events tell us when a business activity should be initiated; it fires into life the process that carries out the activity. There are three types of business event: external, internal and time-based business events.
Business option
A key step in developing a Business Case is to identify the options available to address the business problem or opportunity. A business option describes the scope and content of a proposed business solution and states what it is intended to achieve in business terms.
Business perspective
A view of the business system held by a stakeholder. The business perspective will be based upon the values and beliefs of the stakeholder. These values and beliefs will be encapsulated in a defined world view. There may be several divergent business perspectives for any given business situation. See CATWOE.
Business process
A linked set of tasks performed by a business in response to a business event. The business process receives, manipulates and transfers information or physical items, in order to produce an output of value to a customer. See Business process model.
Business process model
A diagram showing the tasks that need to be carried out in response to a business event, in order to achieve a specific goal. See Swimlane diagram.
Business rule
Business rules define how business activities are to be performed. It is important that these rules are considered when modelling the processing to carry out the activity. There are two main types of business rule: constraints that restrict how an activity is performed; operational guidance that describe the procedures for performing activities.
Business sponsor
A senior person in an organisation who is accountable for delivering the benefits from a business change. The sponsor is also responsible for providing resources to the project team.
Business strategy
A strategy describes the long-term direction set for an organisation in order to achieve the organisational objectives.
Business system
A set of business components working together in order to achieve a defined purpose. The components of a system include people, information, technology processes and the organisation. See IT system.
Business user
An individual member of staff working within the business who is involved in a business change project. A business user may adopt a number of business roles including business sponsor, domain expert and end user for a solution.
Capability Maturity Model Integration (CMMI)
A model of five stages, showing increasing maturity of operation. Provides guidance for improving the quality of processes.
CATWOE
A technique from the Soft Systems Methodology that provides a framework for defining and analysing business perspectives. The mnemonic stands for: C – customer, A – actor, T – transformation, W – world view, O – owner, E – environment. See Business perspective, Soft systems methodology.
CBAP
The Certified Business Analysis Professional awarded by the International Institute of Business Analysis (IIBA®). IIBA® publishes the Business Analysis Body of Knowledge® (BABOK®).
Change control
A process whereby changes to requirements are handled in a controlled fashion. The change control process defines the process steps to be carried out when dealing with a proposed change. These steps include documenting the change, analysing the impact of the change, evaluating the impact of the change in order to decide upon the course of action to take, and deciding whether or not to apply the change. The analysis and decisions should be documented in order to provide an audit trail relating to the proposed change.
Class
A class is a definition of the attributes and operations shared by a set of objects within a business system. Each object is an instance of a particular class. See Object.
Class model
A technique from the Unified Modeling Language (UML). A class model describes the classes in a system and their associations with each other.
Cloud computing
A general term for the delivery of hosted services over the internet.
Competency (or Competence)
A competency is a skill or quality an individual needs to perform his or her job effectively.
Computer-Aided Software Engineering (CASE)
An automated toolset that provides facilities to support requirements engineering and software development. These facilities will include the production and storage of documentation, management of cross-references between documentation, restriction of access to documentation and management of document versions. Sometimes known as Computer-Aided Requirements Engineering (CARE).
Consensus model
The definitive, agreed BAM derived from the individual stakeholder BAMs.
Cost–benefit analysis
A technique that involves identifying the initial and ongoing costs and benefits associated with a business change initiative. These costs and benefits are then categorised as tangible or intangible and a financial value calculated for those that are tangible. The financial values are analysed over a forward period in order to assess the potential financial return to the organisation. This analysis may be carried out using standard investment appraisal techniques. See Payback period (or break-even analysis) and Discounted cash flow/net present value analysis.
Critical success factors
The areas in which an organisation must succeed in order to achieve positive organisational performance.
Discounted cash flow
An investment appraisal technique that takes account of the time value of money. The annual net cash flow for each year following the implementation of the change is reduced (discounted) in line with the estimated reduction in the value of money. The discounted cash flows are then added to produce a net present value. See Net present value.
Document analysis
A technique whereby samples of documents are reviewed in order to uncover information about an organisation, process, system or data.
DSDM
DSDM is a project delivery framework that emphasises continuous user involvement and the importance of delivering the right solution at the right time.
Entity relationship diagram
A diagram produced using the entity relationship modelling technique. The diagram provides a representation of the data to be held in the IT system under investigation. See Entity relationship modelling.
Entity relationship modelling
A technique that is used to model the data required within an IT system. The technique models the data required to describe the ‘things’ the system wishes to hold data about – these are known as the ‘entities’ – and the relationships between those entities.
Ethnographic study
An ethnographic study is concerned with spending an extended period of time within an organisation in order to obtain a detailed understanding of the culture and behaviours of the business area under investigation.
Explicit knowledge
The knowledge of procedures and data that is foremost in the business users’ minds, and which they can easily articulate. See Tacit knowledge.
External business environment
The business environment that is external to an organisation and is the source of forces that may impact the organisation. Types of forces may include the introduction of new laws, social trends or competitor actions. See PESTLE analysis, Five Forces analysis.
Force-field analysis
A technique to consider those forces inside and outside the organisation that will support adoption of a proposal and those that will oppose it. This technique was developed originally by Kurt Lewin and may be used in evaluating options for change and in change management.
Functional requirement
A requirement that is concerned with a function that the system should provide, i.e. what the system needs to do.
Gap analysis
The comparison of two views of a business system, the current situation and the desired future. The aim of gap analysis is to determine where the current situation has problems or ‘gaps’ that need to be resolved. This leads to the identification of actions to improve the situation. The business activity modelling technique may be used to provide an ideal future view which can then be compared with a view of the current situation. An alternative, more detailed approach is to use the business process modelling technique, using ‘as is’ and ‘to be’ process models.
Holistic approach
The consideration of all aspects of a business system and their interactions. This incorporates the people, process and organisational areas, in addition to the information and technology used to support the business system.
IMIS
The Institute for the Management of Information Systems.
Impact analysis
The consideration of the impact a proposed change will have on a business system and on the people working within it.
Intangible benefit
A benefit to be realised by a business change project for which a credible, usually monetary, value cannot be predicted. See Tangible benefit.
Intangible cost
A cost incurred by a business change project for which a credible, usually monetary, value cannot be predicted. See Tangible cost.
Internal business environment
The internal capability of the organisation that affects its ability to respond to external environment forces. Techniques such as MOST analysis or the Resource Audit may be used to analyse the capability of the internal business environment. See MOST analysis and Resource audit.
Internal rate of return
A calculation that assesses the return on investment from a project, defined as a percentage rate. This percentage is the discount rate at which the Net Present Value is equal to zero and can be used to compare projects to see which are the better investment opportunities. Alternatively, this rate may be used to compare all projects with the return that could be earned if the amount invested was left in the bank.
Interview
An investigation technique to elicit information from business users. An interview agenda is prepared prior to the interview and distributed to participants. The interview is carried out in an organised manner and a report of the interview is produced once the interview has been concluded.
IT system
A set of automated components hosted on a computer that work together in order to provide services to the system users. See Business system.
itSMF
An internationally recognised forum for IT service management professionals
Institution of Engineering And Technology (IET)
One of the world’s leading professional bodies for engineering and technology.
Key Performance Indicators (KPIs)
These are specific areas of performance that are monitored in order to assess the performance of an organisation. Key performance indicators are often identified in order to monitor progress of the critical success factors. Measurable targets are set for KPIs. See Critical success factors.
McKinsey 7-S
A framework developed by the McKinsey consultancy organisation. The 7-S model identifies key areas for the implementation of business change.
MoSCoW
An approach to prioritising requirements.
MoSCoW - Must have
A mandatory requirement without which the system has no value.
MoSCoW - Should have
A mandatory requirement that must be delivered, but, where time is short, could be delayed for a future delivery. This should be a short term delay.
MoSCoW - Could have
A requirement that would be beneficial to include if it does not cost too much or take too long to deliver, but it is not central to the project objectives.
MoSCoW - Want to have (but Won’t have this time)
A requirement that may be needed in the future but is not required for this delivery.
MOST analysis
An analysis of an organisation’s Mission, Objectives, Strategy and Tactics to identify any inherent strengths or weaknesses, for example from a lack of strategic direction or unclear objectives. See Internal business environment.
Net present value
The amount an investment is worth once all of the net annual cash-flows in the years following the current one are adjusted to today’s value of money. The net present value is calculated using the discounted cash flow approach to investment appraisal. See Discounted cash flow, Internal rate of return.
Non-functional require ment
A requirement that defines a constraint or performance measure that the system or the functional requirements must comply with.
Object
An object is something within a business system for which a set of attributes and functions can be specified. An object is an instance of a class. See Class.
Payback calculation
An investment appraisal technique where a cash-flow forecast for a project is produced using the current values of the incoming and outgoing cash flows; no attempt is made to adjust them for the declining value of money over time. See Discounted cash flow.
PESTLE
A technique used to analyse the external business environment of an organisation. The technique involves the analysis of the political, economic, socio- cultural, technological, legal and environmental forces that may impact upon an organisation. See External business environment.
Porter’s five forces
A technique used to analyse the industry or business domain within which an organisation operates. See External business environment.
Project initiation document (PID)
A document that defines the business context for a project and clarifies the objectives, scope, deliverables, timescale, budget, authority and available resources.
Protocol analysis
A technique used to elicit, analyse and validate requirements. Protocol analysis involves requesting the users to perform a task and describe each step as they perform it.
Prototyping
A technique used to elicit, analyse and validate requirements. Prototyping involves building simulations of documents, processes or systems in order to enable the business users to visualise any proposed changes and hence increase understanding about the system requirements.
RACI or RASCI
Linear responsibility matrix charts that identify stakeholder roles
and responsibilities during an organisational change process.
Requirement
A feature that the business users need the new system (business or IT) to provide.
Requirements catalogue
An organised set of requirements where each individual requirement is documented using a standard template.
Requirements elicitation
A proactive approach to investigating requirements required to resolve a business problem or enable a business opportunity. Involves working with the business users and helping them to visualise and articulate their requirements.
Requirements management
A governance approach that aims to ensure that each requirement is tracked from inception to implementation (or withdrawal) through all of the changes that have been applied to it.
Resource audit
A technique to analyse the capability of an organisation. The resource audit considers five areas of organisational resource: tangible resources – physical, financial and human; intangible resources – know-how and reputation.
Rich picture
A pictorial technique offering a free-format approach that allows analysts to document whatever is of interest or significance in the business situation. This technique originated from the Soft Systems Methodology. See Soft systems methodology.
Risk
A problem situation that may arise with regard to a project or business situation. Potential risks are identified for each option in a business case, the probability of the risk occurring and the likely impact of the risk are assessed, and suitable countermeasures are identified. See Business case.
Risk management
The identification, assessment, monitoring and control of significant risks during the development, design and implementation of IT systems.
Scenarios
A technique used to elicit, analyse and validate requirements. A scenario traces the course of a transaction from an initial business trigger through each of the steps needed to achieve a successful outcome. Alternative scenarios, for example, where specific conditions are not met, are also traced.
SFIA and SFIAplus
The Skills Framework for the Information Age (SFIA) and the extended version provided by BCS (SFIAplus). Standard frameworks setting out the definition of skills and levels of competency for anyone working in the Information Systems industry.
Shadowing
A technique used to find out what a particular job entails. Shadowing involves following a user as they carry out their job for a period such as a day or two days.
Six thinking hats
A thinking tool developed by Edward de Bono for individuals and for groups to improve the thinking process.
SMART
A mnemonic used to ensure that objectives are clearly defined in that they are specific, measurable, achievable, relevant, time-framed.
Soft Systems Methodology
A methodology that provides an approach to analysing business situations devised by Peter Checkland and his team at Lancaster University.
Special purpose records
A technique that involves the business users in keeping a record about a specific issue or task. Typically the record is based on a simple structure, for example a five bar gate record.
Stakeholder
An individual, group of individuals or organisation with an interest in the change. Categories of stakeholder include customers, employees, managers, partners, regulators, owners, suppliers and competitors.
Stakeholder analysis
The analysis of the levels of power and interest of a stakeholder in order to assess the weight that should be attached to their views. This technique provides a means of categorising stakeholders in order to identify the most appropriate stakeholder management approach.
Stakeholder management
The definition of the most appropriate means to be adopted in order to engage with different categories of stakeholder. The approach to each stakeholder will be different depending on (a) their level of interest in the project and (b) the amount of power or influence they wield to further or obstruct it.
Strategic analysis
The application of techniques in order to analyse the pressures within an organisation’s external business environment and the level of internal organisational capability to respond to these pressures.
Strategy
The direction and scope of an organisation over the longer term. The strategy is defined in order to achieve competitive advantage for the organisation through its configuration of resources within a changing business environment. The strategy also needs to fulfil the stakeholders’ expectations.
STROBE
A technique that represents a formal checklist approach to observation, where the analyst is investigating specific issues. STROBE stands for STRuctured Observation of the Business Environment and is used to appraise a working environment.
Survey
A technique used to obtain quantitative information during an investigation of a business situation. Surveys are useful to obtain a limited amount of information from a large group of people.
Swimlane
A row on a business process diagram/model that indicates who is responsible for a given process or task. Typical swimlanes represent departments, teams, individuals or IT systems.
Swimlane diagram
A technique used to model business processes. A swimlane diagram models the business system response to a business event. The model shows the triggering event, the business actors, the tasks they carry out, the flow between the tasks, the decisions and the business outcome. See Business process model.
SWOT Analysis
A technique used to summarise the external pressures facing an organisation and the internal capability the organisation has available to respond to those pressures. The mnemonic stands for Strengths, Weaknesses, Opportunities and Threats.
Tacit knowledge
Those aspects of business work that a user is unable, or omits, to articulate or explain. This may be due to a failure to recognise that the information is required or to the assumption that the information is already known to the analyst. See Explicit knowledge.
Tangible benefit
A benefit to be realised by a business change project for which a credible, usually monetary, value can be predicted. See Intangible benefit.
Tangible cost
A cost incurred by a business change project for which a credible, usually monetary, value can be predicted. See Intangible cost.
Task
On a Business process model or Swimlane diagram, a piece of work carried out by a single actor at a specific moment in time.
Task modelling
The technique for developing a model which describes the human activities and task sequences required by a business system. The task model elaborates the tasks identified by mapping business processes onto specific individuals or workgroups.
Technical option
A technical option describes how the business solution may be implemented using information technology.
Unified Modeling Language
The Unified Modeling Language (UML) is a suite of diagrammatic techniques that are used to model business and IT systems.
Use case
A use case is something that an actor wants the IT system to do; it is a ‘case of use’ of the system by a specific actor and describes the interaction between an actor and the system.
Use case description
A use case description defines the interaction between an actor and a use case.
Use case model
A technique from the Unified Modeling Language (UML). A use case model consists of a diagram showing the actors, the boundary of the system, the use cases and the associations between them, plus a set of use case descriptions.
Value chain
A concept developed by Michael Porter to identify the primary and support activities deployed within organisations to deliver value to customers.
Value proposition
A clear statement of the value that an organisation believes a product or service delivers, or is perceived to deliver, to the organisation’s customers.
Workshop
An investigation technique whereby a meeting is held with business actors from a range of business areas in order to elicit, analyse or validate information. An agenda is prepared prior to the workshop and distributed to participants. The workshop is run by a facilitator; actions and decisions are recorded by a scribe.
