|
Software Quality and Measurement 400 (670.400)
6 points / Semester 1
Handbook Description
The official Handbook entry Unit Aims
This course will look at the application of the theory of software engineering to
industry. Commercial systems are generally the work of teams of specialists and
are of sufficient scale that it is not realistically possible for a single person to
comprehend all their inherent complexity. The course considers software
development and maintenance as a process which can be defined, measured,
modelled and optimised. In particular, it will consider the assessment of quality
and reliability. There will be some discussion of safety critical issues as well as
standard techniques for the production of systems for the private or public
sector.
At the conclusion of the course, students should understand software
development as a process: its management, planning, control, measurement and
improvement. Specific skills such as estimation, planning, quality assurance,
VV&T (validation, verification and testing), use of ISO standards, user contact,
configuration management, design and use of metrics, reliability modelling and
risk management are covered.
This course is neither a programming unit
nor about learning specific tools - it is concerned with software development
techniques and the underlying theories and concepts. Students are expected to
do some reading of the text (Pressman or Sommerville) and of supplementary
material each week.
Teaching Staff
| Coordinator/Lecturer |
Terry Woodings |
| Tutor |
Terry Woodings |
Textbook
Roger Pressman, Software Engineering - A Practitioner's Approach, 5th edition (European Adaptation) McGraw Hill, 2000.
The 4th edition (1997) is also good.
An excellent (optional) alternative
Ian Sommerville, Software Engineering, 6th edition, Addison Wesley, 2001.
The 5th edition (1995) is also acceptable.
HB90.9-2000, Software Development - Guide to ISO 9001:2000,
available from the University Library web site.
Contact Hours
For this unit you will be required to attend,
on a weekly basis,
two lectures and a tutorial/workshop with lab classes as
needed for particular exercises.
To satisfactorily complete
this unit you are expected to work out-of-hours and
an additional 3 hours per hour of formal contact would be a reasonable
estimate.
| Type |
Time |
Day |
Location |
| Lecture 1 |
2pm |
Tue |
GP2 G16 |
| Lecture 2 |
11am |
Wed |
GP2 G16 |
| |
|
|
|
| Tutorials |
3pm |
Tue |
CSSE 2.28 |
| |
4pm |
Tue |
CSSE 2.28 |
| |
3pm |
Weds |
CSSE 2.28 |
Lecture Details
The lectures will cover the following topics.
This material will be supported through tutorials and worked practical assignments.
| Topic |
Details |
| 1 |
Introduction to the Principles of Quality Management |
| 2 |
Introduction to Quality Principles for Software |
| 3 |
Cost Benefits |
| 4 |
Basic Techniques and Skills for Assuring Software |
| 5 |
Six types of Software Inspections |
| 6 |
Paradigms and Practice of Software Development |
| 7 |
Estimation |
| 8 |
Planning Key Areas |
| 9 |
Systems and Standards |
| 10 |
Standard Operating Procedures |
| 11 |
Specifying the Requirements |
| 12 |
Independent Validation and Verification |
| 13 |
Testing - overview |
| 14 |
Testing - continued |
| 15 |
Configuration Management |
| 16 |
Implementation and Change Control |
| 17 |
Data Integrity |
| 18 |
Users' Acceptance of System |
| 19 |
Suitability Metrics and Usability |
| 20 |
Software Complexity Metrics and Maintenance |
| 21 |
Process Metrics and Management |
| 22 |
Reliability and Safety |
| 23 |
Risk Management |
| 24 |
Peopleware |
| 25 |
Continuous Improvement Programmes |
| 26 |
Strategic Quality Management |
Assessment
The assessment of this unit will consist of two projects, a practical work folder
and a 2 hour final examination held in the June examination period.
| type |
contribution |
due date |
| Work Folder |
5% |
TBA |
| Project 1 |
25% |
TBA |
| Project 2 |
20% |
TBA |
| Examination |
50% |
June |
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.
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 03-Mar-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: 03-Mar-2005 |
