1 Purpose

The primary purpose of this assignment is to help you review (and demonstrate that you have acquired) the knowledge and skills required to implement graphical user interfaces (GUIs).

2 Overview

As you know from an earlier assignment, perspecTV is a (fictitious) company that designs, creates and markets products that provide a new perspective on television. Their products make television both more interactive and more informative. They are in the process of developing a suite of products called forScore for judged competitions of various kinds (e.g., sporting events like diving and gymnastics, singing contests, dance competitions).

They have decided that their earlier command line application limited the size of the potential market. So, they have added two epics that involve the creation of a GUI-based application (named DiveIn) that lets users enter information and display results. The team decided not to write sprintable stories but instead to write use case descriptions and then wrote specifications from the use case descriptions. They further decided that, for this sprint, the GUI need only only work with competitions that have a particular structure.

3 Documents

perspecTV has created several new documents for this release.

• New Stories for forScore
• Tasks for v4 of forScore
• Use Case Descriptions for DiveIn
• Specification of the DiveEditorDialog Class
• Specification of the DiveInWindow Class
• Implementation of of the Main Class (in the app package)

4 A Recommended Plan

As before, the tasks that were identified by the team at perspecTV are organized by feature. Hence, though they are numbered so that they can be referred to in documents and conversations, the numbers should not, in any way, influence the order in which you complete them. I would suggest you sequence your activities as follows.

1. Read and understand all of the documents.
2. Create a new project for this version.
3. Copy all of the classes from the previous version.
4. Implement the DiveEditorDialog class.
5. Implement the DiveInWindow class.
6. Test and debug the complete system.

5 Submission

You must submit (using Gradescope) a .pdf file containing a screen shot that shows the DiveInWindow and the DiveEditorDialog for the scores in ST_Complete_01.div.

You must also submit (using Gradescope) a .zip file containing all of the code necessary to build your application. Gradescope will only be checking to ensure that your code complies with the course style guide. Hence, you may only submit to Gradescope five times. If you can't get your code to comply with the course style guide within five submissions, you will receive a grade of 0 on the assignment.

6 Grading

You will receive one of four grades on this assignment -- 100, 75, 50, or 0. You will receive a grade of 100 if your code is essentially correct (i.e., a limited number of system tests do not cause any failures). You will receive a grade of 75 if you appear to have devoted significant effort to the assignment but your code has small defects. You will receive a grade of 50 if you devoted a reasonable amount of effort to the assignment but your code has major defects. You will receive a grade of 0 otherwise and/or if the code you submit to Gradescope contains any style defects.