Sponsored by the U.S. Department of Defense © 2002 by Carnegie Mellon University July 2002 PSP-TSPi Faculty Workshop Pittsburgh, PA 15213-3890 Lecture.

Slides:



Advertisements
Similar presentations
S3-1 © 2001 Carnegie Mellon University OCTAVE SM Process 3 Identify Staff Knowledge Software Engineering Institute Carnegie Mellon University Pittsburgh,
Advertisements

MODELING THE TESTING PROCESS Formal Testing (1.0) Requirements Software Design Risk Data Approved, Debugged, Eng. Tested Code Automated Test Tools Tested.
SEP1 - 1 Introduction to Software Engineering Processes SWENET SEP1 Module Developed with support from the National Science Foundation.
Tutorial: Using PSP0 Personal Software Process for Engineers: Part I
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 1 1 Disciplined Software Engineering Lecture #7 Software Engineering.
Sponsored by the U.S. Department of Defense © 2002 by Carnegie Mellon University July 2002 Pittsburgh, PA Lecture 6: Team Planning.
Copyright © 1997 Carnegie Mellon University Introduction to the Personal Software Process - Lecture 1 1 Introduction to the Personal Software Process Lecture.
Personal Software Process
Project Management and Communication Represented by: Latifa Jaber Al-Ghafran.
6/19/2007SE _6_19_TSPImp_SVT_Lecture.ppt1 Implementation Phase Inputs: Development strategy & plan Completed, inspected & baselined SRS & SDS.
Chapter 5: Project Scope Management
5/29/2007SE TSP Launch1 Team Software Project (TSP) May 29, 2007 Launch/Strategy Team Formation.
Course Technology Chapter 3: Project Integration Management.
Iterative development and The Unified process
SE 652 Software Quality Management Summer 2007 Lee Vallone.
8/7/2007SE _8_07_Misc_PostMortem.ppt1 Additional Topics & Team Project Post-Mortem.
Personal Software Process Overview CIS 376 Bruce R. Maxim UM-Dearborn.
INFO 637Lecture #31 Software Engineering Process II Launching & Strategy INFO 637 Glenn Booker.
Team Launch Introduction. Real projects are large and complex, and most software is created by teams Merely throwing people together does not result in.
Copyright Course Technology 1999
CS 350, slide set 6 M. Overstreet Old Dominion University Fall 2005.
PMP® Exam Preparation Course
CS 350, slide set 7 M. Overstreet Old Dominion University Spring 2005.
INFO 637Lecture #41 Software Engineering Process II Development Plan INFO 637 Glenn Booker.
CS 350, slide set 8 M. Overstreet Old Dominion University Spring 2005.
Lecture #9 Project Quality Management Quality Processes- Quality Assurance and Quality Control Ghazala Amin.
Preparing for the Launch Mohammed El- Affendi. Launch Major Tasks  The Launch is performed according to script “LAU1”, table 3.1 in the book (page 39),
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 #21 Software Engineering Process II TSP Roles and Overview INFO 637 Glenn Booker.
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 #7 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department.
© 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.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Georgia Institute of Technology CS 4320 Fall 2003.
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
Team Software Process (TSPi) CS4320 Fall TSP Strategy Provide a simple process framework based on the PSP. Use modest, well-defined problems. Develop.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
INFO 424 Team Project Practicum Week 2 - Launch report, Project tracking, Review report Glenn Booker Notes largely from Prof. Hislop.
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.
Chapter 8. The Process Phases 1. Launching teams 2. The development strategy 3. Team planning 4. The requirements process 5. Designing with teams 6. Implementation.
THE POSTMORTEM Chapter 10 Introduction to Team Software Process.
PRODUCT IMPLEMENTATION Chapter 8 Tawatchai Iempairote September 23, 2041.
Focus on design principles and on a process for doing design = To produce a precise, complete, high- quality foundation for product implementation.
Introduction to the Personal Software Process. Overview Process Fundamentals PSP Concepts and Structure PSP Planning and Measurement PSP Quality Management.
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
CSC 480 Software Engineering PSP Project 1 August 20, 2004.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
CS 350, slide set 10 M. Overstreet Old Dominion University Spring 2005.
CSC 205 Programming II Lecture 1 PSP. The Importance of High-Quality Work Three aspects to doing an effective software engineering job producing quality.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support.
CSC 480 Software Engineering Team Issues. Essence of a Successful Team To be successful, teams must  Plan their projects  Track their progress  Coordinate.
Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.
CSC 480 Software Engineering
Personal Software Process Team Software Process
9/18/2018 Department of Software Engineering and IT Engineering
A possible solution: Personal Software Process (PSP)
BSA 376 Competitive Success/snaptutorial.com
BSA 376 AID Lessons in Excellence-- bsa376aid.com.
BSA 376 Education for Service/snaptutorial.com
BSA 376 Teaching Effectively-- snaptutorial.com
Engineering Processes
Adaptive Product Development Process Framework
Engineering Processes
Team Software Process (TSP)
Software Reviews.
Presentation transcript:

