(1) A user-oriented document, which describes the system characteristics from an end users' viewpoint. The document is used to coordinate overall quantitative and non-quantitative system goals for the user, buyer, developer, and other interfacing organizations (e.g., training, facilities, staffing, and maintenance elements). It describes the user organizations and mission from an integrated system point of view. The ConOps document is a place to record non-quantitative systems requirements (also called design goals). (2) A tool used in the elicitation of software requirements. Also called operational concept document (OCD) .