In order to accomplish this step you need to understand a few things here, such as:

• Where they exist.
• The structure of the information flowing in and out.
• Integrity constraints.
• Dependencies (other sources and sinks, perhaps services in some instances).
• Security issues.

So, how do you create a source or sink interface directory?

There are a few key things you need to consider when creating this directory, including attributes that need to be in the directory, including:

System

1. Interface Name
2. Type of Interface
3. Security Issues
4. Structure
5. Standards
6. Enabling Technology
7. Dependencies
8. Performance Issues

System

The system is the name of the system where the interface is located. For instance, if it’s part of an SAP system we may want to call that system SAP_1 or Main_ERP. We’ll use this name to reference services, as well as other interesting things that are internal to this system.

Interface Name

The interface name is simple the name of the source or sink interface. For instance, SAP_Interface_1, or perhaps use given native interface name.

Type of Interface

The type of interface category of the interface. For example, database interface, application integration, embedded device, etc., from our discussion above.

Security Issues

Security issues is where we take into account any security rules or restrictions that should be followed, including security employed, type of security, and who manages the security.

Structure

We use the structure portion of the directory to record the structure of the information flowing from the sources and to the sinks. For example:

F_Name (char 20)
L_Name (char 15)
Address (char 50)
City (char 30)
State (char 2)
Zip (char 10)

Standards

Here is where we record any standards employed, such as Web services (WSDL, SOAP, etc.), XML, or vertical standards such as HIPPA.

Enabling Technology

We need to record the enabling technology including the type and brand of the database employed, or any other enabling technology present, such as screen scraping technology.

Integrity

Here is where we define any integrity issues, such as the fact that you can’t update a particular sink unless for consulting a source.

Performance Issues

Here is where we record any performance issues, that need addressing. Such as the fact that a source can only produce 20 structured records a minute.