UVIC Department of Electrical and Computer Engineering

COURSE OUTLINE
SENG 380 Software Process and Management
Spring 2012

Instructor
  • Name: Dr.Amany Abdelhalim
  • Electronic Mail: amany@ece.uvic.ca
  • phone:(250) 472-5722
 Office hours
  • Days: TW
  • Time: 1:00PM-2:15PM
  • Location: ECS 617
Lectures
  • A-Section(s): A01 / CRN 20796
  • Time: 1:00PM-2:20PM
  • Days: MR
  • Location: ECS 130
 Labs
  • Days: 23- Feb, 8-March, 26- March
  • Location: ELW B220
Assessment
	Assignments: 20 % 
	Term-Paper or Lab-report         10 % 
	Mid-term     20 % 	Date: 20/Feb/2012
	Final        50 %

Final Exam Mark and Course Grade

MidTerm Answers


Lecture Assignments:
Assignment 1   due on  January  26    Assignment1-solutions 

Assignment 2   MARK II FP Guide  due on  February 9   Assignment2-solutions 

Assignment 3    due on  March 19   Assignment3-solutions 

Assignment 4    due on  April 5    Assignment4-solutions

Lab assignments:

Lab1: Lab1-assignment
Lab2: LabSlides Lab2-assignment
Lab3: LabSlides Lab3-assignment

Course Slides




Text Book
Title: Software Project Management, 5th revised edition.
Author: Bob Hughes, Mike Cotterell.
Publisher: McGraw Hill Higher Education.
Year: (April 1, 2009).

References
Bob Hughes, Mike Cotterell, "Software Project Management", 5th revised edition.McGraw Hill Higher Education, 2009.
Lena Johansson, Malin Lundgren, Software Project Planning Light, http://w3.msi.vxu.se/exarb/ljml_ex.pdf
Neville Turbit, Helping Business Managers Evaluate a Potential Project, Project Perfect, white paper, http://www.projectperfect.com.au/info_evaluate_potential_project.php
Andy Jessop, Earned Value Analysis Overview, http://www.projectlearning.net/pdf/I2.1.pdf
Linda Westfall, SOFTWARE RISK MANAGEMENT, http://www.westfallteam.com/Papers/risk_management_paper.pdf
Boehm, B. (1987) A sprial model of software development and enhancement, Software Engineering Project Management, p.128-142.

Course Objectives
The course introduces the students to the software life cycle and software process models.
Project estimating processes to determine who is going to do what, for how much, when and with what associated risks.
The life-cycle management of correct, reliable, maintainable and cost effective software. Software documentation. Project management methods and tools.
Software metrics (productivity and maturity). Configuration management. Planning for change. Managing expectations and contingencies.

Learning Outcomes
By the end of this course, students will be able to:
• Define the scope of software project management, the usual stages of software project, and the success criteria for a project.
• Describe the contents of a typical business plan and project portfolio management.
• Plan for a project, Carry out an evaluation for a selection of projects using a variety of cost-benefit evaluation techniques and evaluate the business risks involved in a project.
• Describe a different selection of appropriate project approaches based on the characteristics of the system to be developed in a project and provide an estimation of effort needed in a project using different techniques.
• Produce an activity plan for a project and estimate the overall duration of a project.
• Perform risk management: identify factors of risk, categorize and prioritize actions for eliminating or contaminating risks.
• Produce a work plan and a resource schedule, monitor the progress of a project and control changes to the project’s requirements.
• Define qualities of good software and design methods of measuring the required qualities in software.

Syllabus
Subjects to be covered:
• Introduction to software project management.
• Software development approaches and models.
• Software cost estimation.
• Software size and effort estimation.
• Software project and activity planning.
• Software risk management.
• Resource allocation.
• Performance tracking and reporting.
• Software Quality.
• Working in Teams.

The final grade obtained from the above marking scheme will be based on the following percentage-to-grade point conversion:
90 <=   A+	<=      100
85 <=	A	<	90
80 <=	A-	<	85
75 <=	B+	<	80
70 <=	B	<	75
65 <=	B-	<	70
60 <=	C+	<	65
55 <=	C	<	60
50 <=	D	<	55
35 <=	E	<	50	Fail, conditional supplemental exam* - for undergraduate courses only.
	F	<	35	Fail, no supplemental exam.
	N	Fail, did not write examination or otherwise complete course requirements by the end of the term or session; no supplemental exam.
* The rules for supplemental examinations are found on pages 88-89 of the current 2010/11 Undergraduate Calendar.
Term in which E Grade was obtained: Application Deadline for Supplemental Exam Supplemental Exam Date
First term of Winter Session
(Sept - Dec)		 Following February 28 First week of following May
Second term of Winter Session
(Jan - Apr)		 Following June 30 First week of following September
Summer Session
(May - Aug)		 Following October 31 First week of following January
Deferred exams will normally be written at the start of the student's next academic term; i.e., approximately 4 months following the deferral of the exam.

Guidelines on Religious Observances
1. Where classes or examinations are scheduled on the holy days of a religion, students may notify their instructors,
at least two weeks in advance, of their intention to observe the holy day(s) by absenting themselves from classes or examinations.
2. Instructors will provide reasonable opportunities for such students to make up work or missed examinations.
3. Students will cooperate by accepting the provision of reasonable opportunities for making up work or missed examinations.
4. The University Secretary's Office will distribute a multi-faith calendar to each academic unit annually.

Commitment to Inclusivity and Diversity
The University of Victoria is committed to promoting, providing and protecting a positive, supportive and safe learning and working environment for all its members.
Standards of Professional Behavior
You are advised to read the Faculty of Engineering document Standards for Professional Behaviour at http://www.engr.uvic.ca/policy/professional-behaviour.php
which contains important information regarding conduct in courses, labs, and in the general use of facilities. Cheating, plagiarism and other forms of academic fraud are taken very seriously by both the University and the Department.