Software engineering.

Slides:



Advertisements
Similar presentations
Ch.21 Software Its Nature and Qualities. Ch.22 Outline Software engineering (SE) is an intellectual activity and thus human-intensive Software is built.
Advertisements

Software Quality Seung Yang CS 525 Software Engineering II Dr. Sheldon X. Liang.
Chapter 4 Software Process and Project Metrics
Metrics for Process and Projects
Software Engineering Software quality. Software quality characteristics:  External: user is aware of. User cares about.  Internal: programmer is aware.
Software Engineering II - Topic: Software Process Metrics and Project Metrics Instructor: Dr. Jerry Gao San Jose State University
Software project management (intro) Quality assurance.
R&D SDM 1 Metrics How to measure and assess software engineering? 2009 Theo Schouten.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
OHT 3.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The need for comprehensive software quality requirements Classification.
Chapter#7.  Part 1: Quality Management ◦ ƒ Understand the definition of quality and the different methodologies to provide quality ◦ ƒ Know quality management.
Software Process and Product Metrics
Factor Of Software Quality
OHT 3.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Managing Software Quality
 The software systems must do what they are supposed to do. “do the right things”  They must perform these specific tasks correctly or satisfactorily.
Requirements specification Copyright, 2001 © Jerzy R. Nawrocki Quality Management.
1 Software Quality CIS 375 Bruce R. Maxim UM-Dearborn.
Software Quality Applied throughout SW Engineering Process Encompasses ▫ Analysis, design, coding, testing, tools ▫ Formal tech reviews ▫ Multi-tiered.
Software Software is omnipresent in the lives of billions of human beings. Software is an important component of the emerging knowledge based service.
Chapter 6 : Software Metrics
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
Software Measurement & Metrics
1. Software Metric- A definition 2. Types of Software metrics 3. Frame work of product metrics 4. Product metrics.
CS460 © 2003 Ray S. Babcock Metrics The term metrics refers to any measurement related to software development. ● Lines of Code ● number of defects ● defects.
Software Engineering Quality What is Quality? Quality software is software that satisfies a user’s requirements, whether that is explicit or implicit.
SOFTWARE SYSTEMS DEVELOPMENT 4: System Design. Simplified view on software product development process 2 Product Planning System Design Project Planning.
Question To know that quality has improved, it would be helpful to be able to measure quality. How can we measure quality?
Software Project Management Lecture # 3. Outline Chapter 22- “Metrics for Process & Projects”  Measurement  Measures  Metrics  Software Metrics Process.
Software Quality Metrics
OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which.
Code Complete Steve McConnell. 20. The Software-Quality Landscape.
Software quality factors
CS551 - Lecture 5 1 CS551 Lecture 5: Quality Attributes Yugi Lee FH #555 (816)
LESSON 3. Properties of Well-Engineered Software The attributes or properties of a software product are characteristics displayed by the product once.
Prepared by: Hussein Alhashimi.  This course introduces fundamental concepts related to Quality Assurance and Measurements and Metrics in the software.
SEN 460 Software Quality Assurance
CSE 303 – Software Design and Architecture
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 15a: Product Metrics for Software Software Engineering: A Practitioner’s Approach, 6/e Chapter.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Test Strategy Best Practices By Gabriel Rodriguez.
Hussein Alhashimi. “If you can’t measure it, you can’t manage it” Tom DeMarco,
Chapter 22 Metrics for Process and Projects Software Engineering: A Practitioner’s Approach 6 th Edition Roger S. Pressman.
OOAD UNIT V B RAVINDER REDDY PROFESSOR DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING.
Software Project Management Lecture # 3. Outline Metrics for Process and Projects  Introduction  Software Metrics Process metrics Project metrics Direct.
SPM UNIT 2 - Prof S. S. Deshmukh. Software measurements  Measurement gives us the insight by providing mechanism for evaluation.  There are four reasons.
TOTAL QUALITY MANAGEMENT
Rekayasa Perangkat Lunak
Software Quality Control and Quality Assurance: Introduction
Software Quality Management
Rekayasa Perangkat Lunak Part-10
Rekayasa Perangkat Lunak
SEVERITY & PRIORITY RELATIONSHIP
Source & Courtesy: Doc. S. Dapkūnas
Software Quality Assurance Software Quality Factor
Software Engineering (CSI 321)
McCall’s Quality Factors
Lecture 15: Technical Metrics
Software Quality Assurance
مقدمه اي بر مهندسي نيازمنديها
Rekayasa Perangkat Lunak
Charakteristiky kvality
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
Managing Software Quality
Software metrics.
Software Requirements Specification (SRS) Template.
Process and Project Metrics
Metrics for Process and Projects
ISO/IEC Systems and software Quality Requirements and Evaluation
Presentation transcript:

