BAM_Functional_Test_Plan.docx

DOCX document 34 KB Posted

Attached to
Business Application Mapping Solution Federal contract opportunity
Solicitation number
HC102813R0046
Issued by
Defense Information Systems Agency

About this file

Test Plan

View the file

Other files for this federal contract opportunity

Other files attached to Business Application Mapping Solution, newest first.
File Type Posted
HC1028-13-R-0046-0007.docx DOCX document
BAM_DD254.docx DOCX document
PastPerformanceQuestionnaire_BAM.docx DOCX document
Sample_Questionaire_Cover_Letter.docx DOCX document
HC1028-13-R-0046-0006.docx DOCX document
HC1028-13-R-0046-0005.docx DOCX document
PP_REFERENCES.docx DOCX document
HC1028-13-R-0046-0004.docx DOCX document
HC1028-13-R-0046-0003.docx DOCX document
QASP_Rev.docx DOCX document
HC1028-13-R-0046-0002.docx DOCX document
HC1028-13-R-0046-0001.docx DOCX document
HC1028-13-R-0046.doc DOC document
QASP.docx DOCX document
Past_Performance.docx DOCX document
Encl13_BAM_DD254_(2)_(2).docx DOCX document
Show all 16

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Business Application Mapping (BAM) Functional Test Plan October 9, 2013

DEFENSE INFORMATION SYSTEMS AGENCY
ENTERPRISE SERVICE DIRECTORATE (ESD)

INTRODUCTION

PURPOSE OF THE TEST PLAN DOCUMENT

The functional test plan document documents and tracks the necessary information required to effectively define the approach to be used during the competitive range testing for the Business Application Mapping (BAM) solution. The target audience is the evaluation team, the testing team and the vendor.

COMPETITIVE RANGE TESTING

TESTING OVERVIEW

The vendor will work with the government for one day to develop a detailed use cases specific to their solution to test the BAM functional items listed in section 2.3. The vendor will be required to work with the government to install and configure the application according to the applicable Department of Defense (DoD) Security Technical Implementation Guides (STIG) the offered BAM solution in a mid-tier and a mainframe environment for testing. Two weeks will be provided to complete both installations. The DoD STIG documentation is referenced in the PWS.

The vendor will provide the government testing team a job aide related to the functional items to be tested in order to assist the test team in navigating the system during testing. Vendor support will be available to the government during the two days allotted for the testing to answer questions and address any concerns.

The vendor will have the two days following testing to mitigate any failures or other issues related to testing. Retesting of findings will be completed in one day. Results after this time frame will be final.

TEST RISKS/ISSUES

Any mitigation provided during testing is assumed to be captured by the vendor as an item to be resolved in the tool prior to deployment if an award is made.

ITEMS TO BE TESTED

Item to test
Test Description
User Access
User will log on, role assignment
Execute Discovery
User will kick off and run targeted discovery
View Discovery Results
User will view service map resulting from targeted component and network discovery
Validate Discovery
User will verify map accuracy/completeness based on actual service footprint
Name View/Map
User will name map/view with appropriate service name and save changes
Modify View/Map
User will modify map/view to remove items not required, add items and save changes
Modify View/Map
User will modify map/view to rename components and save changes
Search View/Map
User will search for map/view a created by service name, locate and view
Drill up/down
User will drill down into the map/view to locate detailed information on components/connections
Detect changes
A change will be executed in the environment and a second discovery will locate the change and be able to compare the previous discovery
Export View/Map/Data
User will export data from the system to a .xls and .csv files

TEST PASS/FAIL CRITERA

In the detailed use cases, expected results will be identified. When expected results are achieved, the test will be documented as passing. When expected results are not achieved, the test will be documented as a failure.

TESTING DELIVERABLES

Testing deliverables include the job aide, detailed use cases and a test results document.

TESTING ENVIRONMENT

The physical location for testing will be Mechanicsburg, PA. The physical location of the environments will be Mechanicsburg, PA for mainframe and Montgomery, AL for mid-tier.

image1.png

File details come from the government source that posted it. Updated .