CS 1530 Project: Beta Testing Instructions, Study Guides, Projects, Research of Software Engineering

The requirements and deadlines for the beta testing phase of a cs 1530 project. Students are expected to submit the complete source code, a test plan, original requirements specification, a user manual, and well-documented code by november 19th. Testers will evaluate the correctness, completeness, and documentation quality of the surpass spreadsheet product. An additional 20% of the grade will be based on students' testing of two other surpass versions by november 29th.

Typology: Study Guides, Projects, Research

Pre 2010

Uploaded on 09/02/2009

koofers-user-ioa-1
koofers-user-ioa-1 🇺🇸

9 documents

1 / 2

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
CS 1530 Project
Beta Testing
Due: November 19th, testing results and testing documents: November 29
For this project milestone, you should have a functional, and mostly complete
implementation of your Surpass spreadsheet product. Something that can be tested at the
customer’s site (beta test). The instructors and two groups will be the testers for your
product.
What to hand in:
1. The complete source code for your project. If it’s not straightforward to compile
and run your Surpass version, a description on how to compile and start it should
be handed in as well. For testing purposes, we will be producing bytecode
executables that we will be using for testing and distribute to other groups for
testing. Only the instructors will see the actual source code. (due 11/19)
2. A test plan along with tests and test cases to test your product. (due 11/29)
3. Your original requirements specification. The test plan should describe how each
of the requirements is tested. (due 11/19)
4. A user manual .(due 11/19)
5. Your code should be well documented. This includes comments in the code but
we also like a short write-up that relates your design to the implementation. (due
11/19)
Please hand in your materials electronically, either as a zip or (compressed) tar archive.
How your project will be graded
:
1. Correctness. The beta testers will try to break your Surpass system in any possible
way. It should be stable, handle errors gracefully, and conform to your
specification.
2. Completeness. Mostly complete should not be read as you can implement just
what you see fit. If there are minor omissions with respect to your design or
specification, this will not affect your grade by much. But every missing feature
will lower your grade. If your Surpass is not usable (can’t create, load or save
spreadsheets, enter data and formulas and calculate) your grade will be an F.
3. The quality of your documentation: this includes the user manual, and code
documentation. If the instructors have any doubts about how your code was
derived from your design you may be asked to make an oral presentation either in
pf2

Partial preview of the text

Download CS 1530 Project: Beta Testing Instructions and more Study Guides, Projects, Research Software Engineering in PDF only on Docsity!

CS 1530 Project

Beta Testing

Due: November 19th, testing results and testing documents: November 29 For this project milestone, you should have a functional, and mostly complete implementation of your Surpass spreadsheet product. Something that can be tested at the customer’s site (beta test). The instructors and two groups will be the testers for your product. What to hand in:

  1. The complete source code for your project. If it’s not straightforward to compile and run your Surpass version, a description on how to compile and start it should be handed in as well. For testing purposes, we will be producing bytecode executables that we will be using for testing and distribute to other groups for testing. Only the instructors will see the actual source code. (due 11/19)
  2. A test plan along with tests and test cases to test your product. (due 11/29)
  3. Your original requirements specification. The test plan should describe how each of the requirements is tested. (due 11/19)
  4. A user manual .(due 11/19)
  5. Your code should be well documented. This includes comments in the code but we also like a short write-up that relates your design to the implementation. (due 11/19) Please hand in your materials electronically, either as a zip or (compressed) tar archive.

How your project will be graded :

  1. Correctness. The beta testers will try to break your Surpass system in any possible way. It should be stable, handle errors gracefully, and conform to your specification.
  2. Completeness. Mostly complete should not be read as you can implement just what you see fit. If there are minor omissions with respect to your design or specification, this will not affect your grade by much. But every missing feature will lower your grade. If your Surpass is not usable (can’t create, load or save spreadsheets, enter data and formulas and calculate) your grade will be an F.
  3. The quality of your documentation: this includes the user manual, and code documentation. If the instructors have any doubts about how your code was derived from your design you may be asked to make an oral presentation either in

class or during office hours explaining your code and relating it to the design. If there’s no apparent relation between your design and the code you turned in, your grade will be an F.

  1. 20% of your grade will be based on your own testing of two other Surpass versions. For this part you will have to hand in your test cases, test plans and test results for the two tested Surpass programs. (due 11/29). We expect to distribute the bytecode before 11/22.