ATTACHMENT_13___MASTER_ACCEPTANCE_TEST_PLAN.pdf

United States Department of Agriculture

Master Acceptance Test Plan

Prepared by: TCO TESTING GROUP

For the Testing and Certification Office

Version 3.1

United States Department of Agriculture Farm Service Agency Testing and Certification Office

Master Acceptance Test Plan Page 2 of 37

Master Acceptance Test Plan Page 3 of 37

TABLE OF CONTENTS

1.0 SUMMARY

1.1 OVERVIEW OF MASTER TEST PLAN AND DETAILED TEST PLAN

TCO Mission TCO Certified Production Ready Master Acceptance Test Plan Detailed Acceptance Test Plan

2.0 TCO APPROACH TO TESTING AND CERTIFICATION

Overview Requirements Testing Materials Required TCO Testing Responsibility in Project Lifecycle

2.1 APPLICATION TESTING EXPECTATIONS

Requirements Test Relationships

2.2 METHODS AND CONSTRAINTS

Methodology Test Plan Format Control and Tracking Conditions Data Recording Constraints

2.3 TESTING CRITERIA AND APPROVAL

Criteria Entrance Criteria for TCO Exit Criteria Test Approval and Risk Acceptance Retest Criteria

APPENDIX A: DETAILED ACCEPTANCE TEST PLAN INSTRUCTIONS

APPENDIX B: TESTING DOCUMENTATION

APPENDIX C: TESTING TOOLS

APPENDIX D: TESTING FLOW PROCESS

APPENDIX E: GLOSSARY

Master Acceptance Test Plan Page 4 of 37

1.0 Summary

1.1 Overview of Master Test Plan and Detailed Test Plan

TCO Mission

The Testing and Certification Office (TCO) is responsible for delivering quality software that is fully tested and certified production-ready in support of the United States Department of Agriculture (USDA) Farm Service Agency (FSA) programs. TCO also has the responsibility for development of testing processes for non-USDA entities and non-TCO tested applications as required by USDA/FSA. This testing approach will be utilized for TCO tested applications and may serve as a guide for non-TCO tested applications.

TCO Certified Production Ready

After a release has been tested, it is processed for production release. To be certified production ready, a release must be accompanied by a System Release Checklist, which details various documentation received and where they are located for an audit. The software release is reviewed throughout the testing process by business sponsors, development, testing, security, database administrators and production staff.

Master Acceptance Test Plan

The Master Acceptance Test Plan contains high level information to meet established TCO goals related to this responsibility.

(1) TCO approach to testing

(2) Provide guidance to develop a Detailed Acceptance Test Plan

(3) Ensure audit documentation compliance

Detailed Acceptance Test Plan

A Detailed Acceptance Test Plan will be created for a software release and has primary goals as well. It is a living document that will be updated and maintained throughout the testing and release cycle. Not all software releases require a test plan. (i.e. production fix, configuration changes, etc.)

(1) Contains information about how the team plans to test a specific software release.

(2) Communication tool for those interested in understanding the test plan

(3) Test Plan will be posted for information sharing

(4) Audit documentation

(5) May correspond to multiple System Release Checklists

(6) May correspond to multiple phases of an application

Master Acceptance Test Plan Page 5 of 37

2.0 TCO Approach to Testing and Certification

Overview

The Testing and Certification Office (TCO) provides final quality assurance testing and configuration management support for software applications developed in-house and COTS packages deployed on a variety of computer platforms. The software must be controlled, installed, tested, certified and released based on project schedules, requirements, change requests, agency standards and system development documentation. Certified software will be released following established procedures for software implementation.

Requirements

Application software Unit and Integration Testing will be conducted by the responsible development area on the appropriate platform.

The Acceptance Testing and Certification of the Application software will be conducted by the

Testing Certification Office (TCO) group located at the Farm Services Agency (FSA) on the appropriate platform in Kansas City, Missouri.

