Requirement All levels A measurable statement of intent about something that the system must do, a property the system must have, or a constraint on the system. Scenario Requirements A sequence of taken to complete a user requirement, Analysis similar to a use case. Subject All levels A subject matter expert is an employee of CMS or a contractor Matter Expert with specific knowledge regarding a domain that interacts with (SME) the system. Stakeholder Enterprise A person, system, or entity that interacts with, is responsible Architecture for, or has some interest/influence in the system being developed. System Requirements A historically umbrella term, which included functional Requirement Analysis nonfunctional, and design requirements. Traceability Requirements The ability to trace relationships between two or more Analysis requirements. Trigger Requirements An action or activity that occurs that causes the scenario to Analysis begin. Use Case Requirements A description of a system’s behavior as it responds to a request Analysis that originates from outside of that system. The use case is made up of a set of possible sequences of interactions between systems and users in a particular environment and related to a particular goal. The use case should contain all system activities that have significance to the users. Use cases typically avoid technical jargon, preferring instead the language of the subject matter expert. User Requirements A requirement that describes how a user interacts with the Requirement Analysis system in order to fulfill a Business Requirement. The UR (UR) could also be internally initiated by the system.
Requirement All levels A measurable statement of intent about something that the system must do, a property the system must have, or a constraint on the system. Scenario Requirements Analysis A sequence of taken to complete a user requirement, similar to a use case. Subject Matter Expert (SME) All levels A subject matter expert is an employee of CMS or a contractor with specific knowledge regarding a domain that interacts with the system. Stakeholder Enterprise Architecture A person, system, or entity that interacts with, is responsible for, or has some interest/influence in the system being developed. System Requirement Requirements Analysis A historically umbrella term, which included functional nonfunctional, and design requirements. Traceability Requirements Analysis The ability to trace relationships between two or more requirements. Trigger Requirements Analysis An action or activity that occurs that causes the scenario to begin. Use Case Requirements Analysis A description of a system’s behavior as it responds to a request that originates from outside of that system. The use case is made up of a set of possible sequences of interactions between systems and users in a particular environment and related to a particular goal. The use case should contain all system activities that have significance to the users. Use cases typically avoid technical jargon, preferring instead the language of the subject matter expert. User Requirement (UR) Requirements Analysis A requirement that describes how a user interacts with the system in order to fulfill a Business Requirement. The UR could also be internally initiated by the system.
RequirementsWritersGuide.docx