Personal Design and Development Software Process PD 2 SP “The unexamined life is not worth living.” Plato.

Slides:



Advertisements
Similar presentations
Software Engineering Lab Session Session 1 – Introduction to the practicum © Jorge Aranda, 2005.
Advertisements

The Personal Software Process (PSP) Lecture #1 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department.
Tutorial: Using PSP0 Personal Software Process for Engineers: Part I
Computer Engineering 203 R Smith Project Tracking 12/ Project Tracking Why do we want to track a project? What is the projects MOV? – Why is tracking.
PRO2 - 1 Introduction to the Personal Software Process SWENET PRO2 Module Developed with support from the National Science Foundation.
Sponsored by the U.S. Department of Defense © 2002 by Carnegie Mellon University July 2002 Pittsburgh, PA Lecture 6: Team Planning.
Degree and Graduation Seminar Scope Management
HIT241 - Project Scope Management Introduction
Personal Software Process
The Software Process Strategy The Software Process Strategy Part III.
Aplicaciones de Ingeniería de Software
Using A Defined and Measured Personal Software Process Watts S. Humphrey CS 5391 Article 8.
Personal software process Mohammed ahmed ali. What is psp The personal software process (psp) is a structured set of process descriptions, measurements.
Personal Software Process Overview CIS 376 Bruce R. Maxim UM-Dearborn.
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 1 1 Disciplined Software Engineering Lecture #1 Software Engineering.
Capability Maturity Model
INFO 637Lecture #31 Software Engineering Process II Launching & Strategy INFO 637 Glenn Booker.
Quality Assurance ITEC Rick Price. Expectations This course is not purely a lecture course – Classroom participation is a large portion – Everyone.
Chapter 15 Projecting Defects( 缺陷预测 ). 山东大学齐鲁软件学院 2 outline  Analyze and use your defect data to help improve both planning accuracy and product quality.
Applied Software Project Management Andrew Stellman & Jennifer Greenehttp:// Applied Software Project Management Chapter 1: Introduction.
N By: Md Rezaul Huda Reza n
INFO 637Lecture #41 Software Engineering Process II Development Plan INFO 637 Glenn Booker.
Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.
CS 350: Introduction to Software Engineering Slide Set 1 C. M. Overstreet Old Dominion University Fall 2005.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
Disciplined Software Engineering Lecture #6 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department.
Software Engineering - Spring 2003 (C) Vasudeva Varma, IIITHClass of 39 CS3600: Software Engineering: Standards in Process Modeling CMM and PSP.
SE 501 Software Development Processes Dr. Basit Qureshi College of Computer Science and Information Systems Prince Sultan University Lecture for Week 6.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Lecture: The Personal Software Process. 2 Overview  Personal Software Process assumptions process stages measures and quality strategy results.
© 1998 Carnegie Mellon UniversityTutorial The Personal Software Process (PSP) The overview of the PSP that follows has been built from material made.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
Software Engineering Prof. Dr. Bertrand Meyer March–June 2007 Chair of Software Engineering Lecture 2: The Personal Software Process.
Team Software Process (TSPi) CS4320 Fall TSP Strategy Provide a simple process framework based on the PSP. Use modest, well-defined problems. Develop.
CS 350, slide set 5 M. Overstreet Old Dominion University Spring 2005.
“Look, who is the most successful in attracting and holding good people? The nonprofits. The satisfaction has to be greater than in business because there.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Disciplined Software Engineering Lecture #2 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department.
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 1 1 Disciplined Software Engineering Lecture #2 Software Engineering.
Computing and SE II Chapter 15: Software Process Management Er-Yu Ding Software Institute, NJU.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Implementation Phase CS4311 – Spring 2008 References: Shach, Object Oriented and Classical Software Engineering E. Braude, Software Engineering, an Object-Oriented.
The Software Process Chapter – II. Topics S/w Engg – A layered Technology A Process Framework Process Patterns Process Assessment Product and Process.
CS 350: Introduction to Software Engineering Slide Set 2 Process Measurement C. M. Overstreet Old Dominion University Fall 2005.
Chapter 6: THE EIGHT STEP PROCESS FOCUS: This chapter provides a description of the application of customer-driven project management.
The Personal Software Process Alan Kelon Oliveira de Moraes May 15, Recife.
1 EMS Fundamentals An Introduction to the EMS Process Roadmap AASHTO EMS Workshop.
THE POSTMORTEM Chapter 10 Introduction to Team Software Process.
INFO 637Lecture #11 Software Engineering Process II PSP Overview & TSP Introduction INFO 637 Glenn Booker.
Software Quality Assurance SOFTWARE DEFECT. Defect Repair Defect Repair is a process of repairing the defective part or replacing it, as needed. For example,
Introduction to the Personal Software Process. Overview Process Fundamentals PSP Concepts and Structure PSP Planning and Measurement PSP Quality Management.
CSC 480 Software Engineering PSP Project 1 August 20, 2004.
INFO 636 Software Engineering Process I Prof. Glenn Booker Week 10 – Process Definition 1INFO636 Week 10.
CSC 205 Programming II Lecture 1 PSP. The Importance of High-Quality Work Three aspects to doing an effective software engineering job producing quality.
TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support.
The Project Management Process Groups
Information Technology Project Management, Seventh Edition.
P ERSONAL & TEAM PROCESS MODELS Lecture 05 Part -2.
Capability Maturity Model. What is CMM? n CMM: Capability Maturity Model n Developed by the Software Engineering Institute of the Carnegie Mellon University.
Software Engineering Lab Session
A possible solution: Personal Software Process (PSP)
Team Project Review the background information and project teams on our course site Work with the engineers (4-5) and your PM team member(s) You have.
Capability Maturity Model
Identifying the Work to Be Done
Goal-Driven Software Measurement
Capability Maturity Model
Presentation transcript:

