VIETNAM NATIONAL UNIVERSITY HO CHI MINH CITY

UNIVERSITY OF INFORMATION TECHNOLOGY

FACULTY OF INFORMATION SYSTEMS

FINAL PROJECT

TOPIC: ORGANIC FOOD B2C

WEBSITE PROJECT
Instructor: Trinh Trong Tin
Group 5:

• Nguyen Le Khoa – 18520925

• Ta Thi Kim Binh – 18520510
• Trieu Kim Ngan – 18521137
• Truong Thi Ngoc Linh – 18521000
• Nguyen Tuan Anh – 18520465

HO CHI MINH CITY - 2021

 INSTRUCTOR’S ASSESSMENT

………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………
………………………………………………………………………………………

1 Group 5 – System Analysis And Design

 THANK YOU
First of all, we would like to express our sincere thanks to all the teachers
University of Information Technology - Vietnam National University, Ho Chi
Minh City and faculty members.

The information system has helped us to have the basic knowledge as a foundation
to do this topic. In particular, the authors would like to express their deepest
gratitude and gratitude to the teacher who taught us over the semester, said Trinh
In Tin, a lecturer in System Analysis And Design. The teacher directly guided
enthusiastically, corrected and contributed many ideas valuable comments to help
the authors complete their subject reports as well.

During one semester of project implementation, the authors have applied the
background knowledge that has been accumulated and combined with the study
and study of new knowledge. From there, the authors make the most of what they
have collected to complete the work into a best project report. However, in the
process of implementation, the team of authors of donors is unavoidable.
Therefore, the author team is looking forward to receiving the suggestions from the
teacher to improve the knowledge that the author group has learned practice and is
a luggage for the group of authors to carry out other topics in the future.

Sincerely thank you from the bottom of my heart!

Group 5 – CTTT2018

2 Group 5 – System Analysis And Design

 TABLE OF CONTENTS

I. INTRODUCTION…………………………………………………..…5
1. Business Profile……………………………………………………..5
1.1. Business Situation……………………………………..5
1.2. Business Observations…………………………………5
1.3. Purpose…………………………………………………6
1.4. Software Objectives……………………………………6
1.5. Work Breakdown Table………………………………..7
2. Organizational Model……………………………………………….9
3. Project Survey……………………………………………………...10
II. REQUIREMENT SPECIFICATION………………………………..11
1. Functional Requirements………………………………………11
1.1. List of Use Cases………………………………………12
1.2. Overview of Use Case…………………………………13
1.2.1. Case Diagram for Sign in…………………………….14
1.2.2. Use Case Diagram for Manage Account……………..16
1.2.3. Use Case Diagram for Manage Product……………...18
1.2.4. Use Case Diagram for Manage Customer……………20
1.2.5. Use Case Diagram for Manage Order………………..22
1.2.6. Use Case Diagram for Report Statistics……………...24
1.2.7. Use Case Diagram for Search Products………………26
1.2.8. Use Case Diagram for Manage Blog…………………28
2. Non-Functional Requirements…………………………………30
2.1. Product Requirement………………………………...30
2.2. Organizational Requirement…………………………..30

3 Group 5 – System Analysis And Design

 2.3. Convenience Requirements……………………………30
2.4. Compatibility Requirements…………………………...31
2.5. Safety Requirements…………………………………...31
2.6. Security Requirements…………………………………31
III. DESIGN SPECIFICATION…………………………………...……..31
1. Business Process…………………………………………….31
2. Entity Relationship Diagram………………………………34
2.1. List of Table………………………………………….34
2.2. Orderdetail Table………………………………….….35
2.3. Transaction Table………………………………. …....35
2.4. Customer Table…………………………………….…37
2.5. User Table………………………………………….…36
2.6. Supplier Table…………………………………...……37
2.7. Product Table…………………………………………37
2.8. Category Table…………………………………….….38
2.9. Blog Table…………………………………………….39
2.10. Delivery Table……………………………………...…39
IV. USER INTERFACES…………………………………………..……...41
V. SUMMARY……………………………………………………..……..48
VI. REFERENCES……………………………………………………..….49

4 Group 5 – System Analysis And Design

 A. INTRODUCTION
1. Business Profile
1.1 Business situation

• Because Vietnam's population is growing, people are becoming increasingly