Risk Identification and Communication

TCO participates in the risk identification process and communicates this information back to the appropriate risk management group which is identified within each project for mitigation or acceptance. The communication should occur as soon as the Tester becomes aware of the Risk.

There are numerous types of “Risk” and additional information can be found in Appendix A –

Detailed Acceptance Test Plan under Waivers and Risk Acceptance.

Testing Materials Required

Materials needed to perform the acceptance testing include infrastructure, software to be tested, compliance to policies and procedures, test data, best practices, and test management tools.

Please refer to Appendix B for a list of current documentation. Also note, not every document will be used on all projects.

TCO Testing Responsibility in Project Lifecycle

The test team shall be orientated to the project and its functions by ensuring their participation in

User Requirements Discussions, project meeting and overview discussions of the project. They shall have a thorough working knowledge of the applicable platform the software will reside on and the functionality of software to be tested. The test team shall also have access to the Test

Team Coordinator, Data Managers, Security Specialists, Program Sponsors, Business Analysts and Software Developers to clarify any issues that affect the preparation and execution of the test scripts. As a TCO tester, you are engaged early in the project as a key team member throughout the entire project.

Master Acceptance Test Plan Page 6 of 37

2.1 Application Testing Expectations

The software is expected to meet the business rules and functionality as defined by the

Applicable User Requirements, and all Standards Documentation including any Technical

Information Advisory (TIA).

Test Relationships

Each business rule test case shall be related to the applicable rule in the User Requirements commonly captured in a document referred to as a traceability matrix.

2.2 Methods and Constraints

Methodology

Design, code, unit and integration testing will be performed by the software development team.

Unit testing is performed to ensure code functionality of individual modules, objects, services, etc. Integration Testing is designed to verify the interaction between application modules, objects, services, etc.

Acceptance Testing and Certification of the software will be performed by the test team in the

TCO (Testing and Certification Office). Acceptance Testing of software is designed to verify that software conforms to user requirements complies with policy and standards, is Section 508 compliant, provides accurate file updates, and has accurate interface and transmission functionality.

Software Certification is the final step in the testing progression prior to release of this software to field locations. If applicable, software can be “Beta Tested” in pilot sites prior to distribution to all National users.

The test coverage will include but not be limited to:

Formal Acceptance Testing as defined by the test cases.

"Artistic" testing performed as non-planned creative actions by the tester to provide unexpected bug detection and a critical view of the product.

Maximum/Minimum testing performed by entering extreme values of data to test numeric limits.

Stress testing performed by testing functions in a multi-user environment.

Diagnostic testing performed to test the system's response to error conditions and that the system generated error and informational messages are tested for accuracy.

Regression testing performed on problem fixes and any redeliver of code changes.

Master Acceptance Test Plan Page 7 of 37

Recovery testing performed to test the system’s ability to recover from unexpected hardware or software failure.

FSA Style Guide and Section 508 Compliance testing.

Test Plan Format

Each test case will have the following format:

Test Description/Condition: the steps required to execute the test case.

Test References: the requirement information specific to the test case.

Test Setup: the environment and test data elements required prior to performing the test.

Expected Results: the anticipated outcome of executing the test case steps.

Actual Test Results: the outcome of completing the test case.

Control and Tracking

Software will be moved to Acceptance Testing with control document KC-287 and submittal requirements documentation. The initial move of software will also include record descriptors for new files and/or database data models as applicable to the specific software.

All problems discovered during the testing period will be monitored and tracked via the defect management system. Test defects will be closed when the following criteria have been met.

Corrected software supplied by the systems development team has been received and installed on the test system and

Corrected software has been verified through retest of the failed test case(s).

Results of test case execution and analysis will be maintained and reported in status reports.

Conditions

Test data generation steps are listed in the test plan as part of Test Setup. The test data generated for each test case may be saved in archives for retesting or may be regenerated as required depending upon the complexity and volume of test data.

