Faculty of Informatics
ITCS934
Software Process Management
Subject Outline
Autumn Session 2007
Head of
School –Professor Philip Ogunbona, Student Resource Centre, Tel: (02) 4221 3606
|
Dr Zhiquan
(George) Zhou |
|
|
Telephone
Number: |
4221 5399 |
|
Email: |
|
|
Location: |
3.222 |
Dr Zhou’s Consultation
Times During Session
|
Day |
Time |
|
Friday |
14:00 to
16:00 14:00 to 16:00 |
|
|
Professor
Aditya Ghose |
|
Telephone
Number: |
4221 4051 |
|
Email: |
|
|
Location: |
3.105 |
Professor Ghose’s
Consultation Times During Session
|
Day |
Time |
|
Monday Tuesday |
8:30 to 10:30 am 8:30 to 10:30 am |
Subject
Organisation
|
Session: |
Autumn
Session, |
||||||
|
Credit
Points |
6 credit
points |
||||||
|
Contact
hours per week: |
2 hours
lectures, 2 hours lab/tutorial |
||||||
|
Lecture
Times & Location: |
|
||||||
|
Tutorial
Day, Time and Location can be found at: |
|
||||||
Students
should check the subject’s web site regularly as important information,
including details of unavoidable changes in assessment requirements will be
posted from time to time. Any
information posted to the web site is deemed to have been notified to all students.
The primary aim of this subject is to acquaint students with the
formal methodologies associated with the task of managing the software
development process. Topics may include: Project Planning, Cost Estimation,
Project Scheduling, Factors Influencing Productivity, Productivity Metrics,
Risk Assessment and Management, Planning for Change, Release and Configuration
Management, Software Process Standards, Software Contracts, Approaches to
Maintenance, Long-Term Software Development, Case Studies of Real World
Projects, Ethics, Professional Organisations, Legal Implications and
Liabilities
On completion of this subject the student should be able to
1. Describe various models of software development process
2. Explain the principles and practices of software process management;
3. Demonstrate proficiency in the selection of an appropriate
process management technique
4. Apply process management skills and knowledge to a group
software project
5. Appropriately use project management tools to develop a
project management plan
Attendance
Requirements
It is the responsibility
of students to attend all lectures/tutorials/labs/seminars/practical work for
subjects for which you are enrolled.
It should be noted that according to Course Rule 003{Interpretation Point 2 (t)} each credit point for a single session subject has the value of about two hours per week including class attendance. Therefore, the amount of time spent on each 6 credit point subject should be at least 12 hours per week, which includes lectures/tutorials/labs etc
Contact
hours for this subject comprise 2 hours of lectures and 2 hours of
tutorials/labs. There is no tutorial/lab in week 1.
Subject
Materials
The
reference books are
Purchasing the above reference books is recommended but not mandatory. Students are encouraged to use the University’s library, the ACM/IEEE digital libraries, and other online resources of academic publications (such as CiteSeer) to locate additional readings and research papers.
These readings/references are recommended only and are not intended to be an exhaustive list. Students are encouraged to use the library catalogue and databases to locate additional readings
This subject has the
following assessment components.
|
Assessment Items & Format |
Percentage
of Final Mark |
Due Date |
|
|
|
|
|
Group project |
50% (including progress report
presentation, final report, and final presentation) |
Progress report presentation:
to be conducted during Week 6 tut/lab Final report: due at Week 12
lecture. Final presentation: To be
conducted during lab/tut from Week 12 to Week 13. |
|
Final
Examination |
50% |
During
Exam Period |
Group project
1 Project components
(1)
40 marks for the final project
report
(2)
5 marks for progress report
presentation
(3)
5 marks for final presentation
2 Assessment
(1)
Students need to form groups of six people.
(2)
Different group members may receive different marks based on their individual
contribution.
(3)
The “individual contribution” of each group member is assessed by all the other
group members (the scale is: “contributed”, “very little”, and “almost no
contribution”). For a group member who has “contributed”, he/she will receive
100% of the group marks; for a group member who contributed “very little”,
he/she will receive 50% of the group marks; for students who made “almost no
contribution”, he/she will receive 0 marks for the group project. The
assessment of individual contribution for each group member should be printed
on the cover of the project report.
(4)
Students may be required to attend an interview on their project.
3 Submission
Each
group should submit: one hardcopy report and TWO identical CDs (in case one
might be broken) including the software developed, screen shots, readme file,
user manual, a softcopy of the project report, and all other documents that you
consider necessary to submit. Students need to submit them in person to the
lecturer in the lecture of the due date.
No late submission is
accepted.
Marks
for projects will be e-mailed to the students and can also be accessed via the
e-Learning website (previously WebCT).
Students must refer to the Faculty Handbook or online references which
contains a range of policies on educational issues and student matters.
Please note that if this is your last session and you are granted a supplementary exam, be aware that your results will not be processed in time to meet the graduation deadline.
Plagiarism
When you submit an assessment task, you are
declaring the following
1.
It
is your own work and you did not collaborate with or copy from others.
2.
You
have read and understand your responsibilities under the
3.
You
have not plagiarised from published work (including the internet). Where you
have used the work from others, you have referenced it in the text and provided
a reference list at the end ot the assignment.
4.
Plagiarism
will not be tolerated.
5.
Students
are responsible for submitting original work for assessment, without
plagiarising or cheating, abiding by the University’s policies on Plagiarism as
set out in the Calendar under University Policies, and in Faculty handbooks and
subject guides. Plagiarism has led to the expulsion from the University.
This outline should be read in conjunction with the following documents:
|
Code of
Practice - Teaching and Assessment http://www.uow.edu.au/handbook/codesofprac/teaching_code.html |
Key Dates |
|
Code of
Practice - Students http://www.uow.edu.au/handbook/codesofprac/cop_students.html |
Information
Literacies Introduction Program |
|
Acknowledgement
Practice Plagiarism will not be
tolerated |
Student
Academic Grievance Policy http://www.uow.edu.au/handbook/codesofprac/cop_supervision.html#8 |
|
Special
Consideration Policy http://www.uow.edu.au/handbook/courserules/specialconsideration.html |
Code of
Practice-Honours |
|
Non-Discriminatory
Language Practice and Presentation |
Intellectual
Property Policy http://www.uow.edu.au/research/researchmanagement/1998IP.html |
|
Occupational Health and Safety http://staff.uow.edu.au/ohs/commitment/OHS039-ohspolicy.pdf |
SCSSE
Internet Access & Student Resource Centre http://www.sitacs.uow.edu.au/info/current/internet_access_and_resource.shtml |
|
SCSSE
Computer Usage Rules http://www.itacs.uow.edu.au/info/current/support/labs/rules.shtml |
SCSSE Style
Guide for Footnotes, Documentation, Essay and Report Writing |
|
SCSSE
Student Guide |
Informatics
Faculty Librarian, Ms
Annette Meldrum, phone: 4221 4637,ameldrum@uow.edu.au |
|
SCSSE
Subject Outlines |
|