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.
ACRONYM LIST Acronym Description BPM Business Process Model BR Business Requirement CMS Centers for Medicare & Medicaid Services DOORS Dynamic Object Oriented Requirements System EIA Electronic Industries Association FIPS Federal Information Processing Standards Federal Information Security Management Act FR Functional Requirement GPO Government Printing Office GTL Government Task Leader HIPAA Health Insurance Portability and Accountability Act IEEE Institute of Electrical and Electronics Engineers IIBA International Institute of Business Analysis IT Information Technology NIST National Institute of Standards and Technology NR Nonfunctional Requirement OIS Office of Information Services RD Requirements Document RU Business Rule RWG Requirements Writer’s Guide SME Subject Matter Expert UR User Requirement XLC Expedited Life Cycle
Source – Provide the legislation, strategic objective, or policy guidance document. Example of a Business Rule Rule Number – RU-0099 Rule – A Plan Sponsor is an entity that sponsors a health plan. This can be an employer, union, or some other entity. Associated Business Requirement(s) – BR-001, BR-002 Type – Term Source – CMS Website B.3 User Requirement Attributes Directions Requirement Number – Provide a unique identifying number. This number will be important when establishing traceability. Requirement (the “shall” statement) – Provide a complete sentence using the word “shall” that describes the capability needed by the business to meet their objective. Associated Business Requirement – Provide the user requirement number of the associated business requirement. Source (optional) – Provide the stakeholder who identified or requested the requirement. Priority (optional) – Identify the requirement as “High” if essential to the project/system, “Medium” if desirable but not essential, and “Low” if optional. Purpose (optional) – Provide a brief rationale for the requirement. Example of a User Requirement Requirement Number – UR-001. Requirement (the “shall” statement) – CBC shall issue monthly payments. Associated Business Requirement – BR-100 Purpose (optional) – This allows for plans to be paid for services. Source (optional) – CBC B.4 Functional/Nonfunctional Requirement Attributes Directions Requirement Number – Provide a unique identifying number. This number will be important when establishing traceability. Requirement (the “shall” statement) – Provide a complete sentence using the word “shall” that describes the action or expectation of what the system will do (functional requirement), or the behavioral property the system must have. Purpose (optional) – Provide a brief rationale for the requirement Validation Measure (Demonstration, Test, Analysis, Inspection, Special Qualification Method, or Not Applicable) – Provide a description of how the requirement will be validated.