Humphrey, W.S. (1997), Introduction to the Personal Software Process, Addison-Wesley, Reading, MA. Humphrey, W.S. (2000), Introduction to the Team Software Process, Addison-Wesley, Reading, MA.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....often promotes the usage of software inspection by reporting savings and improvements to software development. For daily work of individuals, savings or improvements may not have any direct effect. Therefore measures collected from inspections may have no direct meaning. Personal Software Process [Humphrey, 1997] introduces inspection with personal measures and personal perception and experience that inspections make creation of software easier. This raises a question if other participants of software project could also get useful and direct information from inspection. This can be seen also as a short ....

Humphrey, Watts S., Introduction to the Personal Software Process. Addison-Wesley 1997.

....Probably the strongest contribution in this approach is the two level approach to group collaboration in the software development environment. The literature from the Real World Lab and the Studio shows that students can assume various roles, however these roles are relatively flat. Humphrey [19], 20] introduces the personal software process (PSP) and team software process (TSP) that formalizes the role of individual software engineers and the interaction among teams. The approach here is similar to PSP TSP. The students are taught to Fig. 6 Collaborative approaches in the software ....

W. S. Humphrey, Introduction to the Personal Software Process. Reading, MA: Addison--Wesley, 1997.

....in a disciplined, effective manner. The PSP is designed to help engineers organize and plan their work, track their performance, manage software defects, and analyze and improve their personal process. Since 1995, we have used [6] Watts Humphrey s Introduction to the Personal Software Process [7] to teach the material in our undergraduate curriculum starting at freshman year. During the sophomore year, students are required to take the first software engineering class, were they are introduced to the concept of Team Software Process (TSP) TSP is created by Watts Humphrey [8] and is ....

Humphrey, Watts S., "An Introduction to the Personal Software Process", Addison-Wesley, Reading, MA, 1997.

....to implementation and testing. Unfortunately, there are so many examples, both in industry and academia, of the emphasis on a code and test mentality, that we need to state the obvious: concentration on the front end part of development can produce a higher quality product at a lower cost. [5] 0 7803 7444 4 02 17.00 2002 IEEE November 6 9, 2002, Boston, MA Next, notice the double headed arrows connecting the development phases on the left and right. The arrow pointing to the left signifies dynamic testing of the software against a software artifact (system testing of the ....

....(PSP) was developed to help students and professional software engineers to organize and plan their work, track their Personal Software Process and the PSP are service marks of Carnegie Mellon University. progress, manage software quality, and analyze and improve their personal performance [5]. The PSP incorporates the lower part of the V Model for Quality: it includes test planning as one of the design phase activities, and it includes two formal reviews, one for design and one for code (using a defined review process, development standards, and review checklists) Introductory ....

Humphrey, W. S., Introduction to the Personal Software Process, Addison-Wesley, 1997

.... they will, won t they ) We also find that following XP practices makes one a better programmer (just as following XP practices makes a team better) We are exploring whether XP principles can be used as the basis for personal software improvement, much as CMM was used as the basis for the PSP [7 9]. 6 OBJECTIONS With any new methodology, people question whether or not it really works. Here are a few of the concerns raised about XP: Doesn t the removal of some of the core XP principles (particularly pair programming) destroy XP We find it does not. If you can use XP, use it it works. ....

Humphrey, W. Introduction to the Personal Software Process. Addison Wesley Longman. 1996.

....(effort and quality) becomes more predictable when one takes the time to follow a regular process (solve similar problems the same way) uses historical data to build a performance baseline, and leverages this baseline in planning future work. To verify this hypothesis, we added a text book [2] addressing individual time and quality management issues and made minor adjustments to the assignments in the existing ECEN 4553 class. We used PEP to capture planned and actual effort data for each phase of a standard software life cycle [2] Student data were secured via a username password ....

....To verify this hypothesis, we added a text book [2] addressing individual time and quality management issues and made minor adjustments to the assignments in the existing ECEN 4553 class. We used PEP to capture planned and actual effort data for each phase of a standard software life cycle [2]. Student data were secured via a username password protocol so those students could see only their own work. Instructors could see the work of any student, and instructor access was secured via the same username password protocol. Our attempt to capture defect plan and actual data failed due to ....

Humphrey, Watts, Introduction to the Personal Software Process, Addison-Wesley, 1997.

....Probably the strongest contribution in this approach is the two level approach to group collaboration in the software development environment. The literature from the Real World Lab and the Studio shows that students can assume various roles, however these roles are relatively flat. Humphrey [19][20] introduces the Personal Software Process (PSP) and Team Software Process (TSP) that formalizes the role of individual software engineers and the interaction among teams. The approach here is similar to PSP TSP. The students are taught to collaborate in sub group roles, and then the subgroups ....

Humphrey, W.S. Introduction to the Personal Software Process, Addison Wesley, Reading MA 1997

.... a highly regarded industrial strength team software process (TSP) as well as a textbook variant introductory team software process (TSPi) for small teams [4] However, both processes assume that all team members have previously completed substantial training in his personal software process (PSP [5]) Said background is clearly preferable, but pragmatically unrealistic for small software firms, short term virtual teams for small scale open source development, and undergraduate programs with space for only one single semester software engineering course. Although as true for larger scale ....

Humphrey, Introduction to the Personal Software Process, Addison-Wesley, 1997.

