Quality Engineering.

Slides:



Advertisements
Similar presentations
Benchmarking as a factor of an economic crisis consequences levelling V. N. Ostrovkaya Doctor of Economics, Head of Projects and Innovations Chair, North.
Advertisements

Leadership and Strategic Planning
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management.
Components of a Product Vision/Strategy
Chapter 4 Quality Assurance in Context
Establishing Financial Direction
HSA 171 CAR. 1436/4/  Planning Process.  Elements of Planning.  Steps in Operating Planning Process. 5.
Software Quality Engineering Roadmap
School of Computing, Dublin Institute of Technology.
1 Software project management (intro) An introduction.
7-1. McGraw-Hill/Irwin Copyright © 2008 by The McGraw-Hill Companies, Inc. All Rights Reserved. Developing Marketing Strategy Chapter 07.
Leadership and Strategic Planning
Software Process and Product Metrics
CSC230 Software Design (Engineering)
Capability Maturity Model
Marketing Management Indicator 1.03 Employ marketing-information to develop a marketing plan.
Software Project Management Fifth Edition
SAS 03/ GSFC/SATC-ERAU-DoC Fault Tree Analysis Application for Safety and Reliability Massood Towhidnejad Embry-Riddle University Dolores Wallace & Al.
Ch.4: QA in Context  QA and the overall development context Defect handling/resolution How alternative QA activities fit in process Alternative perspectives:
COURSE TITLE: 1 Software Quality Assurance. Course Aims Introduction to software quality assurance. Software testing terminology. Role and responsibility.
 The software systems must do what they are supposed to do. “do the right things”  They must perform these specific tasks correctly or satisfactorily.
N By: Md Rezaul Huda Reza n
Copyright © 2006 by South-Western, a division of Thomson Learning, Inc. All rights reserved. Chapter 19 Pricing Strategies.
Architecture Business Cycle
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 31 Slide 1 Process Improvement u Understanding, Modelling and Improving the Software Process.
Developing and Using a Sales System. Developed To Help TAB Members Achieve Greater Sales And Profits  Uses proven methods that have been used to take.
Logistics and supply chain strategy planning
The Targeting Outcomes of Programs (TOP) framework.
Software Engineering Software Process and Project Metrics.
Chapter 6 : Software Metrics
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 26 Slide 1 Software cost estimation 1.
THE MANAGEMENT AND CONTROL OF QUALITY, 5e, © 2002 South-Western/Thomson Learning TM 1 Chapter 5 Leadership and Strategic Planning.
1 Conducting a needs assessment - 7 Barbie E. Keiser University of Vilnius May 2007.
This chapter is extracted from Sommerville’s slides. Text book chapter
Chapter 10 Marketing Channels and Supply Chain Management.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Software Project Management Lecture # 3. Outline Chapter 22- “Metrics for Process & Projects”  Measurement  Measures  Metrics  Software Metrics Process.
Software Metrics – part 2 Mehran Rezaei. Software Metrics Objectives – Provide State-of-art measurement of software products, processes and projects Why.
Software Testing and Quality Assurance Software Quality Assurance 1.
Controlling MRK151 Chapter 6. Controlling Detecting and correcting significant variations in the results obtained from planned activities. Controlling.
OHT 17.1 © Pearson Education Limited 2003 Brassington and Pettitt: Principles of Marketing, 3rd Edition Personal selling and sales management.
21-22 May 2004IMPROQ 2004 / Impact of SW Processes on Quality Workshop 1 Quality for Components: Component and Component- Based Software Quality Issues.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
1 Chapter 3 1.Quality Management, 2.Software Cost Estimation 3.Process Improvement.
2.4 Key Management Roles KEY CONCEPT
SOFTWARE PROCESS AND PROJECT METRICS. Topic Covered  Metrics in the process and project domains  Process, project and measurement  Process Metrics.
Chapter 13: Software Quality Project Management Afnan Albahli.
Ensure that the right functions are performed Ensure that the these functions are performed right and are reliable.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming.
The Fundamentals of the Global Marketing Mix
Chapter 22 Metrics for Process and Projects Software Engineering: A Practitioner’s Approach 6 th Edition Roger S. Pressman.
Positioning Tools. Positioning Developing a specific marketing mix to influence potential customers’ overall perception of a brand, product line, or organization.
Chapter 3: Purchasing Research and Planning Strategic Planning for Purchasing Strategic planning for purchasing involves the identification of critical.
This has been created by QA InfoTech. Choose QA InfoTech as your Automated testing partner. Visit for more information.
MARKETING OVERVIEW BDI3C
CH5- SETTING GOALS AND OBJECTIVES, IDENTIFYING STRATEGIES AND TACTICS
Chapter 19 Pricing Strategies.
Software Project Planning &
Software Quality Engineering
PLANNING.
Chapter 13 Quality Management
Software Quality Assurance
Capability Maturity Model
Software metrics.
Applying Use Cases (Chapters 25,26)
Applying Use Cases (Chapters 25,26)
Metrics for Process and Projects
Capability Maturity Model
Leadership and Strategic Planning
Presentation transcript:

