Syllabus

Catalog Description

An introductory course to software process and related software project management issues. Emphasis is on the study, use, evaluation, and improvement of the software development process. Topics include software development methodologies, software project planning and tracking, change control, software quality assurance, risk management, and software process assessment and improvement. (SWEN-256) Class 3, Credit 3

Course Objectives

The focus of this course will be on Project Management, which includes several factors that can and do affect Software Engineering. Subjects of study will include: An introduction to process and project measurement and metrics is also presented in this course, which can be studied further in SWEN-350 - Software Process and Project Metrics. Agile Methodologies can be studied further in SWEN-356 - Trends in SW Development Process.

The objective of this course is to provide an understanding of these principals so that, whether as part of a Software Engineering team, or as a full-fledged Project Manager, each student will have a basic understanding of associated methodologies, principles, and terminology, and how they relate to a project.

Subject matter will be presented in dualistic fashion; Project Management as a pure discipline, and applying Project Management principles to Software Engineering frameworks.

Learning Approach

We will be using problem-based learning. Students will be required to work in teams. The learning material is divided into several units. Each unit includes reading material, an in-class presentation, and a set of questions/problems to answer as a team. The questions, teamwork and readings will drive the learning experience, with the instructor acting as facilitator and mentor.

The following 2 textbooks are required reading, and may be available physically or digitally RIT Library or O'Reilly for Higher Education resources or at a reasonable cost in print or in various e-book formats: Page references have been added to the site for supplemental (but not required) reading: Additionally, there are several books that may come in handy and relate well to Software Project Management: Reading assignments should be completed before the first class of the assigned week.

There will be one major course project, which will be developed as a team in stages. Each stage will correspond to material covered in reading and in class. Teams of various sizes and composition will be formed for assignments and in-class activities. Individual performance will be measured within the team activities as well as in quizzes, exams, and individual assignments.

Project Teams

Project teams will consist of about 4 members each, and will remain together throughout the second half of the class. Teams will be self-selected, and participants should use methodology discussed in the first part of the class when making their selection. Team members will evaluate each other based on teamwork, knowledge/skills, dependability, initiative/creativity, adaptability/flexibility, and delivery of results at regular intervals. Teams will also be responsible for cross-team feedback of other team's projects.

Grading and Attendance

The following tables will be used to determine your letter grade at the conclusion of the term:

Item Percentage Notes
Midterm 1 20% Cumulative, Closed Book
Midterm 2 20% Cumulative, Closed Book
Final Exam 20% Cumulative, Closed Book - See Time Posted on SIS/Schedule
Team Project 20% Individual Grading Affected by Peer Evaluations
Quizzes 10% See notes below
Classroom Activities 10%
2 or More Unexcused Absences -2% per Please check with Instructor for clarification if needed
2 or More Late Arrivals -1% per Also affects in-class and team activity related credit

Grade Range
A 93 or Above
A- 90 or Above
B+ 87 or Above
B 83 or Above
B- 80 or Above
C+ 77 or Above
C 73 or Above
C- 70 or Above
D 60 or Above

When assigning final grades, the instructor reserves the right to alter these division points as he or she deems necessary based on the overall evaluation of individual or class performance and effort.

Students will be evaluated individually using quizzes, exams, and assignments. Teams will be given a single grade for units and project deliverables submitted. Individual team members may have their grades for the units and team project adjusted up or down based on their contribution to the project. This adjustment will be based on peer evaluations from teammates.

Missing one class session is significant - most sessions contain class team work that requires all team members to be present to gain full benefit. One unexcused absence (slept in, car won't start, etc.) is granted without consequence.

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 when class begins and last for 5-10 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. As the lowest score will be dropped, there are no make-up quizzes. Grading is:

Academic Honesty

Academic Honesty demands that at all times student work be the work of that individual student (or student group when appropriate), and that any information which a student uses in a work submitted for evaluation be properly documented. Forms of dishonesty include cheating, duplicate submission, and plagiarism, and may in some cases include the use of AI assistance and tools. Students are expected to comply with the RIT Academic Honesty Policy and noncompliance may result in an F on individual assignments or for the entire course. (http://www.rit.edu/studentaffairs/studentconduct/rr_academicdishonesty.php)