OHT 13.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 What is a CASE tool? The contribution of CASE tools to software product.

Slides:

Advertisements

Similar presentations

© by cellconsult.com Application Testing & Test Management.

Advertisements

OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan

PERTEMUAN - 2 SOFTWARE QUALITY. OBJECTIVES After completing this chapter, you will be able to: ■ Define software, software quality and software quality.

CHAPTER 1 Introduction to SQA.

OHT 10.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The testing process Determining the test methodology phase Planning.

OHT 6.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Development plan and quality plan objectives The elements of the development.

OHT 8.1 Galin, SQA from theory to implementation © Pearson Education Limited Review objectives Formal design reviews (FDRs) Participants Preparations.

OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 What is software? Software errors, faults and failures Classification.

OHT 8.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Review objectives Formal design reviews (FDRs) Participants Preparations.

OHT 4.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Pre-project components Software project life cycle components Infrastructure.

Chapter 1 Assuming the Role of the Systems Analyst

Quality assurance in software production Lari Karppinen

OHT 7.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software development methodologies: - The software development life cycle.

OHT 22.1 Galin, SQA from theory to implementation © Pearson Education Limited Objectives of cost of software quality metrics 2.The classic model.

OHT 14.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software quality infrastructure components The need for procedures and.

Components of software quality assurance system overview

Chapter 1 Assuming the Role of the Systems Analyst

OHT 3.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The need for comprehensive software quality requirements Classification.

OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.

OHT 7.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software development methodologies: - The software development life cycle.

OHT 6.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Development plan and quality plan objectives The elements of the development.

Software Quality Assurance

Galin, SQA from theory to implementation © Pearson Education Limited Chapter 13 CASE Tools and their Effect on Software Quality.

Chapter 2 Please note that author slides have been significantly modified.

SQA Architecture Software Quality.

OHT 17.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Corrective and preventive actions — definitions The corrective and preventive.

Issues on Software Testing for Safety-Critical Real-Time Automation Systems Shahdat Hossain Troy Mockenhaupt.

OHT 22.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan

OHT 19.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Controlled documents and quality records Definitions and objectives.

OHT 16.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The objectives of training and certification The training and certification.

SQA Architecture Software Quality By: MSMZ.

Chapter 2 What is software quality ?. Outline What is software? Software errors, faults and failures Classification of the causes of software errors Software.

What is Software Engineering? the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software”

National Cheng Kung University 軟體品質管理期末報告 The SQA Unit and Other Actors in the SQA System Reporter: 羅國益 Teacher: 朱治平 Date: 2014/12/30.

OHT 18.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Chapter 18 Configuration Management.

OHT 25.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The quality assurance organizational framework Top management’s quality.

OHT 23.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The benefits of use of standards The organizations involved in standards.

SE513 Software Quality Control Lecture01: Introduction to Software Quality Assurance Galin, SQA from Theory to Education Limited.

OHT 7.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Chapter 7.1.

Chapter 1 Assuming the Role of the Systems Analyst Systems Analysis and Design Kendall & Kendall Sixth Edition.

OHT 5.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Contract review process and stages Contract review objectives Implementation.

OHT 12.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Introduction Types of external participants Risks and benefits of introducing.

OHT 18.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Introduction The foundations of high quality Foundation 1: software.

OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.

SE513 Software Quality Assurance Lecture07: Maintenance Life Cycle Quality Assurance Tools Galin, SQA from Theory to Education.

OHT 20.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The components of project progress control Progress control of internal.

OHT 7.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software development methodologies: - The software development life cycle.

ANKITHA CHOWDARY GARAPATI

OHT 12.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Introduction Types of external participants Risks and benefits of introducing.

OHT 15.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Templates The contribution of templates to software quality The organizational.

1 Chapter 1 The Software Quality Challenge. 2 The uniqueness of software quality assurance  DO you think that there is a bug-free software?  Can software.

SE513 Software Quality Assurance Lecture10: Documentation and Quality Records Control Galin, SQA from Theory to Education Limited.

Multitude of source of errors - various style of source of errors will affect the SQA components * The environment in which software development & maintenance.

SEN 460 Software Quality Assurance. Bahria University Karachi Campus Waseem Akhtar Mufti B.E(CSE) UIT, M.S(S.E) AAU Denmark Assistant Professor Department.

CASE Tools and their Effect on Software Quality

CASE (Computer-Aided Software Engineering) Tools

OHT 18.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software configuration, software configuration items and software configuration.

OHT 10.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The testing process Determining the test methodology phase Planning.

OHT 15.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Templates The contribution of templates to software quality The organizational.

Components of software quality assurance system overview

Supporting quality devices

Components of software quality assurance system overview

Software Verification and Validation

Software Engineering Lecture #2

What is software quality?

What is software quality?

Chapter # 6 Software Configuration Management

Chapter # 7 Software Quality Metrics

Chapter # 4 Development and Quality Plans

Presentation transcript:

OHT 13.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 What is a CASE tool? The contribution of CASE tools to software product quality The contribution of CASE tools to software maintenance quality The contribution of CASE tools to improved project management

OHT 13.2 Galin, SQA from theory to implementation © Pearson Education Limited 2004 CASE tools are computerized software development tools that support the developer when performing one or more phases of the software life cycle and/or support software maintenance.

OHT 13.3 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Traditional development life cycle Real CASE tool-supported development life cycle

OHT 13.4 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Cause of software errors Classic CASE tools Real CASE tools 1. Faulty requirements definitionNoneAlmost none 2. Client-developer communication failuresNoneAlmost none 3. Deliberate deviations from software requirements NoneHigh 4. Logical design errorsNoneHigh 5. Coding errorsVery high 6. Non-compliance with coding and documentation instructions LimitedVery high 7. Shortcomings in the testing processHigh 8. User interface and procedural errorsLimited 9. Documentation errorsLimitedVery high Extent of contribution to quality

OHT 13.5 Galin, SQA from theory to implementation © Pearson Education Limited 2004 To corrective maintenance: * CASE-generated updated documentation enables easier and more reliable identification of software failure causes. * Cross-referenced queries enable better anticipation effects of proposed correction. * Correction by means of lower CASE or integrated CASE tools provides automated coding and documentation of corrections.

OHT 13.6 Galin, SQA from theory to implementation © Pearson Education Limited 2004 To adaptive maintenance: Full and updated documentation by CASE tools enables thorough examination of possible software adaptations for new applications.

OHT 13.7 Galin, SQA from theory to implementation © Pearson Education Limited 2004 To functional improvement maintenance: * Use of the repository assures consistency of new applications and improvements with existing software systems. * Cross-referenced repository queries enable better planning of changes and additions. * Changes and additions carried out by means of lower CASE or integrated CASE tools enable automated coding and documentation of the changes and additions.