iBeta offers independent testing for your government projects. Independent testing goes beyond traditional IV & V by returning usable information to the client and the system developer that goes beyond pass/fail.
With this approach, iBeta integrates testing into the entire system development process — from the initial gathering of requirements to the delivery of the completed product. Applying quality assurance principles in the earliest phases of the project helps ensure that potential issues can be identified in the early stages when they are the most cost effective to address.
Applying them in the last phases of the project ensures that the delivered system continues to perform as contracted. iBeta’s experience can also make a valuable contribution to the initial generation of a Request for Proposal; load testing the system against anticipated and unexpected database sizes; transaction volumes; network configurations, verification of real-world performance service level agreements, and more.
iBeta contracts directly with the agency sponsoring the project. The activities of such agencies are not bound in any way to the system developer. The independent tester has a separate schedule of milestones and incentives. Our interest is in the quality of the project, and we answer to no one but your agency.
- Application security
- Requirement analysis
- Validation of technical hardware
- System test validation
- Performance testing
- User acceptance testing
- Training performance
- Deployment tracking
In the event that IV & V testing or analysis provides different results from those of the development Vendor, the iBeta IV & V Manager will coordinate with the Project Manager to provide an action plan to evaluate the differences and resolve any outstanding issues.
The requirements analysis services that iBeta provides ensures that the documented requirements are:
- Cohesive – the sum of all requirements defines the total system and that such requirements do not contain contradictions, and apply specifically to the required implementation.
- Complete – the sum of all requirements will take into account any possible conflicting requirements of the various stakeholders.
- Precise – all requirements are defined to a sufficient level of detail according to system design.
- Testable – each requirement provides expected test results that will be used to define the pass/fail criteria for testing.
- Measurable – the performance requirements must be distinctly measurable so that the pass/fail criterion is contained within the actual requirement.
- Relevant – all requirements must pertain to the business’ needs.
- Unambiguous – all requirements are stated concisely with terms such as “easy” and “low” either defined quantitatively or avoided if interpretation of the requirement could be different between stakeholders.