1 Software Testing and Quality Assurance Theory and Practice Chapter 16 Test Team Organization.

Slides:



Advertisements
Similar presentations
Configuration Management
Advertisements

1.Quality-“a characteristic or attribute of something.” As an attribute of an item, quality refers to measurable characteristics— things we are able to.
Software Quality David Jones, Director. 2 Agenda What is it and why is it important? How do we deliver it? Conclusions.
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
More CMM Part Two : Details.
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
Project Closure CHAPTER FOURTEEN Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
 Every stage from phase DESIGN in Software Development Process will have “design document” especially in analysis and design phases.  “Design document”
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
CS CS 5150 Software Engineering Lecture 27 People 2.
1 14. Project closure n An information system project must be administratively closed once its product is successfully delivered to the customer. n A failed.
Chapter 16 Strategically Managing the HRM Function Copyright © 2015 McGraw-Hill Education. All rights reserved. No reproduction or distribution without.
Software Testing and QA Theory and Practice (Chapter 16: Test Team Organization) © Naik & Tripathy 1 Software Testing and Quality Assurance Theory and.
Chapter 16 Maintaining Information Systems
OHT 16.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The objectives of training and certification The training and certification.
Chapter 10.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Matching PMBOK Section
Capability Maturity Model Part One - Overview. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
CPIS 357 Software Quality & Testing
Engineering Management From The Top Power Behind the Storage.
© 2010 The McGraw-Hill Companies, Inc. Managerial Accounting and the Business Environment Chapter 1.
Test Roles and Independence of Testing Telerik Software Academy Software Quality Assurance.
Management & Leadership
Chapter 5 Job Analysis.
Basic of Project and Project Management Presentation.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Software Project Management Lecture # 10. Outline Quality Management (chapter 26)  What is quality?  Meaning of Quality in Various Context  Some quality.
Quality Activity Matrix Presented by Sandra Toalston President, SanSeek 1.
Software Project Management Lecture # 11. Outline Quality Management (chapter 26 - Pressman)  What is quality?  Meaning of Quality in Various Context.
Georgia Institute of Technology CS 4320 Fall 2003.
QUALITY ASSURANCE MANAGEMENT CONTROLS Chapter 9. Quality Assurance (QA) Management is concerned with ensuring: 1) The information system produced by the.
Test Team Organization. 2  Test Groups  Integration Test Group  System Test Group  Software Quality Assurance Group  Quality.
3 1 Project Success Factors u Project management important for success of system development project u 2000 Standish Group Study l Only 28% of system development.
CS CS 5150 Software Engineering Lecture 24 People 2.
CS CS 5150 Software Engineering Lecture 26 People 2.
Principles of Computer Security: CompTIA Security + ® and Beyond, Third Edition © 2012 Principles of Computer Security: CompTIA Security+ ® and Beyond,
Succession Planning Based loosely on “Effective Succession Planning in the Public Sector,” 2007, Watson Wyatt Worldwide Based loosely on “Effective Succession.
Software Testing and Software Quality Assurance Process.
Software Quality Assurance SOFTWARE DEFECT. Defect Repair Defect Repair is a process of repairing the defective part or replacing it, as needed. For example,
Management & Leadership
Requisite Skills for IS Management and Interpersonal Skills.
2-1 Defining Team Success Chapter Nature of Team Success Managers and team members may see success differently Hackman’s three primary definitions.
Chapter 16 Maintaining Information Systems. Objectives:  Explain and contrast four types of system maintenance.  Describe factors affecting maintenance.
Cmpe 589 Spring Fundamental Process and Process Management Concepts Process –the people, methods, and tools used to produce software products. –Improving.
Software Project Management Lecture # 12. Outline Quality Management ( chapter 26 - Pressman )  SQA  Who does it?  SQA Activities  Software reviews.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
by: Er. Manu Bansal Deptt of IT Software Quality Assurance.
Advanced Software Engineering Dr. Cheng
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Pragmatics 4 Hours.
Configuration Management
Software Project Configuration Management
Software Engineering (CSI 321)
Software Configuration Management (SCM)
Systems Analysis and Design in a Changing World, 4th Edition
Testing Process Roman Yagodka ISS Test Leader.
Software and Systems Integration
Chapter 18 Maintaining Information Systems
Configuration Management
Quality Quality is “a characteristic or attribute of something.”
LEVEL OF TESTING J.ALFRED DANIEL, AP/CSE.
Project Management Process Groups
Chapter # 1 Overview of Software Quality Assurance
HHS Child Welfare National IT Managers' Meeting
CHAPTER 1: REVIEW.
Software Reviews.
Presentation transcript:

