Feature completeness testing
Compare documented requirements and product claims with routes, interfaces, APIs, database operations and automated test evidence.
What BSA is designed to examine
- Features claimed in requirements, documentation, user interfaces and marketing material.
- The code, API, database and interface that should implement each claimed feature.
- Present, partial, missing, broken and untested functionality, reported as separate outcomes.
- Interfaces without a backend, APIs without an interface, and deprecated features that are still exposed.
How results are meant to be reported
- Each feature is intended to appear in a verification matrix showing implementation status and test status side by side.
- Missing test coverage is reported as unverified. It is never reported as a broken feature.
- A feature is marked verified only when stored test evidence supports it.
A product declaring that it has a feature is a declaration, not evidence. BSA treats it that way.
Status
BSA is in development. This site describes what the platform is designed to do. It does not report completed audits, customers, certifications or integrations.