Quality Standards D.Sivaraam Presentation At VLB College of Arts and Science On 4th Feb 2005 10/17/08
1
Introduction
10/17/08
Quality Standards Need of Standards Types of Standards Standards used in Software Industry Objective
2
Types of Standards
10/17/08
Project Level Standards Organizational Level Standards Global Level Standards
3
Project Level Standards
10/17/08
Naming Convention GUI Standards Coding Standards Error Message Standards
4
Organization Level Standards
10/17/08
Naming Convention Coding Standards Error Message Standards
5
Global Level Standards
10/17/08
ISO 9001 2000 CMM
6
Naming Convention
Eg: tbMastUser tbTranPurchaseHdr intUser_UserID vchUser_UserName g_str f_str
10/17/08
7
GUI Standards
10/17/08
Screen Sizes Resolution Colors Formats Fonts Controls
8
GUI Standard
10/17/08
More user friendly Less effort for training Project Level
9
Error Message Standards
10/17/08
Uniformity in expressing the message. More user friendly Icons Used helps the user to understand what happened
10
Coding Standard
10/17/08
Project Level Organizational Level Easy for code walk through / review Any programmer can do any program. Easy for maintenance
11
ISO Standards
10/17/08
ISO 9001 2000 Introduction
12
ISO 9001 2000
10/17/08
History Started in 1979 First Release Made in 1987 Second Release in 1994 Third Release in 2000
13
Principles of ISO 9001 2000 Focus 2. Leadership 3. Involvement of People 4. Process Approach
10/17/08
1. Customer
14
Principles of ISO 9001 2000 5. System Approach 6. Continual Improvement 7. Factual approach to decision making. 8. Mutually beneficial supplier relationships
10/17/08
15
ISO 9001 2000 Clauses
1. Scope
2. Normative Reference
This section contains the dated references, subsequent amendments to, or revisions of, any of these publications do not apply…etc
3. Terms and Definitions
10/17/08
Divided into two sub clauses and describes the scope.
This sections gives the terms used in the standard and definitions of the words used. 16
ISO 9001 2000 Clauses
4. Quality Management System - Defining the process - Defining the sequence and interaction of processes
10/17/08
- Documentation requirements - Maintenance of Records
17
ISO 9001 2000
10/17/08
4. Quality Management System Quality Manual Quality Objectives Quality Procedures Quality Forms and Formats Quality Guide Lines
18
ISO 9001 2000
5. Management Responsibility Management Commitment Customer Focus Quality Policy Planning Quality Objectives
10/17/08
19
ISO 9001 2000
5. Management Responsibility Responsibility, authority and communication Management Representative Internal Communication Management Review
10/17/08
20
ISO 9001 2000
6. Resource Management Human Resources Competence, awareness and training Infrastructure Work Environment
10/17/08
21
ISO 9001 2000
7. Product Realization Planning Customer related processes
Requirements Review Communication
10/17/08
22
ISO 9001 2000
7.Product Realization Design and Development Inputs Outputs Reviews Verification Validation
10/17/08
23
ISO 9001 2000
10/17/08
Purchasing
24
ISO 9001 2000
Product Realization Control of Production and service provision Validation of processes Identification and Traceability Customer Property Preservation of Products Control of Monitoring Devices.
10/17/08
25
ISO 9001 2000
8. Measurement, analysis and improvement Internal Audit Customer Feedback Control of Non confirming Product Continual Improvement Corrective Action Preventive Action
10/17/08
26
CMM
Capability Maturity Model Started in Nov 1986 for US department of defense First release is made on 15th Aug 1991
10/17/08
27
CMM
10/17/08
CMM is a common sense application of software or business management and quality improvement concepts to software development and maintenance. It can also be called as a commonly developed guide for evolving towards a culture of engineering excellence, model for organization improvement. 28
Structure of CMM
10/17/08
29
CMM
Common Features Commitment to Performs Ability to Perform Activities Performed Measurements Analysis Verification and Implementation
10/17/08
30
Level 1 – Initial
10/17/08
The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined, and success depends on individual effort and heroics. The system depends on individuals.
31
Level 2 Repeatable
Basic project management processes are established to track cost schedule and functionality. The necessary process discipline is in place to repeat earlier successes on projects with similar applications.
10/17/08
32
Level 2 Repeatable Key Process Areas Requirement Management
Software Project Planning
Project Planning Estimations
Software Project Tracking and Oversight
10/17/08
Contract User Requirement Document
Plan Vs Actual Reviewing , Analyzing and updating the Plan, if necessary 33
Level 2 - Repeatable Key Process Areas
Software Subcontract Management
Maturity of the Subcontractors.
Software Quality Assurance
SQA is expected to review and verify all the activities SQAG is integral part of software engineering and management processes.
Software Configuration Management
10/17/08
Requirement Management Project Planning Project Tracking.
To Ensure integrity of the product through out the Software development life cycle. 34
Level 3 - Defined
10/17/08
The Organizational Level Process are defined both for Management and Engineering activities. Process Documents are Created. Standards are Defined All the projects use an approved , tailored version of OSSP for developing and maintaining software.
35
Level 3 – Defined Key Process Areas
Organizational Process Focus
Organizational Process Definition
To develop the skills and knowledge
Integrated Software Management
10/17/08
Maintain and use of Software Process Assists OSSP , Software Life Cycles Tailoring Guidelines and criteria
Training Program
Developing, Maintaining and improving the processes..
Integrate software engineering and management
36
Level 3 – Defined Key Process Areas
Software Product Engineering
Inter Group Coordination
Participate actively with other engineering groups
Peer Reviews.
10/17/08
Well defined engineering process that integrates all the software engineering activities. Eg: requirement analysis, design , code and test
Remove defects early and efficiently. 37
Level 4 Managed
10/17/08
Effectiveness of the process are measured. Quality of the Product are measured. Both the software process and products are quantitatively understood and controlled.
38
Level 4 – Managed
Software Quality Management
Controlling the Process performance of the software project quantitatively.
Quantitative Process Management
10/17/08
Quantitative understanding of the Quality of the software products.
39
Level 5 Optimizing
10/17/08
Continuous process improvement is enabled by quantitative feedback from the process and from piloting innovative ideas and technologies.
40
Level 5 – Optimized
Process Change Management
10/17/08
Continuously improving the software processes to get improved Quality.
41
Level 5 – Optimized
Technology Change Management
10/17/08
Identifying the benefits of new technologies. –The focus is on performing innovation efficiency in an ever-changing world.
42
Level 5 – Optimized
Defect Prevention
10/17/08
Identifying the causes of defects and prevent from reoccurring.
43
Questions ? 10/17/08
44
Thank You
10/17/08
45