interested in food supply, particularly clean and organic food. What exactly is
clean, organic food? Clean food is food that is free of "dirt". Dirt is defined as
anything that can or may be damaging to one's health, such as dangerous
chemicals from pesticides, heavy metal ions from soil and water, or just dirt
from the environment. Contamination of food during food production and
distribution.
• However, with a dynamic working environment along with the development
of society and information technology, buying goods without having to move
out of the store is also an essential need of customers. Online shopping is an
extremely suitable option for customers, they do not have to work hard for
driving, traffic jams, unfinished work. They can easily order anywhere, and
someone will deliver to the place they want.
• How to manage and operate a website, an online store in the most effective
and simple way? Issues such as purchase orders, inventory, import and export,
customer service. Therefore, when building a website, we need to ensure that
managers, employees as well as customers can easily use it and must ensure
the decentralization of the website.

1.2 Business Observations

• The Ogani store provides hygienic food to consumers around the country,
but because to the impact of the Covid-19 outbreak, it is unable to pay cash
as well as sales employees. As a result, Ogani has shifted to online purchasing

5 Group 5 – System Analysis And Design

 and selling by creating a website. Reduce costs for premises, the direct sales
staff at the store, bring convenience to customers in the buying process
without having to go directly to the store and some related issues.

1.3 Purpose

• The Organi Website provides clean food Oganic provides customer service,
care, management solutions.
• Help customers get more information about the store's products.
• The Organi Website is designed to support faster and more efficient service
than traditional methods.
• Help increase store revenue and profit, reduce management and reduce
business costs.
• Accurate order information, easy to look up customer information as well as
orders.

1.4 Software Objectives

• Business management.
• Product Management.
• Post management.
• Bill management.
• Account login.

6 Group 5 – System Analysis And Design

1.5 Work Breakdown Table

Member name Student ID Task

Tạ Thị Kim Bình 18520510 • Division of work

• Make a report 60%

• Database design

• Back-end

Triệu Kim Ngân 18521137 • Front-end

• Draw BMPN

• Content in Report

Trương Thị Ngọc Linh 18521000 • Back-end

• Tester

Nguyễn Lê Khoa 18520925 • UI-UX

• Front-end

• Usecase

• Make a report 40%

7 Group 5 – System Analysis And Design

Nguyễn Tuấn Anh 18520465 • Front-end

• Draw Business model

8 Group 5 – System Analysis And Design

2. Organization model

9 Group 5 – System Analysis And Design

3. Project survey
Competitors Pros Cons

CleverFood • Famous brand • Management of the

• Building a model of online system is not
selling online mainly and strict.
for a long time. Because it only sells
Website of CleverFood have online, there are many
many functions, easy and nice problems in purchasing.
interface.
VOrganic • Famous brand. • Management of the
• Sell both models online online system is not
and in store. strict.
• VOrganic is both a • The website has
supplier and seller. many limitations
VOrganic ell mainly in store. • The interface is not
user-friendly.

HomeFood • Famous brand.

• Sell both models online
and in store.
• HomeFood thrive both
models online and in
store.
• HomeFood have big
warehouse.

10 Group 5 – System Analysis And Design

 II. REQUIREMENT SPECIFICATION
1. Functional requirements
1.1 List of Use Cases
• Use Case diagram for the whole system.
The general use case diagram includes two actors, the customer and the system
administrator.
The system administrator (admin) performs the following tasks in the system:
o Account Management: Change Password, Retrieve Password, Create A
New Password.
o Product Management: Add New Items, Edit and Update, Delete, Search,
Filter Products.
o Customer Management: Check Customer Account’s List, Delete, Search.
o Supplier Management: Add, Delete, Edit, Search.
o Order Management: Check Invoice, Approve Invoice, Search Invoice, Handle
Canceled Invoices.
o Statistical Reports: Product Statistics, The Order Statistics, Revenue
Statistics, Inventory Statistics.
o Blog Management: Check and Approve New Customers Blog, Add, Delete,
Edit, Search.
Customers when interacting with the website selling organic foods can do the
following tasks:
o Register as a member.
o Sign in.
o Search Products.
o Order Online.
o Cart Management
o Send requested information to the store.

11 Group 5 – System Analysis And Design

 o Make online payments.
o Review for Products
o Read Blogs
Guests when interacting with the website selling organic foods can do the
following tasks:
o Search Products.
o View Products detail
o Add to Cart
o Checkout

12 Group 5 – System Analysis And Design

1.2 Overview of Use Case

13 Group 5 – System Analysis And Design

1.2.1 Use Case Diagram for Sign in

