focus When I started to develop SEI s Personal Software Process, I was The Personal Software Process: guest editor's introduction Status and Trends
|
|
- Bruno Barnett
- 8 years ago
- Views:
Transcription
1 focus guest editor's introduction The Personal Software Process: Status and Trends Watts S. Humphrey, The Software Engineering Institute When I started to develop SEI s Personal Software Process, I was both looking for new processes and methods and trying to satisfy my curiosity. I wanted to answer this question: Would process improvement principles work for individual software professionals? I had spent over 30 years in engineering and engineering management before I started working on software quality and process improvement. These methods worked for organizations and for large projects, but it was not clear how they would work for individuals, particularly those doing creative engineering work. While the principles seemed applicable, I was trained as an experimental physicist and thus needed to understand how a process worked at the atomic level before I could feel I really understood it. During my early PSP research, I was surprised by the insight I gained from using a defined, planned, and measured personal process, not only for routine work, but for creative work as well. After completing my initial PSP research some years ago, I have devoted the ensuing years to getting these principles adopted by individual engineers, software organizations, and the academic community. The four articles on the PSP in this issue examine the topic from various perspectives, but the fundamental question they all address is essentially the same: /00/$ IEEE November/December 2000 IEEE SOFTWARE 71
2 One of the most important factors in improving worker performance is prompt and explicit feedback. How can process improvement help individuals be more effective while doing intellectual work? PSP Overview PSP development is based in part on the quality management principles of W. Edwards Deming and Joseph M. Juran. 1,2 In a more general sense, these methods follow principles that Frederick Winslow Taylor introduced over 100 years ago. 3 Taylor invented what has been variously called task analysis, scientific management, or industrial engineering. He was the first to view manual work as something to analyze and improve, and the first to gather and analyze data to improve the performance of manual tasks. Peter Drucker asserts that Taylor s methods made factories possible and that they were largely responsible for the 50-fold increase in labor productivity over the last 100-plus years. 4 In his insightful book, Management Challenges for the 21st Century, Drucker describes the similarities and differences between manual and intellectual work. 4 The principal similarity is that both kinds of work involve sequences of tasks. Even though manual and intellectual tasks are significantly different, we can measure, analyze, and optimize both and thus apply Taylor s principles equally well. The principal difference between manual and intellectual work is that the knowledge worker is essentially autonomous. That is, in addition to deciding how to do tasks, he or she must also decide what tasks to do and the order in which to do them. The manual worker commonly follows a relatively fixed task order, essentially prescribed by the production line. So studying and improving the performance of intellectual work must not only address the most efficient way to do each task but also consider how to select and order these tasks. This is essentially the role of a defined process and a detailed plan. The process defines the tasks, task order, and task measures, while the plan sizes the tasks and defines the task schedule for the job being done. Besides Taylor s principles, the PSP also considers task selection, planning, and ordering. It shows engineers how to use a defined, measured, planned, and qualitycontrolled process to improve personal performance. When they use the PSP, engineers plan their work, measure the work as they do it, and when done, analyze the measures to improve their performance. We use a course and a textbook to teach engineers the PSP methods. 5 The course guides software professionals through 10 programming exercises that demonstrate how to apply project, process, and quality management methods when writing modulesized programs. By completing the exercises and analyzing their data, the engineers can see how a defined and measured process helps them do better work. They cannot argue that the PSP methods do not work for them, because they can see from their own data that they do. In the PSP course, engineers learn what a defined process is and how to use one. They learn how to make estimates and plans, what data to gather, how to gather data, and how to use data. They also learn how to plan, measure, and manage the quality of their work. The PSP is not only designed for writing module-sized programs, it also teaches general skills that software engineers can use in most aspects of their work, from the initial requirements and system design phases all the way through to final system test and delivery. PSP Course Results Because of the nature of the PSP course, the earliest evidence of its impact is from class data. 6 8 In using these data, we must know whether results are due to the course environment or the PSP material itself. Several published reports now show the PSP s benefits. One study showed that students improvements during the PSP courses were large and statistically significant. 6 Two other articles showed that when engineers were PSP trained, their job performance improved substantially. 9,10 The four articles in this issue add to this body of evidence. These data come from multiple studies, multiple PSP instructors, industrial and academic courses, and a broad mix of lan- 72 IEEE SOFTWARE November/December 2000
3 This Issue s Articles The article by Xiamong Zhong, Nazim Madhavji, and Khaled El Emam, Critical Factors Affecting Personal Software Processes, examines the detailed behavior of the PSP process. The authors measured the performance of 53 students and used regression methods to identify the variables responsible for the productivity and quality results obtained. As far as I know, this is the first article to examine the detailed relationships among the many variables involved in software work. It demonstrates the opportunity for important research with students or professionals who use the PSP. For example, by conducting studies of design methods, review techniques, language features, or tool functions, we could better understand how to develop software processes, tools, or methods to improve the performance of working engineers. Two of the articles address the PSP s use in industry. An Experience Report on the Personal Software Process by Jagadish Kamatar and Will Hayes shows that the PSP, when properly used, can result in substantial improvements. On the first reported project, Kamatar and three PSP-trained colleagues had only three system test defects for a product with 40,000 lines of code. Typical industrial system-test defect levels for such products range from 200 to 400. Kamatar also describes the feedback provided by the PSP data and how he used it to improve product quality and estimating accuracy. Applying the PSP in Industry by Maurizio Morisio describes the introduction of the PSP to an industrial organization. The problems he encountered concerned training, process design, data privacy, paperwork, and data gathering. In addition, he faced a problem common to almost all technology transition efforts: management s unwillingness to interrupt projects for long enough to completely train the engineers. In addressing these concerns, Marisio significantly changed the PSP process and course. As a result, the engineers used part of the PSP methods and obtained only limited benefits. However, the experiment provided useful insights, and the modified process appeared to provide some benefits. At least the engineers seemed to like the process, and the organization continues to use it. The Successful Diffusion of Innovations: A Guide for Software Development Organizations by Gina Green and Alan Hevner examines the introduction of innovative IT technologies, using the PSP as an example. The authors find, not surprisingly, that engineers are more satisfied with a technology and are more likely to use it when they have a choice in selecting it. Engineers also more readily accept technologies that improve their ability to predict the results of their work. In addition, the authors found that when programmers feel increasingly able to control the methods they use, their satisfaction and use of the methods actually decline. On reflection, this finding is consistent with PSP and the SEI s Team Software Process experience: engineers will readily accept and use a precisely defined process as long as it reduces workplace confusion and helps them do their jobs. guages and engineering environments. One of the most important factors in improving worker performance is prompt and explicit feedback We designed the PSP to provide this as an inherent part of the process. In fact, PSP practitioners often cite feedback as the reason for their conviction that the methods help them. So it is fair to say that the performance improvement shown by the PSP is at least partly due to the feedback the engineers get from their own data. Thus, the most pertinent questions are, Are these results unique to PSP courses, are they general, and does the effect persist? So far, as the articles in this issue and other experience show, the answer to all three questions is yes. Introducing the PSP The Green Hevner article provides useful guidance on introducing almost any new technology. It shows how to improve the acceptance of new methods and indicates damaging actions to avoid. For example, they note that practitioners will readily accept and adopt methods that help them reduce the complexity of their working processes. Further, for intellectual work like software, people will resist any attempt to force changes in the way they work. Finally, even new and attractive methods can be rejected if introduced in the wrong way or at the wrong time. The key message here is that software professionals are thinking people; they resent being ordered to do almost anything. If they are treated with respect and have a say in the changes that involve them, the results will be more successful. More specifically on PSP introduction, there are various ways to attack the transition problem. The approach taken by Marisio was to change the PSP process and training to better fit what the particular organization was willing to do. Although this approach has the advantage of initially overcoming user resistance, it has the disadvantage of allowing the desires of uninformed users to drive process design. Be- November/December 2000 IEEE SOFTWARE 73
4 Where PSP introduction has failed, the fundamental problem has been that it was viewed as an engineering training program rather than as an organizationwide process change. cause users almost certainly do not have the training or experience to design a software process and its introduction method, poor results are likely. Several other organizations have objected to the full 14 days of PSP training required for industrial introduction and have devised their own special four- to six-day courses. As Kamatar reports, when engineers receive only limited PSP training, they do not learn the methods sufficiently well to use them in practice. Similarly, several organizations have tried to use the PSP with little or no guidance or adaptation. While this has worked in two cases that I am aware of, generally the engineers soon stop using the PSP. The stated reasons were that the environment didn t encourage PSP use, management didn t support it, and the other engineers were not using it. Under these conditions, engineers generally find it difficult to continue to use the PSP. We at the SEI have worked for the last five years on PSP introduction and have found results similar to those reported by Marisio and by Kamatar and Hayes. The training required is substantial, and organizations are often reluctant to make that large an investment. However, without proper training and support, the PSP methods generally will not be used. Where PSP introduction has failed, the fundamental problem has been that it was viewed as an engineering training program rather than as an organization-wide process change. PSP Training Since training is such an important part of PSP introduction, it would be helpful to know how much training is required. While developing and learning the PSP, I wrote 62 programs in Pascal, Object Pascal, and C++. I then developed a course to teach these personal-process methods to others. I had hoped that others would learn much more rapidly than I had, so I only used 10 programming exercises in the PSP course. To date, our data show that the full PSP course with 10 exercise programs has been effective in teaching both students and working engineers how to use the PSP. From available course data, however, it is also clear that the high rate of improvement during the course continues right up through program 10. Thus, additional exercises could be beneficial. Although some experienced PSP instructors have concluded that more exercises would help, we do not have data to support this conclusion. At the opposite extreme, when engineers only complete six or seven PSP exercises, they generally do not learn the methods or use them afterwards. Perhaps most important, because partially trained engineers do not use the method properly, they cannot complete PSP learning on the job. However, as the three articles in this issue and others have found, even modest use of the PSP methods can be beneficial. 9,14 Learning the PSP process appears to be fundamentally different from the way people learn other topics. With programming languages, for example, introductory courses usually teach programmers enough so they can start using the language. Then they can continue learning the more subtle aspects of the language as they use it on the job. We need to identify the level of fluency required before engineers will properly use the PSP in practice. Then they would presumably become more competent with experience. While the critical point where learning will continue is likely to be different for different people, we at the SEI expect it will probably be at or very near the 10 exercise programs in the current PSP course. Another factor tends to help people learn a programming language but not the PSP. After taking an initial language course, working engineers generally have no choice but to use that language in their work. With the PSP, they can always choose to revert to their previous practices. This is a key challenge of industrial PSP introduction and one of the reasons for the development of the Team Software Process. Some Thoughts on the Future Based on results to date, using a defined, planned, and measured personal process appears to offer many benefits. Assuming that further experience confirms these early results, we can expect the PSP to be widely 74 IEEE SOFTWARE November/December 2000
5 adopted and used. From the experiments reported here and elsewhere, it is also clear that industrial introduction of the PSP will not be easy. To guide organizations through such a comprehensive change program and to facilitate industrial transition to and use of PSP practices, the SEI has developed the Team Software Process. 10,15 17 We at the SEI have concluded that a team-based training and introduction strategy is both easiest to implement and most frequently effective for industrial organizations. Presuming that the demand for skilled software professionals continues to increase, the most appropriate way to introduce the PSP would be through the educational system, just as with other professional disciplines. Rather than having students first learn undisciplined practices and then unlearn them, we should introduce disciplined methods at the beginning of the curriculum. Some universities have started offering such courses, and preliminary results are promising While several universities are also teaching an introductory TSP course to student teams, no published results are available. Additional information on the PSP and TSP is available at 8. P.M. Johnson and A.M. Disney, The Personal Software Process: A Cautionary Case Study, IEEE Software, Vol. 15, No. 6, Nov./Dec. 1998, pp P. Ferguson et al., Introducing the Personal Software Process: Three Industry Case Studies, Computer, Vol. 30, No. 5, May 1997, pp D. Webb and W.S. Humphrey, Using the TSP on the TaskView Project, Crosstalk, Vol. 12, No. 2, Feb. 1999, pp J.L. Dyer, Team Research and Team Training: A Stateof-the-Art Review, Human Factors Rev., The Human Factors Soc., Santa Monica, Calif., 1984, pp. 286, H.M. Parsons, What Happened at Hawthorne? Science, Vol. 183, Mar. 8, 1974, pp R.W. Swezey and E. Salas, eds., Teams: Their Training and Performance, Ablex Publishing Corp., Norwood, N.J., L. Prechelt and B. Unger, An Experiment Measuring the Effects of Personal Process (PSP) Training, IEEE Trans. Software Eng., in press. 15. W.S. Humphrey, Three Dimensions of Process Improvement, Part III: The Team Process, Crosstalk, Vol. 11, No. 4, Apr. 1998, pp W.S. Humphrey, Introduction to the Team Software Process, Addison-Wesley, Reading, Mass., W.S. Humphrey, The Team Software Process (TSP), Tech. Report CMU/SEI-2000-TR-023, Software Eng. Inst., Carnegie Mellon Univ., Pittsburgh, Oct T.B. Hilburn, PSP in Academia and Training, Forum for Academic Software Eng., L. Hou and J. Tomayko, Applying the Personal Software Process in CS1: An Experiment, Proc. 29th SIGCSE Tech. Symp. Computer Science Education, ACM, New York, 1998, pp W.S. Humphrey, Introduction to the Personal Software Process, Addison-Wesley, Reading, Mass., Acknowledgments I thank Dan Burton, Noopur Davis, Will Hayes, Don McAndrews, Julie Mullaney, and Bill Peterson for their helpful comments and suggestions during the preparation of this article. References 1. W.E. Deming, Out of the Crisis, MIT Center for Advanced Engineering Study, Cambridge, Mass., J.M. Juran and F.M. Gryna, Juran s Quality Control Handbook, 4th ed., McGraw-Hill, New York, F.W. Taylor, The Principles of Scientific Management, Harper and Row, New York, P.F. Drucker, Management Challenges for the 21st Century, HarperCollins, New York, W.S. Humphrey, A Discipline for Software Engineering, Addison-Wesley, Reading, Mass., W. Hayes and J.W. Over, The Personal Software Process: An Empirical Study of the Impact of PSP on Individual Engineers, Tech. Report CMU/SEI-97-TR- 001, Carnegie Mellon Univ., Pittsburgh, W.S. Humphrey, Using a Defined and Measured Personal Software Process, IEEE Software, Vol. 13, No. 3, May 1996, pp About the Editor Watts S. Humphrey joined the Software Engineering Institute (SEI) of Carnegie Mellon University in 1986 after 27 years at IBM. At the SEI, he established the Process Program, led initial development of the Software Capability Maturity Model, and introduced the concepts of Software Process Assessment Software Capability Evaluation, the Personal Software Process, and the Team Software Process. This year, the Watts Humphrey Software Quality Institute in Chennai, India, was named in his honor, and the Boeing Corporation presented him with an award for innovation and leadership in software process improvement. He holds five US patents and has published seven books, including A Discipline for Software Engineering; Managing Technical People Innovation, Teamwork, and the Software Process; Introduction to the Personal Software Process; and Introduction to the Team Software Process. Humphrey holds graduate degrees in physics from the Illinois Institute of Technology and in business administration from the University of Chicago. He was also awarded an honorary PhD in software engineering by Embry Riddle Aeronautical University in He is an SEI fellow, a member of the ACM, an IEEE fellow, and a past member of the Malcolm Baldrige National Quality Award Board of Examiners. November/December 2000 IEEE SOFTWARE 75
Comments on Software Quality by Watts S. Humphrey Fellow, Software Engineering Institute Carnegie Mellon University Pittsburgh, PA
Comments on Software Quality by Watts S. Humphrey Fellow, Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Summary This paper reviews the software industry s current approach to
More informationThe Personal Software Process SM (PSP SM )
The Personal Software Process SM (PSP SM ) Watts S. Humphrey November 2000 TECHNICAL REPORT CMU/SEI-2000-TR-022 ESC-TR-2000-022 Pittsburgh, PA 15213-3890 The Personal Software Process SM (PSP SM ) CMU/SEI-2000-TR-022
More informationResults of Applying the Personal Software Process
Computing Practices Results of Applying the Personal Software Process Too often, software developers follow inefficient methods and procedures. The Personal Software Process, developed by Watts Humphrey
More informationThe Advantages of Using a Software Engineering Project Development System
AC 2007-1432: TOOL SUPPORT FOR SOFTWARE PROCESS DATA MANAGEMENT IN SOFTWARE ENGINEERING EDUCATION AND INDUSTRY TRAINING Mark Sebern, Milwaukee School of Engineering MARK J. SEBERN is a Professor in the
More informationIncorporating PSP into a Traditional Software Engineering Course: An Experience Report
Incorporating PSP into a Traditional Software Engineering Course: An Experience Report Jonathan I. Maletic Div of Computer Science Dept of Math Sciences The University of Memphis Memphis TN 38152-3240
More informationThe Personal Software Process 1 by Watts S. Humphrey watts@sei.cmu.edu Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213
The Personal Software Process 1 by Watts S. Humphrey watts@sei.cmu.edu Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213 Copyright (c) 1994 Institute of Electrical and Electronics
More informationWhy Does Software Work Take So Long? Watts S. Humphrey
In writing this column, I plan to discuss various topics of interest to software professionals and managers. In general, I will write about issues related to engineering productivity, quality, and overall
More informationWhy Big Software Projects Fail: The 12 Key Questions
Why Big Software Projects Fail: The 12 Key Questions Software project failures are common, and the biggest projects fail most often. There are always many excuses for these failures, but there are a few
More informationUsing Students as Experiment Subjects An Analysis on Graduate and Freshmen Student Data
Using Students as Experiment Subjects An Analysis on and Student Data Per Runeson Lund University, Dept. of Communication Systems, Box 118, SE-221 00 Lund, Sweden per.runeson@telecom.lth.se ABSTRACT The
More informationProcess Improvement. From the Software Engineering Institute:
Process Improvement From the Software Engineering Institute: The Software Capability Maturity Model (SW-CMM, CMMI) (Especially CMMI V1.1 Tutorial) The Personal Software Process (PSP) (Also see The Team
More informationfocus Process Diversity in Software Development guest editors introduction
focus guest editors introduction Process Diversity in Software Development Mikael Lindvall and Ioana Rus, Fraunhofer Center for Experimental Software Engineering, Maryland one size fits all approach doesn
More informationAN OVERVIEW OF INDUSTRIAL SOFTWARE DOCUMENTATION PRACTICES
AN OVERVIEW OF INDUSTRIAL SOFTWARE DOCUMENTATION PRACTICES Marcello Visconti 1 Departamento de Informática Universidad Técnica Federico Santa María Valparaíso, CHILE visconti@inf.utfsm.cl Curtis R. Cook
More informationCapability Maturity Model Integration (CMMI ) Version 1.2 Overview
Capability Maturity Model Integration (CMMI ) Version 1.2 Overview SM CMM Integration, IDEAL, Personal Software Process, PSP, SCAMPI, SCAMPI Lead Appraiser, Team Software Process, and TSP are service marks
More informationPersonal Software Process in the Database Course
Personal Software Process in the Database Course William I. Bullers, Jr. Anderson Schools of Management University of New Mexico Albuquerque, NM, U.S.A. bullers@unm.edu Abstract This paper describes the
More informationUtilization of Statistical Process Control in Defined Level Software Companies to Manage Processes Using Control Charts with Three Sigma
Proceedings of the World Congress on Engineering and Computer Science 00 Vol I WCECS 00, October 0-, 00, San Francisco, USA Utilization of Statistical Process Control in Defined Level Software Companies
More informationToward Quantitative Process Management With Exploratory Data Analysis
Toward Quantitative Process Management With Exploratory Data Analysis Mark C. Paulk Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213 Abstract The Capability Maturity Model
More informationA Survey of Plan-Driven Development Methodologies
A Survey of Plan-Driven Development Methodologies Plan-driven methodologies have been utilized by organizations for many years. In this chapter, we provide an overview of three prominent, modern plan-driven
More informationAn e-newsletter published by Dec 2010 Software Quality Consulting, Inc. Vol. 7 No. 5
An e-newsletter published by Dec 2010 Software Quality Consulting, Inc. Vol. 7 No. 5 Welcome to Food for Thought TM, an e-newsletter from Software Quality Consulting. I've created free subscriptions for
More informationMANAGING CHANGES FOR IMPLEMENTING TQM IN INNOVATION PROCESS
MANAGING CHANGES FOR IMPLEMENTING TQM IN INNOVATION PROCESS Cosmin DOBRIN The Bucharest Academy of Economic Studies, Bucharest, Romania cosmin.dobrin@man.ase.ro Ana-Maria STĂNCIUC The Bucharest Academy
More informationCapability Maturity Model Integration (CMMI ) Overview
Pittsburgh, PA 15213-3890 Capability Maturity Model Integration ( ) Overview SM CMM Integration, SCAMPI, SCAMPI Lead Appraiser, and SEI are service marks of Carnegie Mellon University., Capability Maturity
More informationA Life-Cycle Engineering Case Study
A Life-Cycle Engineering Case Study Thomas B. HILBURN, Massood TOWHIDNEJAD, Salamah SALAMAH Department of Electrical, Computer, Software, and Systems Engineering Embry-Riddle Aeronautical University Daytona
More informationThe Team Software Process SM (TSP SM )
The Team Software Process SM (TSP SM ) Watts S. Humphrey November 2000 TECHNICAL REPORT CMU/SEI-2000-TR-023 ESC-TR-2000-023 Pittsburgh, PA 15213-3890 The Team Software Process SM (TSP SM ) CMU/SEI-2000-TR-023
More informationThe Team Software Process SM (TSP SM ) in Practice: A Summary of Recent Results
The Team Software Process SM (TSP SM ) in Practice: A Summary of Recent Results Noopur Davis Julia Mullaney September 2003 TECHNICAL REPORT CMU/SEI-2003-TR-014 ESC-TR-2003-014 Pittsburgh, PA 15213-3890
More informationQuantitative Project Management Framework via Integrating
Quantitative Project Management Framework via Integrating Six Sigma and PSP/TSP Sejun Kim, BISTel Okjoo Choi, Jongmoon Baik, Abstract: Process technologies such as Personal Software Process SM (PSP) and
More informationTraining Faculty to Coach Capstone Design Teams*
Int. J. Engng Ed. Vol. 17, Nos. 4 and 5, pp. 353±358, 2001 0949-149X/91 $3.00+0.00 Printed in Great Britain. # 2001 TEMPUS Publications. Training Faculty to Coach Capstone Design Teams* DOROTHY G. TAYLOR,
More informationEvaluation of Intellectual Property Course Offerings for undergraduate engineering students in the Mid Atlantic Region
Evaluation of Intellectual Property Course Offerings for undergraduate engineering students in the Mid Atlantic Region Abstract S. Jimmy Gandhi, M.S, Stevens Institute of Technology Donald Merino, PhD,
More informationAgile, TSP SM, CMMI pick one, pick two, pick all three!
1 Agile, TSP SM, CMMI pick one, pick two, pick all three! Daniel M. Roy Cape Town SPIN 20 February, 2008 PSP, TSP, Personal Software Process and Team Software Process are service marks of CMU CMM is and
More informationProject Quality Management. Project Management for IT
Project Quality Management 1 Learning Objectives Understand the importance of project quality management for information technology products and services Define project quality management and understand
More informationImplementing a Personal Software Process (PSP SM ) Course: A Case Study
Journal of Software Engineering and Applications, 212, 5, 639-644 http://dx.doi.org/1.4236/jsea.212.5874 Published Online August 212 (http://www.scirp.org/journal/jsea) 639 Implementing a Personal Software
More informationMaking Process Improvement Work
Making Process Improvement Work A Concise Action Guide for Software Managers and Practitioners Neil Potter Mary Sakry The Process Group help@processgroup.com www.processgroup.com Version 2.3 1 Session
More informationA PRELIMINARY REPORT ON ADAPTING SOFTWARE DEVELOPMENT INDUSTRY BEST PRACTICES FOR UNDERGRADUATE CLASSROOM USE
1 Abstract A PRELIMINARY REPORT ON ADAPTING SOFTWARE DEVELOPMENT INDUSTRY BEST PRACTICES FOR UNDERGRADUATE CLASSROOM USE Rajendran Swamidurai, David Umphress Alabama State University/Auburn University
More informationA Software Engineering Course with an Emphasis on Software Processes and Security
A Software Engineering Course with an Emphasis on Software Processes and Security Richard G. Epstein Department of Computer Science West Chester University of Pennsylvania West Chester, PA 19383 repstein@wcupa.edu
More informationUsing the TSP on the TaskView Project
Using the TSP on the TaskView Project David Webb, Ogden Air Logistics Center, Software Engineering Division Watts Humphrey, Software Engineering Institute This article reports the first results of using
More informationElectrical Engineering & Computer Science School of Engineering University of Kansas
Electrical Engineering & Computer Science School of Engineering University of Kansas Course Title EECS814: Software Quality Assurance Fall 2007 (14322) Thursdays, 7:10 10:00 PM, Regnier Hall 151 Course
More informationTwo Initiatives for Disseminating Software Assurance Knowledge. embedded in mainstream higher education
Dr. Nancy R. Mead SEI There is general recognition that software engineering practice can best be improved through education. In fact, the establishment of a National Cyberspace Security Awareness and
More informationGirish Seshagiri Advanced Information Services
BIO PRESENTATION FG4 Friday, June 6, 2003 10:30 AM SOFTWARE DEVELOPMENT ON INTERNET TIME-FASTER, CHEAPER, WORSE? Girish Seshagiri Advanced Information Services International Conference On Software Management
More informationChapter 8: Project Quality Management
CIS 486 Managing Information Systems Projects Fall 2003 (Chapter 8), PhD jwoo5@calstatela.edu California State University, LA Computer and Information System Department Chapter 8: Project Quality Management
More informationEnterprise software risk reduction
Enterprise software risk reduction Danny Lieberman dannyl@software.co.il www.software.co.il August 2006 ABSTRACT Operational risk is the risk of loss resulting from inadequate or failed internal processes,
More informationFrom Organizational Challenges to Real Results
Published on Quality Digest (http://www.qualitydigest.com) January 2009 From Organizational Challenges to Real Results Second only to leadership, strategic planning has been likely more written about than
More informationWhat Makes Good Research in Software Engineering?
International Journal of Software Tools for Technology Transfer, 2002, vol. 4, no. 1, pp. 1-7. What Makes Good Research in Software Engineering? Mary Shaw School of Computer Science, Carnegie Mellon University,
More informationImproving Software Developer s Competence: Is the Personal Software Process Working?
Improving Software Developer s Competence: Is the Personal Software Process Working? Pekka Abrahamsson 1, Karlheinz Kautz 2, Heikki Sieppi 3 and Jouni Lappalainen 3 1 VTT Technical Research Centre of Finland,
More information7 A Cross Course Analysis of Product Quality Improvement with PSP
7 A Cross Course Analysis of Product Quality Improvement with PSP Fernanda Grazioli, Universidad de la República William Nichols 7.1 Introduction and Background These days, more and more businesses develop,
More informationTotal Quality Management in Engineering Education
Total Quality Management in Engineering Education EFTHIMIA STAIOU Department of Business Administration University of Macedonia Egnatia 156, P.O. Box 1591, 54006 Thessaloniki GREECE Abstract: - Higher
More informationfeature Trade-offs between Productivity and Quality in Selecting Software Development Practices
feature productivity Trade-offs between Productivity and Quality in Selecting Software Development Practices Alan MacCormack, Harvard University Chris F. Kemerer, University of Pittsburgh Michael Cusumano,
More informationTrends in SwA Practice: Education and Adoption
Trends in SwA Practice: Education and Adoption Carol Woody, Ph.D. Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213 March 9, 2010 Academia Contributes to Software Assurance
More informationTeaching Disciplined Software Development
NOTICE: this is the author s version of a work that was accepted for publication in Journal of Systems and Software. Changes resulting from the publishing process, such as peer review, editing, corrections,
More informationC. Wohlin and B. Regnell, "Achieving Industrial Relevance in Software Engineering Education", Proceedings Conference on Software Engineering
C. Wohlin and B. Regnell, "Achieving Industrial Relevance in Software Engineering Education", Proceedings Conference on Software Engineering Education & Training, pp. 16-25, New Orleans, Lousiana, USA,
More informationHow To Teach Software Engineering
COVER FEATURE What Knowledge Is Important to a Software Professional? Efforts to develop licensing requirements, curricula, or training programs for software professionals should consider the experience
More informationHow to introduce maturity in software change management $
How to introduce maturity in software change management $ Lars Bendix Department of Computer Science Fredrik Bajers Vej 7E Aalborg University Denmark E-mail: bendix@cs.auc.dk Abstract: In this paper we
More informationSoftware Engineering: Analysis and Design - CSE3308
CSE3308/DMS/2004/25 Monash University - School of Computer Science and Software Engineering Software Engineering: Analysis and Design - CSE3308 Software Quality CSE3308 - Software Engineering: Analysis
More informationEfficient Collection and Analysis of Program Data - Hackystat
You can t even ask them to push a button: Toward ubiquitous, developer-centric, empirical software engineering Philip Johnson Department of Information and Computer Sciences University of Hawaii Honolulu,
More informationOPERATIONAL EXCELLENCE A KEY TO WORLD- CLASS BUSINESS PERFORMANCE
OPERATIONAL EXCELLENCE A KEY TO WORLD- CLASS BUSINESS PERFORMANCE NĂFTĂNĂILĂ Ion Academy of Economic Studies, Bucharest, Romania RADU Cătălina Academy of Economic Studies, Bucharest, Romania CIOANĂ Georgiana
More informationC. Wohlin, "Is Prior Knowledge of a Programming Language Important for Software Quality?", Proceedings 1st International Symposium on Empirical
C. Wohlin, "Is Prior Knowledge of a Programming Language Important for Software Quality?", Proceedings 1st International Symposium on Empirical Software Engineering, pp. 27-36, Nara, Japan, October 2002.
More informationAC 2011-1690: REPORTING ON THE USE OF A SOFTWARE DEVELOP- MENT CASE STUDY IN COMPUTING CURRICULA
AC 2011-1690: REPORTING ON THE USE OF A SOFTWARE DEVELOP- MENT CASE STUDY IN COMPUTING CURRICULA Massood Towhidnejad, Embry-Riddle Aeronautical Univ., Daytona Beach Massood Towhidnejad is a tenure full
More informationThe Development of a Supply Chain Management Process Maturity Model Using the Concepts of Business Process Orientation
The Development of a Supply Chain Management Process Maturity Model Using the Concepts of Business Process Orientation Dr. Kevin McCormack Instructor, University of Alabama at Birmingham, School of Business
More informationSTRENGTHENING SUPPLIER RELATIONSHIPS: WITH COMPREHENSIVE AUDIT PLANING
STRENGTHENING SUPPLIER RELATIONSHIPS: WITH COMPREHENSIVE AUDIT PLANING SUMMARY Katherine Lynn Supplier Partnership Consultant South Lake Tahoe, CA 96150 kathyllynn@sbcglobal.net Supplier relationships
More informationUnderstanding High Maturity Organizations
Understanding High Maturity Organizations Donna K. Dunaway, Charles V. Weber, Mark C. Paulk, Will Hayes, and Mary Beth Chrissis Carnegie Mellon University Pittsburgh, PA 15213-3890 Capability Maturity
More informationGREYSTONE COLLEGE ONE PAGERS WWW.GREYSTONECOLLEGE.COM GSC.15.150413
GREYSTONE COLLEGE ONE PAGERS 2015 WWW.GREYSTONECOLLEGE.COM GSC.15.150413 CO-OPERATIVE EDUCATION (WORK & STUDY) PROGRAMS Focused career skill development to help you succeed in the workplace Learn important
More informationAn RSIC-SE2004 Curriculum Framework
Proceedings of the International Multiconference on ISBN 978-83-60810-14-9 Computer Science and Information Technology, pp. 633 638 ISSN 1896-7094 An RSIC-SE2004 Curriculum Framework Thomas B. Hilburn
More informationAnatomy of an Enterprise Software Delivery Project
Chapter 2 Anatomy of an Enterprise Software Delivery Project Chapter Summary I present an example of a typical enterprise software delivery project. I examine its key characteristics and analyze specific
More informationIntroductory Game Creation: No Programming Required
Introductory Game Creation: No Programming Required A.T. Chamillard Computer Science Department University of Colorado at Colorado Springs Colorado Springs, CO 80933-7150 719-262-3150 ABSTRACT Many incoming
More informationThe role of replications in Empirical Software Engineering
Empir Software Eng (2008) 13:211 218 DOI 10.1007/s10664-008-9060-1 VIEWPOINT The role of replications in Empirical Software Engineering Forrest J. Shull & Jeffrey C. Carver & Sira Vegas & Natalia Juristo
More informationV. Phani Krishna et al, / (IJCSIT) International Journal of Computer Science and Information Technologies, Vol. 2 (6), 2011, 2915-2919
Software Quality Assurance in CMM and XP- A Comparative Study CH.V. Phani Krishna and Dr. K.Rajasekhara Rao CSE Department, KL University, Guntur dt., India. Abstract Software Quality Assurance is a planned
More informationISO 9000-3 OR CMM: WHICH IS MORE EXTENSIVE FOR THE QUALITY SYSTEMS IN A SOFTWARE INDUSTRY?
International Journal of Advanced Research in Engineering and Applied Sciences ISSN: 2278-6252 ISO 9000-3 OR CMM: WHICH IS MORE EXTENSIVE FOR THE QUALITY SYSTEMS Monika Yadav* Kaushik Kumar** IN A SOFTWARE
More informationUnit 8: Software Process Improvement
Unit 8: Software Process Improvement Objectives Ð To provide a framework for software process assessment and improvement. Background A framework to help the US DoD pick software vendors more cleverly and
More informationEvaluating the Cost of Software Quality
Evaluating the Cost of Software Quality The time has come to financially justify investments in software quality improvements, just like we justify other software projects. Sandra A. Slaughter, Donald
More informationOptimization of Software Quality using Management and Technical Review Techniques
Optimization of Software Quality using Management and Technical Review Techniques Inibehe Emmanuel Akpannah Post Graduate Student (MSc. Information Technology), SRM University, Chennai, India Abstract
More informationJOURNAL OF OBJECT TECHNOLOGY
JOURNAL OF OBJECT TECHNOLOGY Online at http://www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2006 Vol. 5, No. 1, January-February 2006 On Addressing the Computer Science Crisis
More information1 Every Business Is a Software Business
94_HUMPHREY.ch01.qk 12/13/01 2:54 PM Page 1 1 Every Business Is a Software Business While technology can change quickly, getting your people to change takes a great deal longer. That is why the people-intensive
More informationSoftware Engineering, Not Computer Science. A scientist builds in order to learn; an engineer learns in order to build.
98 0 pp00-6 r6jm.ps 6//03 :3 PM Page 9 Schapter four Software Engineering, Not Computer Science A scientist builds in order to learn; an engineer learns in order to build. fred brooks When interviewing
More informationThe Personal Software Process (PSP) Tutorial
The Personal Software Process (PSP) Tutorial Watts Humphrey / Jim Over Speaker: Daniel M. Roy (STPP, visiting scientist SEI) Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213
More informationInstitutional Entrepreneurs 1
Preliminary draft Comments are welcome Institutional Entrepreneurs 1 David Daokui Li Tsinghua University Hong Kong University of Science and Technology Junxin Feng Hongping Jiang Tsinghua University December
More informationAdult Educational Psychology: Diverse Perspectives from an Emerging Field. Introductory Comments. M Cecil Smith. Northern Illinois University 4/21/99
1 Adult Educational Psychology: Diverse Perspectives from an Emerging Field Introductory Comments M Cecil Smith Northern Illinois University 4/21/99 Presented at the annual meeting of the American Educational
More informationORACLE NAIO Excellence combined with Quality A CMMI Case study
CASE STUDY ORACLE NAIO Excellence combined with Quality A CMMI Case study softwaredi xide com www.qaiasia.com THE CLIENT Process and Quality are important for measuring improvement. Improvement means different
More informationMeasuring the success of virtual tutoring
Measuring the success of virtual tutoring Avi Wiezel Del E. Webb School, of Construction Arizona State University Tempe, AZ, 85287-0204 Abstract Starting spring 1996, the Del E. Webb School of Construction
More informationEmbedded Software Engineering as a Function of Time
Embedded Software Engineering as a Function of Time Abstract Robert Berger Embedded Software Specialist Stratigou Rogakou 24, GR-15125 Polydrosso/Maroussi, Athens, Greece Phone : (+ 30) 697 593 3428, Fax:
More informationSoftware Maintenance Management Strategies: Observations from the Field
Software Maintenance Management Strategies: Observations from the Field George Stark, MITRE Paul Oman, Univ of Idaho Abstract There is much literature describing software maintenance process models, but
More informationControlling software acquisition: is supplier s software process capability determination enough?
Controlling software acquisition: is supplier s software process capability determination enough? Fabrizio Fabbrini, Mario Fusani, Giuseppe Lami Abstract Innovation in automotive is principally due to
More informationThe Software Engineering Ph.D. Program at Carnegie Mellon
The Software Engineering Ph.D. Program at Carnegie Mellon SE Ph.D. Immigration Course Overview Jonathan Aldrich Director, SE Ph.D. Program Software Engineering at Carnegie Mellon Software engineering is
More informationConceptualizing Total Quality Management (TQM) for Improving Housing Areas for the Urban Poor
Conceptualizing Total Quality Management (TQM) for Improving Housing Areas for the Urban Poor Abstract This paper examines the concept of TQM and investigates and identifies factors in all three phases
More informationWhat do you think? Definitions of Quality
What do you think? What is your definition of Quality? Would you recognise good quality bad quality Does quality simple apply to a products or does it apply to services as well? Does any company epitomise
More informationEntrepreneurship from a Diverse University Base Course Outline for Hebrew University
Page 1 of 6 Course Objective Entrepreneurship from a Diverse University Base Course Outline for Hebrew University Entrepreneurship is a heterogeneous phenomenon. It involved people with a wide range of
More informationSurviving the Quagmire of Process Models, Integrated Models, and Standards*
Surviving the Quagmire of Process Models, Integrated Models, and Standards* Mark C. Paulk Senior Systems Scientist Carnegie Mellon University Pittsburgh, PA 15213-3890 Email: mcp@cs.cmu.edu Summary We
More informationSTUDENT PERSPECTIVES ON A REAL WORLD PROJECT
STUDENT PERSPECTIVES ON A REAL WORLD PROJECT Sofya Poger, Frances Bailie Computer Science Department Iona College New Rochelle, NY 10801 914 633 2298 spoger@iona.edu, fbailie@iona.edu ABSTRACT This paper
More informationMeasurable Software Quality Improvement through Innovative Software Inspection Technologies at Allianz Life Assurance
Measurable Software Quality Improvement through Innovative Software Inspection Technologies at Allianz Life Assurance Bernd Freimut, Brigitte Klein, Oliver Laitenberger, Günther Ruhe Abstract The development
More informationthe state of the practice Variations in Software Development Practices
focus the state of the practice invited article Variations in Software Development Practices Capers Jones, Software Productivity Research My colleagues and I at Software Productivity Research gathered
More informationDetermining the Productivity of Instructional Systems
Determining the Productivity of Instructional Systems Dr. Philip McGee, Program Coordinator of the Masters in Human Resource Development, Clemson University, South Carolina ABSTRACT The Productivity Model
More informationJason Bennett Thatcher Clemson University, 101 Sirrine Hall, Clemson, SC 29634 U.S.A. {jthatch@clemson.edu}
RESEARCH ARTICLE IS EMPLOYEE ATTITUDES AND PERCEPTIONS AT VARYING LEVELS OF SOFTWARE PROCESS MATURITY Janet K. Ply Pendére, Inc., 1805 S. 9 th Street, Waco, TX 76706 U.S.A. {janet.ply@pendere.com} Jo Ellen
More informationFact 1 PEOPLE PEOPLE 11
PEOPLE 11 References Davis, Alan M. 1995. 201 Principles of Software Development. New York: McGraw-Hill. Glass, Robert L. 1979. The Power of Peonage. Computing Trends. PEOPLE Fact 1 The most important
More informationThe Importance of Engineering in Software Development
Annals of Software Engineering Volume 10 Comparative Studies of Engineering Approaches for Software Engineering Guest Editors Dilip Patel, PhD and Yingxu Wang, PhD 1 Table of Contents Comparative Software
More informationIf it passes test, it must be OK Common Misconceptions and The Immutable Laws of Software
If it passes test, it must be OK Common Misconceptions and The Immutable Laws of Software Girish Seshagiri, Advanced Information Services Inc. Abstract. As the saying goes, If it passes test, it must be
More informationEvaluating the Quality of Software Engineering Performance Data
Evaluating the Quality of Software Engineering Performance Data James Over Software Engineering Institute Carnegie Mellon University July 2014 Copyright 2014 Carnegie Mellon University This material is
More informationTMP3413 Software Engineering Lab. Lecture 01: Team Software Process Overview
TMP3413 Software Engineering Lab Lecture 01: Team Software Process Overview Topics Working in teams What is TSP? TSP objectives & principles TSP design Team member roles TSP launch TSP project tracking
More informationInterpersonal Communication: Key Competencies for Enterprise Project Management
Interpersonal Communication: Key Competencies for Enterprise Project Management Steven Flannes, Ph.D. Principal, Flannes Associates 2080 Mountain Blvd., Suite 205 Oakland, California 94611 USA Telephone:
More informationSimulation of Different SPI Models
Simulation of Different SPI Models Bharti Sharma Neeraj Sharma Neeshu Sharma Student, M-tech Lecturer Student, M-tech Department of CSE Department of CSE Department of CSE Punjabi University Patiala Punjabi
More informationProfessional Software Engineering: Fact or Fiction?
Guest Editors Introduction For many programmers, software development consists of hacking. As we mature, it is time to follow the example of other professional disciplines, to put the engineering in software
More informationProject Management Competencies in the Project Oriented Organization
Project Management Competencies in the Project Oriented Organization In the project-based organization, project management (pm) competences are not only required by individuals, but also by project teams
More informationSoftware Quality Data Part 1: Basic and Derived Metrics
Abstract We measure, quantify and report on software quality. But can we control it? Can we actually assure quality (as opposed to just measuring it)? This is the first of three papers in which we will
More informationAn Investigation on Learning of College Students and the Current Application Situation of the Web-based Courses
2011 International Conference on Computer Science and Information Technology (ICCSIT 2011) IPCSIT vol. 51 (2012) (2012) IACSIT Press, Singapore DOI: 10.7763/IPCSIT.2012.V51.127 An Investigation on Learning
More information