final mod 5 Flashcards
Define Software Quality and explain the place of software quality in project management
Step 1: Identifying Project Scope and Objectives: Define quality objectives aligned
with project goals.
Example: Set standards for software functionality and user experience.
o Step 2: Identifying Project Infrastructure: Define installation standards with quality
considerations.
Example: Specify the necessary environment for software deployment.
o Step 3: Analyze Project Characteristics: Identify any special quality requirements.
Example: Safety-critical apps may require n-version programming.
o Step 4: Identify Product and Activities: Define entry, exit, and process requirements
for activities.
o Step 8: Review and Publicize Plan: Review quality objectives and integrate them into
the project plan.
2. Quality Across Phases:
o Quality is ensured throughout the lifecycle, from planning to testing and delivery.
o Example: Quality metrics like code reviews and testing are applied in the testing phase.
Conclusion:
Software quality is a continuous concern in project management, addressed at every phase to ensure the
final product meets user needs and performs as expected.
McCall’s Model of Software Quality
Product Operation (External View):
o Correctness: Ensures the software meets specified requirements.
o Reliability: Consistently performs under expected conditions.
o Efficiency: Optimal use of system resources (e.g., memory, CPU).
o Integrity: Protection against unauthorized access and security breaches.
o Usability: Easy and intuitive for users to operate.
2. Product Revision (Internal View):
o Maintainability: Ease of making updates and fixing issues.
o Flexibility: Ability to adapt to changes in requirements.
o Testability: How easy it is to verify software correctness through testing.
3. Product Transition (Change View):
o Portability: Can be deployed on different platforms or environments.
o Reusability: Can be reused in different applications or systems.
o Interoperability: Works effectively with other software systems.
This model helps assess software from both user and developer perspectives, ensuring a balanced view
of quality
Dromey’s Model (Software Quality
High-Level Properties:
o Correctness: Measures if the software meets its specifications and user requirements.
o Internal Characteristics: Evaluates the internal design and performance of the software.
o Contextual Characteristics: Assesses how well the software fits into its intended
environment.
o Descriptive Properties: Includes attributes like reliability, maintainability, and
portability.
2. Hierarchical Structure:
o The model is organized in layers, starting from broad properties and breaking them down
into measurable attributes.
3. Objective:
o To systematically evaluate software quality by considering different dimensions and
focusing on areas for improvement.
This model helps in assessing software quality by breaking it down into key characteristics for better
analysis and management
. Boehm’s model
High-Level Characteristics:
o As-is Utility: Measures how well the software performs its functions (ease of use,
reliability, and efficiency).
o Maintainability: Focuses on how easily the software can be understood, modified, and
retested.
o Portability: Assesses how easily the software can be adapted to new environments or
platforms.
2. Measurable Product Attributes:
o Boehm’s model breaks down these high-level characteristics into measurable attributes to
evaluate software quality more effectively.
3. Objective:
o This model aims to define software quality based on user-centric characteristics and
provides measurable ways to assess these qualities.
Boehm’s model helps in evaluating software quality from a user’s perspective, focusing on utility, ease
of maintenance, and adaptability.
. ISO 9126 Model
Introduction:
o ISO 9126 was introduced in 1991 to define software quality and has evolved into a
detailed set of standards.
o The model serves as a foundation for evaluating software quality, which is now more
comprehensive.
2. Motivation:
o Acquirers: People acquiring software from external suppliers.
o Developers: Those building software products.
o Independent Evaluators: Assessing software quality for a broader user community.
3. Quality in Use:
o Effectiveness: The software’s ability to achieve user goals accurately and completely.
o Productivity: The efficiency with which resources (like staff effort) are used to achieve
user goals.
o Safety: The level of risk involved in using the software, ensuring safety for people and
other entities.
o Satisfaction: The degree of user satisfaction, reflected by a positive user experience.
ISO 9126 is a comprehensive standard, introducing metrics for both software quality and how it
performs in real-world usage, ensuring user goals are met safely and efficiently
