Upload
darrell-morgan
View
228
Download
5
Tags:
Embed Size (px)
Citation preview
PV213 EIS in Practice: 04 – Quality assurance 1
PV213 Enterprise Information Systems in Practice
04 – Quality assurance
PV213 EIS in Practice: 04 – Quality assurance 4
Content of this presentation
Role of quality management and quality assuranceQA planDocument management + toolsReviewsISOCMMINext lesson
PV213 EIS in Practice: 04 – Quality assurance 6
Quality – ISO 9000
Degree to which a set of inherent characteristics fulfils requirements
Characteristic – distinguishing featureRequirement – need or expectation
statedgenerally impliedobligatory
PV213 EIS in Practice: 04 – Quality assurance 7
Quality – other definitions
Reducing the variation around the targetQuality is meeting customer expectations.Quality is conformance to specified requirement & is never an accident
PV213 EIS in Practice: 04 – Quality assurance 8
Kano model
Quality attributes
BasicExpectedExcitingIndifferentReverse
PV213 EIS in Practice: 04 – Quality assurance 9
Quality management
ISO 9000 definitionCoordinated activities to direct and control an organization with regarding to quality
ActivitiesPlanningControlImprovementAssurance
PV213 EIS in Practice: 04 – Quality assurance 10
Quality assurance
ISO 9000 definitionA part of quality management focused on providing confidence that quality requirements will be fulfilled
Different understanding in different companies
PV213 EIS in Practice: 04 – Quality assurance 11
Quality assurance manager in project
Incorporates quality aspects into a project with respect to
Strategic targets and goals of quality organizationBasic processesCustomer interestsThird parties
Four eye principle
PV213 EIS in Practice: 04 – Quality assurance 12
Quality assurance plan
Central planning instrument for all quality activities in projectContent
QA requirements, environmental requirementsDevelopment method and tailoringQA measures, environmental measuresQuality reporting procedure and quality recordsCorrective and preventive measures
PV213 EIS in Practice: 04 – Quality assurance 13
Document management
Update, release and distribution of documentsEnsures that most recently released version of the document is usedStatus (validity) of a particular document is identifiableAudit trail of a document must be traceable
Who created or changed documentWhat was the last changeWho made a review and where are the resultsWho approved itWhen these actions took place
Document management systemsLivelinkMicrosoft SharePoint
PV213 EIS in Practice: 04 – Quality assurance 14
Checks
This is a story about four people: Everybody, Somebody, Anybody, and Nobody.There was an important job to be done and Everybody was sure Somebody would do it.Anybody could have done it, but Nobody did it.Somebody got angry about that because it was Everybody's job.Everybody thought Anybody could do it, but Nobody realized that Everybody wouldn't do it.It ended up that Everybody blamed Somebody when actually Nobody asked Anybody.
PV213 EIS in Practice: 04 – Quality assurance 15
Checks
Nobody/Nothing is perfectErrorsFaultsDeficiencies
Different types of checksAutomatic code analysisTestChecking compliance with processesAudits (ISO)Assessments (CMM/CMMI, EFQM model)Reviews
PV213 EIS in Practice: 04 – Quality assurance 16
Reviews
Formalized, systematic and critical documented check of development results at the end of defined work stages with purpose of finding errorsMost efficient method to reduce “error costs”
Why?
Objects under reviewProject documentationProduct documentationSource codeCompany documentation
PV213 EIS in Practice: 04 – Quality assurance 17
Review phases
PlanningAt project startWhat, who, how, when
InvitationUsually initiated by author
PreparationParticipants according to their role
ExecutionDo not blame author, criticize object
ConclusionAnalysis, correction, verification of found errorsRelease of an object
PV213 EIS in Practice: 04 – Quality assurance 18
Comment review technique
Review object is distributed to reviewers (usually author)Reviewers work through the code segments on their ownReviewers pass their findings to the organizerAuthor evaluates the comments and incorporates changes
RolesAuthorReviewers
PV213 EIS in Practice: 04 – Quality assurance 19
Session review technique
Review object is distributed to reviewersComments are worked through and assessed in one sessionAuthor corrects errors and faults identified as agreed
RolesFacilitatorAuthorMinutes keeperReviewers
PV213 EIS in Practice: 04 – Quality assurance 20
Intensive inspection
Session technique based on Michael Fagan inspectionUp to 6 reviewersMaximum 2 hours per one sessionAdditional step
Introductory sessionRoles
AuthorFacilitator, minutes keeperReaderInspectors with different roles (e.g. designer, architect, user)
PV213 EIS in Practice: 04 – Quality assurance 21
ISO
International Organization for StandardizationISO 9001:2008 Quality management systems
Regular internal ISO9001 process audits for the purpose of improvement
ISO 14001:2004 Environmental management systemsISO 18001:2007 Occupational Health and Safety Assessment SeriesISO 27001:2005 Information technology – Security techniques – Information security management systemsISO 20000-1:2005 Information technology – Service managementISO/IEC 15504 Information technology — Process assessment (Software Process Improvement and Capability Determination – SPICE)
PV213 EIS in Practice: 04 – Quality assurance 22
CMMI
Capability Maturity Model IntegrationBased on CMM (Capability Maturity Model)Appraisal – SCAMPI (Standard CMMI Appraisal Method for Process Improvement)Published appraisal results
http://sas.sei.cmu.edu/pars/
PV213 EIS in Practice: 04 – Quality assurance 24
EFQM, BSC, CMMI and metrics
Process/project metrics projects
processes
business
continuou
s co
ntr
ol
checks at d
efined
intervals
Quality metrics
BalancedScorecard
EFQMassessments
CMMIassessments
ISO9001 audit
Project/risk audit
PV213 EIS in Practice: 04 – Quality assurance 25
Next lesson
Development processDevelopment process in generalProcess tailoringWaterfallIterative and incrementalAgile developmentScrumExtreme Programming