An attempt will be made to develop test case scenarios for all major functions within the process.

However, additional test cases may be defined as additional processes are developed and completed.

Tests dependent on external system interfaces, which are not currently available, will be completed upon availability of those interfaces.

Master Acceptance Test Plan Page 8 of 37

Data Recording

Each test case identifies the sequence of test steps. For each step, the action to be performed and the expected results are indicated.

Constraints

The activity level of the test system may not be as high as the activity level of the production system.

2.3 Testing Criteria and Approval

Criteria

The test evaluation criterion is designed when the test plan is formulated. Each test case defines the expected results of each specific action taken. The actions and the expected results are based on the functionality for Service Center processing. Where applicable, each documented test script includes test data preparation steps.

Entrance Criteria for TCO

The following conditions must be met prior to each test:

Integration testing must be completed for all programs related to the function(s) to be tested.

The complete set of program procedure and files are forwarded to the test team.

Test materials for all tests are made available.

Deployment plan must be started, available and posted to the FSA Deployment

Library.

The entrance criteria section on the System Release Checklist must be completed by development and delivered to TCO with the initial code install.

Programs related to the test cannot be undergoing any functional change.

Programs which are modified after initial Integration Testing are to be retested in the

Integration Testing environment prior to submission to the Acceptance Testing Lab.

Programs modified during Acceptance Testing must be retested by the Acceptance

Test Team in the Acceptance Testing environment.

Exit Criteria

The following conditions must be met prior to the completion of each Acceptance Test:

No functional changes are made to programs related to the test after the test has been started. Programs modified after Acceptance Testing has been done are to be

Master Acceptance Test Plan Page 9 of 37 retested. Considerations for retesting are stated in the "Retest Criteria" stated below.

Each test must meet the criteria of its defined expected result.

Master Acceptance Test Plan Page 10 of 37

Test Approval and Risk Acceptance

The approval authority for determining test completion is listed in the following table:

Software Testing and Certification

Approval Authority

Technical / Requirement Functionality TCO/w/Program Sponsor Concurrence

Notices and Handbooks Program Sponsor

Waiver’s for FSA Style Guide and other

Information Bulletin standard

ITSD Directors (AMC, ADC) and the

Development Architect

Waiver’s for Software Deficiencies

Program Sponsor /w/ Test Team

Concurrence

Retest Criteria

A test must be repeated if any of the following conditions occur:

The program(s) related to the function(s) being tested have been modified.

The test script is altered.

The external interface related to the test is modified.

Master Acceptance Test Plan Page 11 of 37

This page is intentionally left blank

Master Acceptance Test Plan Page 12 of 37

APPENDIX A: Detailed Acceptance Test Plan Instructions

Overview - Creating the Plan

This appendix will provide detail instructions and examples on how to create a Detailed Acceptance Test Plan. The Detailed Acceptance Test Plans are created as “living” documents and updated over the course of testing. As new information becomes available it should be incorporated into the Detailed Acceptance Test Plan. These plans must be created for significant releases into production. Not all software releases require a test plan. (i.e.

production fix, configuration change, etc.) The final determination on the necessity of a detailed test plan will be the decision of the Group Chiefs.

Note: In the event the application is part of a multiple application release, it should be noted within the Detailed Test Plan that multiple system dependencies exist and must be considered.

1.0 GENERAL INFORMATION SECTION

The general information section contains material unique to this release. This section will not address the functional changes or defect resolution but will identify specifically the ownership, environment and team members associated with this release. In this section the application or data warehouse will be identified up front and assumed through-out the document when completing the required information pertaining to the Test Plan. Below listed in Section 1.1 you will find the individual detailed instructions and examples to assist in completing the Detailed Acceptance Test Plan.

PROJECT NAME

PROJECT NAME

Application/Data

Warehouse Acronym

Application/Data Warehouse Name

NRRS National Receipts and Receiving System

