DOCUMENT
R -- USER ACCEPTANCE TESTING (UAT) *LOOKING FOR GSA CONTRACT HOLDERS* - Attachment
- Notice Date
- 2/7/2013
- Notice Type
- Attachment
- NAICS
- 541511
— Custom Computer Programming Services
- Contracting Office
- Department of Veterans Affairs;Health Administration Center;3773 Cherry Creek Drive North, Suite 450;Denver CO 80209
- ZIP Code
- 80209
- Solicitation Number
- VA74113I0101
- Response Due
- 2/14/2013
- Archive Date
- 4/15/2013
- Point of Contact
- MAURICE WALKER
- E-Mail Address
-
E.WALKER@VA.GOV<br
- Small Business Set-Aside
- N/A
- Description
- NAICS - 541511 Agency: Department of Veterans Affairs Office: CBO SYSTEMS MANAGEMENT Notice Type:Posted Date: Sources Sought2/07/2013 Response Date: 2/14/2013 Classification Code: FSS Mobis or Schedule 70 NAICS Code: 541511 Synopsis: THIS IS NOT A SOLICITATION. This is a Request for Information (RFI)/Sources Sought notice issued in accordance with FAR 15.201(e) to conduct market research. This RFI is issued solely for information and planning purposes - it does not constitute a Request for Quote (RFQ) - or a promise to issue a RFQ in the future. This request for information does not commit the Government to contract for any supply or services whatsoever. The Department of Veterans Affairs (VA) is not, at this time, seeking proposals and will not accept unsolicited costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested vendor's expense. Not responding to this RFI does not preclude participation in any future RFQ, if any is issued. Any information submitted by respondents to this RFI is strictly voluntary. All submissions become Government property and will NOT be returned. This announcement is based upon the best information available and is subject to future modification. Contracting Office Address Department of Veterans Affairs (VA), Health Administration Center (HAC) 3773 Cherry Creek Dr. North, Denver, CO, 80209 Point of Contact: Maurice Walker 303-398-7107 (P) Maurice.Walker@va.gov Overview: A skilled contractor is needed to provide an objective and independent assessment of software product and related processes throughout the project lifecycle. The contractor shall test the entire solution from the functional standpoint in order to verify that all features documented are working as specified in the requirements and design documents. Please review the attached draft Performance Work Statement (PWS) detailing the scope and requirements for the User Acceptance Testing (UAT). Please respond to this RFI if your company can perform this requirement in accordance with FAR Part 52.219-14 Limitations on Subcontraction (Nov 2011) As prescribed in 19.508(e) or 19.811-3(e), insert the following clause: Limitations on Subcontracting (Nov 2011) (a) This clause does not apply to the unrestricted portion of a partial set-aside. (b) Applicability. This clause applies only to- (1) Contracts that have been set aside or reserved for small business concerns or 8(a) concerns; (2) Part or parts of a multiple-award contract that have been set aside for small business concerns or 8(a) concerns; and (3) Orders set aside for small business or 8(a) concerns under multiple-award contracts as described in 8.405-5 and 16.505(b)(2)(i)(F). (c) By submission of an offer and execution of a contract, the Offeror/Contractor agrees that in performance of the contract in the case of a contract for- (1) Services (except construction). At least 50 percent of the cost of contract performance incurred for personnel shall be expended for employees of the concern. (2) Supplies (other than procurement from a nonmanufacturer of such supplies). The concern shall perform work for at least 50 percent of the cost of manufacturing the supplies, not including the cost of materials. (3) General construction. The concern will perform at least 15 percent of the cost of the contract, not including the cost of materials, with its own employees. (4) Construction by special trade contractors. The concern will perform at least 25 percent of the cost of the contract, not including the cost of materials, with its own employees. (End of clause) This is only an overview/summary does not include all requirements to complete Performance Work Statement (PWS). Specific Response Instructions: Please submit your RFI response in accordance with the following: 1) No more than 15 pages (excluding transmittal page). Include the name, email address and phone number of the appropriate representative of your company; 2) Submit your response via email to Maurice Walker @ Maurice.Walker@va.gov. 3) Submit your response by 4 P.M. (EST) on 2/14/13; 4) Mark your response as "Proprietary Information" if the information is considered business sensitive. 5) NO MARKETING MATERIALS ARE ALLOWED AS PART OF THIS RFI. The government will not review any other information or attachments included, that are in excess of the 15 page limit. Information Requested from Industry: In response to the RFI, interested contractors shall submit the following information: 1.Company Information / Socio-Economic Status 1.Provide the company size and POC information. 2.VA has identified the appropriate North American Industry Classification System (NAICS) Code 541511 Custom Computer Programming Services, which has a size standard of $25.5 Million for this RFI. Please identify and explain any other NAICS codes your company believes would better represent the predominated work included in the attached PWS. 3.Indicate whether your company, subcontractors, teaming partners, joint ventures have a Federal Socio-Economic Status, e.g., Small Business, Service-Disabled Veteran Owned Small Business, Veteran Owned Small business, Women-Owned Small Business, Disadvantaged Small business, and Hub Zone. If Service Disabled or Veteran Owned Small business, is your company and or partners registered in VA's VetBiz repository? 2.Background/Past Experience - Provide the following information on a maximum of three similar projects dealing with independent assessments of software product implementations and user acceptance testing. All projects referenced must have been completed within the last three years for which the responder was a prime or subcontractor. 1.The name, address, and value of each project. 2.The Prime Contract Type, Firm Fixed-Price, Cost Reimbursement or Time and Material 3.The name, telephone and address of the owner of each project 4.A description of each project, including difficulties and successes 5.Your company's role and services provided for each project. 3.Capabilities/Qualifications - Overview of proposed solution(s). Include a description of the capabilities/qualification/skills your company possesses for each of the below statements: 1.Assessment of capabilities to perform requirements noted in the RFI. 2.Assessment of the types of changes required to accomplish the goals. 3.Approach to be utilized to develop necessary changes to the systems to meet the organizational goals 4.Draft schedule to complete necessary changes. 4.Teaming Arrangements - Description of Teaming Partners, Joint Ventures that your company would consider to perform work. 5.Price Information - Provide your commercial price history and rough order of magnitude for the same or similar products/solutions. 6.Other Market Information - Provide any other relative information, this information must be included within the 15 page limitation. 7.Other Federal Experience - Identify the federal contract vehicles PERFORMANCE WORK STATEMENT (PWS) DEPARTMENT OF VETERAN AFFAIRS Veterans Health Administration Chief Business Office Systems Management (VHA CSM) User Acceptance Testing Services (UAT) ? Department of Veterans Affairs Veterans Health Administration (VHA) Chief Business Office (CBO) Member Services Systems Management User Acceptance Test Services (UAT) 1.BACKGROUND The Chief Business Office (CBO) is responsible for a broad range of business activities associated with health care benefit delivery. These activities occur both at the national and local medical facility level and are governed by statute and policy. The CBO is responsible for developing the business processes supporting the statute and policy governing VHA business programs. In addition, CBO is responsible for the timely and appropriate resolution of veteran inquiries and cases. The Contractor shall provide User Acceptance Test (UAT) services and manages tasks to support the Chief Business Office Systems Management (CSM) and their Customers. The Contractor's services should provide an objective and independent assessment of the software product and related processes throughout the project lifecycle. The Contractor shall test the entire solution from the functional standpoint in order to verify that all the features documented are working as specified in the Requirements and Design documents. SCOPE OF WORK CSM team members employ specialized knowledge; skills and experience that help reduce a project's level of risk and thereby increase its likelihood of success. The suite of CSM tools improves a project's probability of success by building on what has proven to be successful. Project management processes (e.g., risk management, requirements development, project planning, configuration management, and project monitoring and control) are tailored to fit the size and scope of the project and provide proven procedures that lead to a desired result. The phases included in the CSM project management approach include initiating, planning, executing, monitoring and controlling, and closing out the project by transferring the completed product to the stakeholders and end users. From the Initiation through Execution phases processes are in place to support a project request from various stakeholders (such as the CBO Business Engineering Services Team), track status, monitor projects and tasks to further increase the likelihood of project success and provide senior managers with the visibility into the status of a project. Provide User Acceptance Test (UAT) services that include an objective and independent assessment of software product implementations and related processes throughout the project lifecycle. The Contractor will work with Subject Matter Experts and Stakeholders to develop Test Cases and Test Scenarios, define Test Bed requirements, and to execute Testing tasks. The Contractor shall provide services on the following areas: oTask 1: Task Order Management and Administration oTask 2: User Acceptance Test (UAT) Services 3.APPLICABLE DOCUMENTS Documents referenced or germane to this Performance Work Statement (PWS) are listed below. The Contractor shall be guided by the information contained in the documents in performance of this PWS. o44 U.S.C. § 3541, "Federal Information Security Management Act (FISMA) of 2002" oFIPS Pub 201, "Personal Identity Verification of Federal Employees and Contractors," March 2006 o10 U.S.C. § 2224, "Defense Information Assurance Program" oSoftware Engineering Institute, Software Acquisition Capability Maturity Modeling (SA CMM) Level 2 procedures and processes o5 U.S.C. § 552a, as amended, "The Privacy Act of 1974" o42 U.S.C. § 2000d "Title VI of the Civil Rights Act of 1964" oVA Directive 0710, "Personnel Suitability and Security Program," September 10, 2004 oVA Directive 6102, "Internet/Intranet Services," July 15, 2008 o36 C.F.R. Part 1194 "Electronic and Information Technology Accessibility Standards," July 1, 2003 oOffice of Management & Budget (OMB) Circular A-130, "Management of Federal Information Resources," November 28, 2000 oAn Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule, October 2008 oSections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended by the Workforce Investment Act of 1998 (P.L. 105-220), August 7, 1998 oHomeland Security Presidential Directive (12) (HSPD-12) oVA Directive 6500, "Information Security Program," August 4, 2006 oVA Handbook 6500, "Information Security Program," September 18, 2007 oVA Handbook 6500.6, "Contract Security," March 12, 2010 oVA Handbook 6500.1, "Electronic Media Sanitization," November 3, 2008 oVA Handbook 6500.2, "Management of Security and Privacy Incidents," June 17, 2008. oVA Handbook 6500.3, "Certification and Accreditation of VA Information Systems," November 24, 2008. oVA Handbook, 6500.5, Incorporating Security and Privacy in System Development Lifecycle. oTechnical Reference Model (TRM) (reference at http://www.ea.oit.va.gov/Technology.asp) oNational Institute Standards and Technology (NIST) Special Publications oDepartment of Veterans Affairs (VA) Directive 0710, Personnel Suitability and Security Program, September 10, 2004 ? 4.PERFORMANCE DETAILS 4.1Performance Period The period of performance for the contract shall is one (1) twelve (12) month base period with two (2) twelve (12) month optional periods. Any work at the government site shall not take place on Federal holidays or weekends (but may require off-hour work due to network loading or other disruptions that could occur) unless directed by the Contracting Officer (CO). There is ten (10) Federal holidays set by law (USC Title 5 Section 6103). Under current definitions, the four (4) are set by date: HolidayDate New Year's DayJanuary 1 Independence DayJuly 4 Veterans DayNovember 11 Christmas DayDecember 25 If any of the above falls on a Saturday, then Friday shall be observed as a holiday. Similarly, if one (1) falls on a Sunday, then Monday shall be observed as a holiday. The other six (6) are set by a day of the week and month: HolidayDay Martin Luther King's BirthdayThird Monday in January Washington's BirthdayThird Monday in February Memorial DayLast Monday in May Labor DayFirst Monday in September Columbus DaySecond Monday in October ThanksgivingFourth Thursday in November 4.2Performance Order Type, Place, and Hours of Service 4.2.1 Performance Type of Order: Firm Fixed Price (FFP). Place of Performance: The Contractor shall provide all facilities required to support staff assigned to this task order including network connectivity, office space, furniture, and personnel support. Regardless of staff location, the Contractor shall provide contract staff with end user computing equipment including common desktop computing software and hardware to perform the required services and in conformance with the VA guidelines. The Government shall provide VA specific software such as VPN and Remedy. The Contractor shall not transmit, store or otherwise maintain sensitive data or products in systems or media other than VA provided systems within the VA firewall and as permitted by VA and Federal policies. The VA may decide to provide Government Furnished Equipment (GFE) to the Contractor at the Government's discretion. For the purposes of travel cost estimation, the contract place of performance is assumed to be located in Atlanta, GA. The Government shall not be required to pay for contractor travel costs in order to provide services required in Atlanta, GA or its metropolitan area. Hours of service: The contractor shall provide service during normal business hours from 8:00am to 4:30pm Eastern Time Zone Monday through Friday unless otherwise agreed between Contractor and Program Manager. "Business Day" is defined as Monday through Friday, excluding standard Federal Holidays and any other day specifically declared to be a national holiday. 4.3Travel Travel to attend project related meetings and reviews will be required through the period of performance. Travel shall be conducted on a firm fixed price basis and requires concurrence by the VA Project Manager (VA PM) and COTR in advance. The Government estimates the total number of trips in support of this effort is 10 trips totaling 50 days of travel during the first twelve (12) month period. Anticipated travel locations and quantities are as follows: LocationTrips (Base Year)Days (Base Year)Trips (Option Year1)Days (Option Year1)Trips (Option Year2)Days (Option Year2)Trips (Total)Days (Total) Other10501050105030150 Total10501050105030150 Note: Although these are the anticipated travel locations, the decision on the destination is to be determined by the VA PM and approved by the COTR. The budgeting shall be based on anticipated number of days of travel (approximately 50 days for the first period of performance and 50 for the each of the option years). 4.4Minimum Contractor Software/Tools/Methodology Expertise The contractor shall have practical experience using best business Test Management practices, standard and agile project management, and with systems integration. This experience must be described in the proposal. 5.SPECIFIC TASKS AND DELIVERABLES The Contractor shall perform the tasks and create the deliverables described in this statement of work (SOW). The Contractor shall provide resources that have proven experience using best business Test Management practices, standard and agile project management, Test Management Tools and with systems integration. All written deliverables shall be phrased in layperson language. Statistical and other technical terminology and conclusions shall not be used without providing a glossary of terms, any applicable models, and a description of the methodology and underlying approach used. For every task, the Contractor shall identify in writing all necessary subtasks (if any) to an appropriate work package level, associated costs by task with related sub-milestone dates. The Contractor's subtask structure shall be reflected in the technical proposal. 5.1TASK 1 -Task Order Management and Administration The Contractor shall provide a detailed Task Order management plan, work plan, project plan, briefing, and kick-off meeting for the Government that presents Contractor's plan for completing the Task Order. It shall include the Contractor's approach to technical and functional activities needed for management of this SOW, including schedule of deliverables, productivity and management methods such as Quality Assurance, Configuration, Work Breakdown Structure, and Human Engineering and describe in further detail the processes to be used for each aspect of the task order as defined in the technical proposal. The project and work plans shall be kept up to date throughout the life cycle of the contract to ensure it represents all tasks and current timelines. The Contractor shall complete standard administrative tasks (e.g., background investigation forms, staff roster, mandatory training), and regular task updates including burn rates, progress, risks, issues, and opportunities. 5.1.1Deliverable 1.1: Task Order Management Plan The Contractor's Task Order Management Plan shall be delivered within ten (10) business days from date of award and shall describe the technical approach, organizational resources, and management controls to be employed to meet the cost, performance, and schedule requirements throughout task order execution. It should include a detailed project plan and a work plan in Microsoft Project or the VA approved project management software as agreed by the VA PM. The Plan shall include the base period of performance and the plans for optional years. The Contractor shall perform regular updates to the project and work plans as needed during the performance period to ensure the work plan is kept up to date. Updates are required whenever additional activities are deemed necessary, when activities are identified as no longer needed, and/or when the planned completion date of any activity is changed or at a minimum on a monthly basis. These plans will be approved by the CSM Director or Deputy Director. 5.1.2Deliverable 1.2: Kick-off Meeting The Contractor shall coordinate with the COTR a kick-off meeting to review the Task Order Management Plan within fifteen (15) business days from date of award or as agreed upon between VA PM and Contractor. The meeting shall include a project advisory group comprised of key stakeholders and subject matter experts (SMEs) to be identified by the VA PM in order to ensure common understanding of requirements and to set expectations. At the kick-off meeting, the Contractor shall present the details of their intended approach, work plan, project plan, and project schedule, including deliverable dates, for review and approval by the advisory group. Work will not commence until the CSM Director or Deputy Director approves the approach and/or methodology, work plan, and schedule on behalf of the project advisory group. 5.1.3Deliverable 1.3: Key Personnel Roster Contractor shall confirm and provide a roster of key personnel to the Contracting Officer within five (5) business days after award. It shall include a full and complete list of names, Social Security Numbers, and home addresses of personnel for the Background Investigation requirement. 5.1.4Deliverable 1.4: Mandatory Training and Administrative Requirements Mandatory training (e.g., Privacy, Security) required as of the date of award of the order shall be completed and documented as appropriate within twenty (20) business days from date of award. If performance on this order crosses the anniversary date for recurring annual training requirements, such training must be completed within twenty (20) business days of the anniversary date. Training completed by individual staff within the same fiscal year under separate orders as otherwise required for this deliverable will be accepted so long as appropriate documentation is submitted. The Contractor shall submit electronically to the CBO COTR within twenty-five (25) business days of award - or in the case of staff added after performance begins, twenty-five (25) business days of their on-board date - a complete status of training for all staff. Contractor shall submit the signed Business Associate Agreement (BAA) to the Contracting Officer within five (5) business days from date of award. The Contracting Officer will countersign and provide Contractor with a completed copy. 5.1.5Deliverable 1.5: Task Status Reporting The Contractor shall deliver weekly activity and cost management reports. The Contractor may propose formats for the reports, and receive agreement from the Project Manager(s). First report is due within ten (10) business days from contract award, and every Thursday thereafter for the term of the contract. 5.2Task 2 -User Acceptance Testing Services The Contractor shall provide professional services for User Acceptance Testing (UAT) support to provide an objective and independent assessment of software product implementations (and related processes) throughout the project lifecycle. In addition, to facilitate early detection and correction of errors, enhances management insight into risks and mitigates the risks that a project will not meet its goals in terms of project performance, scope, schedule, and budget. The Contractor will work with Subject Matter Experts and Stakeholders to develop Test Cases and Test Scenarios, define Test Bed requirements, and to execute Testing tasks Currently, CSM has a portfolio of programs that are in need of UAT support services. These programs include, but are not limited to, the following lines of business: oHealth Eligibility Center (HEC): Registration, Enrollment, and Eligibility; Member Benefits Handbook; Member Benefits Card; Veterans Identification Card; Income Verification; Informatics; and Health Benefit Plans oService Center Operations (Call Centers): Health Enrollment Center (HEC), Health Revenue Center (HRC), and Consolidated Patient Account Centers (CPACs) oVA Point of Service/Kiosks (VPS) oVeterans Transportation Program (VTP) oAccess to Care oLegislative, Congressional, and President Initiatives Business requirements are developed into systems/applications by the Office of Information and Technology (OI&T) and delivered to the business for UAT. UAT provides the customer with an opportunity to test the software solution, simulate a production environment and allow the validation of the requirements outlined in the Vision and Scope Document (V/S), Business Requirements Document (BRD), and Requirements Software Documentation (RSD). UAT is a method to improve the quality and effectiveness of the product by determining if the system is acceptable and capable of delivering accurate, timely information and satisfactory service to VHA users. As part of User Acceptance Plan, the UAT team will validate end-to-end business functionality to assess whether the application performs to a customer defined acceptable level of application functionality and stability. The Contractor shall be responsible for coordinating the access and availability of databases and applications required to conduct the 'end-to-end' testing for the UAT being conducted. The Contractor shall anticipate working on concurrent UAT efforts for the following projects (names might change). Note, projects might change period of performance (due to OI&T delivery schedules): IndexPeriod ProjectEstimated #Test CasesEstimated #DaysAnticipated Integration Partners UAT1Base YearESR 3.12450-50010Identity Management Services, Content Management System, Workflow Engine, VistA REE UAT2Base YearESR 3.13450-50010Identity Management Services, Workflow Engine, VistA REE UAT3Base YearIVM Enhancements (Phase 1)150-2505VistA REE, Correspondence UAT4Base YearIVM Enhancements (Phase 2)150-2505VistA REE, Correspondence UAT5Base YearVeterans Online Application (VOA Phase 1) 450-50010Identity Management Services, ESR and VistA REE UAT6Base YearVOA (Phase 2) 450-50010Identity Management Services, ESR and VistA REE UAT7Base YearVPS/Kiosks (Phase 2)450-50010Identity Management, Kiosks, Services Bus UAT8Base YearVTP (Phase 1)150-2505VistA, Beneficiary Travel, Ride Sharing Software, and VIC UAT9Base YearMember Support Services (Pilot)450-50010Services Bus and Data Services UAT10Base YearMember Support Services (Phase 1)450-50010Services Bus and Data Services UAT11Base YearHealth Benefits Plans (Phase 1)1,000-2,50015ESR, VistA REE, Billing, Pharmacy, Services Bus UAT12Base YearHealth Benefits Plans (Phase 2)1,000-2,50015ESR, VistA REE, Billing, Pharmacy, Services Bus UAT13Base YearVIC (Pilot)450-50010Identity and Access Management, VIC Program, Computerized Patient Record System (CPRS), ESR UAT14Base YearVIC (Phase 1)450-50010Identity and Access Management, VIC Program. Kiosks UAT15Base YearCCPC (Base year only)1,000-2,50015ESR, VistA REE, Billing, Pharmacy, Services Bus UAT16Option Year 1ESR 3.13 (Proof)1,000-2,50015Identity Management Services, VistA REE, Integrated Electronic Health Record, Services Bus UAT17Option Year 1ESR 3.13 (Deploy)1,000-2,50015Identity Management Services, VistA REE, Integrated Electronic Health Record, Services Bus UAT18Option Year 1ESR 3.14 (Proof)450-50010Identity Management Services, VistA REE, Integrated Electronic Health Record, Services Bus UAT19Option Year 1ESR 3.14 (Deploy)450-50010Identity Management Services, VistA REE, Integrated Electronic Health Record, Services Bus UAT20Option Year 1IVM Enhancements (Phase 3)150-2505VistA REE, Correspondence UAT21Option Year 1IVM Enhancements (Phase 4)150-2505VistA REE, Correspondence UAT22Option Year 1VPS/Kiosks Phase 3450-50010Identity Management, Kiosks, Services Bus UAT23Option Year 1VTP Phase 2450-50010VistA, Beneficiary Travel, Ride Sharing Software, and VIC UAT24Option Year 1Member Support Services (Phase 2)450-50010Services Bus and VIERS UAT25Option Year 1Member Support Services (Phase 2 and Phase 3)450-50010Services Bus and VIERS UAT26Option Year 1Health Benefit Plans (Phase 3)450-50010Services Bus and VIERS UAT27Option Year 1Health Benefits Plans (Phase 4)450-50010ESR, VistA REE, Billing, Pharmacy, Services Bus UAT28Option Year 1VIC (Phase 2)450-50010Identity and Access Management, VIC Program UAT29Option Year 1VIC (Phase 3)450-50010Identity and Access Management, VIC Program UAT30Option Year 2ESR 3.15450-50010ESR, VistA REE UAT31Option Year 2ESR 3.16450-50010ESR, VistA REE UAT32Option Year 2IVM Enhancements (Phase 5)150-2505ESR, IVM UAT33Option Year 2IVM Enhancements (Phase 6)150-2505VistA REE, IRS UAT34Option Year 2VA Self Service 1,000-2,50010Integration with MyHealtheVet, ESR, eBenefits, VOA, HEC portal UAT35Option Year 2Enterprise Service Bus1,000-1,25010Integration with Member Support Services, VBMS, and other Service Bus UAT36Option Year 2User Experience Applications1,000-1,25010Mobil Applications, Service Bus, Portals UAT37Option Year 2Scheduling Application1,000-2,50015ESR, VistA REE, Billing, Pharmacy, Scheduling, Identity Management The Contractor shall be responsible developing the master test plan (to include usability and integration testing), creating a traceability matrix between business requirements and test cases/scripts, writing user acceptance test cases/scripts, coordinating UATs, assisting the users and subject matter experts (SMEs) in executing test scenarios, and documenting findings. The users and SMEs which will exercise the following aspects of the application: Level 1: The integration of components of the required systems; inclusive of testing for defects, coding errors, 508 compliance (as appropriate), and usability. Level 2: To assure the complete system has been delivered. In this level of testing, the business owner is looking to guarantee components/interfaces have not been left out and/or the system conforms to the specified use case requirements. Level 3: To assure the system meets the critical business requirements, such as end-to-end business functionality, volume, performance, and stress testing. Users of the system with the support of the contractor will perform tests, which analysts and developers have derived from the requirements gathered from the business as well as test scenarios written by users. The Contractor shall lead the UAT team in the evaluation of the application by conducting user functionality tests, which consists of creating and executing test cases against the application. The test results will be used to determine whether the following items are included in the system: 1.0 oRequired attributes/functionality are present oTest cases in the required system are implemented oMenus, screens, reports, system interfaces are present as specified and behave as documented and expected oInterfaces to external systems work effectively oSpecified processing algorithms are implemented correctly oEnd to end business processes work appropriately oRequirements and rules are appropriate and complete thereby meeting the needs of the business oRoles-based usage works accordingly The majority of the UAT testing is anticipated to take place in Atlanta, GA. 5.2.1Deliverable 2.1: Develop UAT Management Plan The Contractor shall develop a UAT Management Plan describing the activities, personnel, schedule, standards, and methodology for conducting the UAT for each one of the project engagements (UAT table) listed above. The UAT should be a repeatable process where lessons learned from previous efforts are incorporated to continuously improve the UAT process. 5.2.2Deliverable 2.2: Provide UAT Support The Contractor shall support the customer in performing User Acceptance Testing efforts as described in this Task and for the projects listed in the UAT table above. The activities include UAT planning, designing user acceptance test cases, assist in selecting team to execute UAT test cases, oversee the execution of test cases, documenting defects found during UAT, and providing a summary report upon completion of each UAT. The User Acceptance Test Plan shall outline the UAT Strategy to include the key focus areas, entry and exit criteria. At a minimum, the plan must include: oTest Approach and Methodology oAssumptions and Constraints oSetup of Test Environment (including test bed and user setup) oApproach to Develop Test Cases oTest Period oProcess to Document Test Results oTraceability Matrix (traced back to business requirements) The User Acceptance Test Cases shall be developed in simple language and outline the precise steps to help the Test Execution Team test the application thoroughly. They shall be developed to ensure that the UAT provides sufficient coverage of all the scenarios and will be mapped to the Requirements Traceability Matrix. The User Acceptance Results Document shall be documented in a mutually agreed upon format. It shall document any issues found, such as bugs, crashes, or missing functionality.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/VA/VAHAC741/VAHAC741/VA74113I0101/listing.html)
- Document(s)
- Attachment
- File Name: VA741-13-I-0101 VA741-13-I-0101_1.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=611459&FileName=VA741-13-I-0101-000.docx)
- Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=611459&FileName=VA741-13-I-0101-000.docx
- Note: If links are broken, refer to Point of Contact above or contact the FBO Help Desk at 877-472-3779.
- File Name: VA741-13-I-0101 VA741-13-I-0101_1.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=611459&FileName=VA741-13-I-0101-000.docx)
- Record
- SN02981544-W 20130209/130207234341-3e1e00695b29c419a71b12441a448fce (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |