Coffee Documentation

GC UNIVERSITY, FAISALABAD
FACULTY ECONOMIC &MANAGEMANT SCIENCES
Course Specification
Business Project For Marketing
Session (2020-2022)
Submitted By
Name Hafiz Fahad Ali ID 201562
Coffee & Tea Cafe
A Report Submitted to the Lyallpur Business School
In
Partial Fulfillment of the Requirements for the Associate Degree
In
BBA
By
Student Name: Hafiz Fahad Ali Student-ID: 201562
Director
Prof. Dr. Shahid Kamal

Lyallpur Business School
• Acknowledgement
I am thankful to ALMIGHTY ALLAH who gave me courage and passion and prayers of my
parents and teachers to achieve the goal that was necessary for the degree. Although it was not an
easy task, with the useful direction, kind supervision and co-operation of Mr. Ahmed Ali , it
became easy for me to complete the research work. I am really grateful to my Project Supervisor
because of his profound interest and encouragement throughout the project work.
I would like to acknowledge Prof. Dr. Shahid Kamal Director, Lyallpur Business School GC
UNIVERSITY, FAISALABAD, for encouraging and providing me all the facilities throughout the
project.
Last but not least, I extend my sincere appreciativeness and thankfulness to my Family for their
incredible encouragement. Their love and support means a lot to me.
• undertaking
Coffee & Tea Cafef
Session (2020-2022)
This project is submitted to the , Lyallpur Business School GC University Faisalabad FA,for the
partial fulfillment of the requirement for Associate degree program (BBA)

