Criterion B: Design

Design Overview

For the product, I have decided to use multiple Java Frames with different purposes. They would be referred
to as ‘page’ and ‘pages’ for plural. They are:

1) Log In Page
2) Main Page
3) Add Player Page
4) View Roster Page
5) Add Schedule Page
6) View Schedule Page

1) Log In Page
This is the authentication page. There would be a Java Text field for entering Username and a Java Password
Field for entering Password.

2) Main Page
This is the Java Frame that follows after entering the correct username and password. There will be 5 buttons
that will allow the user to either add player or view roster, add to schedule or view their schedule and close
the program.

3) Add Player Page

In this Java Frame, the user has multiple text fields to enter player data and a button to save the data into the
database. A button to close this Java Frame will also be available.

4) View Roster Page

The user can view their Player datas in a Java Table in this Java Frame. There will also be a button available
to the user to update the data entered in the provided text fields.

5) Add Schedule Page

The user can add important dates and their details to the database in a different table using a button.

6) View Schedule Page

1
As the name implies, the user’s schedule will appear on a Java Table and they can update and delete their
Schedules using a button

UML Diagram

2
Flowcharts

Flowchart for adding data into the database

3
Flowchart for updating data into the database

4
Classes with important Variables

Class : ‘Players’

This class represents a technique to enter the player’s data into the database. The user will have to input the
player’s jersey number, name, height, position and status. If all the fields are entered correctly, the data will
be uploaded into the database.

Variable Name Data Type Description

jTxtJersey jTextField Used to enter player’s Jersey Number

jTxtName jTextField Used to enter player's full name

jTxtHeight jTxtField Used to enter the player’s height

jComboPos jComboBox Used to choose a position

jCheckBoxHealthy jCheckBox Used to indicate a player is healthy and

ready to play

jCheckBoxInjured jCheckBox Used to indicate a player is not healthy

and unavailable to play

jBtnSave jButton Used to add data into the database

Class: ‘View’

The purpose of this class is to view the database in the final product and also update and delete player datas.

Variable Name Data Type Description

jTxtUpJersey jTextField Used to enter player’s jersey number

for executing update query

jTxtUpName jTextField Used to enter player's name for

updating

jTxtUpHeight jTextField Used to enter player's height for

updating

jComboPostition jComboBox Used to select a player’s position for

updating

jComboStatus jComboBox Used to select a player's health status

for updating

jBtnUpdate jButton Used to update the data into the

database

jBtnDelete jButton Used to delete data from the database

5
Class: ‘ViewCalendar’

This class is used to view, update and delete data from the table ‘Schedule’ in database ‘Goldengate’.

Variable Name Data Type Description

jTableCalendar jTable Used to view data from the table

‘Schedule’ in database ‘Goldengate’

jTxtSearchCalendar jTextField Used to enter type and search for dates

with matching type.

jComboDateStatus jComboBox Used to update status of the schedule

jTxtField1 jTextField Used to update time into the database

jBtnDateSave jButton Used to update the datas into the

database.

jBtnCalendarDelete jButton Used to delete the selected date from

the database

6
Testing Plan

1) Unit Testing: It is a type of Function test. Tests that confirm the correct functionality of each component

of the product will be performed.

7) Integration Testing: It is a test to determine if all the combined integrated modules function properly

after integration.

8) User Acceptance Testing: it is a type of test that includes the client to test it and verify if it matches their

needs. In this case, Mr.Bipen will run this test.

9) System Testing: It is a type of test that will determine if the final product matches the success criteria

and the needs stated by my client.

7
Word Count: 401