(Using Clip Art to Help Argue That) Certifying Software Professionals (is the Wave of the Future) Brian Demers February 24, 2000 CS 99 Prof. Kotz.

Slides:



Advertisements
Similar presentations
Quality management in corporate language training Lincq Workshop November 2013.
Advertisements

A presentation from June 20, 2000 Jim Brosseau The ‘How-To’ of Software Process Improvement.
DanMoz Dairies.Sarl Chimoio,Mozamique. Company BackGround & Future Located in Chimoio,Mozambique. Factory located on 250 Ha farm start Milk production.
Okosis Automation & Control Systems “The Automation Specialists !” Introductory Presentation
Tools for Efficient Implementation Tools for efficient implementation: Design environments ----GUI design tools Configuration management Good coding habits--PSP.
How ISO9001 Compares with CMM Mark C. Paulk JAN,1995 CMM version 1.1 ISO9001 July 1994 presented by Zhilan Zhou.
1 State of Michigan Achieving Software Process Improvement with Capability Maturity Model (CMM)
EECS 690 February 26. Professions Just to clear up some word confusion: In common usage, a professional is generally anyone who gets paid to do something.
Can We Trust the Computer?
©2006 OLC 1 Process Management: The Foundation for Achieving Organizational Excellence Process Management Implementation Worldwide.
Software Process Improvement Robin B. Hunter, Ph.D. Vol 2., p Presented by: Andrew Wheeler.
Humboldt University Berlin, University of Novi Sad, University of Plovdiv, University of Skopje, University of Belgrade, University of Niš, University.
Reliability and Safety Lessons Learned. Ways to Prevent Problems Good computer systems Good computer systems Good training Good training Accountability.
Professional Practice and Computing Curricula 2001 Eric Roberts Professor of Computer Science Senior Associate Dean of Engineering Stanford University.
SE 450 Software Processes & Product Metrics 1 Quality Systems Frameworks.
CMM Overview - 1 © Paul Sorenson CMPUT Software Engineering refs. IEEE Software, March 1988, 73-79, and IEEE Software, July 1993, (Capability.
Software Quality Assurance
WHAT DO WE KNOW ABOUT AGILE SOFTWARE DEVELOPMENT? Author : Tore Dyba and Torgeir Dingsoyr Reporter : 卓卿安.
Using A Defined and Measured Personal Software Process Watts S. Humphrey CS 5391 Article 8.
Standardization. Introduction A standard is a document. It is a set of rules that control how people should develop and manage materials, products, services,
Fraud Prevention and Risk Management
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
CS4/542- Software Engineering  Software Design and Development  Required Text -- Code Complete by Steve McConnell  (Focuses on the problems of designing.
Software Project Management
Software Engineering 2 Software and Society Mark J. Christensen Presented by: Feras Batarseh.
S T A M © 2000, KPA Ltd. Software Trouble Assessment Matrix Software Trouble Assessment Matrix *This presentation is extracted from SOFTWARE PROCESS QUALITY:
By Anthony W. Hill & Course Technology 1 User Support Management Beisse.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
CLEANROOM SOFTWARE ENGINEERING.
Professional Software Engineering: Fact or Fiction -Steve McConnell and Leonard Tripp Reprinted: IEEE Software, November/December 1999 Software Engineering:
CS3100 Software Project Management Week 26 - Quality Dr Tracy Hall.
Ch. 101 Epilogue. Ch. 102 Outline What will be the future of the field? What is the impact of SE on society? What ethical issues are raised by SE?
Software testing basic. Main contents  Why is testing necessary?  What is testing?  Test Design techniques  Test level  Test type  How to write.
 CS 5380 Software Engineering. Course Description  This course will survey software engineering methods and processes, including requirements, architecture,
1 Can We Trust the Computer? What Can Go Wrong? Case Study: The Therac-25 Increasing Reliability and Safety Perspectives on Failures, Dependence, Risk,
Lecture 1 Introduction to Software Engineering
Software Engineering - Spring 2003 (C) Vasudeva Varma, IIITHClass of 39 CS3600: Software Engineering: Standards in Process Modeling CMM and PSP.
By Ritesh Reddy Nagaram.  Organizations which are developing software processes are facing many problems regarding the need for change of already existing.
CS 4001Mary Jean Harrold 1 Can We Trust the Computer?
Security Policies and Procedures. cs490ns-cotter2 Objectives Define the security policy cycle Explain risk identification Design a security policy –Define.
Georgia Institute of Technology CS 4320 Fall 2003.
Ethics of Software Testing Thomas LaToza CS 210 Final Presentation 12 / 2 / 2002.
From Quality Control to Quality Assurance…and Beyond Alan Page Microsoft.
CS Process Improvement CMM Hans Van Vliet, Software Engineering, Principles and Practice, 3 rd edition, John Wiley & Sons, Chapter 6. W. Humphrey,
©Ian Sommerville 2004 Software Engineering. Chapter 28Slide 1 Chapter 28 Process Improvement.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
Construction, Testing, Documentation, and Installation Chapters 15 and 16 Info 361: Systems Analysis and Design.
EECS 690 February 26. Professions Just to clear up some word confusion: In common usage, a professional is generally anyone who gets paid to do something.
(1) Cam Moore Collaborative Software Development Laboratory Communication & Information Sciences University of Hawaii, Manoa
Personal Software Process PSP--Personal Software Process.
Reasons, Objectives and Realm of Standardization STANDARDIZATION IN SOCIAL INSURANCE: Reasons, Objectives and Realm – A Conceptual Approach - by: Jean-Victor.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 27 Software Engineering as Engineering.
Chapter 9 The People in Information Systems. Learning Objectives Upon successful completion of this chapter, you will be able to: Describe each of the.
CSE 403, Software Engineering Lecture 6
THE PROFESSION OF TEACHING. Professionals Professional : Possess a high degree of specialized theoretical knowledge, along with methods and techniques.
Dr. Rob Hasker. Classic Quality Assurance  Ensure follow process Solid, reviewed requirements Reviewed design Reviewed, passing tests  Why doesn’t “we.
C&I 212.  Why Teach  Activity  Reading Discussion  Teaching as a Profession  Notes  Review wiki (
Risk Assessment: A Practical Guide to Assessing Operational Risk
Can We Trust the Computer? FIRE, Chapter 4. What Can Go Wrong? What are the risks and reasons for computer failures? How much risk must or should we accept?
Advanced Software Engineering Dr. Cheng
Fundamentals & Ethics of Information Systems IS 201
Information and documentation media systems.
Professional Practices
CS4311 Spring 2011 Process Improvement Dr
Chapter 10 Software Quality Assurance& Test Plan Software Testing
A possible solution: Personal Software Process (PSP)
Reliability and Safety
Professional Software Engineering: Fact or Fiction -Steve McConnell and Leonard Tripp Reprinted: IEEE Software, November/December 1999 Software Engineering:
Week 13: Errors, Failures, and Risks
Presentation transcript:

(Using Clip Art to Help Argue That) Certifying Software Professionals (is the Wave of the Future) Brian Demers February 24, 2000 CS 99 Prof. Kotz

Whom do you trust? And how much do you trust them? Your friend Raoul Your house

Software Developers Today No common background –College grad –Transfer from another field –Self-taught Training is often inadequate (Or, “Did CS 23 really teach you about Software Engineering?”)

Consequences of the Current Situation Non-critical systems –Windows –Netscape –PC Blitz Critical systems: Therac-25 –Radiation treatment device –Hardware interlocks replaced by faulty software –2 dead, 4 crippled by radiation overexposure

How “professional” is software engineering? Deborah Johnson on Special Professions: Requires mastery of an esoteric body of knowledge Autonomy in work Professional society controls “admission” Fulfills important social need

Software Engineering vs. Other Professions SE could meet all four criteria Other professions fail some criteria, but are still thought of as professions All professionals: obligated to some minimum level of performance How can there be a minimum standard of performance with bugs?

BUGS! Errors in computer programs are inevitable …but programmers cannot be absolved of responsibility for serious or careless mistakes …and not all errors are inevitable

Why Certification? Establish a base quality level Expose SEs to more problems –Exposure happens before the job –Tests could change with advances/changes in technology Facilitates identification of negligent programming

Types of Certification Group: –Capability Maturity Model (CMM) –ISO 9001 Individual: –Personal Software Process (PSP) –Microsoft Certification

Group Certification CMM model –5 different levels of process maturity –Describes “what”, not “how” “Documented process” “Monitor and control performance” “Review” Does it work? –Great improvements in meeting ship dates –At one company, number of critical defects at ship time dropped to zero. –Teams claimed to experience higher overall efficiency

Individual Certification PSP –Devised by Software Engineering Inst. (creators of CMM) –Focuses on “how” – avoid introducing error to begin with –Practice large-scale techniques on small problems –Quantitatively analyze results Does this work? –Much improved ability to estimate product completion –EKLOC: dropped from 100 to 20 –LOC/hr remained constant –Shorter test times claimed

Conclusions Ethically, there is a class of problems which good design and implementation principles would help prevent Certification of software engineers: –Seems to help prevent these problems –Increases reliability and productivity overall –Protects against lawsuits in the future? What do you think?