You are on page 1of 18

MYTECC E-COMMERCE SYSTEM

Final Report

Version 1.0

SEMESTER MARCH 2021 – AUGUST 2021

GROUP: CS1104C

KHAIRUL AFNAN BIN AHMAD ZAMAKHSHARI (2019447598)


MUHAMAD SYAHIR ZAKWAN BIN MOHD YUSOF (2019439582)
JOHAN NAZRIN BIN ROSLI (2019262772)
MUHAMMAD ZULHISHAM BIN MISBAH (2019285598)
MUHAMMAD ZIYAD BIN AZHARI (2019432096)
MYTECC E-COMMERCE SYSTEM Version: 1.0.0
Final Report Date: <dd/mm/yyyy>
<person in charge>

Revision History
Date Version Description Author
<dd/mm/yyyy> <x.x> <reason to change the documentation <name>
contents>

Confidential  CS1104C 2021 Page 2 of 18


MYTECC E-COMMERCE SYSTEM Version: 1.0.0
Final Report Date: <dd/mm/yyyy>
<person in charge>

Final Report Grading Rubric


Remarks/Marks
Category
Poor Mediocre Good Excellent Outstanding
1 2 3 4 5
Purpose, scope &
objectives Project are briefly explained with the purpose of development, scope and
objectives to be achieved.
1 2 3 4 5
Assumptions &
Constraints Project clearly defined the limitation after development and constraints during the
development process.
1 2 3 4 5
Project Timeline
Provide the project plan/Gantt Chart created using MS Project or suitable
application and shown detailed the process of development.
1 2 3 4 5
Team Structure Provide the hierarchy of the team organization/structure/chart. The structure
should be created by appropriate tool such as SmartArt in MS Word function.
1 2 3 4 5
Roles &
Responsibilities Provide your group member’s formal picture and their responsibilities with job
designation.
1 2 3 4 5
ERD Place ERD in this section and ensure it uses correction notation whether Crow’s
Foot or Chen. ERD should be matched with physical database.
1 2 3 4 5
Data Dictionary Please provide a list that contains name of tables, attributes and data type. All the
components must be exactly similar with physical database.
1 2 3 4 5

Place DFDs of the proposed information system here. Provide descriptions of the
DFD
proposed information system according to provided diagram. Descriptions must
be cleared to ensure audience able to understand what this document tries to
deliver.
1 2 3 4 5
Conclusion &
Recommendation Able to conclude does the project achieved the identified objectives and how the
objectives are achieved
1 2 3 4 5
Recommendation
Able to recommend new upgrades in the future towards the developed system.

50

Confidential  CS1104C 2021 Page 3 of 18


MYTECC E-COMMERCE SYSTEM Version: 1.0.0
Final Report Date: <dd/mm/yyyy>
<person in charge>

Confidential  CS1104C 2021 Page 4 of 18


MYTECC E-COMMERCE SYSTEM Version: 1.0.0
Final Report Date: <dd/mm/yyyy>
<person in charge>

Table of Contents
1. Introduction 5
1.1 Purpose 5
1.2 References 5

2. Project Overview 5
2.1 Project purpose, scope and objectives 5
2.2 Assumptions and constraints 5
2.3 Project Timeline 6

3. Project Organization 7
3.1 Team Structure 7
3.2 Roles and Responsibilities 8

4. Database and System Design 10


4.1 Entity Relationship Diagram 10
4.2 Data Dictionary 11
4.3 Data Flow Diagram 13
4.3.1 Context Diagram 13
4.3.2 Diagram-0 15

5. Conclusion and Recommendation 17


5.1 Conclusion 17
5.2 Recommendation 17

Confidential  CS1104C 2021 Page 5 of 18


MYTECC E-COMMERCE SYSTEM Version: 1.0.0
Final Report Date: <dd/mm/yyyy>
<person in charge>

1. Introduction

1.1 Purpose

This Final Report summarizes the whole project outcome that we achieved at the end of the project. This
document will explain all about the project from the task division until the final product itself. This
report will emphasize about the project purpose, project organization and the information system
design and how we achieve the purpose of this project.

1.2 References

 Final Report ICT200: MYTECC Sales System


 Software Development Plan: MYTECC E-Commerce System
 Software Requirement Specification: MYTECC E-Commerce System
 Software Design Description: MYTECC E-Commerce System

