SE-280 Dr. Mark L. Hornick 1 Software Engineering Process Based on what you have learned so far… What is your current development process? What can you.

Slides:



Advertisements
Similar presentations
Introduction to PSP Copyright, 1999 © Jerzy R. Nawrocki Personal Software Process Lecture.
Advertisements

Kai H. Chang COMP 6710 Course NotesSlide CMMI-1 Auburn University Computer Science and Software Engineering Capability Maturity Model Integration - CMMI.
27-Feb-01 1 Implementing Effective Requirements Practices Presented by Dr. Ralph R. Young Director, Software Engineering Systems and Process Engineering.
Team Software Process By: Bryan Peterson. Presentation Topics History Brief overview of the Team Software Process (TSP) TSP Team Launch Team-working Conclusion.
Copyright © by Mark J. Sebern Software Engineering Process I Dr. Rob Hasker L-331, hasker (Adapted.
Tools for Efficient Implementation Tools for efficient implementation: Design environments ----GUI design tools Configuration management Good coding habits--PSP.
SEP1 - 1 Introduction to Software Engineering Processes SWENET SEP1 Module Developed with support from the National Science Foundation.
PRO2 - 1 Introduction to the Personal Software Process SWENET PRO2 Module Developed with support from the National Science Foundation.
Software Life Cycles ECE 417/617: Elements of Software Engineering
Important concepts in software engineering The tools to make it “easy to apply common sense”!
Organizational Project Management Maturity Organizational Project Management Maturity Model (OPM3) PMI-MN Breakfast sessions Process Management.
Important concepts in software engineering The tools to make it easy to apply common sense!
1 - Sudhir P, Balasubrahmanyam P Leveraging TSP SM /PSP SM Metrics to drive Predictability and Quality of product releases An Intuit Perspective.
GriffithHonoursCollege Dr Jeanne McConachie, Manager.
The Problem: Software Crisis “ Historically, few software organizations have reliably met their cost and schedule commitments.” -Humphrey, pg. 2 The Solution:
Software Development Process. Process Improvement Using the Shewhart Cycle 1.PLAN - Plan a change aimed at improvement, collect data, and establish a.
Computer Engineering 203 R Smith Process/Plan Model 7/ Development Process Models Development Process Models are different ways to look at the processes.
Fundamental of Software Project Management Team Assignment 1 – K15T2 – Team 07.
Personal Software Process Overview CIS 376 Bruce R. Maxim UM-Dearborn.
CMM Level 3 KPA’s CS4320 Fall Organizational Process Focus (Goals) Software process development and improvement activities are coordinated across.
Productive Engineering Teams
PRIVATE AND CONFIDENTIAL © Bombardier Inc. or its subsidiaries. All rights reserved. TrackSafe An Ontario based story of successful collaboration Mark.
Team Launch Introduction. Real projects are large and complex, and most software is created by teams Merely throwing people together does not result in.
Prof Barry Dwolatzky JCSE at Wits University Government CIO Summit Towards reducing costs of doing business in government and contributing towards achieving.
Software testing techniques Testing Maturity Model Presentation on the seminar Kaunas University of Technology.
SE-280 Dr. Mark L. Hornick 1 Process Adaptations.
J. R. Burns, Texas Tech University Capability Maturity Model -- CMM n Developed by the Software Engineering Institute (SEI) in 1989 –SEI is a spinoff.
Page 1 Sponsored by the U.S. Department of Defense © 2007 by Carnegie Mellon University Watts S. Humphrey The Software Engineering Institute Carnegie Mellon.
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 31 Slide 1 Process Improvement u Understanding, Modelling and Improving the Software Process.
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
SE-280 Dr. Mark L. Hornick 1 In software engineering, we sometimes distinguish between "practice" and "process". By "practice", we mean "what" software.
Lecture 1 Introduction to Software Engineering
SE 501 Software Development Processes Dr. Basit Qureshi College of Computer Science and Information Systems Prince Sultan University Lecture for Week 6.
Copyright, 2006 © L. Ouyang Introduction to PSP Liubo Ouyang Personal Software Process Lecture 1.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
NSF IGERT proposals Yang Zhao Department of Electrical and Computer Engineering Wayne State University.
SE 501 Software Development Processes Dr. Basit Qureshi College of Computer Science and Information Systems Prince Sultan University Lecture for Week 9.
Software Engineering Prof. Dr. Bertrand Meyer March–June 2007 Chair of Software Engineering Lecture 2: The Personal Software Process.
Winter 2005SE-280 Dr. Mark L. Hornick Personal Software Process: Initial Process Overview.
Continuing Education and Curricula for RAC and CE Applications CIWMB CSU, Chico CIWMB CSU, Chico Prepared for Meeting with CIWMB March 7, 2007 Prepared.
©Ian Sommerville 2004 Software Engineering. Chapter 28Slide 1 Chapter 28 Process Improvement.
“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.
PSP Quality Strategy [SE-280 Dr. Mark L. Hornick 1.
SE-280 Dr. Mark L. Hornick 1 SE-280 Software Engineering Process Dr. Mark L. Hornick web: myweb.msoe.edu/hornick SE280 info syllabus,
SE-280 Dr. Mark L. Hornick 1 Design and Code Reviews Review Checklists.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Watts Humphrey IBM director of programming and vice-president of technical development Joined CMU Software Engineering Institute in 1986 Initiator and.
SE 501 Software Development Processes Dr. Basit Qureshi College of Computer Science and Information Systems Prince Sultan University Lecture for Week 11.
Personal Software Process PSP--Personal Software Process.
Software Engineering at MSOE Mark Sebern Professor & BSSE Program Director Milwaukee School of Engineering.
Advanced Software Engineering Lecture 4: Process & Project Metrics.
SE1011 Week 3, Class 2 Today Sit down by someone you don't know Learn their name Find out who came farther to get to MSOE at the start of the quarter Designing.
Introduction to the Personal Software Process. Overview Process Fundamentals PSP Concepts and Structure PSP Planning and Measurement PSP Quality Management.
U16 – Lifestyle Management. Key Points Identify the differences between individuals Explore the pressure on young talented players Identify Strategies.
Process Improvement Understanding, Modelling and Improving the Software Process.
The Software Process CpSc 372: Introduction to Software Engineering Jason O. Hallstrom Authorship Disclaimer. These slides are intended.
Final Report Goals and Objectives. SE-280 Dr. Mark L. Hornick 2 PSP Self-review questions How good is my process? Where can it be improved? What is the.
Watts Humphrey IBM director of programming and vice-president of technical development Joined CMU Software Engineering Institute in 1986 Initiator and.
Essential Needs of Software Test Automation
A possible solution: Personal Software Process (PSP)
Mapping TSPSM to CMMI® Jim McHale Software Engineering Institute
Software Engineering Lecture 16.
Software Engineering I
See The Change USA (STC) and Colorado Geographic Alliance (COGA)*
The role of Planning in the Software Development Process
SE-1011 Slide design: Dr. Mark L. Hornick Instructor: Dr. Yoder
SE-1011 Slide design: Dr. Mark L. Hornick Instructor: Dr. Yoder
Software Engineering Practices
Presentation transcript:

SE-280 Dr. Mark L. Hornick 1 Software Engineering Process Based on what you have learned so far… What is your current development process? What can you say about it? What is good/bad about it?

SE-280 Dr. Mark L. Hornick 2 If you are given a requirements specification for a medium-sized program, could you state in advance how long it would take you to write the program?... how many defects you would inject during its development?... how many defects will remain when it is completed?

SE-280 Dr. Mark L. Hornick 3 Why do we need a Process? Many organizations today cannot meet commitments with repeatability Project A completes without any problems Project B is a disaster Late Incomplete Not tested Too many times, the result is Cancelled projects Management over-reaction

SE-280 Dr. Mark L. Hornick 4 Data from PSP training courses usually show similar results for practicing software engineers and MSOE SE students. SEI: 810 engineersMSOE: 30 sophomore students

SE-280 Dr. Mark L. Hornick 5 And sometimes they don’t agree... SEI: 810 engineersMSOE: 30 sophomore students

SE-280 Dr. Mark L. Hornick 6 Testing time is a major cost in commercial software development; PSP course data shows a general reduction in test time. SEI: 810 engineersMSOE: 30 sophomore students

SE-280 Dr. Mark L. Hornick 7 Even with additional PSP planning and quality activities, overall productivity remains nearly constant. SEI: 810 engineersMSOE: 30 sophomore students

SE-280 Dr. Mark L. Hornick 8 Industry experience shows that the TSP can help teams achieve high levels of quality. Total Delivered Defects/KLOC N. Davis and J. Mullaney, The Team Software Process (TSP) in Practice: A Summary of Recent Results, Technical Report CMU/SEI-2003-TR-014,

SE-280 Dr. Mark L. Hornick 9 [Source: AIS] CMM introduced TSP introduced By increasing predictability, the TSP helps teams to function more effectively.

SE-280 Dr. Mark L. Hornick 10 In 2005, Humphrey was awarded the National Medal of Technology for his work in software process improvement.

Jan 15, 2009 Watts Humphrey named ACM Fellow For contributions to computing and Information Technology For innovations made in areas critical to Global Competitiveness For contributions to software engineering process discipline SE-280 Dr. Mark L. Hornick 11 Watts Humphrey

SE-280 Dr. Mark L. Hornick 12 You can improve your own performance as a software engineer using disciplined methods, but it does take some effort. MSOE sports photos courtesy of Dr. Eric Durant

SE-280 Dr. Mark L. Hornick 13 Here are a few references on SE process, PSP, and TSP. W. Humphrey, PSP – A Self-Improvement Process for Software Engineers, A-W, 2005 W. Humphrey, Introduction to the Team Software Process, A-W, 2000 W. Humphrey, Winning with Software: An Executive Strategy, A-W, 2002 N. Davis & J. Mullaney, The Team Software Process in Practice: A Summary of Recent Results, SEI, 2003 SEI/CMU-2003-TR-014 ( D. Suri and M. Sebern, “Incorporating software process in an undergraduate software engineering curriculum: challenges and rewards”, Proceedings of CSEE&T’04, 2004 M. Sebern, “The software development laboratory: incorporating industrial practice in an academic environment”, Proceedings of CSEE&T’05, 2005