CS 476 / CIS 676: Software Engineering II / Project Management

Transcription

1 CS 476 / CIS 676: Software Engineering II / Project Management Spring 2010 Customers expect high-quality software products to be delivered on time, and within specification. This course investigates techniques in the software development process that can assure high quality on schedule. We will consider software engineering methodologies: Project Management Institute s guidelines, Software Engineering Institute s Capability Maturity Model (SEI CMM) and Extreme Programming. As part of this evaluation we will focus on project management, requirements management, inspection, configuration management, and testing. Finally, software projects require soft skills, including communication and interpersonal skills. These skills will be developed by participation in a real-world software project, as part of a group. Instructor: Susan J Lincke, Ph.D. lincke <at> uwp.edu Web Page: Office Hours: Wed, 1-6 PM Office Phone: (262) or by appt. Office Location: MOLN 255 Class Hours: Tues. 2-3:15 PM Class Location: MOLN 318 Text: Essentials of Software Engineering, Frank Tsui, Orlando Karam Prerequisites: CS 475, CIS 625 or CIS 675: Software Engineering I, and knowledge of Java, C#, or Visual Basic. Projects: Students will participate in a group project Grading: Undergrad: Graduate: Class/Group exercises & participation 10% 5% 2 Exams (20%, 25%) 45% 45% Group project 45% 45% Short Paper 5% Graduate students will in addition write a short paper evaluating 5 related research papers. Grading Scale: A= 90% B=80% C=70% D=60% F<60% Plus grades are assigned for grades within 2% of the next higher grade. Minus grades are assigned for grades with in 2% of the next lower grade. Exam Dates: Exam 1: Tuesday, March 3 Final Exam: Tuesday, May 12, 5:45 PM

2 Course Outline: 1. Introduction to Process (Chapters 3.1, 3.3, Chapter 4) 2. Requirements / User Interface (Chapters 6, 7.3.4, 8.5) 3. Project Estimation & Scheduling (Chapter 13.1, 13.3) 4. Project Plans & Risk (Chapter 13.2) 5. Inspections (Chapter 10.5) 6. Test (Chapter 10) 7. Project Tracking (Chapter ) 8. Change Management (Chapters 11, 12) 9. Metrics & Process Improvement (Handout) 10. Agile/Extreme Programming & Comparison to Traditional (Chapter 5) Course Regulations: Attendance: Excellent attendance is necessary for this class, in order to participate with your group, learn the material, and achieve passing grades. If you cannot attend class, please speak with the instructor in order to determine how best to catch up on missed lectures and exercises. Exam Make-Ups: Prior notice must be given to me when an exam must be missed. No make-up exams will be granted unless satisfactory documentation is produced to show an extenuating circumstance. Academic Honesty: Any indication of copying project work or any behavior during exams that could be considered copying or cheating will result in an immediate zero on the assignment or exam for all parties involved. In addition, the student s advisor/department will be notified. Cheating on assignments is defined to be copying from someone else or providing someone else copies of your answers. Do not show your assignments to anyone else! You may answer questions on labs or project homework asked by other students. Accommodation for Religious Observances: UW-Parkside policy requires that reasonable accommodation for a student s religious beliefs. Please notify your instructor within the first two weeks of classes about any scheduled class date that conflicts with a religious observance. Students with a Disability: Anyone who has special needs that must be accommodated to fulfill the course requirements should contact the Disability Services Coordinator in the Office of Educational Support Services (WLLC D175, ), and keep me informed. The University has many resources available to assist students with their academic studies.

3 The Project Notebook is divided as follows: Group Project Documentation Project Management Section (PM): Project Charter Project Management Plan Early Gantt Chart Software Configuration Plan (QM) Completed PMP Inspection Form (QM) Schedule of Delivery Signoff with Customer Requirements Section: (not PM) Requirements Document (Document including Use Case, Prototype) Change Requests Requirements Signoff with Customer (QM) Design Section: (not PM) Design Document (UML diagrams and explanatory text) Completed Design Document Inspection Form (QM) Code Section: Code & Unit test code (well documented, indented, with programmer name) Note: Every project member must be responsible for coding some part of the total code. Test Plan/Reports Section (TM): Acceptance Test Plan Completed Test Report Defect Reports Completed Acceptance Test Plan Inspection Acceptance Test Signoff with Customer Software Installed Signoff with Customer (TM/OM) Beta Test Completed Signoff with Customer (TM/OM) Status Reports: Status Reports (PM) Completed Change Requests (OM) Closure Report Section (QM): Closure Report & Process Database Updated/Completed Gantt Chart (PM) Optional Sections: Users Manual w. Inspection & Customer Signoff Communications with Customer: e.g., , notes, example reports Grading: (Instructor)