2. Project Overview
2.1 Project purpose, scope, and objectives

This system developed only for the use of Science Computer student of UiTM Pahang Branch, Raub
Campus to make pre-order of MYTECC’s merchandise. The system development objective is to create a
better and more systematic system to record MYTECC’s merchandise order and sales. The idea of this
system is to digitalize the pre-order process to avoid any possibility of losing the order data. Plus, the
old system consumes a lot of time just for collecting the order from the student. With this new digitalize
system, the order can be passed through the vendor safer and faster.

2.2 Assumptions and constraints

In term of our system functionality, our only constrain is that the user cannot use directly make payment
through the system as it requires a huge cost and exceed our project budget. Hence, to compensate of the
payment function, we prepare a section where the user can upload their payment receipt as payment
evidence.

Confidential  CS1104C 2021 Page 6 of 18


MYTECC E-COMMERCE SYSTEM Version: 1.0.0
Final Report Date: <dd/mm/yyyy>
<person in charge>

2.3 Project Timeline

Confidential  CS1104C 2021 Page 7 of 18


MYTECC E-COMMERCE SYSTEM Version: 1.0.0
Final Report Date: <dd/mm/yyyy>
<person in charge>

3. Project Organization
3.1 Team Structure

PROJECT MANAGER
KHAIRUL AFNAN BIN
AHMAD ZAMAKHSHARI
(2019447598)

PROJECT SUPERVISOR
SIR MUHD EIZAN SHAFIQ BIN
ABD AZIZ

DATABASE DESIGNER
JOHAN NAZRIN BIN ROSLI BACK-END DEVELOPER
(2019262772)
MUHAMAD SYAHIR ZAKWAN
BIN MOHD YUSOF
(2019439582)

FRONT-END DEVELOPER 1

MUHAMMAD ZULHISHAM BIN


MISBAH FRONT-END DEVELOPER 2
(2019285598)
MUHAMMAD ZIYAD BIN
AZHARI
(2019432096)

Confidential  CS1104C 2021 Page 8 of 18


MYTECC E-COMMERCE SYSTEM Version: 1.0.0
Final Report Date: <dd/mm/yyyy>
<person in charge>

3.2 Roles and Responsibilities

INFORMATION ROLES AND RESPONSIBILITIES PICTURES

MUHD EIZAN SHAFIQ PROJECT SUPERVISOR


BIN ABD AZIZ
 Provides guides to the
project members to develop
the project.

KHAIRUL AFNAN BIN PROJECT MANAGER


AHMAD ZAMAKHSHARI
 Plan the flow of the project
2019447598 system.
 Guide the team members
regarding the project.
 Make sure the team
members play their roles in
the project.
 Make sure the project
complete before the dateline.

MUHAMMAD FRONT-END DEVELOPER 1


ZULHISHAM BIN
MISBAH  Illustrate design ideas using
storyboards, process flows
2019285598 and sitemaps.
 Design graphic user interface
elements, like menus, tabs
and widgets
 Build page navigation buttons
and search fields

JOHAN NAZRIN BIN DATABASE DESIGNER


ROSLI
 Create an entity-relationship
2019262772 diagram (ERD) according to
the identified requirement.
 Create and modify tables,
views and indexes, PL/SQL
store procedures, functions,
and triggers according to
business requirement.

Confidential  CS1104C 2021 Page 9 of 18


MYTECC E-COMMERCE SYSTEM Version: 1.0.0
Final Report Date: <dd/mm/yyyy>
<person in charge>

MUHAMAD SYAHIR BACK-END DEVELOPER


ZAKWAN BIN MOHD
YUSOF  Construct physical database
based on the entity-
2019439582 relationship diagram.
 Assist database programmer
2 to insert record in every
table.

MUHAMMAD ZIYAD BIN FRONT-END DEVELOPER 2


AZHARI
 Insert most record in every
2019432096 table.

Confidential  CS1104C 2021 Page 10 of 18


MYTECC E-COMMERCE SYSTEM Version: 1.0.0
Final Report Date: <dd/mm/yyyy>
<person in charge>

4. Database and System Design

4.1 Entity Relationship Diagram

Confidential  CS1104C 2021 Page 11 of 18


MYTECC E-COMMERCE SYSTEM Version: 1.0.0
Final Report Date: <dd/mm/yyyy>
<person in charge>

