This unit covers the fundamental products, processes and techniques for system validation and verifications including testing methodologies, static program analysis and code quality measurement and monitoring. Open-source tools will be used to apply in practice knowledge learnt about software testing from a theoretical perspective. Inspection and testing methodologies, analysis of artefacts, robustness, performance analysis configuration management, quality assurance plan and standards, compliance, assessment, certification issues are covered. It shows how to predict, analyse and control defects in complex software systems.
Minimum total expected workload equals 12 hours per week comprising:
(a.) Contact hours for on-campus students:
(b.) Additional requirements (all students):
See also Unit timetable information
You will need to allocate one hour per week for unsupervised lab/tute activity in the MUSE Lab to get familiarised with tools, work on assignments and for self study.
CSE4431
MAT1830 and FIT2004 and FIT2024 and FIT3077
Robert Merkel
Consultation hours: TBA - check Moodle page
Hong-Li Song
Monash is committed to excellence in education and regularly seeks feedback from students, employers and staff. One of the key formal ways students have to provide feedback is through the Student Evaluation of Teaching and Units (SETU) survey. The University’s student evaluation policy requires that every unit is evaluated each year. Students are strongly encouraged to complete the surveys. The feedback is anonymous and provides the Faculty with evidence of aspects that students are satisfied and areas for improvement.
For more information on Monash’s educational strategy, see:
www.monash.edu.au/about/monash-directions/ and on student evaluations, see: www.policy.monash.edu/policy-bank/academic/education/quality/student-evaluation-policy.html
Previous SETU feedback indicated problems with practical relevance and the technology stack used in assignments.
The course material has been completely rewritten from scratch with a greater practical focus, and the technology stack has been changed and simplified to bring the focus back on the testing and quality aspects rather than dealing with the limitations of unreliable tools.
If you wish to view how previous students rated this unit, please go to
https://emuapps.monash.edu.au/unitevaluations/index.jsp
| Week | Activities | Assessment |
|---|---|---|
| 0 | No formal assessment or activities are undertaken in week 0 | |
| 1 | Overview, Fundamentals of software quality assurance | |
| 2 | Quality Assurance Plans | Weekly assessed Tutorial Participation starts in Week 2 |
| 3 | Human review | |
| 4 | Types of testing | |
| 5 | Black box testing | Artifact Review due Week 5 |
| 6 | White box testing | |
| 7 | Documenting testing | |
| 8 | Unit testing | Manual System Testing due Week 8 |
| 9 | Unit testing II | |
| 10 | Integration Testing | |
| 11 | Metrics | |
| 12 | Frontiers of testing | Automated Unit Testing due Week 12 |
| SWOT VAC | No formal assessment is undertaken in SWOT VAC | |
| Examination period | LINK to Assessment Policy: http://policy.monash.edu.au/policy-bank/ academic/education/assessment/ assessment-in-coursework-policy.html |
*Unit Schedule details will be maintained and communicated to you via your learning system.
Examination (2 hours): 50%; In-semester assessment: 50%
| Assessment Task | Value | Due Date |
|---|---|---|
| Artifact Review | 10% | Week 5 |
| Manual System Testing | 15% | Week 8 |
| Automated Unit Testing | 15% | Week 12 |
| Tutorial Participation | 10% | Weekly (starts in Week 2) |
| Examination 1 | 50% | To be advised |
Faculty Policy - Unit Assessment Hurdles (http://intranet.monash.edu.au/infotech/resources/staff/edgov/policies/assessment-examinations/assessment-hurdles.html)
Academic Integrity - Please see resources and tutorials at http://www.monash.edu/library/skills/resources/tutorials/academic-integrity/
Students are expected to attend all tutorials and participate in active discussions. Tutorials will carry 10% assessment and will be assessed on participation.
This assignment will be assessed on:
Extensive written course notes will be provided through Moodle.
A large collection of readings will also be made available. Some will be compulsory and this will be indicated on Moodle.
Monash Library Unit Reading List (if applicable to the unit)
http://readinglists.lib.monash.edu/index.html
Types of feedback you can expect to receive in this unit are:
Submission must be made by the due date otherwise penalties will be enforced.
You must negotiate any extensions formally with your campus unit leader via the in-semester special consideration process: http://www.monash.edu.au/exams/special-consideration.html
It is a University requirement (http://www.policy.monash.edu/policy-bank/academic/education/conduct/student-academic-integrity-managing-plagiarism-collusion-procedures.html) for students to submit an assignment coversheet for each assessment item. Faculty Assignment coversheets can be found at http://www.infotech.monash.edu.au/resources/student/forms/. Please check with your Lecturer on the submission method for your assignment coversheet (e.g. attach a file to the online assignment submission, hand-in a hard copy, or use an electronic submission). Please note that it is your responsibility to retain copies of your assessments.
If Electronic Submission has been approved for your unit, please submit your work via the learning system for this unit, which you can access via links in the my.monash portal.
Please check with your lecturer before purchasing any Required Resources. Limited copies of prescribed texts are available for you to borrow in the library, and prescribed software is available in student labs.
The MUSE Lab in Bldg 26/G13 is the lab used for this unit. However, students can install the required software on their personal computers to minimise interruptions to development and testing. The required software includes:
Students are encouraged to use their own personal computers to work on project assignments. All required software can be downloaded and installed onto personal computers.
Monash has educational policies, procedures and guidelines, which are designed to ensure that staff and students are aware of the University’s academic standards, and to provide advice on how they might uphold them. You can find Monash’s Education Policies at: www.policy.monash.edu.au/policy-bank/academic/education/index.html
Important student resources including Faculty policies are located at http://intranet.monash.edu.au/infotech/resources/students/
The University provides many different kinds of support services for you. Contact your tutor if you need advice and see the range of services available at http://www.monash.edu.au/students. For Malaysia see http://www.monash.edu.my/Student-services, and for South Africa see http://www.monash.ac.za/current/.
The Monash University Library provides a range of services, resources and programs that enable you to save time and be more effective in your learning and research. Go to www.lib.monash.edu.au or the library tab in my.monash portal for more information. At Malaysia, visit the Library and Learning Commons at http://www.lib.monash.edu.my/. At South Africa visit http://www.lib.monash.ac.za/.
This unit is a core unit in the Bachelor of Software Engineering accredited by Engineers Australia. Engineers Australia Accreditation Policy of Professional Engineering Programs requires that programs demonstrate how engineering graduates are prepared for entry to the profession and achieve Stage 1 competencies. The following information describes how this unit contributes to the development of these competencies for the Bachelor of Software Engineering. (Note: not all competencies may be emphasised in this unit).
| Stage 1 competency | How the compency is developed in this unit |
| 1. Knowledge and Skills base | |
| 1.1. Comprehension, theory based understanding of the underpinning natural and physical sciences and the engineering fundamentals applicable to the engineering discipline. | Theoretical lecture materials, prescribed texts and recommended reading, tutorials. |
| 1.2. Conceptual understanding of the mathematics, numerical analysis, statistics, and computer and information sciences, which underpin the engineering discipline. | Lectures and tutorial exercises on discrete mathematics relevant to software testing. |
| 1.3. In-depth understanding of specialist bodies of knowledge within the engineering discipline. | Lectures on testing techniques and methodologies, tutorials, and projects. |
| 1.4. Discernment of knowledge development and research directions within th engineering discipline. | Lectures on testing techniques and methodologies, tutorials, and projects. |
|
1.5. Knowledge of engineering design practice and contextual factors impacting the engineering discipline. |
Lectures, tutorials, and projects involve the consideration of techniques in the contexts of SE project types. |
| 1.6. Understanding of the scope, principles, norms, accountabilities and bounds of sustainable engineering practice in the specific discipline. | Limited discussion in lectures of responsibilities of testers. |
| 2. Engineering application ability | |
| 2.1. Application of established engineering methods to complex engineering problem solving. | Lectures, labs and tutorials teach standard software testing tecniques and processes. |
| 2.2 Fluent application of engineering techniques, tools and resources. | As well as discussed in 2.1, projects involve the use of standard testing and CI tools. |
| 2.3. Application of systematic engineering synthesis and design processes. | Design is not a focus of the unit. |
| 2.4. Application of systematic approaches to the conduct and management of engineering projects. | Management is not a focus of the unit. |
| 3. Professional and personal attributes | |
| 3.1. Ethical conduct and professional accountability. | Responsibilities of testers are discussed briefly in lectures, but not a major focus of the unit. |
| 3.2. Effective oral and written communication in professional and lay domains. | Testability of requirements and reporting is covered in assignments and lectures but is not a major focus of the unit. |
| 3.3. Creative, innovative and proactive demeanour. | Not covered in this unit. |
| 3.4. Professional use and management of information. | Not relevant to this unit. |
| 3.5. Orderly management of self, and professional conduct. | Not covered in this unit. |
| 3.6. Effective team membership and team leadership. | Not covered in this unit. |
| No. | CO 1 | CO 2 | CO 3 | CO 4 | CO 5 | CO 6 | CO 7 | C0 8 | CO 9 | CO 10 | CO 11 | CO 12 | CO 13 |
| 1 | X | X | X | X | |||||||||
| 2 | X | X | |||||||||||
| 3 | X | X | X | ||||||||||
| 4 | X | X | X | X | |||||||||
| 5 | X | X | X | X | |||||||||
| 6 | X | X | X | X | |||||||||
| 7 | X | X | X |
| No. | Assignments | Tests | Practical Exercises | Exam |
| 1 | X | X | ||
| 2 | X | X | X | |
| 3 | X | X | X | |
| 4 | X | X | X | |
| 5 | X | X | X | |
| 6 | X | X | X | |
| 7 | X | X |