Project Name must include the Acronym and Name of your project (i.e., NRRS... National Receipts and Receivables System). See User Requirement documentation for project acronym and name.

PROJECT DESCRIPTION

PROJECT DESCRIPTION

Overview

NRRS is the USDA/FSA Financial System to store and track Farm Program and

Collections. It interfaces with the other Financial Systems.

Project Description is a brief overview of your project. It must contain your project’s purpose, scope and functionality for this release. Project User Requirement documentation is a good resource for creating the project description.

Master Acceptance Test Plan Page 13 of 37

PROGRAM SPONSOR

PROGRAM SPONSOR

Organization

Receivable Management Organization (RMO)

Program Sponsor is the business owner of the application. See User Requirement documentation for program sponsor.

PROJECT SCHEDULE

PROGRAM SCHEDULE

Milestone Planned Start Date Planned Finish Date

Receive Requirement (s)

Complete Detailed Acceptance Test

Plan

Perform Requirement Gap Analysis

Write Test Cases

Perform Peer Review

Microsoft Project Schedule Link:

A baseline testing project schedule is required to set expectations regarding the expected level of effort to complete key testing tasks and allow current and future planning of resource (hardware, software and personnel) availability or allocation. This baseline project schedule is not considered the official project schedule that will be maintained throughout the project and is not to be maintained. Due to size and complexity, a formal project plan may be requested to be developed and maintained using a tool such as Microsoft Project. When a formal plan is required, milestones are not required to be entered in this plan but a link to the formal project plan must be inserted following the table. The project plan location must support access by intended users of the detail test plan.

For releases that do not require a formal project plan, the following milestones are to be evaluated and included in the detail project plan as necessary to communicate release target date and support monitoring and reporting needs. Milestone planned start and planned finish should be based on the expected level of effort taking into consideration program legislated or mandated dates, software delivery dates and testing resource availability.

Receive Requirements - Scheduled start date for receive requirements is either the target date provided for initial delivery of requirements or the date received, if available. Planned finish may be the same date as planned start if a final draft is available when the detail test plan is prepared.

Master Acceptance Test Plan Page 14 of 37

Complete Detailed Acceptance Test Plan – Detailed test plan is a living document with planned start being the date drafting was initially started. Planned finish should reflect the planned date for final review and signoff prior to production release. Ideally the planned final review and signoff will occur 10 days prior to production.

Perform Requirement Gap Analysis - Requirement gap analysis duration is based on number and complexity of requirements. Planned start date for gap analysis should coincide with actual date requirements are being reviewed and planned finish should coincide with date for initial test cases to be completed. In depth analysis is expected for all test projects to confirm requirements are understood, complete and testable resulting in fewer change requests and defects. Gap analysis results may be recorded in a sandbox or other format as determined by the project team.

Write Test Cases – Write test case duration is based on the expected time for documenting initial test cases. This may extend into the overall test time but should be nearly finished at the time testing is planned to begin.

Perform Peer Review - Peer reviews are a short duration activity (one to five days) to leverage expertise among testers and validate coverage by reviewing test plans, test cases or other identified artifacts. Peer review sessions may include internal resources as well as business owners. Reviews are not required for every project and may be determined based on the visibility and complexity of the software being tested.

Benefits Some of key benefits for peer reviews include:

1) Assurance that testing coverage is complete as possible.

2) Leveraging knowledge and expertise from other testers and participants.

3) Confirmation that testing artifacts are consistent and being completed in accordance with any TCO defined SOP’s.

4) Information from reviews can be analyzed and used to improve TCO processes.

Review Process Here is an outline for conducting a peer review:

1) Reviews will be requested by the software tester, manager or business owner.

2) Once a peer review is initiated – the manager will work with the lead tester to identify the artifacts, goals and timeframe will be established.