Image 1.2.1. Use Case Diagram for Sign in

Description Table for Sign in
Use Case Sign in
Name

Description Allows users to sign in to the system

Factor User

Pre-conditions User must create a successful account before

Factor Feedback system

Main event
1 Access the
stream
website

2 Bring up the login interface

3 Enter
information

14 Group 5 – System Analysis And Design

 4 Press Sign in
button

5 The system confirms the information sent

to the checking server:

+ Valid: Display a success message and

display the function screen to the user.

Alternative + Invalid: Issue a notice, request to re-

stream enter information.

Result Successfully logged into the system.

15 Group 5 – System Analysis And Design

1.2.2 Use Case Diagram for Manage Account

Image 1.2.2. Use Case Diagram for Manage Account

Description Table for Manage Account

Use Case Manage Account

name

Description Allows users to change password, recover password when

forgotten or create another new account (for Administrator).

Factor Administrator

Pre- The admin has successfully logged into the system and chosen the
conditions Manage Account function.

16 Group 5 – System Analysis And Design

 Factor Feedback System
Main event
1 The admin chooses
stream
to go to the account
he wants:

1. Edit

2. Delete

2 1. Show a page with enough

information about the selected
account with username (not
edited)
2. Show account deletion message

3 Fill contents want

to replace and click
finish.

4 Bring up the list screen with the

account content that has just been
manipulated.

Alternative
stream

Result

17 Group 5 – System Analysis And Design

1.2.3 Use Case Diagram for Manage Product

Image 1.2.3. Use Case Diagram for Manage Product

Description Table for Manage Product
Use Case name Manage Product

Description Allows users to view, add, edit, delete, search for product
information in the system.

Factor Administrator

Pre-conditions The admin has successfully logged into the system and
selected the Manage Product function.

Main event stream:

18 Group 5 – System Analysis And Design

The admin chooses the type of impact: Add, edit, delete, search for product
information.

+Add product information: Select more products, the system displays the product
information input interface and product list, the user enters product information,
if successful, the system gives a message, if it is wrong Show alternate flow A1,
save information to product list.

+ Edit product information: The system displays a list of products, select the
product to be corrected, enters the information that needs to be changed, if the
information is changed successfully, the system will issue a message. Show
branch line A1, store product list information.
+ Delete product information: The system displays a list of products, selects the
products to be deleted, the system displays a message that the user is sure to
delete, the user chooses to delete, the system deletes the data in the database and
returns it. deleted list deleted order.
+ Search product: Enter the search information in the search box in the list, the
system will display the searchable list.
Alternative A1: The system notices that the input is invalid, re-enters the
stream information, and returns to the main event stream again.

Result The product information is updated in the database and

displayed on the listing page.

19 Group 5 – System Analysis And Design

1.2.4 Use Case Diagram for Manage Customer

Image 1.2.4. Use Case Diagram for Manage Customer

Description Table for Manage Customer
Use Case name Manage Customer

Description Allows users to view, delete and search customer’s

information in the system.

Factor Administrator

Pre-conditions The admin has successfully logged into the system and
selected the Manage Customer function.

Main event stream:

The admin chooses the type of impact: Add, search for customer information

20 Group 5 – System Analysis And Design

+ View customer list: The user selects the customer list item, the system retrieves
data in the database and displays it on the list screen.
+ Delete customer information: The system displays a list of customers, selects
customers to delete, the system displays a message that the user is sure to delete,
the user chooses to delete, the system deletes data in the database and returns it.
deleted list deleted order.
+ Search for customers: Enter search information into the search box in the list,
the system will display a searchable list.

Alternative + The search box is empty, the system requires the user to
stream enter content before searching.

Result +The customer information is updated in the database and

displayed on the listing page.

21 Group 5 – System Analysis And Design

1.2.5 Use Case Diagram for Manage Order

Image 1.2.5. Use Case Diagram for Manage Order

Description Table for Manage Order
Use Case name Manage Order

Description Allows users to view, approve, search, handle canceled

invoices.

Factor Administrator

Pre-conditions The admin has successfully logged into the system and
selected the Manage Order function.

Main stream event:

The admin chooses the type of impact: allows view, approve, search,
canceled invoices.

22 Group 5 – System Analysis And Design

 + Check Invoices: the manager comes to, selects the order he wants to see the
details on the list, the system displays the order details.

+ Approve Invoices: new, unapproved orders are displayed and required to

be processed, the manager views order details, selects order approval, the
system recognizes the impact, puts the order in the approved and standardized
list gone

