Course Description:

This course is an introduction to software process, process models and software project management. This course builds on the student's software engineering knowledge base acquired from Software Engineering I (SE361) and optionally from other SE courses and/or coop experiences. The course takes a project management perspective on process not necessarily to encourage a management career path, but to better understand the activities that occur in all software development projects, be that from the developer or project manager's viewpoint.

* Please spend some time reading this document, as it contains vital information about the texts, course policies and grading.

Sections:

Term:

SPRING 2013

Course Topics:

The course will encompass a variety of concepts and topics, among them are the following:

• Elements of Successful Software Projects
• Teamwork & Managing People
• Risk Management
• Plan-Driven and Agile Process Methodologies
• Process : Selecting, Tailoring, Assessing
• Planning (Estimating, Scheduling, Tracking)
• Introduction to Measurements & Metrics
• Quality Assurance & Frameworks
• Software Product Evolution

Course Objectives:

You will likely not be an expert on Project Management by the end of this course. However, you should gain valuable insight as to the various dimensions of software process and project management. You should understand software planning, estimation and tracking techniques and be able to recognize the effects an effective process and adequate metrics have on project success. Finally, you should be able to compare and contrast the applicability of process models and methodologies as well as be able to select and apply these in creating a software development plan.

Method of Instruction:

Course will combine lecture and in-class activities. Students will collaborate inside and outside of class in support of activities and project deliverables. Assignments will include selected readings, project write-ups, as well as activities focused in supporting the materials reviewed in class.

Textbook(s):

Required: (Note: Both are available at Books 24x7. There should be a plentiful supply of used copies if you would like a print copy.)

• "Rapid Development", Steve McConnell (available in bookstore, also on-line at Books 24x7)
• “Software Project Survival Guide", Steve McConnell (on-line at Books 24x7)

Recommended:

• "Professional Software Development", Steve McConnell - Excellent, every SE should own one
• "Herding Cats: A Primer for Programmers Who Lead Programmers", J. Hank Rainwater (on-line at Books 24x7)
• "The Mythical Man-Month", Frederick Brooks

Attendance Policy:

Come to class. We have 20 scheduled sessions. Missing one session is equivalent to half a weeks worth of classes or 5% of the quarter. Most sessions contain class team work that requires all team members to be present to gain full benefit. You have one unexcused absence (slept in, car won't start, etc.) with no consequences. After that the following cumulative scale applies for additional unexcused absences:

Make up exams will only be granted for very good reasons (job interviews known in advance, documented sickness, family emergencies, etc.) Heavy workload in other (maybe to you more important) courses is typically not a very good reason.

• One unexcused absence - 1 % off final grade
• Two unexcused absences - 3 % off final grade
• Three or more unexcused absences - 5 % off final grade
• Three late arrivals will be considered as one absence – it is your responsibility to notify the instructor the day you arrived late and missed attendance call.

* Additionally, you will also miss credit for activities that took place during the classes you were absent. Bottom line come to class.

Make up exams will only be granted for very good reasons (job interviews known in advance, documented sickness, family emergencies, etc.) Heavy workload in other (maybe to you more important) courses is typically not a very good reason.

Be professional. Practice common courtesy when I or your fellow colleagues are speaking, which leads us to:

Keep your hands off the mouse/keyboard, unless of course we are doing something that requires you to use your computer. From time to time I may forget to use the Net Support software used to monitor machines in our labs. Please refrain from email, IM, Tweeting, browsing, and game play or use the computers in any other unprofessional manner while I or your fellow colleagues are speaking. Likewise for laptops, PDAs and cell phones.

Grading Breakdown:

A final course grade is a combination of your grades on exams, quizzes, class activities and team projects.

Quizzes will be given regularly throughout the Quarter based primarily on reading assignments. They are meant to be reading checking-ups and the questions will be designed to test general concepts – not specific details. They will start at five minutes after class officially begins and last for 10-15 minutes based on the number of questions. The process will be automated through the myCourses quiz feature. All quizzes will be weighted equally with the lowest score being dropped. Quizzes are graded as follows:

• >= 70% : 100% quiz score
• < 70% : Quiz score + 20% (i.e. 60% score + 20 = 80% recorded grade)
• < 50% : Same grade recorded for quiz score
• Missed quiz – 0% (As the lowest score will be dropped, there are no make-up quizzes)

Note: The individual project grades may be adjusted in either direction from the team grade based on the assessment of your contribution by the instructor and your colleagues on the team.

* Please be aware that the myCourses grade-book feature will be used to communicate “raw” grades to you, but is NOT used for calculating final grades.