The project produces a system operational concept (OpsCon) document under its policies; it describes what the system will do and why, from the user's viewpoint, and is best kept separate from the SyRS although a combined item is allowed. The operational scenario content of A.2.7 is produced while producing the stakeholder requirements specification. Each version carries a title and revision notice that single it out, the approved document is placed under configuration control, and it has a preface (purpose, the activities that produced it, authors and why, audience, expected evolution), a table of contents and lists of figures and tables (A.2.1). The scope section gives an overview; the identifying number, title and abbreviation of the system and the document's position among related OpsCon documents; a document overview with purposes, audience and any security or privacy considerations of its use; and a system overview naming purpose, nature, sponsors, user agencies, suppliers, support agencies, certifiers and operating sites, with related documents and a strongly recommended graphical overview (A.2.2). Referenced documents are listed with number, title, revision, date and source (A.2.3).
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.