+Search Invoices: enter search information into the search box in the list, the
system will display a searchable list.

+ Handle Canceled Invoices:

• The customer's order has been canceled showing the order

cancellation confirmation message, the manager views the
information and accepts the order cancellation.
• Customer orders contact the bookstore and ask to cancel, the manager
views the order details, if the order has not been delivered to the
shipping unit, the manager chooses to cancel the order, the system
records and moves to the cancellation list, and refunded if paid.
• If the order has been delivered to the carrier, the manager informs the
customer that the order cannot be canceled.
Alternative stream

Result The order information is updated in the database and

displayed on the listing page.

23 Group 5 – System Analysis And Design

1.2.6 Use Case Diagram for Report Statistics

Image 1.2.6. Use Case Diagram for Report Statistics

Description Table for Report Statistics
Use Case name Report Statistics

Description Allows user to the product statistics, order statistics, revenue

statistics, inventory statistics

Factor Administrator

Pre-conditions The admin has successfully logged into the system and selected
the Report Statistics function.

Main stream event:

24 Group 5 – System Analysis And Design

 + The a chooses the statistical reporting function.

+ The system asks to select the information to be statistics.

+ The manager selects the information and clicks OK.

+ The system searches in the database and displays the results on the screen.
Alternative
stream

Result The order information is updated in the database and

displayed on the listing page.

25 Group 5 – System Analysis And Design

1.2.7 Use Case Diagram for Search Products

Image 1.2.7. Use Case Diagram for Search Products

Description Table for Search Products
Use Case name Search Products

Description Allows users to search for products by product name, supplier

name, genre, author name.

Factor Administrator, Customer

26 Group 5 – System Analysis And Design

Pre-conditions No

Main event stream:

+ Users enter what they want to search for

+ The system searches the database and gives the results.

Alternative Content to search for is empty.

stream

Result The information is taken from the database and displayed on

the screen.

27 Group 5 – System Analysis And Design

1.2.8 Use Case Diagram for Manage Blog

Image 1.2.8. Use Case Diagram for Manage Blog

Description Table for Manage Blog
Use Case name Manage Blog

Description Allows users to check new customers blog, approve it, add
new blog, edit, delete

Factor Administrator

Pre-conditions The admin has successfully logged into the system and
selected the Blog function.

Main event stream:

28 Group 5 – System Analysis And Design

 The admin chooses the type of impact: Allows View and Approve New
Customers Blog, Search, Edit, Add, Delete Blogs

+ Check new customer's blog: the manager comes to, selects new articles that
he wants to see details on the list, the system displays order details.

+ Approve New Customers Blog: new, unapproved blogs are displayed and
required to be processed, the manager views the details of the article, selects
to browse the article, the system recognizes the impact, puts the article in the
list Reviewed and prepared to post on the Blog site.

+ Add Blogs: select add article, the system displays the interface to enter a
new article, the user writes a new article, then selects to complete, if
successful, the system gives a notification.

+ Edit Blogs: the system displays a list of articles shown by a table, select the
article to edit, enter the information to be changed.

+ Delete Blogs: the system displays a list of articles shown by a table, selects
the articles to be deleted, the system displays a message that the user is sure
to delete, the user chooses to delete, the system deletes data in the database
and returns the list. deleted books order deleted.

Alternative stream

Result The information is taken from the database and displayed

on the screen.

29 Group 5 – System Analysis And Design

2. Non-Functional Requirements
2.1 Product Requirements

• Use in the environment: Windows 7 or higher operating system. Minimum

configuration CPU Core i5-6200U, 2.3 GHz, RAM 4GB. Save time: lookup
no more than 10 seconds, update data quickly no more than 5 seconds, report
summary no more than 20 seconds.
• High reliability: results accurate and complete.

2.2 Organization Requirements.

• Install: MySQL for data management. Microsoft Visual Studio is used to build
programs.
• Font: Use a uniform font in all computers working with the system.
• Professional requirements.
• Can satisfy the requirements set out.
• Check regulations and record, save data to the database.
• Find and export relevant information.
• Allows updating or canceling records.
• Allows to change regulation and related parameters.

2.3 Convenience Requirements.

• Allows admin to master the operation in just 10 minutes of instruction.

• The average congestion rate is 3%.
• Intuitive interface, easy to use.

2.4 Compatibility Requirements.

30 Group 5 – System Analysis And Design

 • Ensure synchronization between users. Compatible with all electronic devices
