Mohammed Ozayr
Abdul Kader
Grade: 12A
Information Technology
PAT Phase 2

Context
Database Design:
-ToyDistributionTBL
-StockActivityTBL
-WorkerTBL
-Table Relationship
Role of Database:
GUI Design:
-HCI Principles
-Components
TOE Chart:
-Table
Data Structure:
-All Data types used
OOP:
-Classes and Objects
-Class Diagram
IPO Design and Error Catching:
Table:-
-Input
-Process
-Output
-Validation & Integrity
-Error Message
Testing:
Database Design: StockActivityTBL | Field Name | Data Type | Size | PK/FK | Distribution Number | Text | 8 | PK | DistrictID | Text | 10 | FK | WorkerID | Text | 6 | FK | DonationID | text | 6 | FK | Failed Donations | Number | Integer | | Total Donations | Text | 15 | |

ToyDistributionTBL | Field Name | Data Type | Size | PK/FK | DistrictID | Text | 10 | PK | Area of Donation | Text | 20 | | Age of Child | Number | Integer | | Donation Details | Text | 20 | | Quantity | Number | Integer | | Date of Distribution | Date | Short Date | |

WorkerTBL | Field Name | Data Type | Size | PK/FK | WorkerID | Text | 6 | PK | Surname | Text | 15 | | FirstName | Text | 15 | | Gender | Text | 6 | | Age | Number | Integer | | ContactNumber | Text | 10 | |

DonationTBL | Field Name | Data Type | Size | PK/FK | DonationID | Text | 6 | PK | FirstName | Text | 15 | | Surname | Text | 15 | | Age | Number | Integer | | ContactNumber | Text | 10 | | Address | Text | 30 | | Donation Details | Text | 20 | |

Table Relationship:

Role of Database:
There will be an Administrative section and User’s section. The Administrator will be the Manager and the users are the people who works for The Gift of the Givers.
The admin will have full control and access to the databases. A username and password entered correctly will allow access to the database. He/she will be able to create, sort, read, update and delete records in the respective tables. Extra information will be added to the database table. Unwanted or stale information will be kept for 3 months then deleted permanently of the system.
The users won’t be able to delete or edit information on a database. They will be able to view and add information on the system. The user will enter data information under their own WorkerID. A Search and Sort GUI will be available for easier viewing of Data Information.

GUI Design:
HCI Principles:-
HCI - Human Computer Interaction
Human Computer interaction (HCI) involves the study, planning, and design of the interaction between people (users) and computers. Post on Google answers
Type of Program – The programme will be GUI based, and make use of Java code. Queries will be made via the GUI to the database.
Context and User - The user will be a worker, and the program will be designed using context of data storage.
User needs and Usability - The program will be user friendly. The user will be guided the way to input proper data and will display error messages when necessary. The software solution will be spontaneous, and have an simple navigate to GUI. It will have an precise means of error handling.
Dialogue – The program will interact with the user via dialog boxes by JOptionPanes, or by directing them to a new screen. Error messages will be communicated to the user on a continuous basis.
Clearly marked exits – The user will have options to either exit a current screen, or to go back to the previous screens. He/she will also be able to progress to the next screen.
Help – Every screen will have access to a help feature, explaining what the user needs to do. The help content will be related to that particular screen that user is on.

Components:
The following components will be used in my program, each showing its purpose, followed by an example.
Outline of GUI section: jTable – Display of data, from database table. * Distribution. jButton – Progressing in the program, or to perform a task. * “Help”. jPanel – Isolation of components. * Group items together. jLabel – Show function of component. * Display headings like: “FirstName:” , “Password:”. jTextField – Entry of data. * Contact Number and Username. jTextArea – Used to display information . * Like: “Please Re-enter password”. jSpinner – Used to select an option. (Note that it can move up and down) * Choose the Age. jComboBox – Used to select from the options given. * Choose the correct gender. jPasswordField – Used to hide the password * “*********”

TOE Chart:
These are my tools and guide for the planning and designing an event driven programming application. Task | Object | Event | Get Workers Information | WorkerID | jTextField | Key Pressed | FirstName | jTextField | Key Pressed | Surname | jTextField | Key Pressed | Age | jTextField | Key Pressed | Contact Number | jTextField | Key Pressed | Add Worker | btnAddW | Click | Making Donation | DonationID | jTextField | Key Pressed | FirstName | jTextField | Key Pressed | Surname | jTextField | Key Pressed | Age | jTextField | Key Pressed | Contact Number | jTextField | Key Pressed | Address | jTextField | Key Pressed | Donation Details | jTextField | Key Pressed | Add Donation | btnAddD | Click | Admin Updating Database | Create | btnCreate | Click | Update | btnUpdate | Click | Delete | btnDelete | Click | View | btnView | Click | Clear | btnClear | Click | Exit | btnExit | Click |

Data Structure:

All Data types to be used:- * Integer (int) * String (String) * Array ([]) * Double (double) * Integer (int)

OOP:
Classes and Objects:-
The following attributes will be created in a class called Donation. * Surname * FirstName * Contact Number * Donation
1.Create an Accessor method called getSurname() to return the name of the worker.
2.Create an Accessor method called getFirstName() to return the name of the worker.
3. Create a Mutator method called setNum() to be able to edit the Contact Number of the worker.
4.Create a toString() that will display the attributes as one String in a specific format.
5.The program will create an entity Class.
6.An instance of an object will also be created.
7.The entity class will have Accessors and Mutators.

Worker Class | +getSurname() | +getNum() | +getFirstName() | -setNum() | +toString() | +CalculateTotalDonations() | +TotalDonationsAfterAudit |

Testing:
Example of Test Data and expected results: (Refer to the sample GUI) Test Data (Example) | Results (Example) | Number of Donations made | Submit to ToyDistribution Database | Number of Failed Donations made | Submit to StockActivity Database | GUI Functionality | | Function: (Test Data with result input into GUI) | i. | Minimise ,Maximise ,Exit | ii. | Panel | iii. | Button - Proceed | iv. | Button - Add Donation | v. | Button - Help | vi. | Button - Add | vii. | Button - Delete | viii. | Button - Edit | ix. | Button - Clear | x. | Button - Exit | xi. | Label Heading | xii. | Label for Button - Username | xiii. | Label for Button - Password | xiv. | Label for Button - WorkerID | xv. | Label for Button - Surname | xvi. | Label for Button - FirstName | xvii. | Label for Button - Age | xviii. | Label for Button - ContactNumber | xix. | Combo Box for Gender | xx. | Spinner for Age | xxi. | Table for Data projection | xxii. | TextArea for Display | xxiii. | TextField for Username | xxiv. | PasswordField for Password | xxv. | TextField for WorkerID | xxvi. | TextField for Surname | xxvii. | TextField for FirstName | xxviii. | TextField for ContactNumber | xxix. | Progress Bar for limited inputs |