Distinguish user requirements from system requirements and identify one problem associated with each.

### The concept User requirements are written for people such as end users, client managers, and client engineers. Natural language and diagrams make them accessible, but can introduce ambiguity or mix several needs together. System requirements state functions, services, and operational constraints in greater detail and may form part of an agreement between buyer and developer. Domain requirements can be hard to understand or may remain implicit. ### What a good answer covers - Describes the audience and accessible form of user requirements. - Explains that system requirements are more detailed. - Identifies a user-requirement problem, such as ambiguity. - Identifies a system or domain requirement problem, such as inconsistency or implicitness. ### Terms - **Stakeholder**: A person or group with an interest in the system. - **Implicit requirement**: A requirement assumed but not stated clearly. ### Remember User requirements communicate needs; system requirements specify them in detail.