have a network connection.

2.5 Safety Requirements.

• Confirm before deleting records as required.

• Allow cancel the lake really did not need.

2.6 Security Requirements.

• Record and strictly comply with pre-determined powers.

• All user information, customer information must be kept confidential, only
authorized people can see and affect.

III. DESIGN SPECIFICATION

1. Business Process

Image 1.11 Business Process Modeling Notation Buying Products

Management

31 Group 5 – System Analysis And Design

 Description Table for BPMN

No Implement object Action Explain

1 Customer Search for products to Customers type the

buy name of the product
they are looking for in
the search bar
2 Customer Search for products to After typing the product
buy on the display name, the website will
page display information
related to the product to
be searched.
3 Customer Conduct purchases Customers will make a
purchase, if they buy,
they will continue to do
the next steps,
otherwise leave the
page.
4 Customer Place an order (add to Before adding the
cart) product to the cart, the
customer will check the
product and information
related to the product to
buy
5 Website Check the product Website will
automatically check for
strange products in

32 Group 5 – System Analysis And Design

 stock. If you want to go
to the delivery stage,
otherwise notify the
customer
6 Website Carry out the delivery Customer provides
information for delivery
7 Customer Payment Customers need to
choose a payment
method before
completing the order

33 Group 5 – System Analysis And Design

 2. Entity Relationship Diagram

Image 1.12. Database Model

2.1.List of Table
Table name Content
Orderdetail Storage detail information of order
Transaction Storage information of order
Customer Storage information of customer
User Storage information of user
Delivery Storage information of shipment
Producer Storage information of producer
Product Storage information of product
Category Storage information of category
Review Storage information of review

34 Group 5 – System Analysis And Design

Blog Storage information of blog
Delivery Storage information of shipment

2.2. Orderdetail Table

No Properties Datatype Constraint Note
1 OrderdetailID Int(11) PK
2 TransactionID Int(11) FK
3 ProductID Int(11) FK
4 UserID Int(11) FK
5 DeliveryID Int(11) FK
6 Amount Int(1) Allow null
7 Price Float Allow null
8 Status Int(11) Allow null
9 Trash Int(11) Allow null

2.3. Transaction Table

No Properties Datatype Constraint Note
1 TransactionID Int(11) PK
2 CustomerID Int(11) FK
3 Note Text Allow null
4 Orderdate Datetime Allow null
5 CustomerName Varchar(50) Allow null
6 Phonenum Int(10) Allow null
7 Email Varchar(50) Allow null
8 Money Float Allow null
9 Coupon Float Allow null

35 Group 5 – System Analysis And Design

 10 ShippingFee Float Allow null
11 Sumpay Float Allow null
12 Payment Varchar(32) Allow null
13 Address Varchar(32) Allow null
14 Status Int(1) Allow null
15 Trash Int(1) Allow null

2.3. Customer Table

No Properties Datatype Constraint Note
1 Customer_ID Int(11) PK
2 UserID Int(11) FK
3 CustomerName Varchar(50) Allow null
4 Email Varchar(50) Allow null
5 Password Varchar(20) Allow null
6 Phonenum Int(10) Allow null
7 Address Varchar(50) Allow null
8 Order_date Datetime Allow null
10 Date_update Datetime Allow null
11 Date_at Datetime Allow null
12 Status Int(1) Allow null
13 Trash Int(1) Allow null

2.4. User Table

No Properties Datatype Constraint Note
1 UserID Int(11) PK
2 UserName Varchar(50) Allow null

36 Group 5 – System Analysis And Design

 3 Password Varchar(20) Allow null

2.5. Supplier Table

No Properties Datatype Constraint Note

1 SupplierID Int(11) PK
2 UserID Int(11) FK
3 SupplierName Varchar(100) Allow null
4 Code Varchar(100) Allow null
5 Address Varchar(50) Allow null
6 Email Varchar(50) Allow null
7 Created_at Datetime Allow null
8 Modified Datetime Allow null
9 Status Int(1) Allow null
10 Trash Int(1) Allow null

2.6. Product Table

No Properties Datatype Constraint Note

1 ProductID Int(11) PK
2 CategoryID Int(11) FK
3 SupplierID Int(11) FK
4 UserID Int(11) FK
5 ProductName Varchar(100) Allow null
6 Image Varchar(255) Allow null
7 Sortdesc Text Allow null
8 Info Text Allow null

