SWE 4103 –
Software Quality and Project Management
Fall Term 2009
Software
Quality: Requirements gathering techniques. Formal
specification languages. Verification and validation
techniques. Statistical software reliability engineering.
Software metrics. Software process maturity models
(CMM and ISO 9001). Software Project Management: Software project tracking,
planning and scheduling. Organizing and managing software
teams. Monitoring and controlling software development. Factors influencing productivity and success. Risk analysis. Planning for change.
Note: alternating with SWE 4203. Prerequisite: CS 3043 or CMPE 3213 or
Permission from Instructor. 4ch
(3C 3*L)
This is a
seminar-based course in which students are expected to elicit and share
knowledge. Each student will be assigned to present two topics during the first
and the second part of the course. The topics will be introduced by the course
instructor following the student’s presentation and guided discussion (one presentation
per class). Students are encouraged to discuss topics of interest with the
course instructor during the first two weeks of classes.
INSTRUCTOR: Yevgen Biletskiy e-mail: biletski NA unb.ca
Office: GWC115 phone:
447-3495
LECTURES: MWF
11:30 – 12:20 AM D33
LABS: TBA
OFFICE TIME: W 9:15 – 11:15
AM
LITERATURE (available at UNB libraries):
-
A guide to the project management
body of knowledge (PMBOK guide)
-
James Taylor, Managing
Information technology projects [e-]
- Robert Fantina, Practical software process improvement [e-]
-
James Lewis,
Fundamentals of projects management [e-]
-
Susan Snedaker, How to cheat at IT project management [e-]
-
Kenneth Bainey, Integrated IT project management [e-]
-
Gary Chin, Agile
project management [e-]
-
Gordon Schulmeyer, Handbook of software quality assurance (4-th
edition)
-
Jenner Michael,
Software Quality Management and ISO 9001
-
Sulayman Sowe, Emerging free and open source software practices [e-]
- Jerry Gao, Testing and quality assurance for component-based software [e-]
-
Roger S. Pressman, Software Engineering: A Practitioner’s Approach
-
Ian Sommerville, Software Engineering
-
B.Bruegge, A.H.Dutoit, Object-Oriented Software Engineering: Using
UML, Patterns, and JavaTM
-
Hongji Yang, Martin Ward,
Successful Evolution of Software
Systems
-
Penny Grubb,
Armstrong A. Takang, Software Maintenance: Concepts and Practice (Second Edition)
-
Pigoski “Practical Software Maintenance”
GRADING:
First Seminar -
15%
Second Seminar –
15%
Participation – 20%
Midterm Paper - 20%
Final Paper - 30%
PROPOSED SCHEDULE:
WEEK |
TOPICS |
1-2 |
Introduction
to Project Management and Quality Assurance |
3 |
Software
Process and Product, Software Metrics |
4 |
Requirements
elicitation, Functional and Non-functional Requirements |
5 |
Project
Scope and Integration Management |
6 |
Project
Cost Estimation, Risk Mitigation, Monitoring, Management |
7 |
Project
Scheduling and Tracking |
8 |
Software Testing.
Verification and Validation |
9 |
Software
Change, Software Configuration Management |
10 |
Human
Resource Management, Productivity and Success, Project Communications and
Procurement |
11 |
Software
Standards (ISO, IEEE) |
12-13 |
Advanced
Topics in Project Management and Quality Assurance |
Note that this schedule is not written in
stone! Topics may shift slightly
depending on class progress.
Note that it is
student’s responsibility to attend classes in order to obtain any information
presented and/or announced in class.
General
Regulations on Conduct
Part of the UNB's
PLAGIARISM
Plagiarism includes:
1.
quoting verbatim
or almost verbatim from a source (such as copyrighted material, notes, letters,
business entries, computer materials, etc.) without acknowledgment;
2.
adopting someone
else’s line of thought, argument, arrangement, or supporting evidence (such as,
for example, statistics, bibliographies, etc.) without indicating such
dependence;
3.
submitting someone
else’s work, in whatever form (film, workbook, artwork, computer materials,
etc.) without acknowledgment;
4.
knowingly representing as one’s own work any idea of another.
NOTE: In courses which include group work, the
instructor must define and warn against plagiarism in group work. Unless an act of plagiarism is identified
clearly with an individual student or students, a penalty may be imposed on all
members of the group.
Penalties for Deliberate Plagiarism
In a case of deliberate
plagiarism, the penalties are:
First Offence: If the student does not appeal, or if, on
appeal, the Committee upholds the instructor’s decision:
1.
A notation will be
placed on the student’s transcript of academic record concerning the academic
offence. The length of time the notation
appears on the student’s transcript of academic record is to be decided when
the penalty is imposed and will depend on the severity of the offence.
2.
The student may be
required to submit a satisfactory and genuine piece of work to replace the one
involving plagiarism. If the assignment
is not resubmitted or is unsatisfactory, the student will receive a grade of F
(zero) in the course. NOTE:
If this penalty is assessed, the period of time allowed for the
submission of the work will be determined by the Registrar in consultation with
the faculty member making the charge, and, where appropriate, the Committee.
3.
The student will
receive a grade of F (zero) on the piece of work and, depending on the severity
of the offence, may receive a grade of F for the course.
4.
Other penalties as
outlined in penalties for Other Academic Offences may be imposed.
Subsequent Offence: In cases where the Committee
considers that the student has plagiarized again:
1.
The student will
receive a grade of F in the course and a notation of the academic offence will
appear on the student’s transcript of record.
The length of time the notation appears on the student’s transcript of
academic record is to be decided when the penalty is imposed.
2.
Other penalties as
outlined in penalties for Other Academic Offence may be imposed.
For further information on procedures for dealing with
cases of plagiarism, students should refer to the regulations found in the Undergraduate
Calendar.
DEFERRED EXAMS
University
regulations on deferred exams are described in Section V.C of the current
on-line Undergraduate Calendar.
All deferred
exams in courses offered by the Department of Electrical and Computer
Engineering are scheduled to be written on the fourth day of classes in the
following term. There are no exceptions.