4.2 Data Dictionary

Table Name users


No Attribute Datatype PK FK Lookup Table (If FK)
1 usersId INT (11) Y
2 usersName VARCHAR (128)
3 usersEmail VARCHAR (128)
4 usersUid VARCHAR (128)
5 usersPwd VARCHAR (128)
6 user_types INT (11) Y user_types

Table Name user_types


No Attribute Datatype PK FK Lookup Table (If FK)
1 type_id INT (11) Y
2 type_name VARCHAR (128)

Table Name usersContact


No Attribute Datatype PK FK Lookup Table (If FK)
1 usercontactid INT (11) Y
2 address1 VARCHAR (128)
3 postcode INT(11)
4 city VARCHAR (128)
5 phoneNum VARCHAR (128)
6 stateId INT(11) Y state
7 userId INT(11) Y users

Table Name state


No Attribute Datatype PK FK Lookup Table (If FK)
1 stateId INT (11) Y
2 stateName VARCHAR (128)

Table Name product


No Attribute Datatype PK FK Lookup Table (If FK)
1 productCode VARCHAR (128) Y
2 productName VARCHAR (128)
3 price DECIMAL (10,2)
4 productImg VARCHAR (128)
5 productDisc VARCHAR (128)
6 normalPrice DECIMAL (10,2)

Table Name order


No Attribute Datatype PK FK Lookup Table (If FK)
1 orderCode INT (11) Y
2 orderDate DATE
3 orderTime TIME
4 userId INT (11) Y users
5 statusId INT (11) Y status

Confidential  CS1104C 2021 Page 12 of 18


MYTECC E-COMMERCE SYSTEM Version: 1.0.0
Final Report Date: <dd/mm/yyyy>
<person in charge>

Table Name status


No Attribute Datatype PK FK Lookup Table (If FK)
1 statusId INT Y
2 statusName VARCHAR (20)

Table Name ord


No Attribute Datatype PK FK Lookup Table (If FK)
1 ordId INT (11) Y
2 orderCode VARCHAR (128) Y order
3 productCode VARCHAR (128) Y product
4 size TINY TEXT
5 quantity INT (11)

Table Name pwdreset


No Attribute Datatype PK FK Lookup Table (If FK)
1 pwdResetId INT (11) Y
2 pwdResetEmail TEXT
3 pwdResetSelector TEXT
4 pwdResetToken LONGTEXT
5 pwdResetExpires TEXT

Confidential  CS1104C 2021 Page 13 of 18


MYTECC E-COMMERCE SYSTEM Version: 1.0.0
Final Report Date: <dd/mm/yyyy>
<person in charge>

4.3 Data Flow Diagram


4.3.1 Context Diagram

Entity: Customer
Data: user details
Process: register new account
Description: The user is required to create new account before login to the system if they do not have
account yet.

Entity: Customer
Data: usersId, usersPwd
Process: login process
Description: The user is required to insert their username and password to login the system.

Entity: Customer
Data: update password
Description: The user can reset and set a new password if they forgot their old password.

Entity: Customer
Data: customer detail
Description: The customer can update their contact details before making order.

Entity: Customer
Data: list of product
Description: The customer can view all MYTECC's merchandise before they want to make order.

Entity: Customer
Data: order details
Description: The customer can make order of any MYTECC's merchandise.

Confidential  CS1104C 2021 Page 14 of 18


MYTECC E-COMMERCE SYSTEM Version: 1.0.0
Final Report Date: <dd/mm/yyyy>
<person in charge>

Entity: Customer
Data: edit customer order
Description: The costumer can edit/update their order before confirming the order.

Entity: Customer
Data: payment details
Process: Submit payment receipt
Description: The customer is required to submit a payment receipt for their order.

Entity: Customer
Data: order status
Description: The customer can check their order status from time to time (pending, processed,
delivered).

Entity: Administrator
Data: userId, usersPwd
Description: The admin is required to enter their username and password to login the system.

Entity: Administrator
Data: update password
Description: The admin can reset and set a new password if they forgot their old password.

Entity: Administrator
Data: list of users
Description: The user can display all of the user/customer and their details.

Entity: Administrator
Data: order details
Description: The admin can display selected order from the full order list to make a bulk order to the
merchandise vendor.