37 Group 5 – System Analysis And Design

 9 Origin Varchar(255) Allow null
10 Number_buy Int(11) Allow null
11 Amount Int(11) Allow null
12 Coupon Float Allow null
13 Price Float Allow null
14 Weight Float Allow null
15 Expiry_date Datetime Allow null
16 Status Int(1) Allow null
17 Trash Int(1) Allow null
18 Created_at Datetime Allow null
19 Modified Datetime Allow null

2.7. Category Table

No Properties Datatype Constraint Note

1 CategoryID Int(11) PK
2 CategoryName Varchar(100) Allow null
3 Order Varchar(255) Allow null
4 Image Varchar(255) Allow null
5 Created_at Datetime Allow null
6 Update_at Varchar(255) Allow null
7 Status Int(1) Allow null
8 Trash Int(1) Allow null

2.8.Review Table
No Properties Datatype Constraint Note
1 ReviewID Int(11) PK

38 Group 5 – System Analysis And Design

 2 ProductID Int(11) FK
3 Content Text Allow null
4 Rate Int(10) Allow null
5 Update_at Varchar(255) Allow null
6 Created_at datetime Allow null
7 Status Int(1) Allow null
8 Trash Int(1) Allow null

2.9. Blog Table

No Properties Datatype Constraint Note

1 BlogID Int(11) PK
2 UserID Int(11) FK
3 Title Varchar(100) Allow null
4 Image Varchar(255) Allow null
5 ViewCount Int(11) Allow null
6 Desc Text Allow null
7 Meta_tilte Varchar(255) Allow null
8 Status Int(1) Allow null
9 Trash Int(1) Allow null
10 Created_at Datetime Allow null
11 Update_at Varchar(255) Allow null
12 Modified Datetime Allow null

39 Group 5 – System Analysis And Design

2.10. Delivery Table
No Properties Datatype Constraint Note
1 DeliveryID Int(11) PK
2 ServiceName Varchar(50) Allow null
3 Weight Float Allow null
4 ShippingFee Float Allow null
5 Estimatedate Datetime Allow null
6 Coupon Float Allow null

40 Group 5 – System Analysis And Design

 IV. USER INTERFACES

Image 1.13. Organi’s Home Interface

41 Group 5 – System Analysis And Design

Image 1.14. Login Interface

42 Group 5 – System Analysis And Design

Image 1.15. List Of Products Interface

43 Group 5 – System Analysis And Design

Image 1.16. Add To Cart Interface

44 Group 5 – System Analysis And Design

 Image 1.17. Order Products Interface

Image 1.18. Manage Product Of Admin Interface

45 Group 5 – System Analysis And Design

Image 1.19. Manage Customer Of Admin Interface

Image 1.20. Write Blog Of Admin Interface

46 Group 5 – System Analysis And Design

 Image 1.21. Manage Blog Of Admin Interface

Image 1.22. Manage Order Detail Of Admin Interface

47 Group 5 – System Analysis And Design

 Image 1.23. Manage Transaction Of Admin Interface

V. SUMMARY

• Reason for project development

o A construction project to meet the increasing customer demand in the sector
of sales.
o Assisting retail businessoperations in becoming more convenient.
• The results have been achieved
o The project has been finished and placed into operation in accordance with
the objectives.
o Will initially satisfy customer sales goals before expanding into more
diverse regions.
o Provide basic customer needs.
o Through the project implementation, the project members draw more
experience for themselves such as team work experience, useful knowledge,
the ability to self-study and team work professionally there is a process.
5.1 Experiences
o Project managers will better manage existing human resources.
o Need to have elements to encourage the working spirit of the members even
more.

48 Group 5 – System Analysis And Design

 o Not fully promote the capabilities of the project members, enhance the sense
of responsibility of the members.
o Allocating the number of jobs for members to work without excessive
pressure.
5.2 Conclusion
o Achievements: The project has completed 80% with enthusiastic support and
attitude.

o Evaluation of project results: The project has successfully completed despite

many difficulties in the first time. But with the determination of enthusiastic
work of teammembers, it will help the project to bring about good results.

VI. REFERENCE
6.1. Books
o System Analysis and Design – Selly Cashman Series, 9th
Edition.
o Kenthene Systems Analysis and Design – 2011.
6.2. Tools
o Draw BPMN: Camunda Modeler
o Draw Use Case: Draw.io
o Design UI: Adobe XD

49 Group 5 – System Analysis And Design

THE END

50 Group 5 – System Analysis And Design