• Abstract
My project is coffee & tea cafe selling on their shope or online website.
It serves its consumer the best services and coffee & tea. We source our
own beans. Design our own blend. Produce our own roasts. That’s how
we maintain our flavor and quality. Whether you are escaping your daily
grind or enjoying our premium brews. We are committed to delivering
you the best coffee in every cup.
• Contents
DEDICATION..........................................................................................................................................II
ACKNOWLEDGEMENT......................................................................................................................III
UNDERTAKING.....................................................................................................................................IV
ABSTRACT..............................................................................................................................................V
1. INTRODUCTION.............................................................................................................................1
1.1 Project Overview...........................................................................................................................................1
1.1.1 Problem Statement................................................................................................................................1
1.1.2 Back Ground.........................................................................................................................................1
1.1.3 Proposed Solution.................................................................................................................................1
1.1.4 Customer...............................................................................................................................................1
1.1.5 Goals and Objectives............................................................................................................................1
1.1.6 Dependencies/ External Systems..........................................................................................................1
1.1.7 Definitions and Acronyms....................................................................................................................2
1.1.8 Market Survey/ Domain Analysis........................................................................................................2
2. SYSTEM REQUIREMENT SPECIFICATION..............................................................................4
2.1 Functional Requirements...............................................................................................................................4
2.2 Non-Functional Requirement......................................................................................................................10
2.3 Use Case Models.........................................................................................................................................10
2.3.1 Use Case Diagram..............................................................................................................................11
2.3.2 Usage Scenario...................................................................................................................................11
3. SYSTEM DESIGN..........................................................................................................................20
3.1 System Architecture....................................................................................................................................20
3.2 Class Diagram.............................................................................................................................................21
3.3 Sequence Diagram (Against each use case)................................................................................................22
3.4 Activity Diagram (Against each use case)..................................................................................................23
3.5 Entity Relationship Diagram.......................................................................................................................28
3.6 Data flow Diagram......................................................................................................................................29
3.6.1 Level 0................................................................................................................................................29
3.6.2 Level 1................................................................................................................................................30
3.6.3 Level 2................................................................................................................................................31
4. IMPLEMENTATION......................................................................................................................33
4.1 TOOLS........................................................................................................................................................33
4.1.1 Web Application.................................................................................................................................33
4.1.2 Database.............................................................................................................................................33
4.2 TECHNIQUES............................................................................................................................................34
4.3 LANGUAGES............................................................................................................................................34
4.4 Traceability Matrix......................................................................................................................................34
4.5 Snapshots of Frond End..............................................................................................................................34
5. TESTING.........................................................................................................................................38
5.1 Test Cases....................................................................................................................................................38
5.2 TID template...............................................................................................................................................43
5.3 Decision Table.............................................................................................................................................43
5.4 Black Box Testing.......................................................................................................................................43
5.5 White Box Testing.......................................................................................................................................43
6. RESULTS/OUTPUT/STATISTICS................................................................................................45
6.1 Traceability Matrix (TID vs UID)...............................................................................................................45
6.2 % Completion..............................................................................................................................................45
6.3 % Accuracy.................................................................................................................................................45
6.4 % Correctness..............................................................................................................................................45
7. CONCLUSION AND SUMMARY.................................................................................................47
7.1 CONCLUSION...........................................................................................................................................47
7.2 SUMMARY................................................................................................................................................47
7.3 LESSON LEARNED..................................................................................................................................47
INTRODUCTION
• Introduction
• Project Overview
• Problem Statement
We saw that there are a few cafés selling coffee & tea online and I am personally big-time lover of coffee.
So, I decided what if we build a website that can deliver coffee 24/7 at your door step in less than 20min
in your area. So, we decided to start with a specified area (i.e Lahore cantt area) and then we will
increase. There comes the second question. What is the point of ordering the coffee if it’s not hot? So, we
decided to give coffee warmer with first delivery as a complimentary gift.
• Back Ground
• Existing Systems
There are companies doing the work in coffee industry like Coffee planet, RAAZ unveiled and VERVE
Coffee Roasters etc. They are doing a great work but mostly companies prefer to sell beans and powered
form of coffee because it is easy to manage and can be store. Some of the cafés are selling the coffee but,
in the time, when they are open.
• Drawbacks
Because we are a startup company, we don’t have enough capital to back us up So, we are not able to
provide our services on large scale. We cannot provide heavy deals and discount offers. We cannot hire
riders for delivery we have to contact with third party for delivery services. We have to rent the shop and
where house to store the material and to make coffee.
• Proposed Solution
We started a service to deliver coffee to its consumers. For this we make sure to flow some steps:
• Make sure quantity is not sacrificed.
• We source our beans.
• Blend on our own.
• Brew by our self.
• Make sure quality is not sacrificed.
• Deliver with in the time.
• Reasonable prices.
• Packing must be good.
• Delivery will be 24/7.
• Customer
Our customers are of all age group. Mostly people between 20-40 age drink coffee to relief fatigue,
enjoyment with friends & family, for late night workloads etc.
• Goals and Objectives

The objectives of my website are to provide the good quality coffee on very low prices. Our main focus is to provide
quality product and satisfaction of customer. Our revenue model is transaction and sales revenue model mean we
provides the sale services.
• Dependencies/ External Systems
As the transactions are taking place every day, the system stores all the data which can be used
later on when the website is in need of some financial help from financial institutes or banks.
• Definitions and Acronyms

The external system for the website is basically database which is used as a backend for the html. The
feedback, login/register, and add to cart option works with the Database.
• Market Survey/ Domain Analysis
The system should be defined according to our rules and regulations. In this paragraph, we can explain
that how our system is defined like first user need login and password. secondly, he can visit the website
as user and visitor. Then only registered users can order from our website.
SYSTEM REQUIREMENT SPECIFICATION

