|
The Software Process: Principles, Implementation & Improvement (670.600)
6 points / Semester 1
Handbook Description
The official Handbook entry Unit Aims
This course covers the underlying principles of software processes; the development paradigms they are based on; tailoring a process to a specific environment; assessing the effectiveness of a process; applying that assessment to improve the process. The principles will be reinforced by examples of modern industrial software lifecycles, methodologies and assessment practices. Current research into software processes (particularly modelling) will be emphasised.
At the conclusion of the course, students should understand improvement in software development processes as a necessary foundation for the quality of the information system produced — and as the measure of the capability of the software organisation. In particular students will:
- Gain an understanding of the important aspects of software development lifecycles and processes.
- Learn techniques to critically evaluate a process and tailor it to specific development environments.
- Learn several process methodologies, models and modelling methods.
- Understand techniques for the measurement and assessment of process effectiveness.
- Develop strategies for process improvement using current mechanisms.
- Be able to improve and optimize the process with respect to some desirable criteria.
Teaching Staff
| Lecturer |
Terry Woodings |
| Email |
terry@csse.uwa.edu.au |
Textbook
Walker ROYCE, Software Project Management - A Unified Framework, Addison-Wesley, 1998.
Contact Hours
There will be two lectures and a tutorial/workshop per week. The class is small
enough to be able to run lectures in a highly interactive mode. This course is
neither a programming unit nor about learning specific tools - it is concerned
with the definition, modelling, control and improvement of software development
processes and the underlying theories and concepts. Students are expected to do
substantial reading of texts and of supplementary material each week.
Lecture Details
| Topic |
Details |
| 1 |
The concept of a software process, components and underlying principles |
| 2 |
Basic techniques for modelling work-flows and checkpoints of a process |
| 3 |
A power-set of processes - planning of projects as a meta-process |
| 4 |
Linear-sequential/lifecycle vs the spectrum of prototyping/agile processes |
| 5 |
Controlling and correcting the software development process |
| 6 |
Measurement theory for software process metrics |
| 7 |
The marriage of software and Statistical Process Control (SPC) |
| 8 |
Managing and measuring software process behaviour |
| 9 |
Some specific methodologies — Rational, PSP, Lightweight, Open-Source |
| 10 |
Optimisation and tailoring a software process |
| 11 |
Measuring process improvement — CMMI, 6s, Trillium, AMI, Bootstrap |
| 12 |
Assessment of an organisation’s capability and strategic management |
| 13 |
The ISO15504 (SPICE) standards |
Assessment
There are three specific assignments, a research project and a presentation. There is no examination.
The first assignment, worth 10%, is on the modelling of a process. The second, worth 20%, is on the measurement of the interacting parameters of a process. The third, worth 20%, is on the tailoring or optimisation of a process with respect to given criteria.
The subject for the research project and associated presentation will be chosen and tailored according to the needs and interests of each individual student. Students will be expected to display evidence of depth of thinking and research on the chosen topic. The research project is worth 40% of the final mark. The presentation is worth 10% and may be designed for either an academic or commercial audience.
| Assessment |
% of final mark |
Assessment Dates |
| Assignment 1 |
10 |
TBA |
| Assignment 2 |
20 |
TBA |
| Assignment 3 |
20 |
TBA |
| Project |
40 |
TBA |
| Presentation |
10 |
TBA |
Unsatisfactory Progress
Any student who does not demonstrate satisfactory progress in this
unit, as defined in the FECM
Policy on Assessment Practices and Procedures, may be refused admission to the
final examinations. The final deadline for notification of unsatisfactory progress is the
last day of Week 10.
Penalties
The School of Computer Science and Software Engineering has adopted a policy on
minimum penalties for late items of assessment.
This is the default policy of all units unless indicated otherwise, in writing, by the
specific unit coordinator.
This policy shall apply to all items of continuous assessment, whether
submitted either physically or electronically. Immediately after the submission deadline for an item of continuous
assessment, a penalty of 20 percent will be applied PER DAY or PART THEREOF.
The minimum mark possible for late submission is zero. The
percentage is based on the item´s total contribution to the unit´s
assessment. For example, a project contributing 40% to the unit´s
assessment will incur a penalty of 8 marks for each day late until it is submitted or
a mark of zero results.
A more detailed description is given in this School´s Policy on
Late Submission. The Faculty does have an appeals procedure, the details of which can found at the Policy for Appeals.
This is a small course and group activities are an effective form of learning
and therefore encouraged. However, the assignments and project will all be marked
on an individual basis. Always give credit to other peoples' work that has
been included in any assignment.
In industry, there is usually a preference for an adequate job done early than a perfect job done late. Accordingly, projects may be marked on a sliding scale allowing extra marks for early submissions. That is, there will be a small adjustment of marks (up to 1% per day) for early or (down by 5% per day) for late submission of projects. The marking algorithm will be discussed in class and will be clearly indicated on relevant project sheets.
Plagiarism
Plagiarism is broadly defined to be when any portion
of the work presented for assessment, can be attributed
to another party. The student making the submission should acknowledge
what aspects of the presented work is not directly derived by
them. For the purposes of plagiarism it is irrelevant that you
have been given permission by someone to copy their work
and present it as your own.
You are directed to the School of Computer Science and Software Engineering Policy on Plagiarism and the Faculty of Engineering,Computing and Mathematics Policy on Plagiarism.
Faculty Scaling
Final assessment is subject to the Faculty Scaling Policy.
This information is correct as at 28-Feb-2005, but is subject
to change from time to time. In particular, The University
reserves the right to change the content and/or method of
presentation and/or the method of assessment of any unit of
study, to withdraw any unit of study or programme, and/or to
vary arrangements for any programme.
Copyright© 2005
School of Computer Science, & Software Engineering
The University of Western Australia
CRICOS Provider Code: 00126G
Last updated: 28-Feb-2005 |
