1CS 350: Introduction toSoftware EngineeringSlide Set 1C. M. OverstreetOld Dominion UniversitySpring 2006Spring 2006 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: detailsSpring 2006 CS 350/ODU 3Announcementso CS Dept. Systems groups looking for peopleo Contact Ajay Gupta.o Any interest in working closely with students in Berlin, Germany on term project?o German not required! Everything in Englisho Trip to Berlin in Spring Breako Partial support for tickets likelyo Free stay (almost) in Berlin likelyo Need at least 5 people to make this work2Spring 2006 CS 350/ODU 4CS 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).Spring 2006 CS 350/ODU 5Miscellaneous 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 & 2Spring 2006 CS 350/ODU 6Recitations - 1 Recitations meet on Fridays But not this week!3Spring 2006 CS 350/ODU 7Recitations - 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 questionsSpring 2006 CS 350/ODU 8Announcements You must have a CS dept account: Go to www.cs.odu.edu, pick Online Services, then select Account Creation.Spring 2006 CS 350/ODU 9General Information Prerequisites CS 361 or CS 330  UNIX exposure Helpful background Some simple statistics (but we’ll cover in class as needed)4Spring 2006 CS 350/ODU 10Course 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%Spring 2006 CS 350/ODU 11From the Syllabus Honor code Lateness policy Special needs Read the syllabus!Spring 2006 CS 350/ODU 12Slides 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 member5Spring 2006 CS 350/ODU 13Structure/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 ProcessSpring 2006 CS 350/ODU 14Course 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 performanceSpring 2006 CS 350/ODU 15Course Objectives 2: TSP Assumes large software project Many people Maybe > 100,000 KLOC Working on teams requires specific skills TSP goals: Understand how to build teams Understand different team roles Understand how to work on teams6Spring 2006 CS 350/ODU 16One problem with teaching SE principles Students often don’t see need if they haven’t worked on large software projects if they haven’t worked on projects where quality is required• Society increasing reliance on software whose failure can do significant harm General observation: currently accepted SE principles slow things down in order to speed things up! These techniques work! But programmers (generally) don’t like themSpring 2006 CS 350/ODU 17One definition of software engineering: Computer science with economics What’s the cheapest way to build a quality system? One definition of an engineer: Someone who can for dime what any fool can build for a dollar.Spring 2006 CS 350/ODU 18Quick Survey (Quiz 1!)Due Tues.!! What’s best prog. language? What language do you prefer to use: What’s the best OS? What’s the best debugger! Your largest program:a) < 500 locb) > 500 & < 1 klocc) > 1 & < 10 klocd) > 10 & < 100 kloce) > 100 kloc What’s a kloc?a) comments inc.?b) declarations?c) only exec. stmts?d) number of CRs?Mail to [email protected] Tues. Jan. 177Spring 2006 CS 350/ODU 19SE emphasis on metrics & data It’s not engineering if you can’t measure and predict. You can’t predict if without data!Spring 2006 CS 350/ODU 20PSP composed of this week’s "best-known practices" May be different next year; likely very different in 10 years. 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.Spring 2006 CS 350/ODU 21Unpleasant 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 software process; there a many others. Future of software development? India has bright, well-trained software developers, that earn $15k rather than $80k per year PSP is all about costs, predictability, and quality! In PSP: If you can find a better way to reduce costs, improve quality and improve predictability – and you have data shows it works, you should use it.8Spring 2006 CS 350/ODU 22Process, 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