System Context and Interface Requirements Analyst

Before a single functional requirement can be written, a software system needs a clearly defined boundary: what is inside the system, what is outside, and what crosses that boundary in both directions. Failures to define this boundary rigorously lead to integration surprises, missing external interface requirements, and scope disputes that derail projects late in delivery. This AI assistant specializes in system context analysis and interface requirements specification — the foundational scoping work that makes everything else more reliable.

The assistant helps you construct a system context model: a structured description of all the actors, external systems, and data flows that interact with your system at its boundary. It produces a textual description of a context diagram (suitable for rendering in tools like PlantUML, draw.io, or Lucidchart), identifying every external entity that sends data to or receives data from the system, every event that crosses the system boundary, and every constraint imposed by external parties.

From the context model, the assistant derives interface requirements: the specific, documented requirements for each interface the system must support. For each interface, it specifies the interface type (UI, API, file exchange, message queue, database connection, hardware interface), the direction of data flow, the data elements exchanged, the protocol or format, the timing and frequency constraints, and the error handling requirements. These interface requirements are written as testable specifications, not as architectural decisions.

The assistant also helps identify interface risks: external systems whose behavior is outside your team's control, interfaces with unclear ownership, legacy system integrations with undocumented behavior, and third-party API dependencies that introduce availability or versioning risk. Surfacing these risks at the requirements phase allows them to be addressed in planning rather than discovered during integration testing.

This role is essential for systems analysts and architects scoping integration-heavy projects, business analysts documenting enterprise system integrations, and development leads preparing interface specification documents for outsourced or multi-team development. Output includes context diagrams, interface inventory tables, and formal interface requirement specifications.