cs2001 - group project task 2 studentcycle 1103346 - nishanth chandradas 1019407 - amadou samba...

CS2001 - Group ProjectTask 2

StudentCycle

1103346 - Nishanth Chandradas1019407 - Amadou Samba1218132 - Suleiman Sani1119964 - Humza Ahmad

Group 37

Sequence Diagrams

Text

This is the sequence diagram that shows the process of users creating an account with StudentCycle.

This diagrams shows the interaction between User, the application and the server.

The Android Application

Firstly a user submits their user details in the application. Next the application sends these details to the database to be inserted, if there is an error, the application will alert the user. Else the application will let the user know the details are fine.

Sequence Diagrams

Firstly the user enter the details of the product they would like to put onto studentcycle, if all the required details are entered, they are stored in the database. The user is then confirmed of the successful upload and the date and time are updated in the database.

The second sequence diagram shows one business behavior of student cycle, which is the user uploading Items they want to trade/sell.

Class Diagrams

1 or many Sellers can upload 0 or more products. Each product can be uploaded by only one Customer or by more Customers

We got an exclusive specialization, Subclass from the parent class ‘customer’. This is because the customers got the flexibility to be vendors themselves and sell items as well as order and purchase products.

Each customer can place either 0 or more orders. Each order can be placed by one and only one customer.

ER DiagramsER diagram below is describing components of student cycle and how each component inter-chains together. This is shown in an abstract way based on Richard Barker Crows foot notation 1980s Proposed techniques and methods.

The diagram shows the Customer can either place zero, one or many orders, an order can contain either zero, one or many products, ‘Seller sub class of Customers can either sell zero, one or many products.

Database DesignTo design the database we followed the following

steps:

•Decide the purpose of the database•Decide what information is required to be stored•Split the information into tables•Select primary keys•Set up database relationships•Normalize the database

Normalization

The benefits of normalization in databases is to eliminate data reducing. This in return the performance of the database by reducing the amount of storage it will take up. The less number of columns that exist the smaller the index, this means that queries can be returned quicker.

There are different forms of normalization:

• First Normal Form (1NF): In this form of normalization duplicative content is removed and separate tables are created for related data.

•Second Normal Form (2NF): In this form of normalization everything from 1NF is repeated, however all subsets of data are removed.

•Third Normal Form (3NF):The same as 1NF and 2NF, however all columns that are not dependent upon the primary key are removed.

Database CreationAfter logging into the server, we log into the mysql server.Then we select the database that we would like to use, in this case the database is called “cs2001”.

Once the database is selected, we can then proceed to query the database.

Database CreationHere we have run a command that describes the table “CategoryItems”

Here we have run a command that describes the table “CustomerAccount”

Database CreationAs there is no primary key, I have used “Alter” to add a primary key to the “CategoryItems” table.

Here you can see that the table “CategoryItems” now has an ItemId.

Database CreationHere i am doing the same to the “CustomerAccount” table.

Here you can see that the table “CategoryItems” now has an ItemId.

Jetty

This is how we run the Jetty server.

JettyThis is the Hello.java file that has been modified to show a message in the web browser.

This is the web page that is being served by the server.