4 Group Project Assignments Due Responsibility: Each person is required to contribute to the programming of the project. In addition, each person will be allocated management responsibility for one of the following: Project Management (PM): Project Management Plan, Gantt Chart, Status Reports, Initial customer signoff Prepares Project Charter. Prepares the SPMP: schedules work and standards for team members Submits status reports every week on Tuesdays Prepares and submits Gantt Chart at beginning and end of project Test Management (TM): Test plan development, Test reports, Defect Reports, Final Customer Signoffs. Prepares test plans and test files for integration and acceptance testing Administers or observes tests, and completes test report, which indicates the status of a test plan execution Writes Defect Reports for each bug found during testing Collects final signoffs from customer at end of project Quality Management (QM): Software Config. Plan, Inspection Forms, Closure Reports Updates SCP to describes how software is built, coordinated, and archived Helps others use Subversion configuration management tool. Ensures inspections occur on SPMP, Requirements, Design, Test, (Users) Manuals and appropriate forms are completed Evaluates statistics and writes Closure Report to describe how project progressed. Operations Management (OM): Installations, Customer Training, Users Manual, Maintenance management including creating/driving Change Requests, Final installation signoffs. Coordinates with customer for dates for installation. Prepares and coordinates installation. Collects final signoffs from customer at end of project Writes or updates the Users manual or help screens; trains customer. Competes change requests as changes are implemented. Technical Leader (TL): Technical Training. Trains team members on new programming language Oversees development of Requirements and Design documents; prepares initial change requests Offers technical assistance when technical problems are encountered For projects of 3/4 people, the first 3/4 manager positions shall be selected. Grading: Grading will be both individualized and by group. For example, each manager is responsible for their documents, and associated grades will be assigned only to them. Design documents and code should be done by the group, and thus group grades will be assigned, unless otherwise agreed to. Any stage that is late will encounter a sliding scale two grade deduction for up to 1 week late. Any assignments at or over 1 week late will be eligible only for a D grade. D grades will also be assigned for sub-standard work, which includes inadequately documented work products. Note: Resubmissions will be allowed, but only for a one-grade enhancement for much improved work. Each work product will be graded for completeness, proper format, proper English, and correctlydrawn UML diagrams.

5 Project Charter: Due Feb 9. Provide dates of each stage: Must be realistic and balanced to meet the delivery schedule Provide deliverables for each stage. The deliverables, including their contents must be specified. Project Charter must be signed by customer. Note: (Weight: 10) The Project Charter stage, which is due the third week of the semester, lays out the deliverables and times of each of the stages. Each group will have one week to contact their customer and define the project stages and delivery dates. Schedules are negotiable with instructor, but instructor can overrule suggested dates. Requirements Stage Homework: Tentatively due Feb. 23 Project Management Plan (weight: 10) Change Requests (weight: 2 per CR) Requirements Document (weight: 10) May include Use Case, prototype, activity diagrams, extensive text. Requirements Inspection Form with Accepted Status (weight: 2) PMP Inspection Form with Accepted Status (weight: 2) SCP with changes (weight: 3) Customer Sign-off on Requirements and Schedule of Delivery (weight: 3) Analysis/Design Stage Homework: Design Document (weight: 10) May include Class (/Subsystem) Diagram, E/R Diagram, Sequence/Communication Diagrams, Activity Diagrams, State Diagram, and text. Design Inspection Form with Accepted Status (weight: 2) Note: In CS475, partial designs were sometimes allowed for certain diagram types (e.g. Sequence Diagrams). Also, text was allowed to be short, since we all knew how to play Clue. However, with commercial products, all projects must be fully documented, since I and/or future students will not be able to understand your document without it. Implementation Stage Homework: Due April 13 Gantt Chart (weight: 3) Acceptance Test Plan (weight: 10) Customer Sign-off on Acceptance Test Plan (weight: 2) Acceptance Test Form Passed status & Customer Signoff (weight: 2) Customer Sign-off: Software Installation Completed (weight: 2) Users Manual (weight: 5) Users Manual Inspection Form with Accepted Status (weight: 2) Delivery Stage Homework: Due May 4 Code & Unit Test (weight: 10) Gantt Chart (weight: 2) Defect Recording Logs (weight: 5) Closure Report & Process Database (weight: 10) Customer Sign-off: Beta Test Completed (weight 2)