3) Participants are identified and a meeting request is distributed. The participants may include the lead tester, a manager and a reviewer. The reviewer could be a tester on another project, another manager, business owner or any other person that can provide value to the review session.

4) One week prior to the review the artifacts need to be posted to Sharepoint or a common repository for participants to access.

5) Meeting should cover the artifacts that were previously identified. The level of detail is dependent on the participants and the project being discussed.

6) At the end of the meeting - document any action items or schedule follow-up sessions as necessary.

Master Acceptance Test Plan Page 15 of 37

Configure the Application -Configuration should be planned for completion based on size and complexity of software to be received. Reflects the initial configuration only with the understanding that changes made be made as software is tested. New applications should allow up to 2 weeks for completion with incremental releases planned for longer duration.

Execute Test Cases - Time planned to execute tests. It is unlikely all tests may be executed so the minimum time planned should allow for all critical or high risk tests to be completed. If backend testing is needed by outside resources, this timeline must be coordinated to reflect all system time. Note: If testing timeline does not meet business requested date, please add a business requested date to the detailed test plan for tracking.

Release Software - Planned start should be the date that initial release is being planned, typically 2 weeks in advance of planned production date. Planned finish should reflect plans for final moves.

Close Project - Planned date should begin within 1 week of production move date and be completed within 2 weeks. This milestone is to review effectiveness of testing, update project release folders, and archive documents as needed.

Lessons Learned – Lessons Learned provides a powerful method of sharing good ideas for improving work processes, reducing risk, improving efficiency and enhance the overall effectiveness of the team. Lessons learned should be captured throughout the project and reviewed at the end of the project for what went right, what went wrong, and what should we do differently in the future.

NOTE: Constraints or assumptions used may need to be documented as additional information following the Project Schedule table within the Detailed Test Plan.

Master Acceptance Test Plan Page 16 of 37

WAIVERS AND RISK ACCEPTANCE

WAIVERS and RISK ACCEPTANCE Type Waiver/Defect Number (s)

Architecture

Standards Exceptions

Configuration

Exceptions

FSA Style Guide

Exceptions

All system development is to be conducted in accordance with the Software Development Life

Cycle (SDLC). Development teams shall submit an SDLC Waiver whenever deviating from published standards. When this situation occurs the deviation must be listed in your project’s

Detailed Test Plan by a Waiver or Risk Acceptance.

Waivers consist of the following exceptions: Architecture Standards, Configuration, FSA Style

Guide, PII Data and Security. Waivers must be created by the Development staff.

A Risk Acceptance occurs when the business owners accept the risk of migrating un-resolved severity 1, 2 and Section 508 defects into production. The severity 1 and 2 defect number will be used to identify each Risk Acceptance.

The Lead Tester must list each waiver and severity 1 and 2 defect number associated with each

Risk Acceptance in the Detailed Test Plan for the applicable Waiver and Risk Acceptance type.

See link for additional information on Architectural Decisions/ Waivers within SDLC site:

http://www.fsa.usda.gov/FSA/sdlcapp?area=home&subject=devarc&topic=landing

Below are definitions for each Waiver and Risk Acceptance type:

Architecture Standards and Configuration Exceptions: Architecture Standards and

Configuration Exceptions are deviations from an active Information Bulletin (IB) that establishes architectural and configuration standards for ITSD. See link for list of the current IBs:

http://www.fsa.usda.gov/FSA/sdlcapp?area=home&subject=inb&topic=landing

FSA Style Guide Exception: A FSA Style Guide exception is a deviation from the USDA Web

Style Guide that defines guidelines and standards for look, feel and navigation to promote consistency while also improving the overall user experience. Therefore, it is critical that designers and developers use the FSA Style Guide to understand how to apply the USDA Web standards to all Web-based applications. Additional information can be found at http://www.fsa.usda.gov/Internet/FSA_File/usda_web_styleguide.pdf.

