Professional Documents
Culture Documents
Final Report
Version 1.0
GROUP: CS1104C
Revision History
Date Version Description Author
<dd/mm/yyyy> <x.x> <reason to change the documentation <name>
contents>
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
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
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
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.
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.
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
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.
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.
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.
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.
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.
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.