Quality Assurance Experiences Pete Nordquist Intel / Bear Creek / SOU.

Slides:



Advertisements
Similar presentations
Slide 1 Shall Lists. Slide 2 Shall List Statement Categories  Functional Requirements  Non-Functional Requirements.
Advertisements

System Integration Verification and Validation
Chapter 9 Testing the System, part 2. Testing  Unit testing White (glass) box Code walkthroughs and inspections  Integration testing Bottom-up Top-down.
Solid Palette Gradient Palette I Gradient Palette II APPLYING THESE COLORS Click on the desired color Click on the paintbrush tool located.
R&D SDM 1 Metrics How to measure and assess software engineering? 2009 Theo Schouten.
SE 555 Software Requirements & Specification Requirements Quality Attributes.
CS 325: Software Engineering March 26, 2015 Software Quality Assurance Software Metrics Defect Injection Software Quality Lifecycle Measuring Progress.
Software Process and Product Metrics
Chapter 11: Testing The dynamic verification of the behavior of a program on a finite set of test cases, suitable selected from the usually infinite execution.
Introduction to Software Testing
Non-functional requirements
Software Quality SEII-Lecture 15
1 Requirements Analysis and Design Engineering Southern Methodist University CSE 7313.
Software Project Management Fifth Edition
Software Quality Assurance WELCOME. Portnov Computer School Mikhail Portnov  1978BSEE (major in Telecommunications)  1983MS in Math  Post-Graduate.
Chapter 10.
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.
1 Software Quality CIS 375 Bruce R. Maxim UM-Dearborn.
Rational Requirements Management with Use Cases v5.5 Copyright © Rational Software, all rights reserved 1Welcome! Rational Requirements Management.
Software engineering. What is software engineering? Software engineering is an engineering discipline which is concerned with all aspects of software.
Patterns, effective design patterns Describing patterns Types of patterns – Architecture, data, component, interface design, and webapp patterns – Creational,
Technology for a better society TDT4140 Software Engineering : 1 Experiences from Requirements Engineering: Coping with requirements in large,
Software Measurement & Metrics
Review for the Final Exam CSCI Software Project Management.
Drexel University CS 451 Software Engineering Winter Yuanfang Cai Room 104, University Crossings
Software Testing and Quality Assurance Software Quality Assurance 1.
OOSE Use Case. Requirement Functional: –Features, capabilities, and security Non Functional: –Usability: Human factors, help, and documentation –Reliability:
Software Methods Mö/ slide 1 Methods and Techniques of Software Quality Management ICEL Quality Management Systems: Methods and Techniques of Software.
GBIF Mid Term Meetings 2011 Biodiversity Data Portals for GBIF Participants: The NPT Global Biodiversity Information Facility (GBIF) 3 rd May 2011.
CS551 - Lecture 5 1 CS551 Lecture 5: Quality Attributes Yugi Lee FH #555 (816)
Quality Models in Software Engineering Literature: An Analytical and Comparative Study Rafa E. Al-Qutaish, PhD Al Ain University of Science and Technology.
Quality Factors Chapter Three. Question To know that quality has improved, it would be helpful to be able to measure quality. How can we measure quality?
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Requirements CS121 Spring Administrivia new student: Guillermo artist: Jackie Wijaya.
SEN 460 Software Quality Assurance
1 Software Architecture in Practice Quality attributes (The amputated version)
Hussein Alhashimi. “If you can’t measure it, you can’t manage it” Tom DeMarco,
TESTING (S,S,AND A,B) By KARTHIKEYAN KANDASAMY. TESTING Scenario testing – 1.System & 2. Usecase Defect bash System o Functional and non functional testing.
Review for the Final Exam CSCI Software Project Management.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
System Testing 12/09. Hierarchy of Testing Testing Program Testing Top Down Bottom Up Integration TestingUnit Testing System Testing Big Bang Sandwich.
INFORMATION ASSURANCE POLICY. Information Assurance Information operations that protect and defend information and information systems by ensuring their.
ISQB Software Testing Section Meeting 10 Dec 2012.
Analysis of Current Maturity Models and Standards
Evolutionary requirements
(Professional Business Analyst Training organisation)
Source & Courtesy: Doc. S. Dapkūnas
Software Quality Assurance Software Quality Factor
Black Box Testing PPT Sources: Code Complete, 2nd Ed., Steve McConnell
Chapter 18 Maintaining Information Systems
Software testing
Software Requirements
Unified Process(UP) popo.
Software Quality Engineering CS- 449
UNIT II.
Introduction to Software Testing
Charakteristiky kvality
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
Evolutionary Requirements
Progression of Test Categories
Managing Software Quality
Information Assurance Metrics Taxonomy*
Software Requirements
Quality Factors.
Software Requirements
ISO/IEC Systems and software Quality Requirements and Evaluation
Software Verification and Validation
Presentation transcript:

Quality Assurance Experiences Pete Nordquist Intel / Bear Creek / SOU

Background 4 months – Bear Creek Corp. 14 Years – Intel Corp. MSCS – Oregon Graduate Institute Math Ed / Music Ed – George Fox College

Why Test? Validate system requirements met Validate system integration Provide independent verification Advocate for the users

Furps FUNCTIONALITY: Feature Set - Capabilities - Generality – Security Does it do what it is supposed to do?

fUrps USABILITY: Human Factors - Aesthetics - Consistency – Documentation Can the user make it do what it is supposed to do?

fuRps RELIABILITY: Frequency/Severity of Failure - Recoverability - predictability - Accuracy - Mean Time to Failure How often does it do what it is supposed to do? Under normal conditions Under boundary conditions

furPs PERFORMANCE: Speed - Efficiency - Resource Consumption - Throughput - Response Time Does it do what it is supposed to do in a reasonable amount of time?

furpS SUPPORTABILITY: Testability - Extensibility - Adaptability - Maintainability - Compatibility - Configurability - Serviceability - Installability – Localizability How easy is it to keep it doing what it is supposed to do?

Hints Concentrate on “Sunny Day” scenario Learn everything you can about how the product is supposed to work then extrapolate to how it ought to work. Look for consistency / point out holes Use product under conditions as close as possible to those the real users will encounter. Integrate, integrate, integrate “Trust, but verify”

Politics of Testing Make friends of developers Educate management on risks: design problems, test coverage. Remember you won’t be paid if product does not go out the door. Remember you won’t be paid if product goes out the door and doesn’t work.

FURPS reference: Practical Software Metrics for Project Management and Process Improvement Practical Software Metrics for Project Management and Process Improvement by Robert B. Grady Prentice-Hall ECS Professional 270 pages (May 1992) Prentice Hall PTR; ISBN:

Other references Capability Maturity Model ISO Testing Computer Software -- Cem Kaner, et al; html

Backup

Quality Week 2000 Protecting Intellectual Property in an Open Source World 13th International Software / Internet Quality Week Software Research, Inc