2. agenda Why do software 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
4. failure ineffective testing system 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
8. Testing Business Need Requirements 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
10. Business Need Requirements Technical 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 the comprehensive 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 capture the 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 building the 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 much higher 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 tracked Requirements 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 visible to 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 critical Requirements Verification & Validation Engineering Workspace why do software projects go wrong? why doesn’t testing work? why is Software Assurance the answer? CASE STUDY
19.
20. Software Assurance the proven 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 Assurance each 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
24. our work with the 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
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
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
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!
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!
