SOFTWARE QUALITY ASSURANCE Asst. Prof. Dr. Selim BAYRAKLI Maltepe University Faculty of Engineering SE 410.

Slides:



Advertisements
Similar presentations
HOW TO EVALUATE A MOBILITY PROJECT Training Unit 11.1 Procedures, tools and roles for the evaluation of a mobility project.
Advertisements

Effectively applying ISO9001:2000 clauses 6 and 7.
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
More CMM Part Two : Details.
Stepan Potiyenko ISS Sr.SW Developer.
Software Quality Metrics
Planning a measurement program What is a metrics plan? A metrics plan must describe the who, what, where, when, how, and why of metrics. It begins with.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
SE 470 Software Development Processes James Nowotarski 12 May 2003.
School of Computing, Dublin Institute of Technology.
Capability Maturity Model (CMM) in SW design
Software Configuration Management (SCM)
Software Engineering Project Management Presented by James Roberts EEL6883 Spring ‘07.
ISO 9000 Certification ISO 9001 and ISO
Software Configuration Management
Standardization. Introduction A standard is a document. It is a set of rules that control how people should develop and manage materials, products, services,
Introduction to Computer Technology
Release & Deployment ITIL Version 3
Chapter : Software Process
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
Chapter 10.
Chapter 4 Interpreting the CMM. Group (3) Fahmi Alkhalifi Pam Page Pardha Mugunda.
Software Project Management
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
Chapter 2: Software Process Omar Meqdadi SE 2730 Lecture 2 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Chapter 2 Process: A Generic View
Lecture 1 Introduction to Software Engineering
Software Engineering Lecture # 17
Software Project Management Lecture # 7. What are we studying today? Chapter 24 - Project Scheduling  Effort distribution  Defining task set for the.
1 Chapter 5 Software Engineering Practice. 2 What is “Practice”? Practice is a broad array of concepts, principles, methods, and tools that you must consider.
10/16/2015Bahill1 Organizational Innovation and Deployment Causal Analysis and Resolution 5 Optimizing 4 Quantitatively Managed 3 Defined 2 Managed Continuous.
Software process improvement Framework for SPI SPI support groups, maturity and immaturity models Assessment and gap analysis Education and training Selection.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
a guidance to conversion
Paul Hardiman and Rob Brown SMMT IF Planning and organising an audit.
 Management ◦ The activities and tasks undertaken by one or more persons for the purpose of planning and controlling the activities of other in order.
Software Engineering - I
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
QUALITY. QUALIDOC Web site: Telephone: 44+ (0) JEAN WHITE.
Process: A Generic View
Ch-1 Introduction The processes used for executing a software project have major effect on quality of s/w produced and productivity achieved in project…
Principles of Computer Security: CompTIA Security + ® and Beyond, Third Edition © 2012 Principles of Computer Security: CompTIA Security+ ® and Beyond,
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming.
Software Engineering Lecture # 1.
Software Engineering (CSI 321) Software Process: A Generic View 1.
MSA Orientation – v203a 1 What’s RIGHT with the CMMI?!? Pat O’Toole
SE513 Software Quality Assurance Lecture12: Software Reliability and Quality Management Standards.
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
Submitted By: Tanveer Khan M.Tech(CSE) IVth sem.  The ISO 9000 standards are a collection of formal International Standards, Technical Specifications,
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Advanced Software Engineering Dr. Cheng
School of Business Administration
Chapter 11: Software Configuration Management
CS4311 Spring 2011 Process Improvement Dr
Chapter 10 Software Quality Assurance& Test Plan Software Testing
Software Engineering (CSI 321)
Quality management standards
Engineering Processes
CMM Overview A Focus on Level 2
Lecture 09:Software Testing
BASIC DEFINITIONS Errors : An error is a mistake, misconception, or misunderstanding on the part of a software developer. In the category of developer.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 2 Process: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Chapter 11: Software Configuration Management
Prepared and Presented By:- Abhishek Rautela
Chapter # 8 Quality Management Standards
Presentation transcript:

SOFTWARE QUALITY ASSURANCE Asst. Prof. Dr. Selim BAYRAKLI Maltepe University Faculty of Engineering SE 410

CHAPTER 2 SOFTWARE PROCESS 2 SE Software Quality Assurance

3 Process Concept Process for Software Aim of Process Technology Conceptual Model of a Process What is Software Engineering Process Process Approach Software Process Establishment Software Process Assessment Software Process Improvement Organization and Process Overview

What is Process SE Software Quality Assurance 4 “Product is not important but Process” Developing the software and products integrated with the software – plus – activities, methods and applications that are used for maintenance

