Downloaded 15 times
More Related Content
Similar to TestIT Software Assurance
TestIT Software Assurance
- 1. safeguarding your ITinvestment Software Assurance
- 2. agenda Why dosoftware projects fail? Why doesn’t testing work? Why is Software Assurance the answer? Case Study: Maritime & Coastguard Agency Software Assurance delivering on time , on budget and on spec
- 3. why do software projects go wrong?
- 4. failure ineffective testingsystem incompatibility inadequate communication ambiguous requirements weak change discipline ineffectual gateway reviews why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY
- 5. why doesn’t testing work?
- 6. conflicting priorities cultureimpact on vendor profitability Vendor Testing - what are the problems? why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY
- 7. prescriptive approach totesting ‘ culture of complaint’ too little, too late Internal Testing - what are the problems? why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY
- 8. Testing Business NeedRequirements Technical Specification Solution done correctly, testing only proves that the solution meets the technical specification why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY
- 9. why is independentSoftware Assurance the answer?
- 10. Business Need RequirementsTechnical Specification Solution why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY software assurance proves that the solution meets the business need
- 11. Software Assurance thecomprehensive solution why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY Requirements Verification & Validation Engineering Workspace
- 12. Requirements that capturethe business need Verification & Validation why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY Requirements Engineering Workspace
- 13. Are we buildingthe right product? Are we building the product right? Requirements why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY Verification & Validation Engineering Workspace
- 14. Operating to muchhigher standards Requirements Verification & Validation why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY Engineering Workspace
- 15. Changes comprehensively trackedRequirements Verification & Validation why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY Engineering Workspace
- 16. Controlled and visibleto all Requirements Verification & Validation why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY Engineering Workspace
- 17. Engineering Workspace - the ‘single source of truth’ Requirements Verification & Validation why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY Engineering Workspace
- 18. Independence is criticalRequirements Verification & Validation Engineering Workspace why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY
- 19. deploy with confidencereduced risk cost savings entire project team engaged reputations saved! the benefits of software assurance why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY
- 20. Software Assurance theproven model why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY Requirements Verification & Validation Engineering Workspace
- 21. independent Software Assuranceeach critical stage validated & verified integrated management of changes proactive search for defects effective project-wide communication governed by a rigorous engineering discipline ‘ assures’ the quality of every element of your IT development and manages the inherent risks why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY
- 22. CASE STUDY theMaritime & Coastguard Agency
- 23. adding value atthe MCA our remit what have we delivered? why has it been so successful? what are the financial benefits? case study why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY
- 24. our work withthe MCA CERS/SVD Consolidated European Reporting System/Single Vessel Database PROJECT: to provide independent Software Assurance of the system development, to ensure it was delivered fit for purpose REMIT: why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY
- 25. verification & validationof the system requirements and of every stage of the development lifecycle a robust process to manage change an effective Quality Management System seamless, real-time communications a formal acceptance mechanism commercial independence from the vendor what have we delivered? why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY
- 26. what have beenthe financial benefits? development costs reduced overheads (meetings, travel, etc) reduced post-deployment costs reduced remedial work covered by vendor why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY
- 27. confidence MCA nowhas the tools, processes and discipline to tightly control their project and deploy with confidence vendor management MCA has what they need to manage their vendor effectively ‘ breaking the cycle of failure’ why has it been so successful? why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY
- 28.
Editor's Notes
- #7 conflicting priorities emphasis is on getting the application approved, as quickly as possible they need it to work, so tests will be designed accordingly culture is to be ‘positive’ – there’s pressure on the vendor’s testers to keep quiet about concerns no proactive focus on finding defects testing is seen as a ‘lesser task’ impact on vendor profitability vendor’s over-riding priority is to be profitable testing is a direct cost, so the vendor will often do the minimum communication is often very poor no cross-functional, cohesive system inadequate management reporting
- #8 prescriptive approach to testing xx culture of complaint a ‘culture of complaint’ can very quickly build up and have a detrimental effect on relations with your vendor too little, too late xxx
- #9 Why doesn’t testing work? it’s not integrated at all key stages of the programme it’s left to the end of the project it’s usually done by the vendor!
- #11 Why doesn’t testing work? it’s not integrated at all key stages of the programme it’s left to the end of the project it’s usually done by the vendor!