PII Data Exception: Personally Identifiable Information refers to information which can be used to distinguish or trace an individual’s identify, such as their name, social security number, biometric records, etc. A Personally Identifiable Information (PII) Data exception occurs when

PII data is displayed within electronic systems and paper documents. Safeguarding personally http://www.fsa.usda.gov/FSA/sdlcapp?area=home&subject=devarc&topic=landing http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FFSA%2Fsdlcapp%3Farea%3Dhome%26subject%3Dinb%26topic%3Dact&sa=D&sntz=1&usg=AFQjCNF1PXXbYw_QQHs-qt-f72RJQxiSxg http://www.fsa.usda.gov/FSA/sdlcapp?area=home&subject=inb&topic=landing http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.fsa.usda.gov/Internet/FSA_File/usda_web_styleguide.pdf http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw

Master Acceptance Test Plan Page 17 of 37 identifiable information in the possession of the government and preventing its breach are essential to ensure the government retains the trust of the American public.

See link for additional information on PII:

https://fsa.sc.egov.usda.gov/mgr/itsd/devinfo/Wiki%20Pages/Personally%20Identifiable%20Info rmation%20Resources.aspx

Security Exceptions: A Security Exception occurs when an application or business process does not meet a security policy requirement of the Information Security Office (ISO). The

Security Exception formally documents management approval when a security exception occurs.

It includes the business case, identifies the policy requirement not met, justification, risk statement/assessment, and compensating controls (additional protection to make up for the requirement not being met).

See ISO Policies and Waiver information in following links:

ISO Security Policies:

https://fsa.sc.egov.usda.gov/mgr/iso/public/Wiki%20Pages/Security%20Policy%20Gateway.

aspx

ISO Waiver page:

https://fsa.sc.egov.usda.gov/mgr/iso/public/Wiki%20Pages/Get%20Waivers%20and%20Exc eptions.aspx

Section 508 Exceptions: Section 508 Exceptions occur when software is not compliant with

Section 508 Standards. Section 508 Standards mandate that electronic and information technology (EIT) must be accessible to individuals with disabilities. If a Section 508 defect cannot be resolved, the business owners must accept the risk and provide sign-off to allow the defect to be migrated into production.

Software/Requirements Exceptions: A Software/Requirements Exception occurs when software is not compliant with your project’s software requirements resulting in a severity 1 or 2 defect. In such cases, a defect will be opened to request a software fix from the Development team. If a severity 1 or 2 defect cannot be resolved, the business owners must accept the risk and provide sign-off to allow the defect to be migrated into production.

http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw http://www.google.com/url?q=http%3A%2F%2Fwww.fsa.usda.gov%2FInternet%2FFSA_File%2Fusda_web_styleguide.pdf&sa=D&sntz=1&usg=AFQjCNFL-os_MhtPG9UpIGjFpjAgQICgJw https://fsa.sc.egov.usda.gov/mgr/itsd/devinfo/Wiki%20Pages/Personally%20Identifiable%20Information%20Resources.aspx https://fsa.sc.egov.usda.gov/mgr/itsd/devinfo/Wiki%20Pages/Personally%20Identifiable%20Information%20Resources.aspx https://fsa.sc.egov.usda.gov/mgr/iso/public/Wiki%20Pages/Security%20Policy%20Gateway.aspx https://fsa.sc.egov.usda.gov/mgr/iso/public/Wiki%20Pages/Security%20Policy%20Gateway.aspx http://www.google.com/url?q=https%3A%2F%2Ffsa.sc.egov.usda.gov%2Fmgr%2Fiso%2Fpublic%2FWiki%2520Pages%2FGet%2520Waivers%2520and%2520Exceptions.aspx&sa=D&sntz=1&usg=AFQjCNFKpwfL4A4pbAtrRHw1YSvugxkTdQ https://fsa.sc.egov.usda.gov/mgr/iso/public/Wiki%20Pages/Get%20Waivers%20and%20Exceptions.aspx https://fsa.sc.egov.usda.gov/mgr/iso/public/Wiki%20Pages/Get%20Waivers%20and%20Exceptions.aspx

