Q.

Explain the six sigma characteristics in details ( UNIT 6 )

Six Sigma is a data-driven methodology aimed at improving business processes by identifying and eliminating
defects, reducing variability, and ensuring quality control. It focuses on achieving near-perfect processes with fewer
than 3.4 defects per million opportunities

1. Customer Focus Definition:goal of Six Sigma is to meet or exceed customer expectations. Every process
improvement should be centered around delivering value to customer, whether external or internal.it emphasizes
understanding the customer’s needs and expectations.

2. Data-Driven Decision Making Definition: Six Sigma is a highly data-driven methodology. Decisions regarding
process improvement are based on hard data and statistical analysis rather than intuition or
assumptions.Techniques like statistical process control (SPC), hypothesis testing, regression analysis, control charts
are used to measure performance and identify areas for improvement.

3. Process Improvement Definition: Six Sigma focuses on improving processes by reducing variation and
eliminating defects. The methodology identifies inefficiencies or errors in processes and works on optimizing them.:
By analyzing the root causes of defects and inefficiencies in a process, Six Sigma aims to enhance process stability
and predictability.

4. Variation Reduction Definition: One of the core goals of Six Sigma is to reduce variation in processes. By doing
so, it ensures that processes are predictable, stable, and deliver consistent results.Variability is a major cause of
defects in any process. Six Sigma uses statistical tools to analyze and control sources of variation.

5. Continuous Improvement Definition: Six Sigma is not a one-time fix. It promotes a culture of continuous
improvement where businesses constantly seek ways to improve processes.The idea is to make incremental
improvements over time, so there is never a final "perfect" state.

6. Employee Involvement Definition: Six Sigma encourages participation from all levels of the organization, from
top management to frontline employees, in the improvement process.
Successful Six Sigma implementation requires collaboration across departments..

DMAIC:methodology for improving processes (Define, Measure, Analyze, Improve, Control).

DMADV: for creating new processes or products (Define, Measure, Analyze, Design, Verify).
____________________________________________________________________________________________
Q.Compare the Ishikawa’s flowchart and Histogram tools

Ishikawa’s Flowchart Histogram

Identifying root causes of a problem | Understanding data distribution
Qualitative | Quantitative
Fishbone diagram (categorical causes) | Bar chart (data intervals).
Contributing factors (causes). | Frequency of values
Root cause analysis. | Data distribution analysis
Visual map of possible causes. | Graphical distribution of data
Used in root cause analysis
quality management | Used in statistical analysis to understand
Requires user brainstorming
to identify categories | Requires data collection and statistical plotting
Focuses on causes of issues or defect. | Focuses on the spread, center, and shape of data
Ease of Interpretation | Easy to interpret for identifying cause relationships
Easy to interpret for data trends and patterns
Q.What parameter required for achieving good software quality ( unit 6)

Achieving good software quality requires a combination of various factors, processes, and parameters that focus on
delivering reliable, efficient, and maintainable software. Here are the key parameters required to achieve good
software quality:

1. Functionality
Definition: The software must perform the required functions correctly as per the defined specifications with
Correctness,Compliance,Suitability.

2. Reliability software perform consistently in expected conditions and be resilient to errors.

With Stability,Fault Tolerance,Recoverability

3. Usability : The software should be easy to use and intuitive for its intended users.
With Ease of Learning,Efficiency,User Experience (UX)

4. Performance Definition: The software should perform efficiently, utilizing system resources optimally and
ensuring fast response times.
With Response Time,Throughput,Resource Efficiency

5. Maintainability The software should be easy to maintain and update over its lifecycle.with
Modularity,Readability,Testability

6. Security : The software should be secure, protecting against unauthorized access, data breaches, and other
security threats. With Authentication and Authorization,Data Protection, Vulnerability Management

7. Scalability
Definition: The software should be able to handle increased load or growth without degrading in performance.
With Horizontal Scaling,Vertical Scaling,Load Balancing

8. Interoperability Definition: The software should be able to work seamlessly with other software systems,
hardware, and platforms with integration,Standards Compliance

9. Portability
Definition: The software should be able to run on different platforms (e.g., Windows, Linux, macOS, mobile
devices) with minimal changes. With Platform Independence,Migration

10. Documentations
____________________________________________________________________________________________

Q.Maintaining Software Quality Assurance (SQA)

1. Define Quality Goals: Set measurable objectives aligned with stakeholder expectations.
2. Adopt Standards: Use frameworks like ISO 9001 or CMMI for structured processes.
3. Testing: Perform unit, integration, and system testing to catch defects early.
4. Automation: Use tools for testing, version control, and continuous integration.
5. Reviews: Conduct code, design, and requirement reviews.
6. Risk Management: Identify and mitigate risks proactively.
7. Monitor Performance: Track metrics like defect density and response time.
8. Traceability: Use RTM to map requirements to deliverables.
9. Collaboration: Encourage communication between developers, testers, and stakeholders.
10. Continuous Improvement: Use feedback and retrospectives to enhance processes.

Q.SQA Task Goals and Metrics ( unit 6)

1. Requirement Quality: Metric: Requirement Stability Index (tracks requirement changes).