Software engineering

McCall’s Quality Factors Revision Adaptation Maintainability Flexibility Testability Portability Reusability Interoperability Operation The attributes that provide an indication of quality remain the same. Correctness The extent to which a program satisfies its specifications and fulfills the customer’s mission objectives Reliability The extent to which a program can be expected to perform its intended function with required precision. Efficiency The amount of computing resources required by a program to perform its function Integrity Extent to which access to software or data by unauthorized persons can be controlled. Usability Effort required to learn, operate, prepare input, and interpret output of a program Maintainability Effort required to locate and fix an error in a program Flexibility Effort required to modify an operational program Testability Effort required to test a program to ensure that it performs its intended function Portability Effort required to transfer the program from one hardware and/or software system environment to another. Reusability Extent to which a program can be reused in other applications Interoperability Effort required to couple one system to another. Correctness Reliability Usability Integrity Efficiency

Operation Correctness The extent to which a program satisfies its specifications and fulfills the customer’s mission objectives Reliability The extent to which a program can be expected to perform its intended function with required precision. Efficiency The amount of computing resources required by a program to perform its function

Operation Integrity Extent to which access to software or data by unauthorized persons can be controlled. Usability Effort required to learn, operate, prepare input, and interpret output of a program

Revision Maintainability Effort required to locate and fix an error in a program Flexibility Effort required to modify an operational program Testability Effort required to test a program to ensure that it performs its intended function

Adaptation Portability Effort required to transfer the program from one hardware and/or software system environment to another Reusability Extent to which a program can be reused in other applications Interoperability Effort required to couple one system to another

Measuring Quality Correctness Maintainability Integrity Usability

Measuring Correctness Degree to which software performs its function Defects/FP or Defects/KLOC Defects verify lack of conformance to requirements These are problems reported by the user after release Defects are counted over a standard period of time, typically during the first year of operation

Maintainability The ease with which a program can be corrected if an error is encountered, adapted if environment changes, enhanced if the customer requires an enhancement in functionality Its an ‘indirect measure’

Measuring Maintainability MMTC – mean time to change Time it takes to analyze the change request, design an appropriate modification, implement the change, test it, and implement it Spoilage – cost oriented metric The cost to correct defects encountered after the software has been released to the users

Integrity Software’s ability to withstand attack (both accidental and intentional) to its security. To measure integrity, two additional attributes are needed. threat security.

Integrity Threat is the probability (derived or measured from empirical evidence) that an attack of a specific type will occur within a given time Security is the probability that an attack of a specific type will be repelled. Integrity = Σ [(1-threat) x (1-security)]

Usability It is a measure of user friendliness Can be measured in terms of 4 characteristics: Physical or intellectual skill required learn the system The time required to become moderately efficient in the use of system The net increase in productivity A subjective assessment

Defect Removal Efficiency It’s the valuable at both the project and process level. Effectiveness of the quality processes during development as a percentage of total defects DRE = E/(E+D) E – errors found before delivery D – errors found after delivery (typically within the first year of operation)

Defect Removal Efficiency Capers Jones 1997 Sample Size – 1500 Projects