1CS 350: Introduction toSoftware EngineeringSlide Set 1C. M. OverstreetOld Dominion UniversityFall 2005Fall 2005 CS 350/ODU 2Lecture overview Announcements Class expectations Structure, grading, project, logistics, semester structure PSP: what’s it about TSP: what’s it about PSP0: detailsFall 2005 CS 350/ODU 3CS 350: Intro to SETexts: 1) PSP: A Self-Improvement Process for Software Engineers Watts S. Humphrey, Addison-Wesley, 2005.2) Introduction to the Team Software Process, Watts S. Humphrey, Addison-Wesley, 2000 (not used till we finish PSP text).2Fall 2005 CS 350/ODU 4Miscellaneous Class Information Class material is available on web (www.cs.odu.edu/~cmo under cs350) Class is time consuming But more time spent on process than coding Reading assignments:  PSP, chapters 1 & 2Fall 2005 CS 350/ODU 5Recitations - 1 Recitations meet on Tuesdays & Fridays But not this week!Fall 2005 CS 350/ODU 6Recitations - 2 Recitations: You must register for one You must attend Will be used for:•Group meetings (later)•Project discussions•Covering some software tools•Reviews of class performance on programming• Your data compared to class averages•Answering questions3Fall 2005 CS 350/ODU 7Announcements You must have a CS dept account: Go to www.cs.odu.edu, pick Online Services, then select Account Creation.Fall 2005 CS 350/ODU 8General Information Prerequisites CS 361 or CS 330  UNIX exposure Helpful background Some simple statistics (but we’ll cover in class as needed)Fall 2005 CS 350/ODU 9Course Overview Activities: 5 programming assignments, PSP based 1 team project, TSP based 2 in-class exams & comprehensive final recitation/class assignmentsGrading: Individual projects: 25% Team project: 20% In-class exams: 25% Recitation/class assignments: 10% Final exam: 20%4Fall 2005 CS 350/ODU 10From the Syllabus Honor code Lateness policy Special needs Read the syllabus!Fall 2005 CS 350/ODU 11Slides Available before class on Web Slides are OUTLINE only. For content, read textbooks, assigned readings For content, come to class If class is missed, get GOOD notes from class memberFall 2005 CS 350/ODU 12Structure/purpose of class projects Not about programming Focus is on the process used to develop software products. Learning the process involves using it to development some software. Five individual projects involving coding However you will spend more time on process steps than coding• Industry data: of total project time, 15% is coding Emphasize your Personal Software Process One team project Emphasizes the Team Software Process5Fall 2005 CS 350/ODU 13Course Objectives 1: PSP Introduce you to a process-based approach to developing software Show you how to measure and analyze your Personal Software Process (PSP) Improve your software development skills: faster development fewer errors (i.e. better software) more predictable (more accurate estimates of time required to complete a project) Show you how to use data to improve your personal performanceFall 2005 CS 350/ODU 14Course Objectives 2: TSP Working on teams requires specific skills TSP goals: Understand how to build teams Understand different team roles Understand how to work on teamsFall 2005 CS 350/ODU 15Quick Survey (Quiz 1!) By Fri.!! What’s best prog. language? What language do you prefer to use: Your largest program: a. < 500 loc b. > 500 & < 1 kloc c. > 1 & < 10 kloc d. > 10 & < 100 kloc e. > 100 kloc What’s a kloc? a. comments inc.? b. declarations? c. only exec. stmts? d. number of CRs?Mail to [email protected] 2005 CS 350/ODU 16Difference in CS and SE - 1 SE: Mgmt: How do you predict costs, project time, determine if on budget & schedule?  Economics: What's the cheapest way to build it? Reliability, etc: How do you make it reliable? CS: What can computers do? How do you make computers do things efficiently? Some people think CS is part of SE, others that SE is part of CS. Which is correct?Fall 2005 CS 350/ODU 17Other Differences Frequent student view: I assume (or hope) the code I wrote works. Typical professional view: I assume the code doesn't work (no matter who wrote it).  Someone (usually me) must prove it does before I let it mess other things up. In many organizations, correctness of a new component must be demonstrated before it is incorporated into project base.Fall 2005 CS 350/ODU 18SE emphasis on metrics & data It’s not engineering if you can’t measure and predict. You can’t predict if without data!7Fall 2005 CS 350/ODU 19PSP composed of this week’s "best-known practices" May be different next year; probably very different in 10 years as we learn more. Approaches similar to PSP are widely advocated, and often used in industry. Past perception: most software organizations use poor practices resulting in overly expensive, late, and unreliable software. This must change otherwise more software jobs will move to India! Now required of DoD software contractors.Fall 2005 CS 350/ODU 20Unpleasant Facts of life: Some PSP aspects I don’t like. Some I don't believe. You may not either, but after this course, you should be knowledgeable. You will have been exposed in detail to one highly regarded soft process; there a many others. Future of software development? India has bright, well-trained software developers, earn $15k rather than $80k per year It's all about costs, predictability, and quality! In PSP If you can find a better way to reduce costs, improve quality and increase predictability – and can show it works, you should use it. And you can make a lot of money!!!!Fall 2005 CS 350/ODU 21Process, Process, Process! Current industry belief: the process used to develop software has significant impact on quality and costs. Things like programming language or design notation mostly don’t C++, C#, Java, PHP, UML will be replaced with something So get the process right!8Fall 2005 CS 350/ODU 22The PSP Metaprocess A process consists of a defined sequence of a steps. For PSP, each step consists of: A set of entry criteria - step cannot start until all entry conditions are satisfied A sequence of carefully defined activities - this is the work to be done in