Software Engineering Lab Session

Slides:



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

The Baseline Personal Process Copyright, 1999 © Jerzy R. Nawrocki Jerzy Nawrocki Personal Software Process Lecture 3.
Tutorial: Using PSP0 Personal Software Process for Engineers: Part I
Software Engineering Lab Session Session 4 – Feedback on Assignment 1 © Jorge Aranda, 2005.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
SE 501 Software Development Processes Dr. Basit Qureshi College of Computer Science and Information Systems Prince Sultan University Lecture for Week 7.
Important concepts in software engineering The tools to make it easy to apply common sense!
山东大学齐鲁软件学院 1 Chapter 9 Managing Schedules. 山东大学齐鲁软件学院 2 In the chapter  How to develop schedules to track the progress of your work.  How to use checkpoints.
Personal Software Process
1 PSP in CS1: not so wise after all Briana Morrison Southern Polytechnic State University Marietta, GA.
The Software Process Strategy The Software Process Strategy Part III.
Aplicaciones de Ingeniería de Software
Microsoft ® Office Word 2007 Training Reuse text and other document parts: Introducing building blocks [Your company name] presents:
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.
Global Studies Homework Expectations. Know when assignments are due! Check the side whiteboard every day before class begins and update your agenda. Assignments.
MJ2A Ch 5.10 – Arithmetic & Geometric Sequences. Bellwork Write and solve the following: 1.4 1/6 = r + 6 1/4 2.1/3 + h = 5/6 3.5/6q = 15/42 4.7/8d = 56.
Chapter 15 Projecting Defects( 缺陷预测 ). 山东大学齐鲁软件学院 2 outline  Analyze and use your defect data to help improve both planning accuracy and product quality.
SE 501 Software Development Processes Dr. Basit Qureshi College of Computer Science and Information Systems Prince Sultan University Lecture for Week 8.
INFO 637Lecture #41 Software Engineering Process II Development Plan INFO 637 Glenn Booker.
Disciplined Software Engineering Lecture #4 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department.
Disciplined Software Engineering Lecture #6 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department.
Mail merge I: Use mail merge for mass mailings Perform a complete mail merge Now you’ll walk through the process of performing a mail merge by using the.
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.
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.
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.
CS 350, slide set 5 M. Overstreet Old Dominion University Spring 2005.
1 Project 5: New Venue. 2 New Venue Based on the posted New Venue scenario 077_Ticket_Booth_Scenarios.pdf.
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 1 1 Disciplined Software Engineering Lecture #4 Software Engineering.
INFO 636 Software Engineering Process I Prof. Glenn Booker Week 8 – Reviews 1INFO636 Week 8.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
INFO 636 Software Engineering Process I Prof. Glenn Booker Week 3 – Planning and Measuring 1INFO636 Week 3.
INFO 636 Software Engineering Process I Prof. Glenn Booker Weeks 1-2 – Introduction 1INFO636 Weeks 1-2.
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.
SOFTWARE METRICS. Software Process Revisited The Software Process has a common process framework containing: u framework activities - for all software.
Implementation Phase CS4311 – Spring 2008 References: Shach, Object Oriented and Classical Software Engineering E. Braude, Software Engineering, an Object-Oriented.
Watts Humphrey IBM director of programming and vice-president of technical development Joined CMU Software Engineering Institute in 1986 Initiator and.
CS 350: Introduction to Software Engineering Slide Set 2 Process Measurement C. M. Overstreet Old Dominion University Fall 2005.
Sponsored by the U.S. Department of Defense © 2002 by Carnegie Mellon University July 2002 PSP-TSPi Faculty Workshop Pittsburgh, PA Lecture.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Personal Design and Development Software Process PD 2 SP “The unexamined life is not worth living.” Plato.
Lab Lesson Three: How to save to a USB (or Flash) Drive.
CSC 480 Software Engineering PSP Project 1 August 20, 2004.
Management of Software Project CSM Review By:Nafas.
CSC 205 Programming II Lecture 1 PSP. The Importance of High-Quality Work Three aspects to doing an effective software engineering job producing quality.
SE-280 Dr. Mark L. Hornick 1 Measuring Software Size.
Perform a complete mail merge Lesson 14 By the end of this lesson you will be able to complete the following: Use the Mail Merge Wizard to perform a basic.
Watts Humphrey IBM director of programming and vice-president of technical development Joined CMU Software Engineering Institute in 1986 Initiator and.
Applied Software Project Management SOFTWARE TESTING Applied Software Project Management 1.
T Project Review X-tremeIT I1 Iteration
Practical Office 2007 Chapter 10
Disciplined Software Engineering Lecture #6
LCGAA nightlies infrastructure
Conducting the performance appraisal
Adding Assignments and Learning Units to Your TSS Course
Conducting the performance appraisal
A possible solution: Personal Software Process (PSP)
Janet has used PSP for the last 6 months
CS 2530 Intermediate Computing Dr. Schafer
Bug Report Part 3.
Software Engineering Lab Session
Presentation transcript:

Software Engineering Lab Session Session 2 – PSP0.1 COME FOR YOUR ASSIG2 HANDOUT, BUT DO *NOT* HAND IN YOUR ASSIG1 YET! WAIT A MOMENT… © Jorge Aranda, 2005

Overview Before handing in Assignment 1… Alright, how was it? PSP0.1 AOB?

Before handing in Assignment 1… You will need some of the numbers from Assignment 1 for your Assignment 2 forms But we’ll have those forms by the time you need them Make sure to copy the following numbers from the Project Plan Summary: Planned total time Actual times for each phase Defects injected on each phase Defects removed on each phase Don’t lose those numbers! You’ll need them soon For the next assignments, before handing in the forms, make a copy of them!

Alright, how was it? Feedback on each aspect of the assignment: Yes, yes, the textbook… The actual programming task (no PSP) The Project Plan Summary The Time Recording Log The Defect Recording Log Other documents for the assignment Impressions on the PSP in general

Assignment 2 Write a program to count the number of lines of C code in a file, excluding blanks and comments Deliverables: Exactly the same as for the previous assignment, but the Project Plan Summary changes a bit… Process: PSP0.1 Make a copy of your completed assignment forms for yourself!

PSP0.1 Mainly the same as PSP0, but introducing line counts and more detailed estimates Time recording log remains the same Defect recording log remains the same

PSP0.1 Project Plan Summary When planning the assignment, estimate the total of lines of lines of code you will write When planning the assignment, estimate the time you’ll spend on each phase, and the total time for the assignment When on the postmortem phase, treat the time and defect fields just as in PSP0. The numbers for lines of code require a bit more explanation…

PSP0.1 Lines of code: Base – The lines upon which you’re building new stuff (doesn’t apply for Assignment 2) Deleted – Lines deleted from the base Modified – Lines modified from the base Added – predictable… Reused – Stuff you developed previously, that is not the base, but which you use to save some time Total New and Changed – All added or modified lines Total LOC – The final size of the program Total New Reused – Stuff you developed for this program that you think is ready for reuse on other programs

AOB? Questions, comments?