Attachment J2 - QASP.xlsx
XLSX spreadsheet 9 KB Posted
- Attached to
- BARD Mobile Development Services IDIQ
- Solicitation number
- 030ADV24R0004
- Issued by
-
Library of Congress
About this file
This document outlines a Quality Assessment Surveillance Plan (QASP) for mobile development services provided under solicitation number 030ADV24R0004 from the Library of Congress. The QASP establishes performance standards and acceptance levels for key deliverables including code quality, accessibility, security, and user research. Code must have 90% test coverage and comply with linting and styling guidelines. Web content must meet WCAG 2.1 AA standards and pass automated accessibility tests. Applications are required to meet OWASP Application Security Verification Standard Level 2 with no medium or high vulnerabilities. User research artifacts must be provided at the end of each sprint in accordance with the vendor's research plan. Performance will be evaluated using a combination of manual reviews, automated testing, and documentation.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment J5-TO 1 iOS SOW rev.docx | DOCX document | |
| Attachment J6-TO 2 Android SOW rev.docx | DOCX document | |
| Attachment J4 - Question and Answers.pdf | ||
| Amendment 0001_030ADV24R0004 0001.pdf | ||
| Attachment J3 - Pricing Schedule 12.18.2023.xlsx | XLSX spreadsheet | |
| Attachment J1 - NLS Agile Methodology Guide.docx | DOCX document | |
| Attachment J5 - TO 1 iOS SOW.docx | DOCX document | |
| Attachment J6 - TO 2 Android SOW.docx | DOCX document | |
| Attachment J4 - Questions_Template.xlsx | XLSX spreadsheet | |
| Attachment J7 - TO 3 FireiOS SOW.docx | DOCX document | |
| 030ADV24R0004.pdf |
Show all 11
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1 Quality Assessment Surveillance Plan (QASP)
| Deliverable | Performance Standard(s) | Acceptable Quality Level | Method of Assessment |
| Tested Code | Code delivered under the order must have substantial test code coverage and a clean code baseVersion-controlled, public repository of code comprising the product, which will remain in the government domain | Minimum of 90% test coverage of all code | Combination of manual review and automated testing |
| Properly Styled Code | GSA 18F Front-End Guide | 0 linting errors and 0 warnings | Combination of manual review and automated testing |
| Accessibility | Web Content Accessibility Guidelines 2.1 AA standards | 0 errors reported using an automated scanner, and 0 errors reported in manual testing | Pa11y |
| Deployed | Code must successfully build and deploy into staging environment | Successful build with a single command | Combination of manual review and automated testing |
| Documented | All dependencies are listed and the licenses are documented. Major functionality in the software/source code is documented. Individual methods are documented inline using comments that permit the use of documentation-generation tools such as JSDoc. A system diagram is provided | Combination of manual review and automated testing, if available | Manual review |
| Security | OWASP Application Security Verification Standard 4.0, Level 2 | Code submitted must be free of medium- and high-level static and dynamic security vulnerabilities | Clean tests from a static testing SaaS (such as npm audit) and from OWASP ZAP, along with documentation explaining any false positives |
| User research | Usability testing and other user research methods must be conducted at regular intervals throughout the development process (not just at the beginning or end) | Artifacts from usability testing and/or other research methods with end users are available at the end of every applicable sprint, in accordance with the vendor’s research plan | Manual review |
https://frontend.18f.gov/https://github.com/pa11y/pa11yhttp://usejsdoc.org/https://www.owasp.org/images/d/d4/OWASP_Application_Security_Verification_Standard_4.0-en.pdfhttps://docs.npmjs.com/cli/audit
File details come from the government source that posted it. Updated .