CS 501: Software EngineeringAbout the CourseCourse AdministrationAcademic IntegritySlide 5Slide 6Grading (Subject to Change)Feedback about the Group ProjectsOverall Aim of the CourseProjectsProject SelectionThoughts about Project SelectionVariety of Software ProductsSoftware is ExpensiveSoftware in ExpensiveClientClients: Categories of Software ProductSoftware is RiskySlide 19TeamsObservations about Big ProjectsPrevious Experience (Yours)Future ExperiencePrevious Experience (Mine)Course Themes: RiskCourse Themes: VisibilityCourse Themes: ProcessCourse Themes: ScaleWhat is Good Software?The Craft of Software DevelopmentProfessional ResponsibilityStudy of Group ProjectsNext Steps1CS 501 Spring 2006CS 501: Software EngineeringLecture 1Introduction to Software Engineering2CS 501 Spring 2006About the CourseWeb site: www.cs.cornell.edu/Courses/cs501/2006sp/Email: [email protected] (student to course team)Newsgroup: cornell.class.cs501 (student to student)Instructor: William ArmsTeaching assistants: Theresa Velden, Gopal Parameswaran Assistant: Susan Moskwa3CS 501 Spring 2006Course AdministrationEmailTo contact members of the course team, send email to:[email protected] not send email to the instructor or an individual teaching assistant, except for questions to the teaching assistant assigned to your project.Teaching Assistants do not have office hours, but you can schedule an appointment by email.4CS 501 Spring 2006Academic IntegritySoftware Engineering is a collaborative activity. You are encouraged to work together, but ...• Some tasks may require individual work.• Always give credit to your sources and collaborators.Good professional practice: To make use of the expertise of others and to build on previous work, with proper attribution. Unethical and academic plagiarism: To use the efforts of others without attribution.See: Code of Academic Integrity on the course Web site, which points to the Cornell code.5CS 501 Spring 2006About the CourseSyllabusFor the schedule of lectures, assignments, readings and quizzes, see the Syllabus file on the course Web site. (Note that this syllabus may change as the course progresses.)QuizzesFour quizzes held during class times. No examinations. (See Quizzes on the Web site for details.)Wednesday eveningThis time is for project team meetings. You may choose to meet at other times, but each project should have at least one regular weekly meeting.6CS 501 Spring 2006About the CourseReadings:There is no course textbook. See the Books and Readings file on the Web site. Technical writing:Engineering undergraduates may be able to use the project for their technical writing requirement. Contact me if you wish to do so.7CS 501 Spring 2006Grading (Subject to Change)Project (group) 45%Project (individual) 25%Quizzes 30%8CS 501 Spring 2006Feedback about the Group ProjectsThere will be five questionnaires, at the beginning of the course and at the time of each assignment.Assignment questionsQuestions about how each member of your team contributed to the work of the group -- to identify those individuals who make extra effort or do not contributed fully.Study of group projectsStudy by Professor Connie Yuan and Sadat Shami on group projects -- to improve this course and other courses that require group work. Introduced by Sadat at the end of this class. Everybody must sign a consent form.9CS 501 Spring 2006Overall Aim of the CourseWe assume that you are technically proficient. You know a good deal about computing, can program reasonably, can learn more on the job.When you leave Cornell, you are going to work on production projects where success or failure costs millions of dollars.Soon you will be in charge! It may be your money!We want you to make your mistakes now and learn from your mistakes.10CS 501 Spring 2006ProjectsThe Course is Built around the Projects• Real project for real client who intends to use the software in production.• Select your own project, any branch of software development• Project teams, 5 to 7 people.• Feasibility study and plan: due February 17• Three group presentations and reports:either: requirements, design, finalor: 1st iteration, 2nd iteration, finalThe class on Thursday will discuss the projects.11CS 501 Spring 2006Project SelectionRead the Web site• Some projects are suggested on the Web site and will be discussed in class on Thursday• You are encouraged to find other projectsContact potential clients• Gain idea of their expectations• Estimate scope and complexity of the project• Discuss business decisionsAssemble project team• Post message on newsgroup cornell.class.cs501• Advertise at the beginning of class12CS 501 Spring 2006Thoughts about Project SelectionProjects• Target must be a production system (not research)• Client should be one or two designated people -- client should be prepared to meet with you regularly and attend the presentationsTeam• Teams need many strengths -- organizational, technical, writing, etc.• Consider appointing a leader to coordinate the effort13CS 501 Spring 2006Variety of Software ProductsExamplesReal time: air traffic control Embedded systems: digital camera, GPS, iPodData processing: telephone billing, pensionsInformation systems: web sites, digital librariesSensors: weather dataSystem software: operating systems, compilersCommunications: routers, telephone switchesOffices: word processing, video conferencesScientific: simulations, weather forecastingGraphical: film making, design etc., etc., etc., ....14CS 501 Spring 2006Software is ExpensiveSoftware is expensive!The major costs are salaries (your salaries)!Every software project has a trade-off between: Functionality Resources (cost) TimelinessExample: Console monitor15CS 501 Spring 2006Software in ExpensiveWho is paying the money?What does that person or organization want?• What is success?• What is failure?Technical people may have very different criteria of success from the people in charge of the organization.Example: Early Unix workstations, Sun and IBM16CS 501 Spring 2006ClientClient (a.k.a. Customer)The client provides resources and expects some product in return.The client is often a member of the organization that is providing the money. The client's job success depends on the success of the software project. Client satisfaction is the primary measurement of success in a software project.Question: Who is the client for Microsoft
View Full Document
Unlocking...