Mc call's software quality model
Download as PPTX, PDF•2 likes•9,583 views
McCall's software quality model, introduced by Jim McCall in 1977, aims to bridge the gap between users and developers by focusing on software quality factors that reflect user views and developer priorities. The model identifies quality factors across product operation, revision, and transition, addressing aspects like correctness, efficiency, maintainability, portability, and more. Each quality factor is influenced by multiple criteria, and there's an interplay where improving one factor may affect others, emphasizing the complexity of software quality management.
Mc call's software quality model
- 1. McCall's Software Quality Model Yatharth Aggarwal Mayank Chauhan IV.4 Software Engineering
- 2. Quality can be defined as..... • Conformance to requirements • Fitness for the purpose • Level of satisfaction
- 3. Introduction… • Jim McCall (McCall, Richards & Walters, 1977) introduced this model (also known as the General Electrics Model of 1977). • This model, as well as other contemporary models, originates from the US military (it was developed for the US Air Force, promoted within DoD) and is primarily aimed towards the system developers and the system development process. • This quality model attempts to bridge the gap between users and developers by focusing on a number of software quality factor that reflect both users’ views developers’ priorities. • At NASA, the criteria for evaluation of software quality are taken from McCall’s software quality factor model.
- 4. The model Product Operation Product revision Product transition identifies quality factors that influence the extent to which the software fulfils its specification
- 5. Quality factors (representation of behavioral characteristic of a system) • Product Operation Correctness : Does it do what customer wants ? (meeting specifications) Efficiency : Does it quickly solve the intended problem ? (enough computing resources) Integrity : Is it secure ? (access limitations to people) Reliability : Does it do it accurately all of the time ? (successful performance) Usability : Can I run it ? (efforts in learning/operating)
- 6. Quality factors (dependence of a system on ethical issues) • Product Revision Maintainability : Can it be fixed ? (fixing bugs and errors) Flexibility : Can it be changed ? (modifying an operational program) Testability : Can it be tested ? (ensuring performance) • Product Transition Portability : Can it be used on another machine ? (platform dependence) Reusability : Can parts of it be reused ? (generic coding) Interoperability : Can it interface with other system ? (coupling system)
- 7. Quality criteria (attribute of a quality factor related to software development)
- 8. Quality criteria (subject validating the factors of quality mgmt.)
- 9. Quality criteria (many-many relation b/w factors and criteria)
- 11. Relationship Between Quality Factors and Quality Criteria • Each quality factor is positively influenced by a set of quality criteria, and the same quality criterion impacts a number of quality factors. • Example: Simplicity impacts reliability, usability, and testability. • If an effort is made to improve one quality factor, another quality factor may be degraded. • Portable code may be less efficient. • Some quality factors positively impact others. • An effort to improve the correctness of a system will increase its reliability.
- 12. Thank you ………………… ??? Ques ???