• System Requirement specification
• Functional Requirements
Functional requirements are basically the features and functions that the software must offer. It is
used to enable users to perform their task. Functional requirements are different for each user
like Admin, User and Manager. Functional Category has 3 types:
• Website has Add to Cart Option which has all the products you select to buy.
• Website has proper Log in Page where you can register yourself.
• Website has Complain Page which is responsible to take complaints regarding products.
• We have 24 Hours Chatting Page where you can talk with us anytime.
• We have secured Login option because sometimes unauthorized persons can hack the
account.
• Only Admin is able to edit the products.
• Only admin has an option to edit and reset the password and email.
ID: User_01
Name: Add to Cart
Description Input Output Requirements Basic Work Flow
User can select User can The product Internet User can select anything and then
Select the Connectivity
anything and can add to click onto add to cart option to
product and required,
then add that then click it cart which correct add that product into list and after
product into cart on Add to you can username and that customer can delete or add
to sell that Cart Button. select. password. anything into add to cart option.
product.
ID: User_02
Name: Login for User

User can G mail Id The admin Internet User can register them by giving
Connectivity
register them by can send them their g mail account. Then it
required,
giving them them an correct will send to admin to approve the
their g mail approve username and customer.
account. request to get password.
registered.
ID: User_03
Name: Complaint Page
If users have any problem Correct The admin can Internet User can complaint our produ
username and Connectivity
with our product like quality, receive the they feel any problem with
Password required,
then can complaint. complaint and correct quality, color, fabric shrinking et
then resolve username and
that issue. password.
ID: Admin_01
Name: Chatting Page
If users have any User can chat The admin can receive Internet Connectivity User can chat with
with admin to required, correct
problem with our the Message and then case of any diff
keep in touch but username and password.
product like quality, first enter his id reply as soon as possible. like how to order,
then can chat with us. and password to to register etc.
login.
ID: Admin_04
Name: Edit the Product
Admin can edit Admin can Admin can Internet Admin can edit/delete or update
enter his Connectivity
the product only click on edit, the product to meet the
password and required,
because he is correct login. delete correct requirements.
the main owner Admin can product to username and
of the website. change/edit change the password.
the product
requirement.
price, quality
etc.
ID: Admin_05
Name: Edit/Reset the Login and Password
Admin can edit Admin can Admin Internet Admin can edit and reset the
and reset the change the login and password in case of
password and required,
password and id correct login. login and correct forget password.
in case of password of username and
forget. specific user password.
ID: Visitor_01
Name: Contact through social media
Visitor can visit Visitor can Visitor in on Internet Visitor can visit our website by
add the link of Connectivity
the website then our website proper link and click on our
our website. required,
click on social and on correct social media links to visit our
media links to footer, he/she username and social media pages.
contact with us have links of password.
for information. social media.
ID: Admin_08
Name: Order & Checkout
Description Input Output Requirement
Place order and after Order items, billing Order is places and Products user billing and
address, shipping shipping address and
payment checkout is done. delivered.
address, Payment payment
method
ID: User_08
Name: Product Attributes
Description Input Output Requirement Basic Work
Product attributes Product details Products positive Products and its complete Products
details and presentation.
refer to the impression. presentatio
characteristics that decision.
define a service or
product and
influence customer
buying decisions.
ID: User_14
Visitor_05
Name: Recommended Items
Description Input Output Requirement Basic Work Flow
Similar items Similar Displayed Products Similar products are shown

products details
are displayed similar under the products user opens.
entries
under product product
user opens under
product
page
ID: Admin_14
User_15
Name: User data security
We send User User data is User We secure the data of user

confirmation authenticity
confirmation secure. though security systems
message system
massage to integrated in applied in our website.
users to website.
check their
authenticity.
ID: Admin_15
Name: Secure payment portal

We secure you Payment’s Secure Payment Payments for the products are
portals portal
bank details and transaction done though payment portals.
APIs are APIs.
Credit card details. integrated is done
So, we can provide in website
secure payment
portal to our users
ID: Admin_13
Name: SEO
SEO is done to Tags, Knowledge

Website’s Put targeted keywords, detect
rank your website attractive of SEO.
or ecommerce ranking will on-site issue and detect them,
store on first page heading and
thumbnail. improve. optimize your website.
of google.
ID: Admin_06
Name: Different Identity
Admin can give Admin can Admin can Internet Admin can enter his login and
different see the list, password and see the list, giving
Username and required,
password and Password giving correct different username and passwords
username to correctly. different username and to each user for security purpose.
every user for username and password.
security. pass.
• Non-Functional Requirement
• Website should take very less time to load so that it saves the time of user.
• The website should handle 20 million users at a time easily.
• Website is well maintained with proper working features.
• Our website has quick and better search result.
• Our website has accessibility standards on every device like mobile, laptops, pc etc.
• Website must have Security Features.
• Use Case Models

•Actors & use cases
•Use case diagrams
•High level, essential use cases
• Use Case Diagram

Figure 1: System Level Use Case Diagram
• Usage Scenario
USE CASE 1 Login

Description User enters the information to login.
Preconditions User must have username and password.
Post-conditions Successfully login to User panel.
Failed End User didn’t login to User panel and message is displayed
Condition “Incorrect username or password”
Actors User
Trigger Login request comes in.

Basic Events Step Action
Flow
1 User enter username.
2 User enter password.
3 Click “Login” button.
4 Successfully login.
EXTENSIONS Step Alternative Flow (Branching Action)
1 User enter wrong information.
1. Display error message “Incorrect username or
password”.
2. Redirect to login page again.
2 User click “Cancel” button.
1. Clear all data form fields.
2. Redirect to home page.
Superordinate No Superordinate
USE CASE 2 Order & checkout
Description Place order and after payment checkout is done.
Preconditions Order items, billing address, shipping address, Payment method
Post-conditions Order is places and delivered.
Failed End Order is not delivered.

Condition
Actors Admin
Trigger Order is received.

Flow
1 Items are selected and all the details are filled then order is
preceded to checkout.
1 Order is not delivered.
Superordinate Login authentication (use case 1)
USE CASE 3 Chat Bots
Description Chat-bot is a program which generates automated text on behalf of a

company to another person.
Preconditions Text integrated in program of chat-bot.
Post-conditions Gives answer to other person on behalf of the company.

Failed End Message will not display.
Condition
Actors Admin
Trigger Gives an appropriate message

Flow
1 Auto generate text to a person on behalf of the company.

1 Message will not display.
USE CASE 4 Product Attributes
Description Product attributes refer to the characteristics that define a service or

product and influence customer buying decisions.
Preconditions Product details
Post-conditions Products positive impression.
Failed End Failure in product display.

Condition
Actors Admin
Trigger Product details are managed.

Flow
1 Products are displayed and better presentation puts influence on
buyer’s decision.
1 Failure in product display.
-
USE CASE 5 Recommended Items
Description Similar items are displayed under product user opens
Preconditions Similar products entries
Post-conditions Displayed similar product under product page
Failed End Recommended item will not show.

Condition
Actors Admin
Trigger Similar products are shown under the product details.

Basic Events Flow Step Action
1 Similar products are shown under the products user opens.

1 Recommended item will not show.
USE CASE 6 User data security
Description We send confirmation massage to users to check their authenticity.
Preconditions User confirmation message

Post-conditions User data is secure.
Failed End User data leaked.

Condition
Actors Admin
Trigger User data is secured.

1 We secure the data of user though security systems applied in our website.
1 User data may leak.
USE CASE 7 Social Sharing

Description Share the app link and products you like on different social media platform.
Preconditions Product and app links for sharing

Post-conditions Traffic for the website/app will increase.
Failed End Cannot share products on social media.

Condition
Actors Admin
Trigger Generates a link of product.

1 People share the products and the reach of website will increase and also the
popularity will surely increase.
1 Cannot share products on social media.
USE CASE 8 Secure payment portal

Description We secure you bank details and Credit card details. So, we can provide secure
payment portal to our users
Preconditions Payment’s portals APIs are integrated in website
Post-conditions Secure transactions are done.
Failed End Transection is not done.

Condition
Actors Admin
Trigger Online money transfer is done
1 Payments for the products are done though payment portals.

1 Transection is not done.
USE CASE 9 SEO

Description SEO is done to rank your website or ecommerce store on first page of google.
Preconditions Tags, attractive heading and thumbnail.

Post-conditions Website’s ranking will improve.
Failed End Traffic cannot not be generated on website.

Condition
Actors Admin
1 Put targeted keywords, detect on-site issue and detect them, optimize your
website.
1 Traffic cannot not be generated on website.
SYSTEM DESIGN
• System design
• System Architecture
A system's architecture acts as a blueprint. It establishes a communication and coordination
mechanism among components and gives an abstraction to control system complexity.
• It specifies a structured solution that satisfies all technical and operational criteria while improving
common quality features such as performance and security.
• Furthermore, it entails a series of important organizational decisions connected to software development,

each of which can have a substantial influence on the end product's quality, maintainability, performance,
and overall success. These choices are made up of a variety of factors.
These decisions comprise of:
• Selection of structural elements and their interfaces by which the system is composed.
• Behavior as specified in collaborations among those elements.
• Composition of these structural and behavioral elements into large subsystem.
• Architectural decisions align with business objectives.
• Architectural styles guide the organization.
Figure 3: System Architecture
• Class Diagram
• Sequence Diagram (Against each use case)
• Activity Diagram (Against each use case)

• Entity Relationship Diagram
• Data flow Diagram
Figure 22 Data Flow Diagram
• Level 0
Figure 23 Level 0
• Level 1
Figure 24 Level 1
• Level 2
Figure 25 Level 2
IMPLEMENTATION
• Implementation
• TOOLS
• Web Application
• MICROSOFT WORD
It is used in the website documentation to provide a full explanation. It may also be used to
check the website's functionalities.
• Photoshop (Adobe)
My logo and About Us page boxes, which will be displayed with the display photo, were created
in Photoshop.
• Visual Paradigm
UML stands for Use Case Diagrams, and Visual Paradigm is used to create them. It facilitates the
creation of a system diagram quickly and easily. Because the elements such as Actors, Lines, and
Shapes can be dragged and dropped, it is simple to use and maintain.
• VISUAL STUDIO CODE
It is suitable editor for Web Based Application. It has many functions like Multiple Selections,
Page Linking, and other emits which helps the programmer to complete the coding in a
convenient manner.
• HTML5
It is a Hyper Text Markup Language which is used to build the structure of the website. It is the
core of Web Based Application. HTML5 is the latest version which has very easy tags to
implement.
• CSS
It is a Hyper Text Markup Language which is used to build the structure of the website. It is the
core of Web Based Application. HTML5 is the latest version which has very easy tags to
implement.
• Database
• SQL
Structured Query Language is used to add, update or delete something from the website. We can
used SQL to Add, Update, and Delete the products from the website.
• XAMPP SERVER
We can used XAMPP Server as to connect the html with database. It needs no internet to connect
it. For the purpose of connection, we can use this server. It creates a host on the local machine in
which we are working.
.
• TECHNIQUES
• My SQL
Query with Structure
To add, alter, or remove something from the website, language is utilized.
To add, update, and delete products from the website, we can utilize SQL.
• PHP
It connects the HTML with the database.
It does not require the use of the internet to connect.
This server can be used to establish a connection.
• LANGUAGES
• HTML
It is a Hyper Text Markup Language (HTML) that is used to create the website's structure.
It is the central component of a web-based application.
HTML5 is the most recent version, with extremely simple tags to integrate.
• CSS
Cascading style sheet (CSS) is used to style the html website.
• Traceability Matrix
While the database allows for easy access to and tracking of an individual's full work history, each employee may
access just their own personal information through a human resource information system.
• Snapshots of Frond End

Form Title: Heading of the form
Interface Id: UI – 01
Description: Main Window of café & coffee System opens when application is started.
This window will contain home page for user.
Snapshot:
TESTING
•
• testing
• Test Cases
Test Cases should be at least against use cases
USE CASE 1 Login

Description User enters the information to login.
Preconditions User must have username and password.
Post-conditions Successfully login to User panel.
Failed End User didn’t login to User panel and message is displayed
Condition “Incorrect username or password”
Actors User
Trigger Login request comes in.

1 User enter username.
2 User enter password.
3 Click “Login” button.
4 Successfully login.
1 User enter wrong information.
1. Display error message “Incorrect username or
password”.
2. Redirect to login page again.
2 User click “Cancel” button.
1. Clear all data form fields.
2. Redirect to home page.
Superordinate No Superordinate
USE CASE 2 Order & checkout
Description Place order and after payment checkout is done.
Preconditions Order items, billing address, shipping address, Payment method

Post-conditions Order is places and delivered.
Failed End Order is not delivered.

Condition
Actors Admin
Trigger Order is received.

Flow
1 Items are selected and all the details are filled then order is
preceded to checkout.
1 Order is not delivered.

USE CASE 3 Chat Bots
Description Chat-bot is a program which generates automated text on behalf of a

company to another person.
Preconditions Text integrated in program of chat-bot.
Post-conditions Gives answer to other person on behalf of the company.
Failed End Message will not display.

Condition
Actors Admin
Trigger Gives an appropriate message

Flow
1 Auto generate text to a person on behalf of the company.

1 Message will not display.
USE CASE 4 Product Attributes

Description Product attributes refer to the characteristics that define a service or
product and influence customer buying decisions.
Preconditions Product details
Post-conditions Products positive impression.
Failed End Failure in product display.

Condition
Actors Admin
Trigger Product details are managed.

Flow
1 Products are displayed and better presentation puts influence
on buyer’s decision.
1 Failure in product display.
USE CASE 5 Recommended Items
Description Similar items are displayed under product user opens
Preconditions Similar products entries
Post-conditions Displayed similar product under product page
Failed End Recommended item will not show.

Condition
Actors Admin
Trigger Similar products are shown under the product details.

Flow
1 Similar products are shown under the products user opens.

1 Recommended item will not show.
USE CASE 6 User data security
Description We send confirmation massage to users to check their

authenticity.
Preconditions User confirmation message
Post-conditions User data is secure.
Failed End User data leaked.

Condition
Actors Admin
Trigger User data is secured.

Flow
1 We secure the data of user though security systems applied in
our website.
1 User data may leak.
USE CASE 7 Social Sharing

Description Share the app link and products you like on different social media
platform.
Preconditions Product and app links for sharing
Post-conditions Traffic for the website/app will increase.
Failed End Cannot share products on social media.

Condition
Actors Admin
Trigger Generates a link of product.

Flow
1 People share the products and the reach of website will
increase and also the popularity will surely increase.
1 Cannot share products on social media.
USE CASE 8 Secure payment portal

Description We secure you bank details and Credit card details. So, we can
provide secure payment portal to our users
Preconditions Payment’s portals APIs are integrated in website
Post-conditions Secure transactions are done.
Failed End Transection is not done.

Condition
Actors Admin

Flow
1 Payments for the products are done though payment
portals.
1 Transection is not done.

USE CASE 9 SEO

Description SEO is done to rank your website or ecommerce store on first
page of google.
Preconditions Tags, attractive heading and thumbnail.
Post-conditions Website’s ranking will improve.
Failed End Traffic cannot not be generated on website.

Condition
Actors Admin

Flow
1 Put targeted keywords, detect on-site issue and detect
them, optimize your website.
1 Traffic cannot not be generated on website.
• TID template
While the database allows for easy access to and tracking of an individual's full work history,
each employee may access just their own personal information through a human resource
information system.
• Decision Table
• Black Box Testing

Only specified functionalities are visible to users for security and privacy reasons, such as only
the administrator may reset/update the password and access a list of customers.
• White Box Testing

Customers can see the product and can also see the options for quantity and size of coffee cup.
White box testing is basically the features that are displaying on the screen, which means the
entity and its attributes, such as customers can see the product and can also see the options for
quantity and size of coffee cup.
RESULTS/OUTPUT/STATISTICS
•
• Results/Output/Statistics
• Traceability Matrix (TID vs UID)
• % Completion
About 80% is current completion rate.
• % Accuracy
• % Correctness
CONCLUSION & SUMMARY

• Conclusion and summary
• CONCLUSION
My Final Project is on café & coffee website in which we are using different languages like HTML, CSS and PHP
which is connected with Database. I am delivering the quality and authentic coffee taste and flavors that a coffee
lover wishes to enjoy. It gives satisfaction to those people who have no time to go outside for relaxation.
• SUMMARY
When you open your website home page is displayed. We have 5 subpages like home page, menu Page,
Registration/Login Form, about us, Contact Us Page. The home page contains the Navigation Bar, Product List with
Banner and Footer. Product Page basically has the album of Products to make the website more attractive. Login
form page contains the proper form which has your proper details like name, email, password etc. The About Us
page has 3 things which are Services, Quality and History. We have 24 hours of services and we entertain every user
of our website. Quality page contains the information about our coffee that how they make the coffee for the users.
About us page contains the history like when we start our company and what is our objective. The Last is our
Contact us page which has our email address, Whatsapp Cell no with 24 hours services.
• LESSON LEARNED
This final assignment has taught me a lot. Because when I first started this endeavor, I realized how little I knew
about the website. This final project allows me to demonstrate my dedication to my profession.
REFERENCES
• References
 Allen, Stewart Lee (1999). The Devil's Cup: Coffee, the Driving Force in History. Soho: Random
House. ISBN 978-1-56947-174-6.
 Esat Ayyıldız. “ HYPERLINK "https://ia801502.us.archive.org/27/items/kahve_202201/Kahve%20S
%C3%B6zc%C3%BC%C4%9F%C3%BCn%C3%BCn%20Etimolojisi%20ve%20Arap%20Literat
%C3%BCr%C3%BCndeki%20Yans%C4%B1malar%C4%B1.pdf" HYPERLINK
"https://ia801502.us.archive.org/27/items/kahve_202201/Kahve%20S%C3%B6zc%C3%BC%C4%9F
%C3%BCn%C3%BCn%20Etimolojisi%20ve%20Arap%20Literat%C3%BCr%C3%BCndeki%20Yans
%C4%B1malar%C4%B1.pdf" HYPERLINK
%C4%B1malar%C4%B1.pdf"Kahve HYPERLINK
%C4%B1malar%C4%B1.pdf"Sözcüğünün HYPERLINK
%C4%B1malar%C4%B1.pdf"Etimolojisi HYPERLINK
%C4%B1malar%C4%B1.pdf"ve HYPERLINK
%C4%B1malar%C4%B1.pdf" Arap HYPERLINK
%C4%B1malar%C4%B1.pdf"Literatüründeki HYPERLINK
%C4%B1malar%C4%B1.pdf"Yans HYPERLINK
%C4%B1malar%C4%B1.pdf"ımaları HYPERLINK
%C4%B1malar%C4%B1.pdf"”. International Anatolian Conference on Coffee & Cocoa: Full Text Book.
ed. Sinem Karakundakoglu. Malatya: IKSAD Global Publishing House, 2021. p.61-68.
 Bersten, Ian (1999). Coffee, Sex & Health: A History of Anti-coffee Crusaders and Sexual Hysteria.
Sydney: Helian Books. ISBN 978-0-9577581-0-0.
 Clarke, Ronald James; Macrae, R., eds. (1987). Coffee. 2: Technology. Barking, Essex: Elsevier
Applied Science. ISBN 978-1-85166-034-6.
 Clifford, M. N.; Wilson, K.C., eds. (1985). Coffee: Botany, Biochemistry and Production of Beans and
Beverage. Westport, Connecticut: AVI Publishing. ISBN 978-0-7099-0787-9.
 Kummer, Corby (2003). The Joy of Coffee: The Essential guide to Buying, Brewing, and Enjoying.
Boston: Houghton Mifflin. ISBN 978-0-618-30240-6.
 Pendergrast, Mark (2001) [1999]. Uncommon Grounds: The History of Coffee and How It Transformed
Our World. London: Texere. ISBN 978-1-58799-088-5.
 Souza, Ricardo M. (2008). Plant-Parasitic Nematodes of Coffee. シュプリンガー・ジャパン株式会社 .
ISBN 978-1-4020-8719-6. Retrieved 18 November 2015.
 Weinberg, Bennett Alan; Bealer, Bonnie K. (2001). The World of Caffeine: The Science and Culture of
the World's Most Popular Drug. New York: Routledge. p. 3. ISBN 978-0-415-92722-2. Retrieved 18
November 2015.

Coffee Documentation

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Coffee Documentation

Uploaded by

Copyright:

Available Formats

GC UNIVERSITY, FAISALABAD

FACULTY ECONOMIC &MANAGEMANT SCIENCES

Business Project For Marketing

FACULTY ECONOMIC &MANAGEMANT SCIENCES

Coffee & Tea Cafe

A Report Submitted to the Lyallpur Business School

Partial Fulfillment of the Requirements for the Associate Degree

Student Name: Hafiz Fahad Ali Student-ID: 201562

Prof. Dr. Shahid Kamal

FACULTY ECONOMIC &MANAGEMANT SCIENCES

• Goals and Objectives

• Definitions and Acronyms

• Market Survey/ Domain Analysis

SYSTEM REQUIREMENT SPECIFICATION

Name: Add to Cart

Description Input Output Requirements Basic Work Flow

Name: Login for User

Description Input Output Requirements Basic Work Flow

Name: Complaint Page

Description Input Output Requirements Basic Work Flow

Name: Chatting Page

Description Input Output Requirements Basic Work Flow

Name: Edit the Product

Description Input Output Requirements Basic Work Flow

Name: Edit/Reset the Login and Password

Description Input Output Requirements Basic Work Flow

Name: Contact through social media

Description Input Output Requirements Basic Work Flow

for information. social media.

Name: Order & Checkout

Description Input Output Requirement

Name: Product Attributes

Description Input Output Requirement Basic Work

Description Input Output Requirement Basic Work Flow

Similar items Similar Displayed Products Similar products are shown

Description Input Output Requirement Basic Work Flow

We send User User data is User We secure the data of user

Name: Secure payment portal

Description Input Output Requirement Basic Work Flow

SEO is done to Tags, Knowledge

Name: Different Identity

Description Input Output Requirements Basic Work Flow

• Use Case Models

• Use Case Diagram

USE CASE 1 Login

Trigger Login request comes in.

USE CASE 2 Order & checkout

Description Place order and after payment checkout is done.

Preconditions Order items, billing address, shipping address, Payment method

Post-conditions Order is places and delivered.

Failed End Order is not delivered.

Trigger Order is received.

Basic Events Step Action

USE CASE 3 Chat Bots

Description Chat-bot is a program which generates automated text on behalf of a

Post-conditions Gives answer to other person on behalf of the company.

Trigger Gives an appropriate message

Basic Events Step Action

EXTENSIONS Step Alternative Flow (Branching Action)

USE CASE 4 Product Attributes

Description Product attributes refer to the characteristics that define a service or

Post-conditions Products positive impression.

Failed End Failure in product display.