Dr Sita Ramakrishnan
Senior Lecturer
Phone: +61 3 990 58689
Fax: +61 3 990 55159
Dr Sita Ramakrishnan
Senior Lecturer
Phone: +61 3 990 58689
Fax: +61 3 990 55159
Dr Sita Ramakrishnan, Bldg 63, Room 119, Clayton campus
Available for consultation in 119/63 for 1 hour after FIT4004/5171 lecture
sitar@infotech.monash.edu.au
Mr Quazi Mamun, Bldg 63, level 1 p/grad room, Clayton campus
quazi.mamun@infotech.monash.edu.au
Tutor/assessor/marking role- shared between Sita and Mamun for FIT4004/5171 assignments and also for assessing assignments demonstrated in the MUSE lab.
Welcome to FIT4004.
In this unit, we will examine system validation and verification, quality and standards. In particular, we will review the important phases of testing and emphasize the significance of each phase when testing different types of software. The course will commence with challenges and taxonomy of testing and examine concepts such as test adequacy, test coverage, data-flow testing, category-partition method, test automation, test generation, test oracles, software standards, test selection, regression testing, test prioritization, mutation testing and model based testing. By the end of the course, students should be able to apply state of the art in testing technology for O-O, component-based, GUI and web based systems. Students will also become familiar with open research issues in testing. They will gain hands-on testing and analysis experience via the assignments.
plus 1 hr tutorial/wk plus 1 hour unsupervised tute-like activity in the MUSE lab
Estimated weekly hourly commitment needed for the unit, including classes, reading, assessment, time needed for computer access, and other activities:
two-hour lecture, one-hour tutorial and one-hour unsupervised lab/tute activity in the MUSE Lab to familiarise with tools, work on assignments, self study etc, a minimum of 2-3 hours of personal study per one hour of contact time in order to satisfy the reading and assignment expectations. You will need to allocate up to 5 hours per week in some weeks, for use of a computer, including reading research papers for an assignment and lab discussions with class members.
Lectures as specified below from weeks 1 - 13
1 hour tute/week for reinforcing material covered in lectures through discussion & students' particiption with preset hurdle exercises and marks allocated for a final assessment in the tute.
Unsupervised lab/tute like activity in the MUSE lab to encourage students to learn the material covered and exercise it in tools available in the lab, and get ready for assignments.
3 assignments.
For information on timetabling for on-campus classes please refer to MUTTS, http://mutts.monash.edu.au/MUTTS/
On-campus students should register for tutorials/laboratories using the Allocate+ system: http://allocate.its.monash.edu.au/
| Week | Date* | Topic | Key dates |
|---|---|---|---|
| 1 | 01/03/10 | Basic Testing, Concepts, IEEE definition, Role of V& V in SDLC, Challenges in Testing | Sem 1 2010 commences in March 2010 |
| 2 | 08/03/10 | Faults, Failures and Errors, Test Oracle problem, Taxonomy of software testing | fri - last day to add a unit to sem 1 enrolment |
| 3 | 15/03/10 | Automated testing: JUnit testing, Automating JUnit, Run tests from Ant, Bugzilla, Rational tools, V Model | |
| 4 | 22/03/10 | Testing Techniques, Documenting tests, Test Adequacy and Test Coverage | |
| 5 | 29/03/10 | Testing Techniques: Data-flow testing, Category-Partition method; Test levels; Testing & Certification | Last day to discontinue sem 1 unit & receive fee refund of tuition fees |
| Mid semester break | |||
| 6 | 12/04/10 | Test case Generation (contd): Data-flow Testing; OO test methods; automated GUI testing; Web testing | Ass 1 40% due Week 6, Students complete their assignment and Demo their work in the MUSE Lab - exact schedule for demos will be allocated later. |
| 7 | 19/04/10 | Test Oracles; Test Maturity Model; Software Standards | |
| 8 | 26/04/10 | Test Selection: Usage-based testing techniques; Code instrumentation; Effective test prioritization; Regression Testing | |
| 9 | 03/05/10 | Model Based and Model Driven Testing; Quality; Aspect Testing | Ass.2 20% |
| 10 | 10/05/10 | Mutation Testing | |
| 11 | 17/05/10 | Component Testing | |
| 12 | 24/05/10 | Experimental SE and Software Testing | Ass.3 40% |
| 13 | 31/05/10 | Revision/Presentations | Guest lecture - to be advised |
*Please note that these dates may only apply to Australian campuses of Monash University. Off-shore students need to check the dates with their unit leader.
Monquest evaluation is planned for this unit.
There is no one set text for the unit. However students are expected to read widely from the recommended reading list. Recommended books are available in the Hargrave Library and may also be in the bookshop should you wish to purchase your own copies.
Daniel J.Mosley, Bruce A. Posey (2002) Just Enough Software Test Automation, Addison-Wesley
MUSE Lab in Bldg 26/G13 is the lab used for this unit. Has all the software in the standard student labs plus is equipped with
Software may be:
Bachelor of Software Engineering is offered only for On-campus students. You may use the facilities available in the computing labs. Information about computer use for students is available from the ITS Student Resource Guide in the Monash University Handbook. You will need to allocate up to 4hours per week for use of a computer in the lab for doing assignments.
Study resources we will provide for your study are:
For more information for units including FIT4004:
You can access MUSO and Blackboard via the portal (http://my.monash.edu.au).
To pass a unit which includes an examination as part of the assessment a student must obtain:
If a student does not achieve 40% or more in the unit examination or the unit non-examination total assessment, and the total mark for the unit is greater than 50% then a mark of no greater than 49-N will be recorded for the unit.
Students are required to pass each of the assignments to be assigned a Pass in the unit. There is no formal examination for this unit.
Assignment coversheets are available via "Student Forms" on the Faculty website: http://www.infotech.monash.edu.au/resources/student/forms/
You MUST submit a completed coversheet with all assignments, ensuring that the plagiarism declaration section is signed.
Assignment submission and return procedures, and assessment criteria will be specified with each assignment.
Please make every effort to submit work by the due dates. It is your responsibility to structure your study program around assignment deadlines, family, work and other commitments. Factors such as normal work pressures, vacations, etc. are not regarded as appropriate reasons for granting extensions. Students are advised to NOT assume that granting of an extension is a matter of course.
Students requesting an extension for any assessment during semester (eg. Assignments, tests or presentations) are required to submit a Special Consideration application form (in-semester exam/assessment task), along with original copies of supporting documentation, directly to their lecturer within two working days before the assessment submission deadline. Lecturers will provide specific outcomes directly to students via email within 2 working days. The lecturer reserves the right to refuse late applications.
A copy of the email or other written communication of an extension must be attached to the assignment submission.
Refer to the Faculty Special consideration webpage or further details and to access application forms: http://www.infotech.monash.edu.au/resources/student/equity/special-consideration.html
Assignments received after the due date will be subject to a penalty of 5% per day, including weekends.
Assignments received later than one week after the due date will not normally be accepted.
Students can expect assignments to be returned within two weeks of the submission date or after receipt, whichever is later.
Please visit the following URL: http://www.infotech.monash.edu.au/units/appendix.html for further information about: