Skip to content
Browse
BABOK Guide
BABOK Guide
10. Techniques
Introduction 10.1 Acceptance and Evaluation Criteria 10.2 Backlog Management 10.3 Balanced Scorecard 10.4 Benchmarking and Market Analysis 10.5 Brainstorming 10.6 Business Capability Analysis 10.7 Business Cases 10.8 Business Model Canvas 10.9 Business Rules Analysis 10.10 Collaborative Games 10.11 Concept Modelling 10.12 Data Dictionary 10.13 Data Flow Diagrams 10.14 Data Mining 10.15 Data Modelling 10.16 Decision Analysis 10.17 Decision Modelling 10.18 Document Analysis 10.19 Estimation 10.20 Financial Analysis 10.21 Focus Groups 10.22 Functional Decomposition 10.23 Glossary 10.24 Interface Analysis 10.25 Interviews 10.26 Item Tracking 10.27 Lessons Learned 10.28 Metrics and Key Performance Indicators (KPIs) 10.29 Mind Mapping 10.30 Non-Functional Requirements Analysis 10.31 Observation 10.32 Organizational Modelling 10.33 Prioritization 10.34 Process Analysis 10.35 Process Modelling 10.36 Prototyping 10.37 Reviews 10.38 Risk Analysis and Management 10.39 Roles and Permissions Matrix 10.40 Root Cause Analysis 10.41 Scope Modelling 10.42 Sequence Diagrams 10.43 Stakeholder List, Map, or Personas 10.44 State Modelling 10.45 Survey or Questionnaire 10.46 SWOT Analysis 10.47 Use Cases and Scenarios 10.48 User Stories 10.49 Vendor Assessment 10.50 Workshops

3. Techniques

3.13 Interface Analysis

Guide to Business Data Analytics

3.13.1 Purpose

Interface analysis is used to identify where, what, why, when, how, and for whom information is exchanged between solution components or across solution boundaries.

For more information, see BABOK® Guide v3, chapter 10.24.
3.13.2 Business Data Analytics Perspective

An interface represents a connection that facilitates the exchange of information between one or more solution components, organizational units, or business processes. Interface analysis helps the team understand what information is exchanged through the interface, as well as the volume of data through that interface.

.1    Identify the Research Question

Interface Analysis does not have a significant role in the Identify the Research Question domain. However, understanding what data is available through different interfaces can be used to frame better quality research questions.

.2    Source Data

During data sourcing, an interface can be analyzed to correlate interface elements to database attributes and discover any underlying data or business rules. How the data is saved in the corresponding database entities can be viewed and these findings can be documented through data mapping to be leveraged during extract, load, and then transform (ELT) activities.

For instance, an update to a customer's profile may update the corresponding data record for the customer, or it may create a new record with an identifier for it being the most recent record. This data mapping work is a beneficial resource for stakeholders who are responsible for business reporting.

.3    Analyze Data

Understanding data transitioned through an interface is important in ensuring good quality data is being generated to answer research questions. Typically, data entered in a system is leveraged for reporting. However, a system acts on that data and generates transactional data which is also valuable to the analytics team.

For instance, to evaluate the success and usage of a newly launched claims application, the analytics team analyzes the data related to the interface to:
  • ensure that the interface elements and sequence accurately represent the business process.
  • evaluate whether data entered via the interface is being saved in the corresponding entities correctly.
  • determine both user and system usage patterns based on activities occurred or events generated. The analysis and reporting of this data helps answer questions such as: What were the most frequently used features in the application? What were the top reasons for an incomplete claim?
  • assess system performance and identify top areas of improvement based on system issues. Analysis and reporting of this data helps answer questions related to interface performance such as: What was the average time to complete a claim? What were the top issues with interface usage (for example, time taken to load a page, issue with password entries)? Were there any security issues?
.4    Interpret and Report Results

Interface Analysis does not have a significant role in the Interpret and Report Results domain. However, thoroughly understanding the data generated through various interfaces improves the team's knowledge of how the data is modified, transitioned, and used. This leads to more accurate interpretation and reporting of results.

.5    Use Results to Influence Business Decision-Making

Interface Analysis does not have a significant role in the Use Results to Influence Business Decision-Making domain. However, a thorough understanding of data generated through various interfaces instills confidence in the results and leads to more confidence in influencing decision-making.

.6    Guide Organization-Level Strategy for Business Analytics

Interface Analysis does not have a significant role in the Guide Organization- Level Strategy for Business Analytics domain. However, a good understanding of an organization's interfaces and the data that is generated leads to more robust information and data models that are maintained for organizational use.