Show Menu

Quality in IT Projects Cheat Sheet by

Quality in IT Projects

Key quality concern for IT projects

Providing customers with systems they need
Meet requir­ements at affordable price
Requires a commitment from all parties
Costs of remedying lapses in quality great.

Quality charac­ter­istics

ISO 9126-1­:2001, seeks to define a set of standard charac­ter­istics by which software quality can be measured
Functi­ona­lity: meet user requir­ements
Reliab­ility: Consistent
Usability: Intuitive, minimum training
Effici­ency: good with resources
Mainta­ina­bility: easy to modify
Portab­ility: between platforms

Quality plan

Specifies standards that apply to the project
Maybe existing, new, industry, modified versions of existing, developed internally
Specifies how, when and by whom the quality control activities should be undertaken
Specifies quality assurance processes
May also include config­uration management and change control procedures

Quality process requir­ements

Entry requir­ements state what must exist before the stage or activity can begin
Implem­ent­ation requir­ements define how the process should be done
Exit requir­ements indicate what should be in place for a successful sign-off of the activity
Part of quality criteria

Formal inspection structure

Prepar­ation. The reviewers review the docume­ntation and annotating the product and recording defects
Meeting: discussion of potential defects, confirm or deny they actually are defects. Agree follow up of each.
Recording: follow-up actions, respon­sib­ili­ties, agreement of outcome and sign-off if approp­riate
Follow up
advising the project manager of the outcome;
planning remedial work;
Signing off when complete

V Model

Model in which the solid lines represent the forward progress of the project and the dotted lines represent the way in which quality control is exercised


specif­ically aimed at producers and suppliers of any products and services, not necess­arily software
Organi­sations are inspected and awarded ISO 9001 certif­ication by accredited auditors
ISO 9001:2008 is based on the following princi­ples:
Customer focus: unders­tanding and meeting or exceeding the customer requir­ements
Leader­ship: providing this for the organi­sation to give it the purpose, unity and direction to achieve quality objectives
People: involv­ement of staff at all levels of the organi­sations involved
Process approach: attention to individual processes which produce interm­ediate or delive­rable products
Systems approach to manage­ment: focusing on inter-­related processes producing delive­rable products;
Continual improv­ement
Factual approach to decisi­on-­making
Mutually beneficial client­-su­pplier relati­onships

Defini­tions of quality

A degree or level of excellence
Confor­mance to standard
Delive­rables should be fit for purpose

Quality criteria

Quality criteria must be specified at beginning, before product developed
Each product definition includes a section headed quality criteria
Used by team to ensure fit for purpose
Specific, measur­eable and achievable
Company should develop standards for product defini­tions for its quality procedures

Defect removal process

ID defects so you can remove them
Easy at end of project in dynamic testing
Techniques for IDing defects at beginning stages
desk checking: Authors, or creators, of products review what they have produced
document review: other people read document to ensure meets QC
peer review: The author’s co-workers (or peers) examine copies of the document and make comments about it. Answer things liek: is it feasible, is there a better way, does it conform to company standards, does it commun­icate with other parts of the system, are requir­ements covered, are there any ambigu­ities
Inspection Formal review of product.
Walkth­rough: The author takes the audience through the documents and they feed back their comments on it
Pair progra­mming: in agile develo­pment enviro­nments, code developers sometimes work in pairs. The pair take turns to type in code at the workst­ation while the other advises and checks on what is being entered.
Static testing: Software tools analyse structure of code. Look at the branches and loops in a program and calculate a measure of comple­xity. More complex = difficult to maintain

Evaluating suppliers

Important to establish whether those third party suppliers have the necessary quality procedures in place to ensure that the software to be supplied is to the standard expected.
Must be recognised that the supplier and the customer have different business object­ives. Making a project a success therefore needs both parties to see the project as a joint venture

Evaluating suppliers

Important to establish whether those third party suppliers have the necessary quality procedures in place to ensure that the software to be supplied is to the standard expected.
Must be recognised that the supplier and the customer have different business object­ives. Making a project a success therefore needs both parties to see the project as a joint venture


Cannot guarantee software will never fail
Hardware & infras­tru­cture might also fail
Examine ways system will behave in event of various types of failure
Might need to make it ‘fail safe’ so that it will revert to a safe state

QC vs QA

The quality control framework is called the quality management system (QMS)
The QMS may be based on the ISO 9001 series of standards
The QMS includes quality strategy and quality assurance processes
Quality strategy defines QMS and includes
procedures and standards for creating a project quality plan
a definition of quality criteria
quality control procedures
quality assurance procedures
a statement of compliance with or allowed deviation from industry standards
acceptance criteria
Allocation of respon­sib­ilities for defining or undert­aking qualit­y-r­elated activities
Quality assurance is like an audit. It is designed to confirm that proper procedures are in place and have been applied correctly
QC = Quality control
QA = Quality assurance

Dynamic testing levels

Test data for usual range of input
Functions tested
Test various comboss & sequences
Test for outliers of limits
Alphabetic fields tested longer than that which the system should permit
Mandatory fields are left blank
Ensures unit will not fail because of bad data or unusual combin­ations but will handle them in a predefined way
Record all faults
Links a number of system components and runs them as a whole
checks that the units commun­icate properly
Final stage in testing by the develo­pment profes­sionals
Running the whole system on the infras­tru­cture that will be used when the system is operat­ional
Operat­ional, response time, workload cope, effect of high loading
User acceptance
Can the users operate the system? Does it meet their expect­ations, not just their requir­ements?
Running an agreed set of test data through the system again to confirm that the original error has been corrected and no further errors have been introduced or uncovered
For each type of testing, a set of test data and a set of expected results must be produced
- Test data for usual range of input expected for system
- Functions tested

Capability maturity models

Where the organi­sation is assessed as being at a particular level of process maturity
Assessment can be internal or external
Capability maturity model (CMM) has five levels
(1) Initial. Any organi­sation would be at this level by default. Good quality work may be done, but customers cannot be sure that this is always the case.
(2) Managed. Some basic project management and other systems are in place.
(3) Defined. The way each task in software develo­pment is done is defined to enable consistent good practice.
(4) Quanti­fiably managed. Processes and their products are measured and controlled – for example, the number of errors created in each process
(5) Optimi­sing. The measur­ement data collected is analysed to find ways of improving processes.


No comments yet. Add yours below!

Add a Comment

Your Comment

Please enter your name.

    Please enter your email address

      Please enter your Comment.

          More Cheat Sheets by NatalieMoore