In This Chapter:
Benefits of Interface Analysis
Types of Interface Analysis Meetings
Rules for Effective Interface Analysis
Tailoring Interface Analysis
Analyzing interfaces involves reviewing the system, people, and process linkages that will exist in the proposed business solution. System interfaces define system interactions: which systems provide input, which systems require output, and what medium is used. Interface analysis can also describe what manual or automated processes the proposed business solution requires.
Analyzing interfaces enables the creation of a list of inputs and outputs that other systems, processes, or people will use. Table 12-1 shows benefits and disadvantages of interface analysis.
Common interface analysis meeting types are:
Customer review meetings. Formal requirements are identified that provide the linkages between information, people, processes, and systems that are necessary to provide a robust, complete, and accurate solution.
Developer review meetings. Early, high-level requirements documentation and system models are reviewed to identify interfaces, regulations, or technical standards.
Table 12-1—Benefits and Disadvantages of Interface Analysis
Benefits of Analyzing Interfaces | Disadvantages of Analyzing Interfaces |
Discovers missed interfaces and their purpose Determines regulations or interface standards Provides missed requirements Uncovers areas of project risk |
Not useful as a standalone elicitation activity if domain and technical expertise is high Can begin to focus on too many technical details Can be redundant with modeling activities |
Key rules for effective interface analysis are:
Conduct an internal meeting as a part of any product development process. At this meeting, developers can take an honest and early first look at the system to see inconsistencies and errors.
Create clearly defined roles for follow-up:
Have the project manager clarify scope boundary issues with the sponsor or the group that is paying for the project.
Have the business analyst follow up on open issues on user intention and goals.
Continue to update business requirements documents with information and assumptions about interfaces. The documentation may be in the form of a list or updated use case diagrams or context diagrams.
Interface analysis is necessary and valuable for any initiative size. The business analyst scales activities to the project environment. Table 12-2 shows the variances scaled to the project profile.
Table 12-2—Interface Analysis Scaled to Project Size, Risk, Complexity