Personal Design and Development Software Process PD 2 SP “The unexamined life is not worth living.” Plato

Cynics’ Guide to Personnel Management Those who work get to keep their jobs. Raises become effective when you do. It’s better for you to tell them than for them to find out.

How do you meet expectations and still have a life?

What It Means to be Effective As software professionals you must know your own performance. You should measure, track, and analyze your work. You should learn from your performance variations. You should incorporate these lessons in your personal practices.

Introduction Measure and analyze your personal design and development software process (PD 2 SP). Use process data to improve your personal performance. Understand variation in your work patterns. Plan and estimate software development tasks.

What Metrics Do You Need? Time: –Class, Prep for class, Recording time, Design time, Planning Time, Programming, Debugging. –Provide both planned and actual times. Code: Quality and Quantity. Results: Demonstrated Correct, Complete Code.

Cost of PD 2 DP The time required to learn and use it. The emotional cost of maintaining the needed discipline. The potential risk to your ego.

Benefits of PD 2 DP The insight you gain into your talents and abilities. The stimulation of an almost unlimited stream of ideas. The framework provides for personal improvement. The degree of control you gain over your time and work. The feeling of pride and accomplishment. An improved basis for effective teamwork. The conviction to do the job the way you know you should.

By the end of the semester: You will understand some methods are effective for you. You will do better work. You will have long-term improvement goals.

PD 2 SP Principles The quality of a software system is governed by the quality of its worst components. The quality of a software component is governed by the individual who developed it. You are governed by your –knowledge –discipline –commitment

What do you know about your software development skills? Can you –Design, estimate, and plan your work? –Meet your commitments? –Resist unreasonable commitment pressures? Do you –Understand your ability? –Have an improvement plan?

A PD 2 SP Also Provides A basis for developing and practicing industrial-strength personal disciplines. A discipline that shows you how to improve your personal process. The data to continually improve the productivity, quality, and predictability of your work.

What is a PD 2 SP? A personal process for developing software defined steps forms standards A measurement and analyses framework to help you characterize your process A defined procedure to help you to improve your performance

SEI Capability Maturity Matrix Broadly agreed-upon definition of how a software organization matures and improves. Based on manufacturing process improvement and “best practices” from software engineering Some dramatic successes.

Each key process area has five common features: Goals to be achieved; Ability to perform; Activities performed; Measurement and analysis; Verification

PD 2 SP Overview

Since this is so late in your education, can’t do it all in one course. Focus on how to make your more efficient in time We’ll just do the first step.

PD 2 SP0 Identify your current software development process including: –Planning - Produce a plan to do the work. –Development - The actual software development. –Postmortem - Comparison of actual performance with your plan.

The measurements will be Based on your current process. Measure where you spend the bulk of your time. We will use minutes as the base granularity for data to be meaningful. Defect Recording. A defect recording log is used to hold data on each defect found and corrected.

Don’t Panic You will NOT be graded on how long it takes or how many defects you find

ThePD 2 SP0 Summary Your original estimate of the LOC you expect to develop. The actual LOC you developed. Your original estimate of the time required for each phase. The actual time required for each phase. The total number and the percent of defects injected in each phase. The total number and the percent of defects removed in each phase

Task Planning Task planning involves estimating the development time and completion data for each project task. It also provides a basis for tracking schedule progress.

Process Time and Schedule Management Requirements Management Design and Work Breakdown Structure Development Reporting Earned Value Estimation

Time and Schedule Management Enter initial project data in the project plan summary (PDSP0). Complete Initial Time Schedule Template (SPT). Begin Time Recording (TRT).

Requirements Planning Complete the Requirements Work Template (RWT) in the Excel workbook. –Constraints are logical statements –Criteria are performance statements

Design and Work Breakdown Use developed requirements document. Complete a Work Breakdown Structure Estimate the required development time. Complete the task plan (WBS).

Reporting Complete the project plan summary with actual time, defect, and size data. Complete the PIP (PD 2 SP0). Coding Standard Size measurement Process improvement Proposal

Rules of the Game Please keep accurate track of time. YOU WILL NOT BE GRADED ON YOUR TIME OR QUALITY from this report!! Quality measurement comes from testing Keep your programs simple. You will learn as much from small programs as from large ones. Keep your reports and standards simple and short. Do not hesitate to copy or build on the PD 2 SP materials.

Rules of the Game II Do it right the first time. If you are not sure, find out. Software is not a solo business so you do not have to work alone. You must, however, produce your own estimates, designs, and code. You may have others review your work and you may change it as a result. You should note this help in your process report, include the review time you and your associates spend, and log the defects found.

Grading Your process report must be: –complete –legible –in the specified order Your process data must be: –accurate –precise –self-consistent

The PD 2 SP0 Process A simple defined personal process Use your current design and development methods. Gather data on your work: time spent by phase defects found in compile and test

Prepare a summary report. A project plan summary form A process script A time recording log A defect reporting log A defect type standard

More Process Planning - estimate development time Development - develop the product using your current methods Postmortem - complete the project plan summary, with the time spent and defects found and injected in each phase. Design - design the program, using your current design methods

The End of the Beginning

Defect type standard Date defect was found. Defect number. Defect type (documentation, syntax, assignment, interface, etc.). Phase where defect was injected. Phase where defect was removed. Time it took to fix the defect. If injected while fixing another defect, that defect’s number. A succinct description of the defect. The project plan summary holds the estimated and actual project data.

The defect types 1.Documentation 2.Syntax 3.Assignment 4.Interface 5.Checking 6.Data 7.Function 8.Environment