....(aimed at undergraduate or graduate software engineering courses) 15 complete working days (spread over 15 weeks) are required. Many project managers are interested in the PSP at rst until they hear about the learning e ort. Even a reduced PSP variant such as the one presented by Humphrey in [3] and aimed at introductory programming education is considered by most industrialists to be far too expensive to learn. Furthermore, the volume of bookkeeping proposed by the PSP is so large that data quality may become dubious [4] The problem is that you cannot learn the PSP just by listening ....

Watts S. Humphrey. Introduction to the Personal Software Process. SEI series in Software Engineering. Addison-Wesley, Reading, MA, 1997.

....improvement, estimation, and metrics. The resulting course covers the advanced topics of OO design and programming within the framework of process improvement. We have experimented with using both of the textbooks on PSP. In using the textbook, Introduction to the Personal Software Process [13], we found that it did not fit perfectly into an upper division course. The other textbook, A Discipline for Software Engineering [11] is often over the heads of inexperienced undergraduates. While, either of these books are a good additional reference for the course, we found ourselves ....

Humphrey, W. S., Introduction to the Personal Software Process, Addison Wesley, 1997.

....National Quality Award, and become ISO 9000 certified, while the rest of IBM came tumbling down. Watts Humphrey did one bet Page 4 ter by creating the Personal Software Process (PSP) a scaled down version of what IBM Rochester used, and many are becoming quite successful using this approach [4, 28, 29, 30, 31, 32]. Many more so now will benefit from the PSP as a Vertical Life Cycle Strategy, and the Software Inspection Process as a Vertical Process Strategy will rapidly fade from view. Powerful SPI Solutions While it has been already established that the Vertical Process Strategy and the Vertical Life ....

.... conjunction with the Software Inspection Process to predict and manage software development and software quality management [7, 12, 25, 26, 27] Personal Software Process (PSP) The PSP is a precisely defined, measurement intensive, portable, and individualized Defect Removal Model Life Cycle [4, 28, 29, 30, 31, 32]. Defect Prevention: Defect Prevention is a process of capturing and studying defects and defect trends, with the intention of preventing them from happening again [8, 11, 40, 41] Defect Prevention popularly takes the form of educating design programmers of common mistakes not to repeat. ....

Humphrey, W., "Introduction to the Personal Software Process," Addison Wesley, 1996.

....approach could also allow the user to see results of data analysis in many different formats and give the user access to raw data for further study. Although Humphrey describes a manual approach to PSP in A Discipline for Software Engineering [9] and Introduction to the Personal Software Process [11], he also indicates that automation is desirable. For example, Tool support can make the methods described in this book more efficient and easier to use. Such standard aids as word processors, spreadsheets, and statistical packages provide an adequate base initially, but ultimately CASE ....

Watts S. Humphrey. Introduction to the Personal Software Process. AddisonWesley, New York, 1997.

....[14] This text describes a one semester curriculum for advanced undergraduates or graduate students in computer science that teaches concepts in empirically guided software process improvement. Since its introduction, experience with the PSP has been reported on in several case studies [2, 6, 15, 16]. Although empirically guided software process improvement is a key feature of other software engineering initiatives, such as the Capability Maturity Model (CMM) 18] ISO 9000, and Inspection [7] the PSP differs from these other approaches in important ways. The CMM, ISO 9000, and Inspection ....

Watts S. Humphrey. Introduction to the Personal Software Process. Addison-Wesley, New York, 1997.

....[8] This text describes a one semester curriculum for advanced undergraduates or graduate students in computer science that teaches concepts in empirically guided software process improvement. Since its introduction, experience with the PSP has been reported on in several case studies [1, 4, 9, 12, 10]. Although empirically guided software process improvement is a key feature of other software engineering initiatives, such as the Capability Maturity Model (CMM) 11] ISO 9000, and Inspection [5] the PSP differs from these other approaches in important ways. The CMM, ISO 9000, and Inspection ....

Watts S. Humphrey. Introduction to the Personal Software Process. Addison-Wesley, New York, 1997.

No context found.

Humphrey, W.S. (1997), Introduction to the Personal Software Process, Addison-Wesley, Reading, MA. Humphrey, W.S. (2000), Introduction to the Team Software Process, Addison-Wesley, Reading, MA.

No context found.

Humphrey, W.S. (2000): Introduction to the Personal Software Process. Sydney, Addition-Wesley, ISBN 0201548097.

No context found.

W. Humphrey, "Introduction to the Personal Software Process." Boston: Addison-Wesley, 1996.

No context found.

W. S. Humphrey. Introduction to the Personal Software Process. Addison-Wesley, 1996.

No context found.

Humphrey W., Introduction to the Personal Software Process, Addison Wesley 1997

No context found.

Humphrey, W. (1997). Introduction to the Personal Software Process. Reading, MA: Addison Wesley.

No context found.

W. Humphrey. Introduction to the Personal Software Process, Addison Wesley 1997.

No context found.

W.S.Humphrey. Introduction to the Personal Software Process. Addison Wesley Longman,Inc, 1997.

No context found.

Watts S. Humphrey. Introduction to the Personal Software Process. Addison:Wesley, New York, i997.

No context found.

Humphrey, W. S. Introduction to the Personal Software Process. Reading, MA: Addison Wesley, 1997.

No context found.

W. S. Humphrey, Introduction to the Personal Software Process, Addison-Wesley, Reading, Mass., 1997.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC