System design for JollyChic (online ordering system)

CIT 460 - System Analysis and Design Project – Section 002
College of Technological Innovation
JollyChic.com ordering system
Ordering System Project
Group Member:
Khawla Alnuaimi 201305282
Raudah Salem 201313463
Alreem AlAmeri U2915237
Fatima Yousif 201307886
Instructor: Dr.Sinan Salman

Introduction:
Jollychic.com is an online shopping website where you can find affordable,
numerous fashion cloths and accessories for instants, shoes, bags, clothes,
toys, electronica accessories, home decoration and essentials…etc. Jollychin
collaborate with different companies, warehousing, logistic companies and the
after sales products providers so you can get the best price! Moreover, they
offer a fast shipment worldwide and 24/7 customer service. The aim of the
whole project is to improve, improve the online ordering system for
Jollychic.com to have a better business and to manage their data effectively
and efficiently. The system we are going to develop and produce is going to
facilitate the customer shopping process and will result in increasing the
organization profit.
Businesscase:
Business Profile:
Vision & Mission:
“Alongside the designs & innovations, we intend to present premium
commodities originated from the best Chinese factories, to the rest of the
world with a decent price.”
Strategy:
JollyChic's strategy is to provide their customers with the best Chinese
products by offering the latest fashion for those who are interested, along with
the opportunity of business collaboration to maximize their business potentials
with customers around the world. In fact, JollyChic aims to be one of the best
companies that offer its customers the best competitive prices. Also, their
products are not going to be sold to specific countries, but to every country
around the world. For instance JollyChic aims to expand overseas, and to be
known around the world.By providing the customers with the best service,

quality, price to build the best relationship and trust with their customers and
partnership, they can expand, improve, and even become a better company
with increased loyal customers.
So, our strategy aims to improve some of Jollychic's main problems. for
example, many items have outdated pictures. In fact, most of the pictures
posted about the products that are being sold are expired. Therefore, out goal
is to create a design that will help the ordering system to check the availability
of the items, then update the pictures and information of the items. Hence, the
ordering system of JollyChic is going to be better, easier, and attracting for
loyal and more customers.
Functions:
The main objective of JollyChic is to make original Chinese products that will
meet the customer’s requirements as well as expand their relations with their
business partners and future business potentials. Various popular fashion
brands are available at reasonable prices. Users can register firstly on the
website. After they log in, they can add the items in the shopping cart. Then
they can check out and submit the order. After they paid for the order, it has
been placed successfully. Also here is a link for video showing by steps about
“how to order”: http://www.jollychic.com/special-howToOrder20140730-
index.html.
Products and Services:
JollyChic works on providing both individual costumers and businesses with
the latest trends and offers a catalog with different popular fashion items from
the fashion industry. It also has an online customer service that is available at
all time during the week. JollyChic’s products are supplied from the best
factories in China to introduce the world to original products.
Constraints:
The products are limited to Chinese originated items only. JollyChic cannot

make any change to the order after it has been confirmed, so it justifies that
there system is lacking something that can not control the order after it has
been chosen and confirmed for delivery.
Future directions:
To be the best online store in the world, and to exceed JollyChic’s yearly
record of 2 million customers. JollyChic has no plans of opening branches and
will remain as an online store.
SWOT analysis:

Problem statement:
The main problem is the Inefficient system and their lack of product
authenticity. JollyChic has mixtures of unique products, however the
description of their products is not satisfying and the expectation of their
website does not meet the requirements which means there is something
wrong with the system. Moreover, there is a problem with the customer
service because they do not change the order or contact supplier in case of
problem occurring. The display image of the products is sometimes expired
and shows sizes and colors different than what the description shows. As the
market competition grows, the customer’s attention will be distracted by better
and more efficient online stores such as: Namshi, and souq.com, because
what JollyChic lacks, other dominating online stores such as Amazon make
up for it. Therefore, it is very important to achieve their information system
requirements while keeping in mind the customer's needs so they can
improve and compete with other websites, companies, or more specifically the
online market.

