According to the BABOK® Guide, interface analysis is a key part of your requirements elicitation and analysis efforts. Interface analysis identifies the interfaces between solutions and/or solution components. This technique allows you to define the requirements for how the solution and its component pieces and parts interact with one another and with the outside world. You will find yourself defining many common interface types: user interfaces, interfaces to and from external applications and interfaces to and from external hardware devices.
Early identification of interfaces addresses the interoperability of the new solution. Interoperability issues can impact the planned solution delivery date due to additional work and testing of the interfaces and data, so the sooner interfaces are identified the better. Interface identification creates the need for collaboration with other systems or projects that the new solution interfaces with, and impacts integration and implementation at the end of the development life cycle.
Interface analysis is performed in three steps – preparation, identification and definition:
Well, that is our closer look at yet another technique used by business analysts, interface analysis. I have found this technique to be of great help on many projects, particularly for IT projects where your interfaces can make or break a successful project. Give a shout if you have another BABOK® technique you would like to explore in more detail!
Business analysts are increasingly becoming the critical liaisons between business and solution development (oftentimes IT), so they must communicate and relate with equal effectiveness throughout all levels of an organization. Download this free White Paper to see which five common obstacles business analysts face and how to address them to ensure success.