ud494 »

Test Driven Development Assignments

Part 2 Details

Preamble

The customers loved the first delivery so much that they decided to expand the project by

  • Adding functionality
  • Adding a GUI

To this end, they provided the teams with additional story cards that describe the additional requirements.

Being extremely good at drawing, they also provided a sketch of the GUI they envision for the tool.

They also provided task cards for clarity.

Instructions

  1. Carefully read the story and task cards presented below.
  2. Write a set of JUnit test cases that cover the additional functionality.
    • Use your judgment and the guidelines provided in the videos to decide when the set of test cases is adequate
    • The set of test cases should include (1) tests for all relevant methods of the new classes, and (2) tests that target the new or modified functionality in existing classes
    • You do not need to supply any JUnit test cases for the GUI, but you may if you wish.
  3. By the due date, go to the Udacity quiz to submit your test cases.  You will not be submitting the code itself for this part.  Note that since your new tests will cover functionality that is not yet implemented, they will not pass, but you may write skeleton code/stubs for the classes so that the tests compile in Eclipse if you wish. 

Remember, you should NOT write the code to implement the functionality described in these cards, just the JUnit tests for that code!

Part 2 Story Cards

Story Card 1

Instructors and TAs use the GradesTool application to get information about the students’ performance. They can pick the name of a student from a list, and the application shows the student information. A possible GUI for the tool is the following:

Screen Shot 2013-12-31 at 2.49.57 PM.png

Story Card 2

Using the tool, users can see a student’s name, GT ID, e-mail address, project information, and assignment information. Project information includes, for each project, the student’s team grades, the average grade across teams, and the average contribution received by the student from his/her team members. Analogously, assignment information includes, for each assignment, the student grade and the average grade for the class.

Story Card 3

The users of the tool can select a student and save his/her information in a file named after the student (e.g., LaraineSmith.txt)

Part 2 Task Cards

Task 1

Create a Team class to hold information about a particular team, including team number, list of Student names, team grade, and list of average contribution ratings.

Task 2

Create a Project class to hold information about a particular project, including project number, project description, list of Teams, and average project grade

Task 3

Create an Assignment class to hold information about a particular assignment, including assignment number, assignment description, list of Student grades, and average grade

Task 4

Expand the Student class to hold additional information about the student, including email address, and each Team the student was on.

Task 5

Expand the GradesDB class to hold a list of Projects, accessible by project number, and a list of Assignments, accessible by assignment number. Also, create a method to output all information for a student, which can be either written to a text file or the the text box in the GUI

Task 6

Create a GradesToolGUI class with a title bar to display the application name, combo box to display a list of Students, text box to display information about the selected Student, and a save button to save the Student information to a text file

Part 2 Submission

Remember, to submit, go to the Udacity quiz.

Part 3 Details

Write the code that will make the set of test cases you wrote for Part 2 pass.  Remember, do NOT do this until after Part 2 is due.