FishboneDiagram:
Feasibility study:
Operational feasibility:
Operational feasibility will quantify how well the system supports the customer
satisfaction throughout the operation phase and how efficient the system is
after the implementation. The redesign of the system will benefit the
customers they would like to deal with it because it is accurate and easy to
find what they need. In JollyChic the system will be designed to improve

accuracy of the website, so that it will be more professional as well as it will
gain customers trust.
Technical feasibility:
JollyChic's new system update aims to deal with all the issues faced in the old
one, and find the errors to improve it. The analyst is the one who is going to
catch up with the new system to check for any errors and to make sure the
system is performing in its best way. Also it will make this system suitable,
scalable and reliable for the future.
Economic feasibility:
Economic feasibility helps to evaluate the efficiency of the new JollyChic
system if it will maximize the benefits or not. As well as measuring the
processes, cost saving and incomes analysis. For example, JollyChic system
should estimate the cost for IT staff, hardware, and software. Therefore, this
feasibility will achieve both of tangible and intangible benefits. Hence, the
system will ensure to increase the profits with providing the best operational
impacts for customers and enhancing customers satisfaction.
Schedule:
Schedule feasibility will compute the needed time to finish and apply the new
system and the management will determine if the project due time is suitable
or not. In addition, JollyChic needs to plan with their suppliers to avoid any
risks that you may encounter the project. This project should be completed
within one year to promote the system and train the employees and
customers to use it.
Recommendation to management:
The aim of the new project is to increase the performance and maintenance of
the data. We will recommend following and going through the feasibility study
to reduce errors and think about the project in different fields. First, to have an
efficient system, we need to carefully understand, identify what we need, what

are the issues and what are the solutions. Therefore, they can make the right
decision and have a better system.
System Requirements:
Business requirements:
o The system will help the business be stable because of the
disaster recovery plan.
o The system will make it easier for the employees to take shifts in
the business.
o The system will support offline access for the employees.
o The system will have other systems linked to it from other
organizations for better success.
o The system will make the business become the best around the
world
o The system will have a member dictionary for each employee to
increase awareness.
o The system will provide posters showing the employees how
customers come first.
o The system will make the business focus on fulfilling its
objectives successfully, and efficiently.
o The system is going to make the business secure, and free from
errors as much as possible.
o The system will improve the business, and help it expand.
User requirements:
o The system will verify the user's information.
o The system will store user's information in a database.
o The system will recommend products for the user based on
what was placed in the cart.
o The system will help the user find what he needs or seeks.
o The system will have everything clear and concise for the user.
o The system will make the user be able to share feedback.

o The system will allow the user to share his/her experiences with
others.
o The system is going to provide the user with clothing
measurements to fit the user perfectly.
Functional Requirements:
o The system should allow customers to change or add
requirements to the order.
o The system should be connected to the Chinese factories in
case of unavailability of product items.
o The system should be up to date and with new descriptions and
pictures
o The system should be up to date, the information on the website
should be accurate and meets their capabilities.
o The system should require more than two pictures for the
product, to give customers an all angle view of it.
o The system should be able to eliminate any product that is out of
stock.
o The system should be clear of duplicated items.
o The system should have product checkpoint before the product
becomes a real item that is sold in the website.
Non-Functional Requirements:
o The operations of the system should have a quick response and
best performance.
o The system should be finished within a year.
o The system must achieve the desired maximum benefit from it.
o All data must be protected from any unauthorized access.
o The system should have a backup option.
o The operations must be done by the user faster than before.
o The ratio of errors and crashes in the system must be low.
o It should be easy to use the new system.