Master Acceptance Test Plan Page 18 of 37

1.2 PROJECT TEAM MEMBERS SECTION

PROJECT TEAM

PROJECT TEAM

Division/Roles Name

TCO Manager (Chief)

Application Lead

Tester

Application Tester(s)

Remote Tester(s)

Project Team Roles and Responsibilities Link:

This table is used to list all the key team members for a given test project. A separate document may be used for listing all the team members depending on the size and complexity of an individual project. If a separate document is used – the location or link should be provided in the Project Team Roles and Responsibilities Document Link: section below this table.

Please note that all the team members in this table may not be applicable for certain software projects (i.e., a project manager or remote tester may not be available or needed based on the size of the project).

TCO Manager (chief) – TCO Group Chief over the testing project. Responsible for overseeing the software testing, resources assigned to the project, participation in status meetings and reporting to upper management on testing progress (as needed).

Application Tester Lead – Lead tester responsible for all documentation and testing of the assigned software. Lead is also involved in project meetings and any requirements/design clarification with the business sponsor or development groups.

Application Tester(s) – Supporting testers are responsible for assisting in software testing under the direction of the lead tester.

Remote Tester(s) – Remote testers are responsible for assisting in software testing under the direction of the lead tester. Remote testers may include Business team members, Field Office employees or other designated testers outside the TCO office.

TCO – CMSG Team – Default value is the CMSG group e-mail address. Any specific CMSG team members can be listed here is necessary. CMSG team is responsible for controlling the software documentation, configuring and installing the software and releasing any software to production (on the request of the lead tester for the project).

Master Acceptance Test Plan Page 19 of 37

TCO – CMSG S36/AS400 Member(s) – Default value is the current CMSG resources assigned to System36/AS400 software. Any other specific CMSG team members can be listed here is necessary. This group is responsible for loading and releasing all AS400/System36 software to the field offices. This group also prepares (with assistance from the lead tester) and posts any Web or State/County Transmittals to the FSA intranet.

Development Manager (chief) – Development Group Chief over the software project.

Responsible for overseeing the software development, resources assigned to the development team, participation in status meetings and reporting to upper management on software progress (as needed).

Development Lead – Lead developer on the project. Responsible for the development of software and supporting of Acceptance Testing as software modifications are required.

Project Manager – Project Manager assigned on the project (not applicable for all projects). Responsible for overseeing the overall software project from development through implementation (schedule, resources, reporting, etc.).

Program Sponsor Manager (chief) – Program Sponsor Group Chief over the project.

Responsible for overseeing the entire software automation process and direction of the program specialists.

Program Specialist – Program Specialist assigned to the project. Responsible for working with the development and testing organizations to provide the detailed requirements and guidance on the implementation of the software.

Other(s) – Any other key team members that are assigned to this project. This could include members from the Architecture Management Center, Stress Lab team, DBMO, IPUSO or any other group that is heavily involved in the software testing effort.

Master Acceptance Test Plan Page 20 of 37

1.3 ENVIRONMENT AND PRETEST BACKGROUND SECTION

The purpose of the ENVIRONENT AND PRETEST BACKGROUND SECTION is to define specific project information related to documents needed for reference, test environment, test data used, software dependencies, tools, tables updated and files for the project. These details will be recorded in the Detailed Acceptance Test Plan for the individual project.

REFERENCES

REFERENCES

Document Link

Master Acceptance

Test Plan

Dependencies

Diagram

Within the reference table you will list all the documents that are used to create the Detailed Test Plan for your specific project. Some common reference documents are prefilled for your convenience. This is not a complete list and your project may have a variety of documents that are not already included on the list. These documents may be required for audit purposes. See Appendix B: Testing Documentation for a definition of the documents listed below.

Document –…