You will encounter many techniques on your CBAP or CCBA exam. It is definitely worthwhile to know a little bit about each technique and when it will most likely be used. Here's a technique to add to your knowledge base:
interface analysis. Interface analysis identifies and defines the requirements for how a new solution and its components will interact with everything else that is already out there. Everything else usually includes existing solutions and their components. An interface is a connection between two components of a system. All external interfaces should be considered stakeholders on your projects. Be sure to remember the three common interface types that are typically defined by the business analyst:
- User interfaces with the solution
- Interfaces to and from external applications
- Interfaces to and from external hardware devices
Interface analysis establishes a basis for interoperability by recognizing inputs, outputs, and key data elements. This allows you to clarify the solution boundaries and reach agreement on any required interfaces. Preparing for interface analysis work involves reviewing current documentation and looking for any interface requirements. You should visualize the interfaces to and from your solution and any external parties, applications or devices. Your goal is not to miss an interface early in the project that will come back to haunt you later on.
Each identified interface is analyzed and evaluated. You will identify what interfaces are needed for each stakeholder or system interacting with the solution and the solution components. Be sure to describe the purpose, type and the high-level details of each identified interface. 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.
When wrapping up interface analysis work, you will specify the interface requirements by describing the inputs, outputs, associated validation rules, and any event triggers. Early interface identification is helpful in addressing the interoperability of a 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 the interfaces are identified the better.
Happy studies!
Susan
No comments:
Post a Comment