Quality Engineering

Quality Engineering Activities Pre-QA activities: Quality planning. (a) Set specific quality goals. (b) Form an overall QA strategy, which includes two sub-activities: Select appropriate QA activities to perform. Choose appropriate quality measurements and models to provide feedback, quality assessment and improvement.

Quality Engineering Activities In-QA activities: Executing planned QA activities and handling discovered defects. Select QA activities Deal with the discovered problems

Quality Engineering Activities Post-QA activities: Quality measurement, assessment and improvement Provide quality assessment and feedback so that various management decisions can be made and possible quality improvement initiatives can be carried out.

QA Activities: Mapping from defect-centered view to V & V view

Feedback in Quality Engineering Short term direct feedback to the QA activities The short term feedback to QA activities typically provides information for progress tracking, activity scheduling, and identification of areas that need special attentions. For example, various models and tools were used to provide test effort tracking, reliability monitoring, and identification of low- reliability areas for various software products developed in the IBM Software Solutions Toronto Lab to manage their testing process (Tian, 1996).

Feedback in Quality Engineering long-term feedback to the overall quality engineering process Feedback to quality planning so that necessary adjustment can be made to quality goals and QA strategies. For example, if the current quality goals are unachievable, alternative goals need to be negotiated. If the selected QA strategy is inappropriate, a new or modified strategy needs to be selected. Similarly, such adjustments may also be applied to future projects instead of the current project. Feedback to the quality assessment and improvement activities. For example, the modeling results may be highly unstable, which may well be an indication of the model inappropriateness. In this case, new or modified models need to be used, probably on screened or pre-processed data.

Quality Planning: Goal Setting and Strategy Formation 1. Setting quality goals by matching customer’s quality expectations with what can be economically achieved by the software development organizations in the following sub-steps: (a) Identify quality views and attributes meaningful to target customers and users. (b) Select direct quality measures that can be used to measure the selected quality (c) Quantify these quality measures to set quality goals while considering the market environment and the cost of achieving different quality goals. 2. In forming a QA strategy, we need to plan for its two basic elements: (a) Map the above quality views, attributes, and quantitative goals to select a specific set of QA alternatives. (b) Map the above external direct quality measures into internal indirect ones via selected quality models. This step selects indirect quality measures as well as usable models for quality assessment and analysis.

Quality Planning: Goal Setting and Strategy Formation 1. We need to select or dejne the quality measurements and models commonly accepted by the customers and in the software engineering community. For example, as pointed out in Chapter 2, reliability and safety are examples of correctness-centered quality measures that are meaningful to customers and users, which can be related to various internal measures of faults commonly used within software development organizations. 2. We need tofind out the expected values or ranges of the corresponding quality measurements. For example, different market segments might have different reliability expectations. Such quality expectations are also influenced by the general market conditions and competitive pressure.