Sponsored by the U.S. Department of Defense © 2002 by Carnegie Mellon University July 2002 PSP-TSPi Faculty Workshop Pittsburgh, PA Lecture 5: Cyclic Development

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 2 Lecture Overview TSPi Cycle structure Phase process structure Project schedule

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 3 TSPi Cycle Structure Each cycle consists of eight phases and their associated processes. Phase Process Script Team launchLAU Development strategySTRAT Development planPLAN Requirements SpecificationREQ High level designDES Product implementationIMP Integration and system testingTEST PostmortemPM

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 4 Process Structure Each cycle phase has a process script. The process script describes entry criteria interaction of the instructor and the team responsibilities of team managers and members products for the phase exit criteria A process begins with an introduction by the instructor description of the process products of the process explanation of new concepts to be applied in the process The team follows the rest of the process.

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 5 Script Versions Some activities of a phase are unique in the first cycle, e.g., the instructor only describes the product during the launch of the first cycle. For each phase there are two versions of the associated process script, e.g., LAU1 and LAUn. The “1” script is used during the first cycle, and the “n” script is used during subsequent cycles.

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 6 Postmortem Test Postmortem Project Schedule (15 week semester) PSP Review Launch Strategy Planning Requirements DesignImplementTest Launch Strategy Planning Requirements Design Implement Test Postmortem Launch Strategy Planning Requirements Design Implement Test Cycle 1 Cycle 3 Cycle

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 7 Weeks 1 and 2

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 8 Launch Process Activities: Session 1 Instructor Describe objectives of the courseDescribe objectives of the course Request student information and describe how it will be used to make team and role assignmentsRequest student information and describe how it will be used to make team and role assignments Describe the product objectivesDescribe the product objectives

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 9 Launch Process Activities: Session 2 Instructor Assign teams and rolesAssign teams and roles Motivate goal settingMotivate goal setting Describe weekly meeting formatDescribe weekly meeting format Team Leader Discuss individual goalsDiscuss individual goals Discuss team goalsDiscuss team goals Establish weekly meeting timesEstablish weekly meeting times Establish process for getting data to Planning ManagerEstablish process for getting data to Planning Manager Planning Manager Review data required for weekly status reportsReview data required for weekly status reports

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 10 Strategy Process Activities Instructor Describe development strategyDescribe development strategy Explain how to produce size and time estimatesExplain how to produce size and time estimates Development Manager Discuss strategy criteriaDiscuss strategy criteria Select a development strategySelect a development strategy Produce preliminary size and time estimates for the entire projectProduce preliminary size and time estimates for the entire project Conduct risk assessmentConduct risk assessment Support Manager Produce a configuration management planProduce a configuration management plan

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 11 Launch and Strategy Phase Products At the end of the launch and development strategy phases for cycle 1 the team has been formed agreed upon its goals set weekly meeting and reporting times documented a development strategy defined a configuration management process created and updated the project notebook

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 12 Week 3

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 13 Planning Process Activities Instructor Describe the planning processDescribe the planning process Explain task and schedule plans and how to produce task and schedule plansExplain task and schedule plans and how to produce task and schedule plans Explain the quality plan and how to produce itExplain the quality plan and how to produce it Planning Manager Produce the Task PlanProduce the Task Plan Produce the Schedule PlanProduce the Schedule Plan Quality/Process Manager Produce the Quality PlanProduce the Quality Plan Planning Manager Produce engineers’ personal plansProduce engineers’ personal plans Balance the team workloadBalance the team workload

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 14 Planning Phase Products At the end of the planning phase for cycle 1 the team has defined all team member tasks and schedules for cycle 1 completed a project plan summary for cycle 1 estimated sizes of all components for the project defined a quality plan for the project updated the project notebook

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 15 Week 4

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 16 Requirements Specification Process Activities 1 Instructor Describe the requirements processDescribe the requirements process Explain how the SRS will be reviewed and reportedExplain how the SRS will be reviewed and reported Development Manager Review the need statementReview the need statement Formulate questions for the instructorFormulate questions for the instructor Instructor Discuss needs questions with the teamDiscuss needs questions with the team

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 17 Requirements Specification Process Activities 2 Development Manager Outline the SRS and assign team members to write parts of itOutline the SRS and assign team members to write parts of it Produce the SRS draftProduce the SRS draft Lead team in producing and reviewing the System Test PlanLead team in producing and reviewing the System Test Plan Quality/Process Manager Inspect drafts of the SRS and the System Test PlanInspect drafts of the SRS and the System Test Plan Development Manager Complete the SRSComplete the SRS Give SRS to the instructorGive SRS to the instructor Instructor Approve the SRSApprove the SRS Support Manager Place the SRS under configuration controlPlace the SRS under configuration control

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 18 Requirements Specification Phase Products At the end of the requirements specification phase for cycle 1 the team has a completed and inspected SRS and system test plan under configuration control updated the project notebook

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 19 Week 5

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 20 Design Process Activities Instructor Describe the design processDescribe the design process Show a sample SDSShow a sample SDS Explain how the SDS will be inspected and reportedExplain how the SDS will be inspected and reported Development Manager Define products for the cycleDefine products for the cycle Assign design tasks to team membersAssign design tasks to team members Quality/Process Manager Lead the team in defining design standardsLead the team in defining design standards Development Manager Allocate SDS tasks among team membersAllocate SDS tasks among team members Produce the SDS draftProduce the SDS draft Produce the integration test planProduce the integration test plan Quality/Process Manager Inspect the SDS draftInspect the SDS draft Development Manager Produce final SDSProduce final SDS Support Manager Place SDS under configuration controlPlace SDS under configuration control

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 21 Design Phase Products At the end of the design phase for cycle 1 the team has completed, inspected, and corrected the SDS completed, inspected, and corrected the integration test plan completed forms for all inspections updated the project notebook

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 22 Week 6

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 23 Implementation Process Activities Instructor Describe the implementa- tion processDescribe the implementa- tion process Emphasize concern for qualityEmphasize concern for quality Explain how to handle poor quality componentsExplain how to handle poor quality components Team Leader Define and allocate tasks among team members.Define and allocate tasks among team members. Team Members Develop detailed designsDevelop detailed designs Conduct design reviews.Conduct design reviews. Develop unit test cases and procedures for unit testsDevelop unit test cases and procedures for unit tests Produce source codeProduce source code Remove compile defectsRemove compile defects Quality/Process Manager Lead team inspection of componentsLead team inspection of components Team Members Conduct unit testsConduct unit tests Quality/Process Manager Determine whether a component satisfies quality standards and what to do about it if it doesn’tDetermine whether a component satisfies quality standards and what to do about it if it doesn’t Support ManagerSupport Manager Enter components that satisfy quality criteria into the configuration management systemEnter components that satisfy quality criteria into the configuration management system

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 24 Implementation Phase Products At the end of the implementation phase for cycle 1 the team has completed, reviewed, and inspected all cycle 1 components entered each component into the configuration management system completed forms for all inspections updated the project plan summary and quality plan summary updated the project notebook

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 25 Week 7

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 26 Testing Process Activities Instructor Describe the integration and test processDescribe the integration and test process Emphasize the need for high quality components prior to integration testingEmphasize the need for high quality components prior to integration testing Explain how to handle components that don’t meet quality criteriaExplain how to handle components that don’t meet quality criteria Development Manager Lead test developmentLead test development Define build processesDefine build processes Develop integration test procedures and toolsDevelop integration test procedures and tools Develop system test procedures and toolsDevelop system test procedures and tools Team Members Build the productBuild the product Development Manager Lead integration tasksLead integration tasks Lead system test tasksLead system test tasks Lead the team in producing user documentationLead the team in producing user documentation

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 27 Testing Phase Products At the end of the testing phase for cycle 1 the team has completed, integrated, and system tested the cycle 1 components recorded data in the testing log updated the project plan summary and quality plan summary updated the project notebook

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 28 Week 8

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 29 Postmortem Process Activities Instructor Describe the process.Describe the process. Emphasize the need for good dataEmphasize the need for good data Explain the contents of the cycle reportExplain the contents of the cycle report Explain how performance will be evaluatedExplain how performance will be evaluated Quality/Process Manager Lead team in analyzing team data.Lead team in analyzing team data. Prepare PIPsPrepare PIPs Team Leader Lead team in evaluating role performanceLead team in evaluating role performance Assign tasks for cycle report.Assign tasks for cycle report. Assemble, review, and correct the final cycle reportAssemble, review, and correct the final cycle report Team Members Evaluate role performance of peers and rolesEvaluate role performance of peers and roles

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 30 Postmortem Phase Products At the end of the postmortem phase for cycle 1 the team has produced a well documented high quality product placed the product under configuration control evaluated process data and prepared PIPs where appropriate evaluated roles, both personal and of other team members completed all TSPi forms completed the project notebook for cycle 1

© 2002 by Carnegie Mellon University July, 2002 Lecture 5: Cyclic Development - page 31 Lecture Summary Effective planning is a critical element in the success of a software project. The TSPi has a well defined structure. TSPi has three cycles; each cycle has eight phases and an associated process. The process script for each phase defines the activities for each role and the products to be produced.