Entity: Administrator
Data: update order status
Description: The admin need to update the order progress whether it is pending, processing or delivered
so that customer can track their order status.

Entity: Administrator
Data: order status
Description: The admin can check all of order status to keep track with the order demand.

Confidential  CS1104C 2021 Page 15 of 18


MYTECC E-COMMERCE SYSTEM Version: 1.0.0
Final Report Date: <dd/mm/yyyy>
<person in charge>

4.3.2 Diagram-0

Entity: Customer
Data: user details
Process: register new account
Description: The user is required to create new account before login to the system if they do not have
account yet.

Entity: Customer
Data: usersId, usersPwd
Process: login process
Description: The user is required to insert their username and password to login the system.

Entity: Customer
Data: update password
Process: reset password
Description: The user can reset and set a new password if they forgot their old password.

Confidential  CS1104C 2021 Page 16 of 18


MYTECC E-COMMERCE SYSTEM Version: 1.0.0
Final Report Date: <dd/mm/yyyy>
<person in charge>

Entity: Customer
Data: customer detail
Process: update customer details
Description: The customer can update their contact details before making order.

Entity: Customer
Data: list of product
Process: display all MYTECC's merchandise
Description: The customer can view all MYTECC's merchandise before they want to make order.

Entity: Customer
Data: order details
Process: make an order
Description: The customer can make order of any MYTECC's merchandise.

Entity: Customer
Data: edit customer order
Process: edit/update order
Description: The costumer can edit/update their order before confirming the order.

Entity: Customer
Data: payment details
Process: Submit payment receipt
Description: The customer is required to submit a payment receipt for their order.

Entity: Customer
Data: order status
Process: display order status
Description: The customer can check their order status from time to time (pending, processed, delivered).

Entity: Administrator
Data: userId, usersPwd
Process: login process
Description: The admin is required to enter their username and password to login the system.

Entity: Administrator
Data: update password
Process: reset password
Description: The admin can reset and set a new password if they forgot their old password.

Entity: Administrator
Data: list of users
Process: display list of users
Description: The user can display all of the user/customer and their details.

Entity: Administrator
Data: order details
Process: display selected order details
Description: The admin can display selected order from the full order list to make a bulk order to the
merchandise vendor.

Confidential  CS1104C 2021 Page 17 of 18


MYTECC E-COMMERCE SYSTEM Version: 1.0.0
Final Report Date: <dd/mm/yyyy>
<person in charge>

Entity: Administrator
Data: update order status
Process: update order status
Description: The admin need to update the order progress whether it is pending, processing or delivered
so that customer can track their order status.

Entity: Administrator
Data: order status
Process: display order status
Description: The admin can check all of order status to keep track with the order demand.

5. Conclusion and Recommendation


5.1 Conclusion

The project we are running is to set up a business system for the MYTECC club. This project has fulfilled
the system’s objectives. This system makes it much easier for MYTECC to run their business because they
no longer need to store their data manually or on a paper. All data from registered customers will be
stored in this system securely and can protect customer information from being lost. This is because, the
probability of data stored in the system to be lost, is very low, compared to data stored manually.

Apart from that, the system has achieved its objectives in terms of saving time for MYTECC members, as
well as customers. Customers no longer need to meet with MYTECC members to make the purchase, they
just need to place orders for the items they want directly on the system that we provide. As a result,
customers and MYTECC members can save a lot of time because they can place any orders anywhere and
anytime.

5.2 Recommendation

There are a few features that we will add more in this system in the future. For example, customers can
make payments directly into the system as we will be adding payment gateway API features. Not only that,
but we also plan to make this system, the official website for MYTECC in the future. On the website, we
will put all the information related to computer science students, so that users are always up to date with
the important matters or important dates.

Furthermore, we also intend to update the user interface to make it more user-friendly and enhance the
system in the form of a mobile interface. Users will be able to access our website more easily using only
their smartphones as a function of this. In addition, we will add capabilities in the future that allow users
to update their profile picture in this system. These features will optimize the system and increase
customer interest in visiting our website.

Last but not least, administrators will be able to sort orders based on date, time, customers name,
semester, and so on. This will further make it easier for the administrator to find any orders with these
features in this system. Administrator can also save their time to find the order they are looking for.

Confidential  CS1104C 2021 Page 18 of 18

You might also like