o The system should be capable to work on all Internet browsers.
o The IT staff should be able to maintain the system and update it
to deal with increasing number of users.
o Commitment on time for the arrival of product to the consumer's
hands.
o The system should be usable for all customers around the
world.
o The system should facilitate the maintenance processes in the
future as well.
o The employees should be adapted to new working environment.
Use case diagram:
This is the use case diagram along with the description for each use case to
have the big picture of how Jollychic’s ordering system works when a
customer places an order. This diagram is used to see how the actors
collaborate with each other and the system by taking certain actions when a
customer places an order. There are many features for this diagram like the
actors which includes the Supplier, the Salesman, the Driver, and the
Customer. The actions that are happening in this use case diagram are
placing the order, checking items availability, confirming the order, preparing
the invoice, applying the payment, and delivering the product.

Use case: JollyChic Order System:

Data flow Diagrams (DFD's):
The following Data flow charts will explain the ordering process system in
JollyChic, as well as illustrate the necessary inputs and outputs to run the
process. This part explains the system and how it works, t consists of a
context Diagram, Diagram 0, Diagram 1, Diagram 2, Diagram3 and Diagram
4.
ContextDiagram:
- In this context diagram it describes the ordering system of JollyChic and how
does it work by interacting with the salesman, delivery, supplier, bank, and
most importantly the customer. This is the big picture of what occurs when a
customer places an order in JollyChic order system, and how JollyChic
responds to it by interacting with other entities.

Diagram level0:
- In diagram 0 it describes what is happening within JollyChic ordering
system, and how it works with so many process right after a customer places
an order. However, this diagram was created after breaking JollyChic ordering
system into small processes that interacts with each other to process the
customer’s request by preparing the order, checking the stock for the item that
was requested so if it is available the customer is asked to pay, and then the
system proceeds to the delivery service, and deliver the item/product to the
customer.

Diagram level1:
- Diagram level 1 explains what is happening in the first process that took
place in Diagram level 0, which is preparing the order, or in other words how
the system supposed to respond when the order is placed, and prepared for
the customer. Hence, when the customer places an order in JollyChic, the
system starts to verify the order by checking if the order is available or not so
a decision is made whether the order should be accepted or rejected. By
accepting the order, the order will be collected from the supplier after the
supplier is informed by the inventory update. On the other hand, if the order
was not available it will be rejected and the customer will be notified.

Diagram level2:
- In diagram level 2 we broke “Check Stock” process that took place in
Diagram level 0 to two processes which are “Checking availability” and
“Confirm order”. Simply, this diagram explains how the ordering system
responds when the customer places the order, and the item should be
checked whether it is available or not, and by that the supplier is notified by
the request to check availability, so if the product is available the supplier is
going to agree on the product, and management system is notified. Hence,
the order confirmation continues until the product is sold and the inventory is
updated with the information.

Diagram level3:
- Diagram level 3 explains what happens in the process number “3” in
Diagram level 0 which is known to be “Apply payment”. Basically, the
processes was exploded into “3” more processes that takes place when the
customer is applying the payment. So, when the customer pays for the
product the system deposits the money from the bank after the payment
method is verified. Hence, when the payment process takes place, the system
prepares the transaction by sending payment info to “account receivable” data
store, and prepares the invoice where the sales department sends the
payment report to the system and the customer is notified.

Data Dictionary:
Data dictionary is a central storehouse of information of JollyChic's system. It
organizes and describes all the data in data flow diagram. The following
tables illustrate different type of data such as data elements, records, data
flows, data stores, processes, and the external entities.
 Customer data table:
Data
name
Alias Type
&
length
Defa
ult
value
Accept
able
value
Source Security Respon
sible
user
Descripti
on &
commen
t
Custo
mer
name
Nam
e
Text
(20)
None - Customer None None Customer
name
Mobile
numbe
r
Phon
e
Numb
er (12)
- Any 12
digit
number
Customer Registratio
n office
None Customer
mobile
number
Addres
s
- Text
(30)
- - Customer Registratio
n office
Custome
r
Customer
address
Email Email Text
(30)
- Custom
er
name@
Compa
ny
name
Customer Delivery
company,
registration
office
Custome
r
Customer
email
Credit
Card
Numbe
r
Credi
t
Card
Numb
er (16)
- Any 16
digit
number
Customer Financial
departmen
t
financial
departm
ent
Customer
credit
card
number

 Item table:
Data
name
Alias Typ
e &
leng
th
Defau
lt
value
Accepta
ble value
Source Security Description
& comment
Item
name
Item
name
Text
(20)
- - Stockperson Salesman,
Production
department
Product
name
Code Produ
ct
code
Num
ber
(8)
- Litter(A-
Z) then
any 7
number
Salesman Salesman,
Production
department
Product code
Price Price Num
ber
(8)
- DHS Stockperson Production
department
Products
price
Type Type Text
(10)
- - Salesman Salesman,
Production
department
Products type
Disco
unt
Disco
unt
Num
ber
(3)
- 00% Stockperson Production
department
Discount
 Order table:
Data
name
Alias Type &
length
Default
value
Acceptable
value
Source Security Description
& comment
Order
number
Order
number
Number
(8)
- - Salesman Salesman,
Delivery,
customer
Order
number
Date Date Number
(10)
- 00/00/0000 Salesman Salesman,
customer
Order Date
Time Time Number
(5)
- 00:00 Salesman Salesman,
customer
Order Time

Shipping
charge
Shipping
charge
Number
(2)
- $ Delivery Delivery Order
Shipping
charge
Quantity Quantity Number
(2)
- - Customer Salesman Order
Quantity
 Account receivable (Invoice) table
Data
name
Alias Type &
length
Default
value
Acceptable
value
Source Security Descrip
& comm
Invoice
number
Invoice
number
Number
(10)
- Any 10 digit
number
Salesman Salesman,
Delivery
company
invoice
number
Customer
name
Name Text
(20)
None - Customer Customer Custom
name
Shipping
Address
Customer
Address
Text
(30)
- - Customer Salesman,
Stockperson
Custom
address
Item
name
Item
name
Text
(20)
- - Stockperson Production
department
Product
name
Quantity Quantity Number
(2)
- Any one or
two digit
number
Customer Salesman,
Stock
person
Order
Quantity
 Customer payment details table
Data
name
Alias Type
&
lengt
h
Defa
ult
value
Accepta
ble
value
Sourc
e
Security Description &
comment
Credit
Card
Number
Credit
Card
Numb
er
(16)
- Any 16
digit
number
Custo
mer
Financia
l
departm
ent
Customer credit card
number

Expirati
on
Date
- Numb
er (5)
- 00/00/00
00
Custo
mer
Financia
l
departm
ent
Expiration
Date
Card
Security
Code
CSC Numb
er (4)
- Any 4
digit
number
Custo
mer
Financia
l
departm
ent
Card Security Code
Card
Verificati
on Value
CVV Numb
er (3)
- 3 digit
number
Custo
mer
Financia
l
departm
ent
The three number on
the back of card
Custom
er name
Name Text
(20)
None - Custo
mer
None Customer name
 Delivery table
Data name Alias Type &
length
Default
value
Acceptable
value
Source Security
Customer
Name
Name Text
(20)
None - Customer None
Mobile
number
Phone Number
(12)
- Any 12 digit
number
Customer Registration office
Address - Text
(30)
- - Customer Registration office
Invoice
number
Invoice
number
Number
(10)
- Any 10 digit
number
Salesman Salesman, Delivery
company
Deliverable
person
Driver Text
(15)
- - Stockperson Salesman, Delivery
Company

 Data Flows
Name or
label
Description Alternate
name
Origin Destination Record Volum
freque
Order - Create
order
Customer
external
entity
Place order
process
Order
table
Approx
500 pe
Order notice - None Place order
process
Stockperson
external
entity
Order
table
Approx
500 pe
Confirm - None Stockperson
external
entity
Verify order
process
Order
table
Approx
250 pe
Check
availability
- Find out
the
availability
Verify order
process
Stockperson
external
entity
Item
table
Approx
600 pe
Send order - None Stockperson
external
entity
Deliver
order
process
table Approx
500 pe
Delivery
information
- Delivery
details
Deliver
order
process
Delivery Delivery
table
Approx
500 pe
Payment - None Customer
external
entity
Apply
payment
process
Invoice
table
Approx
300 pe
Payment
notice
- None Apply
payment
process
Stockperson
external
entity
Invoice
table
Approx
300 pe
Confirmation
notice
- None Verify order
process
Customer
external
entity
Order
table
Approx
350 pe
Confirmation
notice
- None Verify order
process
Salesman
external
Order
table
Approx
400 pe

entity
Generate
invoice
- None Salesman
external
entity
Prepare
invoice
Invoice
table
Approx
350 pe
Invoice - None Prepare
invoice
Customer
external
entity
Invoice
table
Approx
350 pe
Deposit - None Apply
payment
process
Bank
system
external
entity
Invoice
table
Approx
300 pe
Verify - None Bank
system
external
entity
Apply
payment
process
Invoice
table
Approx
550 pe
Order - None Customer
external
entity
Create
order details
process
Order
table
Approx
500 pe
Confirm
order
- None Customer
external
entity
Confirm
order
placement
process
Order
table
Approx
450 pe
Order details - None Create
order details
process
Confirm
order
placement
process
Order
table
Approx
450 pe
Send
customer
order
information
- None Create
order details
process
Customer
data store
Customer
table
Approx
400 pe
Product list - None Confirm
order
Stockperson
external
Item
table
Approx
350 pe

placement
process
entity
Update order
information
- Update
order
details
Confirm
order
placement
process
Order data
store
Order
table
Approx
450 pe
Order - Create
order
Customer
external
entity
Check
availability
process
Item
table
Approx
500 pe
Check - None Check
availability
process
Stockperson
external
entity
Item
table
Approx
500 pe
Cancel - None Stockperson
external
entity
Cancel
order
process
Order
table
Approx
400 pe
Confirm - None Stockperson
external
entity
Confirm
order
process
Order
table
Approx
300 pe
Reject
notification
- None Cancel
order
process
Customer
external
entity
Order
table
Approx
250 pe
Confirmation
notice
- None Confirm
order
process
Customer
external
entity
Order
table
Approx
300 pe
Confirmation
notice
- None Confirm
order
process
Salesman
external
entity
Order
table
Approx
350 pe
Pay - None Customer
external
entity
payment
process
(process)
Customer
payment
details
table
Approx
450 pe
Deposit - None payment
process
Bank
system
Customer
payment
Approx
400 pe

(process) external
entity
details
table
Verify - None Bank
system
external
entity
payment
process
(process)
Customer
payment
details
table
Approx
600 pe
Send invoice - None payment
process
(process)
Customer
external
entity
Customer
payment
details
table
Approx
400 pe
Payment
information
- Payment
details
payment
process
(process)
Prepare
transaction
process
Customer
payment
details
table
Approx
300 pe
Payment
information
- None Prepare
transaction
process
Account
receivable
data store
Customer
payment
details
table
Approx
per da
Payment
details
- None Account
receivable
data store
Prepare
payment
process
Customer
payment
details
table
Approx
300 pe
Payment
notice
- None Prepare
payment
process
Stockperson
external
entity
Customer
payment
details
table
Approx
300 pe
Update - None Stockperson
external
entity
Update item
process
Item
table
Approx
450 pe
Update - None Update item
process
JOLLYCHIC
items data
store
Item
table
Approx
450 pe

 Data Stores
Name or
label
Description Alternate name Attributes Volume and
frequency
Customer
Data
Customer
information
CUSTOMER
INFORMATIOM
 Customer
Name
 Phone
 Address
 Credit card
 Email
500-1000 data
Account
receivable
Invoice
details
INVOICE  Invoice
number
 Customer
name
 Shipping
Address
 Order number
 Product name
 Quantity
5000-10000 per
week
Order data Order
details
ORDER
INFORMATION
 Order number
 Quantity
 Date
 Time
 Shipping
charge
1000-2000 per
day
JOLLYCHIC
Items
Items
details
ITEMS DETAILS  Item Name
 Price
 Discount
 Code
 Type
5000-10000
items
 Processes

Name or label Description Process
number
Process description
Place Order Customer
creates or
places order
1 Input data flow: ORDER
Output data flow: ORDER NOTICE
Create Order
Details
Create order
details
1.1 Input data flow: ORDER
Output data flow: ORDER DETAILS
Confirm
Order
Placement
Confirm order 1.2 Input data flow: ORDER DETAILS,
CONFIRM ORDER
Output data flow: UPDATE ORDER
INFORMATION, PRODUCT LIST
Check Items Check items 2 Input data flow: CONFIRM
Output data flow: CHECK AVAILABILITY,
CONFIRMATION NOTICE
Check
Availability
Check
availability
2.1 Input data flow: ORDER
Output data flow: CHECK
Cancel Order Cancel order 2.2 Input data flow: CANCEL
Output data flow: REJECT NOTIFICATION
Confirm
Order
Confirm order 2.3 Input data flow: CONFIRM
Output data flow: CONFIRMATION NOTICE
Prepare
Invoice
Prepare
invoice
3 Input data flow: GENERATE INVOICE
Output data flow: INVOICE
Apply
Payment
Apply
payment
4 Input data flow: VERIFY, PAYMENT
Output data flow: DEPOSIT, PAYMENT
NOTICE
Deliver Order Deliver order 5 Input data flow: SEND ORDER
Output data flow: DELIVERY
INFORMATION
Payment
Process
Payment
process
5.1 Input data flow: VERIFY, PAY
Output data flow: DEPOSIT, SEND
INVOICE, PAYMENT INFORMATION
Prepare
Transaction
Prepare
transaction
5.2 Input data flow: PAYMENT INFORMATION
Output data flow: PAYMENT

INFORMATION
Prepare
Payment
Prepare
payment
5.3 Input data flow: PAYMENT DETAILS
Output data flow: PAYMENT NOTICE
Update Items Update items 5.4 Input data flow: UPDATE
Output data flow: UPDATE
 External Entities
Entity name Description Alternate
name
Input data
flows
Output
data flows
Customer Customer Client,
Purchaser,
User.
Receipt Order,
Payment
Salesman JollyChic's
Employee (or
Manager)
Marketer,
Salesperson
Confirmation
notice
Invoice
Stockperson Vendor, who
provides
goods
Supplier Check
availability
Confirm
availability
Bank
System
Bank - Deposit Verify
Delivery Delivery
company
Delivery
details
Delivery
information
-

Decision Table:
Placing an order:
Simplified decision table:

Decision tree:
Modular Design:

Commentary:
We learned many things throughout the progress of making flowcharts, and
especially the DFD (Data Flow Diagrams). Hence, we have learned to think
behind the system, not how the customer looks at it. In fact, we learned how
the system works and how the processes go on after a customer places an
order or rather an input into the system which results by an output for example
if the customer pays for the product, the system should send an invoice for
the customer. Therefore, when we created many DFD’s diagrams individually
and afterward, we had a meeting and discussed about what we have done,
studied the diagrams and the different points of view, then integrated our work
together as a team. This really helped us to have the best diagrams and
decide what process should the system has and we understood how each
process works, and how the system is working with all those processes inside
it by details. Moreover, it was difficult to come up with a use case at first, but
once we started with it, everything was easier to work with.
PART 3: Object Modelling  
Use Case DescriptionDocuments:

ObjectRelationship Diagram:
- The object relationship diagram shows the relationships between different
objects in JollyChic ordering system. When a customer places an order in
JollyChic ordering system, an order notice is sent to the stock person who is
responsible for checking the item's availability. If the order is available the
stock person confirms the availability of the order, after that a notice is sent to
the salesperson to generate an invoice and send it to the customer to apply
payment. When the payment is successfully applied and confirmed by the
salesperson, he/she is to send an order confirmation notice to the stock
person who will start preparing the order for shipment and then to the driver
who will deliver it to the customer.

Class Diagram:
This diagram, Class Diagram is based on the ORD diagram and the Use
Case diagram. The actors and entities are the classes and the use cases or
actions are their attributes and methods. This diagram helped us understand
the relationships between the actors and their action. Therefore, we were able
to distinguish between some similar actions and identify the right assignment
for each.

SequenceDiagram:
This is a sequence diagram that considers as a dynamic model of a use case.
It shows the interactions between classes during a particular period of time.
The sequence diagram has some features such as classes like customer,
JollyChic manager, warehouse, supplier, and shipment. The second feature is
the lifelines, which are coming from each of the entities (Customer, Jollychic
manager) and representing the time during which the object above can
interact with. In addition, the X mark in the shipment lifeline illustrates the end
of its interaction with any other object. The third feature is the messages.
They are shown as an arrow which run the information about contents
between two objects. Place an order is a message between customers to the
JollyChic manager. The last feature is the focus, which demonstrates a
narrow vertical shape that comprises the lifeline. To clarify, supplier has the
smallest focus in this diagram because it has received one message and has
sent one message.

State TransitionDiagram:
This is a state transition diagram, which shows how the order object changes
from one state to another. The changing happens based on the events that
affect the status. For instance, one of the states is the active object that will be
canceled if there is any in-stock item. In addition, object also can have more
that one event depended on if there has been any changing of the state.

Activity Diagram:
This is an Activity diagram which shows the actions and events involved in
customer ordering product from JollyChic website. It illustrates the order in
which the actions take place and identify the outcomes. This diagram shows
the big picture and the entire actions that happen in this particular process. In
this case, the diagram illustrates the ordering process and starts with when
the customer places an order to how it ends with a final report. It contains
multiple actions, which are placing an order, payment, delivery, checkout, and
system update.

BusinessProcessModel(BPM):
Business Process Model (BPM) represents the people, events, and
interaction in a system, BPM concerned with 'mapping' and 'workflow' to
enable understanding, analysis and positive change. It is a method for
improving project quality and efficiency. This BPM describes the Jollychic
payment process. It has five roles participating in the process and they are
Customer, Warehouse, Bank, Jollychic Manger and the ERP System.

Part 3 Commentary:
We have learnt many things going through this part of the project. In fact, we
had difficulties creating the class diagram, where the objects are interacting
with each other. However, we have learned how to easily design the
sequence diagram, the activity diagram, the state transition diagram. Hence,
the business process diagram was a little difficult to design, we had to put
more thought into it before actually designing it. Overall, this part of the project
was not as hard as the previous part, it was easier that creating the DFD
diagrams.
Final commentary:
We have gone through many diagrams, and many planning to come up with
the best use case diagram. Choosing the use case diagram and changing it
many times was really difficult for us. Since we had trouble with changing the
use case, it affected all the DFD diagrams. Therefore, every time we changed
the use case, or deleted, or added something we changed things in the DFD
diagrams. Hence, writing the strategy and the problem statement was top
priority for us, because that is what our project was based on, or focusing on.
In fact, we have learned that we can not have a data flow coming from an
entity to another entity. However, we also had to change the use case
description many times, and because of that we had some difficulties.
Moreover, the project was really interesting, and it was fun to work on, it just
requires a long time to finish, and work on. Also, it requires a long time to
decide on the best diagram to come up with. Finally, there were many
interesting topics we have discussed with each other, it is true that the
diagrams took a long time to be better and simpler, but it was entertaining.

Sources:
Jollychic. "About Jollychic.Com". Jollychic.com. N.p., 19 Feb. 2017.

System design for JollyChic (online ordering system)

Recommandé

Recommandé

Contenu connexe

Dernier

Dernier (20)

En vedette

En vedette (20)

System design for JollyChic (online ordering system)