Quality in IT Projects Cheat Sheet by NatalieMoore

Meet requir­ements at affordable price

Costs of remedying lapses in quality great.

-

Functi­ona­lity: meet user requir­ements

-

Usability: Intuitive, minimum training

-

Mainta­ina­bility: easy to modify

Maybe existing, new, industry, modified versions of existing, developed internally

Specifies quality assurance processes

Implem­ent­ation requir­ements define how the process should be done

Meeting: discussion of potential defects, confirm or deny they actually are defects. Agree follow up of each.

-

planning remedial work;

Organi­sations are inspected and awarded ISO 9001 certif­ication by accredited auditors

-

Customer focus: unders­tanding and meeting or exceeding the customer requir­ements

-

People: involv­ement of staff at all levels of the organi­sations involved

-

Systems approach to manage­ment: focusing on inter-­related processes producing delive­rable products;

-

Factual approach to decisi­on-­making

Confor­mance to standard

Reliab­ility

Each product definition includes a section headed quality criteria

-

Specific, measur­eable and achievable

Easy at end of project in dynamic testing

-

desk checking: Authors, or creators, of products review what they have produced

-

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

-

Walkth­rough: The author takes the audience through the documents and they feed back their comments on it

-

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

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

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

Hardware & infras­tru­cture might also fail

Might need to make it ‘fail safe’ so that it will revert to a safe state

The QMS may be based on the ISO 9001 series of standards

Quality strategy defines QMS and includes

-

a definition of quality criteria

-

quality assurance procedures

-

acceptance criteria

Quality assurance is like an audit. It is designed to confirm that proper procedures are in place and have been applied correctly

Test data for usual range of input

Test various comboss & sequences

Alphabetic fields tested longer than that which the system should permit

Ensures unit will not fail because of bad data or unusual combin­ations but will handle them in a predefined way

checks that the units commun­icate properly

Final stage in testing by the develo­pment profes­sionals

Operat­ional, response time, workload cope, effect of high loading

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

Assessment can be internal or external

(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.

(3) Defined. The way each task in software develo­pment is done is defined to enable consistent good practice.

(5) Optimi­sing. The measur­ement data collected is analysed to find ways of improving processes.