Process Concept SE Software Quality Assurance 5 The aim of process is to develope a standard, to reduce variabilities and to provide consistent enhancements. Characteristics of a Process; Process is a way of performing a job to realize an aim, Generally it consists of sub-processes, steps and operaitons, Documented as written and graphically, Repeatable, Has inputs and outputs, Has actors, Has rules. Can be defined as simple or complex.

Process Concept (cont) SE Software Quality Assurance 6 Example; Customer Relations can be defined as a single process. Or you can devide this process into sub processes like; market research process, capturing client requirements process, feasibility process, modeling requirements.

Example: A Good Organisation Process SE Software Quality Assurance 7 Test engineer writes up a problem report and sends it to project manager. Project manager checks out the problem report and arranges a change request. Then sends the request to the analyst. The Analyst analyses the change request, indicates additional modules and performs requested changes. Afterwards design changes are made and the document «Change Request 1» is produced.

Example: A Good Organisation Process (cont) SE Software Quality Assurance 8 The configuration manager modifies requirements and design documents configuration. Gives the «Change Request 1» to the programmer. Programmer modifies/updates the code. Gives the new code back to the configuration manager. The configuration manager sends the new code to testing and integration. If the results are positive, the product can be released to market.

Process Concept for Software SE Software Quality Assurance 9 Software Process is the definition of how the tasks are performed like implementation, management, planning, support, enhancement.

Process Concept for Software (cont) SE Software Quality Assurance 10 Examples of Software Processes; Software Specification (Engineering), Design & Implementation (Engineering), Verification, Validation (Support), Execution (Support), Quality Management (Management), Project Management (Management).

Aim of Process Technology SE Software Quality Assurance 11 To produce a process model and to base that model upon all softwsare operations. Besides to provide computer aided process support.

Conceptual Model of a Process SE Software Quality Assurance 12 One of the main factors of the process model is the actor and its role. Other factors are activities, products, tools and policies.

What is Software Engineering Process SE Software Quality Assurance 13 The series of all software engineering activities that are essential to make the client’s requirements into software. Software engineering process consists of technical methods and automated tools.

Process Approach SE Software Quality Assurance 14 There are three stages in Software Process: Software Process Establishment Software Process Assessment Software Process Improvement

Software Process Establishment SE Software Quality Assurance 15 To achieve a stable production environment by identifying and documenting processes, staff training, starting implementation and being on the track.

Software Process Establishment (cont) SE Software Quality Assurance 16 Determine and analyse reference model Determine and analyse your own needs Define processes Work with your process system between 1-3 year and make necessary changes.

Software Process Assessment SE Software Quality Assurance 17 SPA is examining and grading the software processes of an organization in a disipled way. Two objectives: Create a program to enhance the process, Determining abilities (to assign job/project). Assessment is based on an international standard method.

Process Assessment (cont) SE Software Quality Assurance 18 There are different models and standards: CMM, Bootstrap, CMMI, and ISO grades the process or the software developer team. ISO 9001 and TickIT grades as «Passed» or «Failed». Organization can have their own models.

Software Process Improvement SE Software Quality Assurance 19 According to the assessment results, a plan must be prepared and applied to change the processes in an appropriate and required way. Then the results must be re- evaluated to see whether the expected improvement is provided or not. Provides to perform organisation’s business objectives; productivity growth, quality improvement, Client satisfaction.

Process Improvement (cont) SE Software Quality Assurance 20 SPI can be performed; to gain a targeted grade, for continuous improvement,

The Aim of Measure and Enhancement SE Software Quality Assurance 21 SPA Where are we? Where is the world? BusinessRequirements Comparisonstandards Where do we want to be

Process Assessment Environment SE Software Quality Assurance 22 Process ProcessImprovementSkillDetermination Process Assessment Determines Changes Analyses Determines skills and risks motivates guides guides

Organisation and Process SE Software Quality Assurance 23 A software of high quality can only be developed with an appropriate infrastructure. The maturity level of the organisations effects the quality of the software directly.

Mature Organisations… SE Software Quality Assurance 24 A skill can be found in organization-wide to manage the software development and maintenance. The software development process is delivered to all employee and new staff correctly. All activities are carried out with regard to a certain plan. Roles and responsibilities are determined for the Project and organisation.

Immature Organisations… SE Software Quality Assurance 25 Software development processes are not documented. Processes are developed during the Project extemporarily. No specific software development process. Managers are always busy to resolve crisis Activities for quality improvement are usually ignored because of late delivery.