National Electronic Disease Surveillance System (NEDSS ...

More documents

Recommendations

Info

NEDSS Phase II, Deliverables 1 and 2 QA Roles and Responsibilities Describe the organizational and functional alignment of the QA staff. Describe the roles and responsibilities at the management, team leader, and specialist levels. Processes Provide an overview of the processes that QA uses to ensure that processes and products associated with hardware, software, and documentation are monitored, sampled, and audited to ensure compliance with methodology, policy, and standards. Peer Review Commit to QA participation in the peer review process to identify, document, measure, and eliminate defects in a work product. Process Review Describe audit and assessment reviews that ensure that appropriate steps are taken to carry out activities specified by the project plan. Describe methods by which QA monitors processes by comparing the actual steps carried out with those in the documented procedures. Discuss QA's responsibility to provide review data to management to provide an indication of the quality and status of the project. Problem Reporting Describe the role of QA in identifying problems and recommending corrective actions. Identify the requirement for tasks to include QA in problem reporting and corrective action functions. Discuss the procedures and formats for the preparation, tracking, and management involvement in the use of Quality Action Reports (QARs) used in the program. QA Escalation Procedure Describe the QA escalation procedures that bring high-risk or long-standing, unresolved noncompliance-tracking issues to senior management's attention. QA Report Formats Describe the report formats that formally document and transmit information from QA audits and/or assessment reviews. Standards Describe requirement of QA to ensure that standards are identified that establishes the prescribed methods for development of work products. Also discuss QA's role in assessing standards for adequacy and applicability. Tools Describe the tool sets that QA employs in the conduct of administrative and technical functions. PHRG Page 21 of 35 September 28, 2001
NEDSS Phase II, Deliverables 1 and 2 Appendix C – Project Management Glossary Acceptance Test - Formal testing conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the system. See User Acceptance Test. Activity - A unit of work to be completed in order to achieve the objectives of a work breakdown structure. See Work Breakdown Structure. In process modeling, an activity requires inputs and produces outputs. See Input/Output. Application - A system providing a set of services to solve some specific user problem. Application Model - A model used to graphically and textually represent the required data and processes within the scope of the application development project. Application Software - Software specifically developed to perform a specific type of work; for example, a word processor. Compare to System Software. Architecture - The structure of a computer system, either a part or the entire system; can be hardware, software, or both. Audit - A formal review of a project (or project activity) for the purpose of assessing compliance with contractual obligations. Availability - The degree to which a system (or system component) is operational and accessible when required for use. Baseline - A work product (such as software or documentation) that has been formally reviewed, approved, and delivered and can only be changed through formal change control procedures. See Allocated Baseline, Functional Baseline, Operational Baseline, Product Baseline. Benchmark - A standard against which measurements or comparisons can be made. Bottom-up - The process of designing a system by designing the low-level components first; then integrating them into large subsystems until the complete system is designed; bottom-up testing tests these low-level components first, using software drivers to simulate the higher level components. See Top-down. Build - An operational version of a software product incorporating a specified subset of the complete system functionality. See Version. Business Process Reengineering - The redesign of an organization, culture, and business processes to achieve significant improvements in costs, time, service, and quality. Capability - A measure of the expected use of a system. Capacity - A measure of the amount of input a system could process and/or amount of work a system can perform; for example, number of users, number of reports to be generated. Certification - Comprehensive analysis of the technical and non-technical security features and other safeguards of a system to establish the extent to which a particular system meets a set of specified security requirements. Change - In Configuration Management, a formally recognized revision to a specified and documented requirement. See Change Control, Change Directive, Change Impact Assessment, Change Implementation Notice. PHRG Page 22 of 35 September 28, 2001
Page 1 and 2: Phase II Deliverables #1, 2 and 3 f
Page 3 and 4: NEDSS Phase II, Deliverables 1 and
Page 21: NEDSS Phase II, Deliverables 1 and
Page 37 and 38: Phase II, Task #3 Deliverable: NEDS
Page 39 and 40: PHASE II Task 3 Deliverable Nationa
Page 41 and 42: PHASE II Task 3 Deliverable on-line
Page 43: PHASE II Task 3 Deliverable impleme

National Electronic Disease Surveillance System (NEDSS ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?