PV213 EIS in Practice: 04 – Quality assurance 1
PV213 Enterprise Information Systems in Practice
04 – Quality assurance
PV213 EIS in Practice: 04 – Quality assurance 2
PV213 EIS in Practice: 04 – Quality assurance 3
PV213 EIS in Practice: 04 – Quality assurance 4
Content of this presentation
Role of quality management and quality assuranceISO, CMMI, EFQMQA planDocument managementReviewsToolsLeanNext lesson
PV213 EIS in Practice: 04 – Quality assurance 5
Quality
What is quality?
PV213 EIS in Practice: 04 – Quality assurance 6
Quality – 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 7
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 8
Kano model
Quality attributes
BasicExpectedExcitingIndifferentReverse
Project management areas
Integration ManagementScope ManagementTime ManagementCost Management and ControllingQuality ManagementHuman Resource ManagementCommunications ManagementRisk and Opportunity ManagementProcurement Management
PV213 EIS in Practice: 04– Project management 9
PV213 EIS in Practice: 04 – Quality assurance 10
Quality management
ISO 9000 definitionCoordinated activities to direct and control an organization with regarding to quality
ActivitiesPlanningControlImprovementAssurance
PV213 EIS in Practice: 04 – Quality assurance 11
Quality management levels
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 12
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 systemsOHSAS 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 13
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 14
PV213 EIS in Practice: 04 – Quality assurance 15
EFQM model
PeoplePeople
Policy andStrategy
Policy andStrategy
Partnershipand Resources
Partnershipand Resources
Leader-ship
Leader-ship ProcessesProcesses
ResultsResults
PeopleResults
PeopleResults
CustomerResults
CustomerResults
SocietyResults
SocietyResults
KeyPerformance
Results
KeyPerformance
Results
90
80
90
90
200
60100 140 150
Innovation and LearningInnovation and Learning
EnablersEnablers
PV213 EIS in Practice: 04 – Quality assurance 16
Balanced scorecards
Balanced scorecards perspectives:The customer perspective (Customers / Market)To achieve our vision, how should we appear to our customers? The financial perspective (Finances)To succeed financially, how should we appear to our shareholders? The learning and growth perspective (Human resources / Innovation)To achieve our vision, how will we sustain our ability to change and improve? The internal process perspective (Internal processes)To satisfy our shareholders and customers, what business processes must we excel at?
PV213 EIS in Practice: 04 – Quality assurance 17
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 18
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 19
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 20
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 21
What went wrong?
This is a story about four people named 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 Somebody could do it but Nobody realized that Everybody wouldn't do it.In the end Everybody blamed Somebody when Nobody did what Anybody could have done.
PV213 EIS in Practice: 04 – Quality assurance 22
Checks
Nobody/Nothing is perfect Errors, Faults, DeficienciesChecks to identify them as early and as efficiently as possible
Different types of checksAutomatic code analysisTestChecking compliance with processesAudits (ISO)Assessments (CMM/CMMI, EFQM model)Reviews
Costs of fault identification
PV213 EIS in Practice: 04 – Quality assurance 23
Phase in which a fault is detectedRela
tive c
ost
s fo
r dete
ctin
g a
nd c
leari
ng
a f
ault
Requirements Design Code Developmenttest
Acceptancetest
Operation
1000
500
200
100
50
20
10
5
2
1
PV213 EIS in Practice: 04 – Quality assurance 24
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 25
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 26
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 27
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 28
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)
Code review - example
class Hello { public String text; public Hello() { text = null; }
// method to set text public void set(String t) { text = t; }
public String get() { return text; }}
PV213 EIS in Practice: 04 – Quality assurance 29
PV213 EIS in Practice: 04 – Quality assurance 30
Microsoft
MS Project + Enterprise Project ManagementMS Team Foundation Server + SharePoint
Reporting and trackingSource control
MS ExcelEasy to enhanceStandard SW setLimited functionality
PV213 EIS in Practice: 04 – Quality assurance 31
Trac
http://trac.edgewall.org/ OSSWikiTickets, milestonesSCM interface
PV213 EIS in Practice: 04 – Quality assurance 32
Redmine
http://www.redmine.org/OSSWikiTicketsSCM interface
Atos standard tools
IBM Rational Team Concert
IBM Rational ClearQuestIBM Rational ClearCaseHP Application Life Management
PV213 EIS in Practice: 04 – Quality assurance 33
Development toolsexample
PV213 EIS in Practice: 04 – Quality assurance 34
PV213 EIS in Practice: 04 – Quality assurance 35
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 36
Company tools unification
Costs vs. benefitsBuy vs. buildTraining costs
Lean
Value addedWaste
ReworkOver-processingOverproductionMotionInventoryWaitingTransportIntellect
Necessary but Non-Value-Added
PV213 EIS in Practice: 04 – Quality assurance 37
NNVA
Value Added Activity
Waste
Elements of work
ELIMINATE WASTE
Never stop trying to eliminate waste MINIMISE Necessary
Non Value Add (NNVA)Necessary for the value added to happen, under
the current circumstances
MAXIMISE Value Add (VA) activities;
Changes form, fit or function towards
customer requirements
Lean in SW development
Eliminate wasteAmplify learningDecide as late as possibleDeliver as fast as possibleEmpower the teamBuild integrity inSee the whole(source: wikipedia.org)
PV213 EIS in Practice: 04 – Quality assurance 38
PV213 EIS in Practice: 04 – Quality assurance 39
Next lesson
Development processDevelopment process in generalProcess tailoringWaterfallIterative and incrementalAgile developmentScrumExtreme Programming
PV213 EIS in Practice: 04 – Quality assurance 40
Děkuji za pozornost.