COMP2002 LectureCopyright DMU 2001 COMP2002 TickIT

COMP2002 LectureCopyright DMU 2001 TickIT R developed by the DTI R to raise awareness of what quality is R to raise awareness of how it may be managed R to provide a recognised QMS certification scheme

COMP2002 LectureCopyright DMU 2001 TickIT background RISO9001/ EN29001/ BS5750 Part 1 (1987) published 1987 RDTI established relevance of standards to the production of software RTwo complementary studies were commissioned: –Software Quality Standards: the costs and benefits (Price Waterhouse) –Quality Management Standards for Software (Logica)

COMP2002 LectureCopyright DMU 2001 Research conclusions RAll QMS standards were generically similar RThe best harmonisation route was ISO9001 REstablish an accreditation body(s) for the software sector Rguidance material to assist in relating ISO9001 to specific software QMS procedures and to facilitate auditing RImprove professional practice amongst software QMS auditors

COMP2002 LectureCopyright DMU 2001 Result - TickIT Scheme TickIT scheme documents: RAn introduction to certification, quality management issues and a brief overview of ISO9001 Rauthoritative interpretation of what the requirements set out in ISO9001 mean in the production of information systems and products which involve software development Rexplanation of purchasers expectations of a suppliers QMS, assessed and certified to ISO9001 Rguidance to suppliers and in-house developers implementing quality management systems for compliance to ISO9001 Rauditor’s guide

COMP2002 LectureCopyright DMU 2001 Total Quality Management Management commitment to improve Measurement for improvement Motivation to improve The Quality Management System The 3 driving components for continuos quality improvement

COMP2002 LectureCopyright DMU 2001 Assessment RFirst party - organisation assesses itself by internal QMS reviews, audit and client satisfaction surveys RSecond party - assessed by a purchaser against product or quality system standards selected by the purchaser organisation, and tend to be relatively narrow in scope RThird party - assessed by an external impartial body to national/international standards. Successful assessment signified by award of certification

COMP2002 LectureCopyright DMU 2001 Accreditation Criteria EN Certification bodies EN29000 Developers QMS Consumers To ensure 3rd party certificates are acceptable, the issuing bodies must be accredited by a recognised national accreditation authority CONFIDENCE Market eye

COMP2002 LectureCopyright DMU 2001 TickIT accreditation TickIT uniform accreditation arrangements: Ruse of the TickIT name and logo Rthe certification cycle Rmonitoring the applicants management review activities Rmutual recognition of accredited TickIT certification Ruse of TickIT guidance documentation Ruse of TickIT auditors

COMP2002 LectureCopyright DMU 2001 Quality Control Software supply is a design & development activity, rather than a production activity. RISKS Rrequirements specification Runderstanding customer needs Rassimilating large quantities of information Rintangible nature of software Raccommodating change Rpressure to deliver Rlack of exhaustive testing

COMP2002 LectureCopyright DMU 2001 Containing Risks R Methods & controls in place from the start R Correction = too late, too costly, too risky R Adopt a relevant lifecycle

COMP2002 LectureCopyright DMU 2001 Intro to ISO /TickIT R Functional specification R Project plan R Software design R Software coding R Software testing & validation R Replication, delivery & installation R Maintenance R Document control R Configuration management

COMP2002 LectureCopyright DMU 2001 References Welcome to TickIT, Jan 2001