2. Defect Reduction: Metric: Defect Density (defects per KLOC).
3. Testing Effectiveness: Metric: Defect Detection Percentage.
4. Efficiency: Metric: Cycle Time (time from development to release).
5. Process Maturity: Metric: Process Adherence (compliance with standards).
6. Customer Satisfaction: Metric: Customer Satisfaction Index (feedback-based).
7. Maintainability: Metric: Mean Time to Repair (MTTR).
8. Scalability: Metric: Code Complexity (cyclomatic complexity).
9. Compliance: Metric: Compliance Rate (meeting standards).
10. Monitoring: Metric: Defect Arrival Rate (defects reported over time).

Q.Comparison of Run Charts and Control Charts

1. Purpose: Run charts show trends over time; control charts assess process stability.
2. Data Representation: Run charts plot data points; control charts include control limits.
3. Control Limits: Run charts lack control limits; control charts define upper and lower limits.
4. Focus: Run charts identify trends and shifts; control charts differentiate variation causes.
5. Statistical Analysis: Run charts lack statistical boundaries; control charts use them to ensure control.
6. Usage: Run charts are for initial trend detection; control charts are for continuous monitoring.
7. Interpretation: Run charts are simple to interpret; control charts need statistical knowledge.
8. Application: Run charts track small dataset trends; control charts ensure process consistency.
9. Complexity: Run charts are simpler; control charts require statistical calculations.
10. Example: Run charts show sales trends; control charts monitor defect levels within limits.

Q.Activities to Achieve High Software Quality

1. Define Clear Requirements: Establish precise, complete, and unambiguous requirements to ensure alignment
with user needs.
2. Use Standardized Processes: Follow industry standards like ISO or CMMI to maintain consistency in development.
3. Conduct Thorough Testing: Perform unit, integration, system, and acceptance testing to identify and resolve
defects early.
4. Code Reviews: Regularly review code to ensure it meets quality standards and is free of errors.
5. Continuous Integration: Implement CI tools to identify issues promptly and maintain code stability.
6. Risk Management: Proactively identify and address potential risks to avoid future problems.
7. Monitor Performance Metrics: Track metrics like defect density and mean time to failure to measure software
quality.
8. Ensure Proper Documentation: Maintain accurate documentation for requirements, design, and testing to
support quality processes.
9. Focus on User Feedback: Gather and act on feedback to improve usability and meet user expectations.
10. Continuous Improvement: Regularly analyze processes and implement changes for better quality outcomes.
Q. explain ISO 9000 Standard ( unit 6)

1. Overview: ISO 9000 is a family of standards for quality management systems (QMS) that ensure organizations
consistently deliver products or services meeting customer and regulatory requirements.

2. Purpose: It provides guidelines for improving processes, ensuring customer satisfaction, and achieving
continuous improvement.

3. Key Principles: Customer Focus: Meeting customer needs and enhancing satisfaction.
- Leadership: Establishing a clear vision and strong governance.
- Process Approach: Managing activities as interconnected processes.
- Continuous Improvement: Consistently enhancing processes and outcomes.

4. Core Standards: iSO 9000: Covers the basics of QMS, including terminology and principles.
- ISO 9001: Specifies requirements for implementing and maintaining QMS.
- ISO 9004: Focuses on improving organizational performance.
5. Certification: ISO 9001 certification demonstrates an organization's commitment to quality management and
continual improvement.

6. Benefits: - Enhances customer satisfaction and trust. - Improves process efficiency and reduces errors. -
Facilitates compliance with legal and regulatory requirements.
7. Implementation Steps: - Analyze organizational needs and define quality objectives. - Develop and
document QMS processes and procedures. - Train employees and allocate resources. - Conduct internal audits
to ensure compliance.

8. Applicability: ISO 9000 is relevant to all industries and sectors, helping organizations of any size improve
quality management practices.

Q.software Maintenance
Software maintenance involves updating, improving, and fixing software after its release. It includes:
1. Corrective Maintenance: Fixing defects or issues identified after deployment.
2. Adaptive Maintenance: Modifying the software to work in changing environments (e.g., OS upgrades).
3. Perfective Maintenance: Enhancing performance or adding new features.
4. Preventive Maintenance: Improving the software to prevent future issues.

Q.Facts to Achieving Software Quality

1. Clear Requirements: Well-defined accurate requirements ensure alignment with user needs.
2. Proper Planning: Establishing clear goals, timelines,esources efficient development.
3. Effective Testing: Rigorous testing at all stages to identify defects early.
4. Continuous Monitoring: Regularly track performance and defect metrics to ensure quality.
5. Team Collaboration: Effective communication between stakeholders, developers, and testers leads to better
outcomes.
6. Risk Management: Identifying and mitigating risks to prevent quality issues.
7. Adherence to Standards: Following industry standards like ISO 9001 helps maintain consistent quality.
8. User Feedback: Gathering feedback helps in enhancing usability and fixing real-world issues.
9. Training: Continuous skill development for the team to keep up with evolving technologies.
10. Continuous Improvement: Regularly refining processes and practices to improve quality over time.