Você está na página 1de 15

Quality management

What is quality management?(1)

Difficulties with SW quality management


The specification should be oriented towards the characteristics of the product which the customer wants. However, the development organization may also have requirements which are not included in the specification. We do not know how to specify certain quality characteristics in an unambiguous way. Software specifications are usually incomplete.

Quality management
Ensuring that software is developed without faults and conforms to its specification. Broader aspects of software quality

What is quality management?(2)

Safety Security Reliability Resilience Robustness

Understandability Portability Testability Usability Adaptability Reusability Modularity Efficiency Complexity Learnability

Three activities of quality manager Quality assurance : establish organizational procedures and standards which lead to high-quality software. Quality planning : select appropriate procedures and standards and tailor them for a specific software project. Quality control : ensure that procedures and standards are followed by the software development team.

What is quality management?(3)

An international standard which can be used in the development of a quality management in all industries is called ISO 9000. Quality management should be separate from project management.

Process quality assurance

The quality of the development process directly affects the quality of delivered products. The prescribed process may be inappropriate for the type of software.

Define process

Develop product

Access product quality

Improve process

Quality OK?

Standardize process

Quality reviews(1)

Principal method of validating the quality of a process or product. Review types


Design/program inspections Progress reviews : to provide information for management about the overall progress of the project. This is both a process and a product review and is concerned with costs, plans and schedules. Quality reviews :

Quality reviews(2)

Three functions
A quality function in that they are part of the general quality assurance procedures used in the organization. A project management function whereby they provide information to management about progress. A training function in that engineers explain their design and justify their design functions.

Reviews are document-based but are not limited to specifications. Review team
Include those project members who can make an effective contribution. Three/four people : should not be too large.

Quality reviews(3)

Three type of comments


No action : either the comment was factually incorrect or the review decided that the cost of rectifying the problem was unjustified. Refer for repair : the review detected a problem and asked the document originator or designer to fix that problem. Reconsider overall design :The best way to solve an identified problem is to change the overall design of the system or process.

Software standards(1)

Product standards : define characteristics that all product components should exhibit.
Process standards : define how the software process should be conducted.

Reasons for standards


Standards provide an encapsulation of best Standards provide a framework around which the quality assurance process may be implemented. Standards assist in continuity where work carried out by one person is taken up and continued by another.

Quality assurance teams who are developing standards should normally base organizational standards on national and international standards.

Software standards(2)

Steps for the quality assurance organization setting standards.


Involve software engineers in the development of product standards. Review and modify standards regularly to reflect changing technologies. Where standards set out clerical procedures such as document formatting, software tools should be provided to support these standards.

Software metrics(1)

Control metrics
Those used by management to control the software process. Provide information about process quality.

Predictor metrics
Measurements of a product attribute that can be used to predict an associated product quality. Allow us to predict the value of some external attributes of the software by measuring an internal attribute.

Software metrics(2)

A relationship between external and internal attributes.


Number of procedure parameters

Maintainability
Reliability Portability Usability

Cyclomatic complexity
Program size in lines of code Number of error messages Length of user manual

Software metrics(3)

If the measure of the internal attributes is to be a useful predictor of the external software characteristic, three conditions must hold:
The internal attribute must be measured accurately. A relationship must exist between what we can measure and the external behavioral attribute. This relationship is understood, has been validated and can be expressed in terms of a formula or model.

Software metrics(4)-Data collection

Three types of automated data collection


Static product analysis : involves developing or buying software tools that statistically analyze the software product and measure various product parameters. Dynamic product analysis : instrumenting the software system so that it collects information about its own usage and about faults or various kinds which occur. Process data collection : given that project management tools are used, it is possible to modify or extend these tools to process management data input to the tools so that it is collated in a useful form for further analysis. There are no general guidelines which may be used as data analysis is only possible when local circumstances are understood.

Product quality metrics

The process of using metrics for quality prediction


Choose measurements to be made Select Component to be assessed Measure component characteristics Analyze anomalous components Identify anomalous measurements

Você também pode gostar