Objective:
The primary objective of this project is to give you practice in
testing a "real" software project. Although the scope of the
project is restricted due to the length of the semester, it will provide
you with valuable experience in terms of analyzing and validating
development models, writing test cases, and creating test
documents. This project
will
involve writing code!
Grading Scheme: The grade
for this project shall be based on three deliverables and two class
presentations, representing
30%
of the final grade. Note that some exam questions will be
based on the knowledge acquired from participating in project team work.
The following is a brief description of the deliverables and
presentation:
Deliverable 1
|
Software Requirements Test
Document (SRTD)
|
Due
Oct. 3
|
Presentation 1
|
A brief description of
SRTD. Details will follow.
|
Oct.
3
|
Deliverable 2
|
Design Test Document (DTD)
|
Due
Nov. 7
|
Final Deliverable
|
Test documentation consisting
of:
- Software Requirements Test Document,
- Design Test Document,
- Code for drivers, stubs and harnesses.
- Developer's Test Guide
- A CD with all project material.
|
Due
Dec. 2
|
Presentation 2
|
A brief description of the
process used to test the systems.
The presentation should be no more
than 20 mins.
|
Dec.
5
|
Note: All students in a
project team shall receive the same grade unless members of the team
request otherwise. In the event such a request is made then each
team member will have to write a report describing her/his contribution
and the contribution of the other team members. If the team
members would like to be graded individually the request should be made
before the final presentation.
Project Teams: Each team
shall consist of
3 or 4 students.
I will assign the project teams.
Selection of Project:
- A software application (developed by students in the software
engineering class) will be assigned to each team.
This means you will have to spend time understanding the application and
getting the implementation to run. In some cases you will also
have to get a feel of the implementation language.
- Each team must use the
Rational Functional Tester tool and one other free testing/metrics tool
to assist in testing the project. At the end of the course you
will have to evaluate the tools using specified criteria.
Last
modified 08/26/2005