1 Software Testing and Quality Assurance Theory and Practice Chapter 16 Test Team Organization

2 Outline of the Chapter Test Groups Integration Test Group System Test Group Software Quality Assurance Group Quality Management Group System Test Team Hierarchy Effective Staffing of Test Engineers Recruiting Test Engineers Retaining Test Engineers Team Building

3 Test Groups There is no right or wrong ways to organize test teams The structure one chooses will affect productivity, quality, customer satisfaction, employee morale, and budget Unit tests are developed and executed by the software developers themselves, rather than an independent unit test group It is recommended to have at least two test groups: –integration test group –system test group The acceptance test group is formed on a demand basis consisting of people from different backgrounds The acceptance test group is dismantled after the project is completed

4 Integration Test Group The mandate of this group is to ensure that unit-tested modules operate correctly when they are combined The leader of the integration test group reports to the software development manager The software developers, who together built the modules, must be involved in performing integration testing In practice, the developers themselves may integrate the system The system architects are also involved in integration testing for complex systems The test group may perform other duties, such as: –code inspection, configuration management, release management, and management of development laboratory.

5 System Test Group The mandate of this group is to ensure that the system requirements have been satisfied and that the system is acceptable The system test group is truly an independent group, and they usually have a separate headcount and budget The manager of this group is a peer to the hardware or software development managers The system test group conducts different categories of tests as discussed in Chapter 8 The group executes business acceptance tests identified in the user acceptance test plan Figure 16.1: Structure of test groups

6 Software Quality Assurance Group Software quality assurance deals not only with the location of the defects, but also with mechanisms to prevent defects Software quality assurance group has a larger role in ensuring, conformance to the best development practices throughout the organization It is recommended to have a separate group for quality management work as shown in Figure 16.2, rather than assign quality management task to system test engineers. Figure 16.2: Structure of software quality assurance group.

7 Quality Management Group This group works on customizing software development processes and ensuring that processes are adhered to The group is responsible for creating and implementing a quality management program plan for the entire organization The group proactively works to drive process improvement initiatives across the organization Quality control is another term that is often used in the literature. Quality control is defined in the IEEE standard 610 as: A set of activities designed to evaluate the quality of developed or manufactured products The term is used in a production or hardware manufacturing environment, where large a number of physical items are produced

8 System Test Team Hierarchy Figure 16.3: System test team hierarchy.

9 Effective Staffing of Test Engineers A successful test team is made up of members whose strengths are complementary It is advisable to have people on the test team with diverse background and experience, such as: – developers –integration testers –information technology administrators –technical support personnel –technical writers –quality management personnel –experienced test engineers –recent graduates

10 Effective Staffing of Test Engineers It is useful to keep in mind the following five-C characteristics a good test engineer must possess. –Controlled,Comprehensive, Considerate, Critical and Competent In addition to the five-C characteristics, test engineers are expected to have the following skills –Have credibility with software developers –Understand developers’ terminologies –Know when the code is ready for testing –Be able to evaluate the impact of a problem on the customers –Assist software developers in expediting defect resolution –Reduce false-positive and false-negative results in testing –Develop expertise in test automation –Mentor the junior test engineers

11 Recruiting Test Engineers Figure 16.3: Six phases of the effective recruiting process

12 Retaining Test Engineers The following are key factors that positively impact the ability of an organization to retain good system test engineers –A Career Path –Training On-site commercial training: Public forum training In-house training Specialty training Mentoring –Reward System

13 Team Building The essential ingredients of a good team building: –Expectations –Consistency –Information Sharing –Standardization –Test Environments –Recognitions