Solution

The correct answer is Context Diagram

Key Points

• Context Diagram:
  • Also known as a Level 0 Data Flow Diagram (DFD), it provides a high-level view of an information system and does not go into details about processes.
  • Context diagrams are typically included in a requirements document to show how the system interacts and will interface with other systems. In layman’s term, it can be termed as a bird’s eye view of the system environment.

Additional Information

• Use Case Diagram:
  • This is a type of diagram from UML (Unified Modeling Language). It shows the relationships among actors and use cases within a system.
  • A "use case" represents a distinct functionality of a system, a component, a package, or a class. "Actors" are people, or other systems, that interact with the system being represented.
• Sequence Diagram:
  • Also a type of diagram from UML, it represents the sequence of actions and interactions of different parts (or "actors") of a system over time.
  • Each actor or component will have a "lifeline" and the interactions between them are represented by "arrows" indicating the flow or direction of interaction. It's particularly useful to represent the flow of logic within the system or process.
• Prototype Diagram:
  • This is not common terminology related to systems design or UML. However, "prototyping" is a common approach in system development, involving creation of an early, simplified model of a final system or product.
  • This can be used to test concepts, designs, and interactions. This term might be referring to diagrams used during prototyping, but these can vary widely depending on the specifics of the project and the techniques used.