Definitions

40.3.9 - Definitions (Rev. 105, Issued: 06-02-17, Effective: 07-03-17, Implementation: 07-03-17) These definitions are provided to ensure common understanding. Base Shared System - The FISS, MCS, VMS, or CWF system, which is routinely released by the Shared System Maintainers to their respective user community prior to any user customization. This includes all components released by the Shared System Maintainer, including but not limited to the claim adjudication subsystem, the financial subsystems, and other integrated components (i.e., Pricer, OCE, MCE, Grouper). Functional Testing – Testing to ensure that the functional requirements have been met. Functional testing is performed by the SSMs and the STC. Integration Testing – Testing combinations of interacting software components that make up parts of a system. Integration testing is performed by the SSMs, and the STC. Interface Testing – Testing conducted to evaluate whether subsystems or systems pass data. Interface testing is performed by the STC. Local Components – A Local Component as referenced in section 40.3 is any component or module that supports Medicare claims processing, but is not part of the Base System and is under the control and maintenance of the MAC. Maintainer – The Maintainer is an entity to which CMS directly contracts to maintain a Medicare claim processing shared system (FISS, MCS, VMS, or the Common Working File (CWF) system). The Maintainer, as referenced in section 40.3, does not refer to an entity to which a A/B or DME MAC subcontracts to operate their data center or perform other claim processing support activities. Operational Testing – Testing conducted to evaluate a system in its operational environment. Testing to ensure that the aggregate operational systems and their interfaces can be operated securely with the instructions provided. Operational Testing is performed by the SSMs and the A/B and DME MACs. Performance Testing – Testing that applies heavy transaction and processing loads to the system to ensure that response times, throughput rates, and processing windows remain acceptable and can accommodate production workloads. Performance Testing is performed by the STC. Regression Testing – Testing conducted on a system or components to verify that modifications have not caused unintended effects and that the system or components still complies with its requirements. Regression testing is performed by the SSMs and the STC. Regression Test Set – A set of selectable test cases designed to exercise a system over its functional capabilities and assure that it still works properly after changes have been applied. Requirement Identifier – A unique number assigned to each requirement comprised of the Shared System Maintainer CR Number, the CMS CR Number, and an alphanumeric element to uniquely qualify each requirement. For testing purposes CMS requires that each Test Case Identifier incorporate the Requirement Identifier to which it is traced. Stress Testing – Testing that applies a steadily increasing load to the system until it reaches the point where performance degrades to unacceptable levels. System Testing – Testing to discover any incorrect implementation of the requirements or incompatibilities in the software/hardware environment. System testing includes functional testing, performance testing, and operational testing. System testing is performed by the SSMs and the STC. Test Case Specification – A description of an input situation and of the required results associated with a specific test objective or purpose. Test Case Identifier – A unique identifier assigned to each test case. Test Log – A chronological record of relevant detail about the execution of tests. Relevant details include run date, run time, test status, and actual results. Test Requirement - A specific requirement that is under test and to which one or more test cases are traced. Test requirements may be derived from various types of requirements i.e., business functional requirements, performance requirements etc. Note: Any well-written requirement that is “testable” may be considered a Test Requirement. Any requirement contained in the Business Requirements section of a CR or transmittal, also constitutes a test requirement. Test Set – A collection of test cases that have a common usage. Unit Testing – The testing of individual units (i.e., software components, modules) or groups of related units. It is the lowest level of testing and is usually performed by programmers. Unit testing may be both functional (requirements oriented) and structural (i.e. logic oriented, code coverage oriented). Unit testing is performed by the SSMs.