Requirements for System Integration

All systems are connected, they talk to each other. Almost every project requires integration and it has to be specified well, to make sure that the end result will match the expectations.

Want to learn more?

Subscribe to the course

How is this helpful?

  • Understand what system integration and API mean. Understand the basics about client side and server side, methods and parameters.
  • Build architectural and sequence diagrams to represent the system interaction. Everybody can understand diagrams. Learn how to represent the integration specifics on diagrams. The architectural diagrams provide the big picture, while the sequence diagrams present the flow of individual messages.
  • Describe the requirements from the client side and from the server side perspectives. As a Business analyst you usually work on either side – the client or the server. Each side has its specifics to represent the requirements for the dev team.
  • Make the integration secure. Make sure no malicious user will sniff the traffic or perform unauthorized actions. Be ready to raise those topics with technical stakeholders.
  • Consider design specifics for different types of APIs. RESTful, RPC or SOAP – what’s the difference, advantages and disadvantages – be prepared for technical calls

Want to learn more?

Subscribe to the course