Interface Analysis with Worked Out Example

Introduction

Interface analysis is an important business analysis technique. In this blog, we will understand what interface analysis is using a real-life example using Adaptive’s GRCPerfect solution.

Before we get into interface analysis, let’s first understand the term “interface.”

What is an interface?

An interface is a connection between two components or solutions. Identify interfaces and interactions between solutions and/or solution components. Interface types are:

• User interfaces - Users interacting with the system plus reports.
• Data interfaces between systems.
• Application programming interfaces (APIs).
• Hardware devices.
• Business processes.
• External partners.

What is analysis?

Analysis involves understanding something in-depth. Analysis often involves applying the 5WH principle – Who, Why, What, When, Where, and How.

What is Interface analysis?

Interface analysis delves into understanding the details of any specific interface. Such as,

• Why is the interface needed? Why will business analysts use the interface?
• What information will be exchanged? When will information be exchanged?
• How frequently? Where will information exchange occur?
• How interface should be implemented?

Steps for Interface Analysis:

Prepare for interface analysis

Utilize techniques like document analysis, observation, scope modeling (Use case model), interviews, etc., to understand which interfaces need to be identified.

Identify interfaces

Identify interfaces that are needed in the future for each stakeholder or system that interacts with the system. Describe the function of the interface, assess usage, evaluate the suitable type, and elicit details about the interface.

Define interfaces

Include name, exchange method between entities, message format, exchange frequency, etc.

Strengths

• Helps in identifying stakeholders for elicitation.
• Early identification leads to increased functional coverage. 
• Interface specifications provide a structured means of allocating requirements, business rules, and constraints to the solution.
• Avoids over-analysis of fine details owing to its broad application.

Limitations

• Does not provide insight into internal components / other aspects of the solution.

Interface Analysis Worked out Example

Through an example, let us learn how business analysts use a glossary. Governance, Risk and Compliance (GRC) management system is developed for the ITES and IT domain. Governance, Risk, and Compliance (GRC) management system has various features, one of which is to plan and track programs and projects using standards such as CMMI, ISO 9001, ISO 27001, etc. Its main objective is to help companies implement Governance, Quality, and Information Security Management Systems in an integrated manner.

The proposed GRC system needs to interface with the company’s ERP system, which is Oracle Apps. The following data mapping table defines the interface between Oracle Apps and the GRC system.

Data mapping

Best Practices and Techniques for a Digital Business Analyst

Conflict Resolution Techniques for Business Analysts

Comparing Key Business Analyst Decision-Making Techniques