Note: This unit version is currently under review and is subject to change!
ELEC5618: Software Quality Engineering (2017 - Semester 1)
|Unit:||ELEC5618: Software Quality Engineering (6 CP)|
|Faculty/School:||School of Electrical & Information Engineering|
|Session options:||Semester 1|
|Versions for this Unit:|
|Brief Handbook Description:||This unit will cover software quality planning, validation and verification methods and techniques, risk analysis, software review techniques, software standards and software process improvement and software reliability.
Students who successfully complete this unit will understand the fundamental concepts of software quality engineering and be able to define software quality requirements, assess the quality of a software design, explain specific methods of building software quality, understand software reliability models and metrics, develop a software quality plan, understand quality assurance and control activities and techniques, understand various testing techniques including being able to verify and test a unit of code and comprehend ISO standards, SPICE, CMM and CMMI.
|Assumed Knowledge:||• You are capable of writing programs with multiple functions or methods in multiple files. • You are capable of design complex data structures and combine them in non trivial algorithms. • You know how to use an integrated development environment. • You are familiar and have worked previously with software version control systems. • You know how to distribute the workload derived from the unit of study effectively throughout the week and make sure that time is truly productive.|
Dr Stepien, Peter
|T&L Activities:||Tutorial: Weekly tutorial on course materials. Follows the weekly lecture material. The lab session each week is used to provide some structured learning experiences. The lab sessions also provide time for you to meet as a group and work on your projects.
Independent Study: As well as the scheduled hours, each student is expected to devote eight (8) extra hours each week to ELEC5618. This includes time spent doing assessment tasks, reading the reference books, trying out ideas, planning your work, meeting your group, etc.
Attributes listed here represent the key course goals (see Course Map tab) designated for this unit. The list below describes how these attributes are developed through practice in the unit. See Learning Outcomes and Assessment tabs for details of how these attributes are assessed.
|Attribute Development Method||Attribute Developed|
|Students analyse the various activities in the several stages of software development and assign risk to various activities using well-defined methodologies.||Design (Level 4)|
|The use of feedback to improve development and the QA process itself is demonstrated and templates for review provided.||Engineering/IT Specialisation (Level 4)|
|Students rank activities according to risk and be able to calculate and justify such rankings.||Maths/Science Methods and Tools (Level 4)|
|Students are given reading lists and topics throughout the semester. Students must be able understand and analyse the various activities in the several stages of software development. Students must calculate the various `costs` involved in performing/not-performing various QA activities.||Information Seeking (Level 3)|
|Students write a report evaluating an independent third-party website installation and commenting on its usability.||Communication (Level 3)|
|Students are exposed to best-practice development and QA methodologies.
Students write a group report.
|Professional Conduct (Level 4)|
For explanation of attributes and levels see Engineering & IT Graduate Outcomes Table.
Learning outcomes are the key abilities and knowledge that will be assessed in this unit. They are listed according to the course goal supported by each. See Assessment Tab for details how each outcome is assessed.Design (Level 4)
Assignment: Software quality plan, verification and software testing
Assignment: Software test plan, case studies.
Final Exam: Final exam.
|Policies & Procedures:||See the policies page of the faculty website at http://sydney.edu.au/engineering/student-policies/ for information regarding university policies and local provisions and procedures within the Faculty of Engineering and Information Technologies.|
Note: References are provided for guidance purposes only. Students are advised to consult these books in the university library. Purchase is not required.
Note that the "Weeks" referred to in this Schedule are those of the official university semester calendar https://web.timetable.usyd.edu.au/calendar.jsp
|Week 1||Course description and scenario|
|Week 2||Software quality in a company|
|Week 3||Software Quality Planning, Assurance and Control|
|Week 4||Software Requirement Specification and Use Cases|
|Week 5||Verification vs. Validation|
|Week 6||Software Testing|
|Assessment Due: Assignment|
|Week 7||The Software Test Plan|
|Week 8||Tools for Testing|
|Week 9||SQE in Agile Environments|
|Week 10||Practical Case Study (I)|
|Week 11||Design a Weekly Agile Cycle|
|Week 12||Practical Case Study (II)|
|Week 13||Course revision|
|Assessment Due: Assignment|
|Exam Period||Assessment Due: Final Exam|
The following is a list of courses which have added this Unit to their structure.
This unit contributes to the achievement of the following course goals:
|Project and Team Skills (Level 3)||No||0%|
|Design (Level 4)||Yes||18.75%|
|Engineering/IT Specialisation (Level 4)||Yes||43.76%|
|Maths/Science Methods and Tools (Level 4)||Yes||13.75%|
|Information Seeking (Level 3)||Yes||3.75%|
|Communication (Level 3)||Yes||5%|
|Professional Conduct (Level 4)||Yes||15%|
These goals are selected from Engineering & IT Graduate Outcomes Table which defines overall goals for courses where this unit is primarily offered. See Engineering & IT Graduate Outcomes Table for details of the attributes and levels to be developed in the course as a whole. Percentage figures alongside each course goal provide a rough indication of their relative weighting in assessment for this unit. Note that not all goals are necessarily part of assessment. Some may be more about practice activity. See Learning outcomes for details of what is assessed in relation to each goal and Assessment for details of how the outcome is assessed. See Attributes for details of practice provided for each goal.