Online Coca Cola Company Management System SRS

Online coca cola company Management System
Online Coca Cola Company Management System
Software Requirements Specification Document
[Sheeba Noureen RollNo 183211]

Session: 2018 - 2020 | ROLLNO. 183211
<Department of IT government khawaja fareed post/g college rahim
SRS Document 1.0 Page 1 of 84 05/08/24

Revision History
Date Description Author Comments
<date> <Version 1> <Sheeba Noureen> <First Revision>
Document Approval
The following Software Requirements Specification has been accepted and approved by the following:
Signature Printed Name Title Date

SIR USMAN GHANI Supervisor, CSIT 21306 <date>

Table of Contents
1. Introduction 1
2. 1.1 Purpose 1
3. 11.2 Scope 1-2
1.3 Definitions Acronyms and Abbreviations 2-3
1.4 References 3-4
1.5 Overview 4
2. Overall Description 4
2.1 Product Perspective 4
2.2 Product Function 4-5
2.3 User Characteristics 5
2.4 Constraints 5
2.5 Assumptions and Dependencies 6
3. Specific Requirements 6
3.1 External Interface Requirements 6
3.1.1 System Interface 6-7
3.1.2 Interfaces 7-8
3.1.3 Hardware Interfaces 8
3.1.4 Software Interfaces 8
3.1.5 Communication Interfaces 9
3.2 Functional Requirements 9
3.2.1 Registration 9
3.2.1.1 Introduction 9
3.2.1.2 Input 9

3.2.1.3 Processing 9
3.2.2 Login 9
3.2.2.2 Input 10
3.2.2.4 Output 10
3.2.2.5 Error Handling 10
3.2.3 Search 11
3.2.3.2 Input 11
3.2.3.4 Output 12
3.2.4 Add to Shopping Cart 13
3.2.4.2 Input 14
3.2.4.4 Output 15
3.2.5 Delete From Shopping Cart 16
3.2.5.2 Input 17
3.2.5.4 Output 17
3.2.6 Checkout 18

3.2.6.2 Input 19
3.2.6.4 Output 20
3.2.7 Proceed to Checkout 21
3.2.7.2 Input 22
3.2.7.4 Output 23
3.2.8 Contact us 24
3.2.8.2 Input 24
3.2.8.4 Output 25
3.2.9 Update Account Information 26
3.2.9.2 Input 26
3.2.9.4 Output 27
3.2.10 Shipping Status 27
3.2.10.2 Input 16

3.2.10.4 Output 16
3.2.11 Add new Book Detail 17
3.2.11.2 Input 17
3.2.11.4 Output 17
3.2.12 Delete Book Detail 18
3.2.12.2 Input 18
3.2.12.4 Output 18
3.2.13 Payment 18
3.2.13.2 Input 19
3.2.13.4 Output 19
3.2.14 Update Books Information 18
3.2.14.2 Input 19

3.2.14.4 Output 20
3.2.15 Update Profile 20
3.2.15.2 Input 20
3.2.15.4 Output 20
3.2.16 Track Orders 21
3.2.16.2 Input 21
3.2.16.4 Output 21
3.2.17 View All Order 21
3.2.17.2 Input 21
3.2.17.4 Output 22
3.2.18 Top Selling Books 22
3.2.18.2 Input 22
3.2.18.4 Output 22


3.2.19 Give Feedback 23
3.2.19.2 Input 23
3.2.19.4 Output 23
3.2.20 Notify Out of Stock Books 24
3.2.19.2 Input 24
3.2.19.4 Output 24
3.2.21 Logout 24
3.2.21.2 Input 24
3.2.21.4 Output 25
3.3 Use Case 25
3.3.1 Login 26
3.3.3 Search 28
3.3.4 View Categories and Items 29
3.3.5 Checkout Items 30
3.3.6 Update Profile 31

3.3.7 Manage Orders 3

3.3.8 Place an Order 33
3.3.9 Payment 34
3.3.10 Update Shopping Cart 35
3.3.11 View Shopping Cart 36
3.3.12 Contact Us 37
3.3.13 Feedback 38
3.3.14 Add Book Detail 39
3.3.15 Delete Book Detail 40
3.3.16 Logout 41
3.4 Class Diagram 42
3.4.1 Login Credential 42
3.4.2 Database 42
3.4.3 Administrator 43
3.4.4 Customer 43
3.4.5 User 44
3.4.6 Shopping Cart 44
3.4.7 Inventory 45
3.4.8 Stock 45
3.4.9 Books 46
3.4.10 Product 46
3.4.11 Review 47
3.4.12 Order 47

3.4.13 Supplier 48
3.4.14 Comment 48
3.4.16 Purchase 49
3.4.17 Payment System 50
3.4.18 Transaction 50
3.4.19 Shipment 51
3.4.20 Feedback 51
3.5 Non-Functional Requirement 52
3.5.1 Performance 52
3.5.2 Reliability 52
3.5.3 Availability 52-53
3.5.4 Security 53
3.5.5 Maintainability
53
3.5.6 Portability 53
3.5.7 Easy to User 54
3.5.8 The System Should not be overly technical 54
3.5.9 Logical Database Requirements 54
3.5.9.1 ER-Diagram 54
3.5.10 ER-Diagram of Online coca cola company 55
4. Analysis Models 56
4.1 Sequence Diagrams 56

4.1.1 Login 56
4.1.2 Shopping Cart 57
4.1.3 Place Order 58
4.1.4 Feedback 59
4.1.5 Logout 60
4.2 Data Flow Diagram 60
4.2.1 Context Diagram of Online coca cola company 61
4.2.3 Level 1 Diagram of Online coca cola company 63
4.2.3 Level 1 Diagram of Online coca cola company 63
4.3 State Transition Diagram 64
4.3.1 State Transition Diagram of Registration 64

4.3.2 State Transition Diagram of Specific product
4.3.3 State Transition Diagram of Search products 83
4.3.4 State Transition Diagram of Stock Maintenance 84

1. Introduction
The following section provides an overview of the derived Software Requirements
Specification (SRS) for the subject Online Coca Cola Company Management System. To
begin with, the purpose of the document is presented and its intended audience outlined.
Subsequently, the scope of the project specified by the document is given with a particular
focus on what the resultant software will do and the relevant benefits associated with it. The

nomenclature used throughout the SRS is also offered.To conclude, a complete document
overview is provided to facilitate increased reader comprehension and navigation.
1.1 Purpose
The purpose of this SRS is to outline both the functional and non-functional
requirements of the subject Online Coca Cola Company Management System. The purpose of
this SRS is to outline both the functional and non-functional requirements of the subject
OCCCMS. In addition to said requirements, the document also provides a detailed profile of
the external interfaces, performance considerations and design constraints imposed on the
subsequent implementation. It is the intention that the presented set of requirements possesses
the following qualities; correctness, completeness, consistency. Consequently, the document
should act as a foundation for efficient and well-managed project completion and further
serve as an accurate reference in the future.The purpose of the software requirements
specification (SRS) is a comprehensive description of the indented purpose and environment
for software under development. The SRS fully describes what the software will do and how
it will be expected to perform.
1.2 Scope
The Coca Cola company one of the most valuable and recognizable brand across the
globe, is the world’s largest beverage company. It offers nearly 4,000 drink options through
its 500 different brands, 21 of which generate more than $1 billion in annual retail sales.
Coca Cola owns and markets four of the world’s top five sparkling non-alcoholic
beverages: coca cola, diet coke, sprite, coca cola zero sugar. The company creates its own
new products and also buying existing companies and continues their activities addition to
traditional, popular, and globe brands which are known in almost every country of the
world, coca cola portfolio also includes unique for each individual market. These are drinks
that once lived their “independent” life, are popular with buyers in a certain region, and
then brought buy coca cola and now successfully continue to exist in the market. And often
the consumer does not realize that his favourite drink is now bottled at one of the factories

owned by coca cola for example Inca Kola and others.The committee of Coca Cola
company represents and assist the Board in fulfilling its oversight responsibility to the
integrity of the company’s financial statements and the financial reporting process, the
systems of internal accounting and financial controls, the internal audit function, the annual
independent audit of Company’s financial statements, the Company’s compliance with
legal and regulatory requirements, and its ethics programs as established by management
and the Board, including the Company’s Code of Business Conduct. The committee shall
also oversee the independent auditors’ qualifications and independence.
1.3 Definitions,Acronyms,and Abriviations:
PHP A sever scripting language used by Drupal
OS Operating System
ERD Entity Relationship Diagram
DB Database

OCCCMS Online Coca Cola Company Management System
ERD Entity Relationship Diagram
DB Database
1.4 References
www.oxfordreference.com
www.nndb.com
www.coca-colacompany.com
IEEE STD-830-1998, “IEEE Recommended practice for software requirement

specification” 1998 Edition, IEEE, 1998
1.5 Overview
In the first section we see the introduction, scope and purpose of the SRS that we
write about Online Coca Cola Company management System. The section 2 of SRS is
describing the overall description of product prospective, product function, user
characteristics and assumptions. The 3rd section of SRS consists of specific requirements
of project. Don’t rehash the table of contents here. Point people to the parts of the document
they are most concerned with. Customers/potential users care about section 2, developers
care about section 3.The section 4 provides the non-functional requirements. Section 5 of

this SRS shows the class diagrams and section 6 the use case diagrams. Then the
appendices appear next.
2.The Overall Description

Coca Cola company world’s largest manufacturer, distributor and marketer of
concentrates syrups used to produce nonalcoholic beverages.Coca-Cola has relied on
independent bottling franchises, and this system has served us well. Created in 1886 in
Atlanta, Coca-Cola was first offered as a fountain beverage at Jacob’s Pharmacy by mixing
Coca Cola syrup with carbonated water.The demand of Coca Cola increased.The company
quickly out grow its facilities. A new building erected in 1898 was the first headquarters
building devoted exclusively to the production of syrup and the management of the
business.The product has been put into perspective through a detailed assessment of the
system, user, hardware, software and communication interfaces, memory considerations,
operational modes and site adaptation requirements. Further, characteristics of the system’s
end-users are discussed along with the identified system constraints and assumptions. To
conclude the section, an apportioning of requirements has been outlined.
2.1 Product Perspective

Coca Cola is the most popular and biggest-selling soft drink brand in history.
The Coca-Cola Company’s core is, the production, marketing and selling of many of the
world’s most beloved beverages .Historically, for the bottling of our beverages. The
perspective of coca cola to focus on key areas of profit, people and partners.Coca Cola also
also focused on its marketing efforts as a part of advertising strategies. Coca Cola company
business strategy focuses on building its existing brands and broadening of its family
brands, products and services.The core capabilities of Coca Cola are consumer marketing,
commercial leadership, franchise leadership, bottling, and distribution operations.Coca

Cola introduced productivity and reinvest program to strengthen the brands and reinvest
resources to derive long term profitable growth.The software described in this SRS is the
software for a complete OCCCMS system.
2.2 Product Functions

It is a tool through which customers or any.one can search about coca cola
company. This tool provides their customers to see all coca cola soft drink brands and
they can buy their favourite one by online order like coca cola, coca cola zero sugar, diet
coke vanilla coke etc. Similarly consumers can give their feedback after their experience
that is online soft drink order then the company enhance the products according to
consumers demands which increase the company’s reputation . This tool provides
company details like history its brands detail about products prices and quality of
products. different prices may be gain if the Coca-Cola sells in the bazaar or market
because the price of product various according to their price size and place.
All bottling partners work closely with customers--grocery stores, restaurants,

street vendors, convenience stores, movie theaters and amusement parks, among many
others--to execute localized strategies developed in partnership with our Company. AH,
finally the real meat of section 2. This describes the functionality of the system in the
language of the customer. What specifically does the system that will be designed have to
do? Drawings are good, but remember this is a description of what the system needs to
do, not how you are going to build it. (That comes in the design document).

2.3 User Characteristics

The end-users of the OCCCMS fall into three primary categories, unskilled, partly
skilled and highly skilled.The users of the surface computers are walk-in customers and
should therefore be assumed to have no relevant prior skills or education other than basic
abilities to operate an automated system; no more complex than a parking meter or vending
machine. The partially skilled users must be able to explain all elements of the user
interfaces except the server. Supervisors also fall into the same category, though they will
have to learn other sections of the system (refunds etc); these should not be of notably
greater complexity than the standard functions. This class of user would be expected to
have a junior high-school certificate education or equivalent. This class of user is expected
to have a high-school certificate or equivalent, as well as extensive computer experiences
and they can easily handle errors that occur.
2.4 General Constraints

Coca-Cola’s marketing strategies, including memorable advertising slogans,
catchy jingles, and sporting event sponsors, played a significant role in winning the hearts
and minds of consumers globally. Technology advances, including product transportation,
telecommunication, and computerization, became the driving force behind Coca-Cola’s
ability to capitalize on the rapidly expanding marketplace across the globe.It also increased
health information concerning obesity deterring consumers and untapped segments
reluctant to associate with coca cola that are the company’s constraints. General constraints
of this system is that the system provide web access for all customers. The user interface

will be enough so that no training is required by customers or administrators. Software will

work on windows XP, 7, 8, 10, and also required internet connection. The main Constraint
here would be the checking the genuineness of the buyer, which is not always possible.
There can be security risk involved.
2.5 Assumptions and Dependencies

The preparation of our consolidated financial statements requires us to
make assumptions and dependencies that affect the reported amounts of assets, liabilities,
revenues and expenses and the disclosure of contingent assets and liabilities in our
consolidated financial statements and accompanying notes. The discount rate
assumptions used to account for pension and other post retirement benefit plans reflect
the rates at which the benefit obligations could be effectively settled. The rate of
compensation increase assumption is determined by the Company based upon annual
reviews. We review external data and our own historical trends for health care costs to
determine the health care cost trend rate assumption.
1. Specific Requirements
Depending on the system being described, different categories of
requirements are appropriate. System Owners, key End-User, Developers, Engineers, and
Quality Assurance should all participate in the requirement gathering process, as
appropriate to the system.The following section presents the complete set of functional
and non-functional requirements identified for the subject OCCCMS. Functional
requirements are listed first, according to their relationship to the overall system,
customers, owner, End users, Developers etc. The non-functional requirements that
pertain to safety, security, the interface, human engineering, qualification, operation,
maintenance and performance are subsequently presented. The functional requirements

have been specified using a natural language description and as such, the reader is
directed to Section 4 (UML Analysis Models) for further detail.
3.1 External Interface Requirements
3.1.1 System Interfaces

Marketing initiatives, words, images, audio and video materials Coca-
Cola employs tries to communicate a message that this drink satisfies the thirst in the
best possible manner and partially for this reason Coca-Cola is consumed by millions of
people per day.The system interface provides facilities to the user for interaction such as
graphics, sound, position, movement, so the user can easily understand without any
difficulty.
3.1.2 Interfaces
The Public Affairs and Communications (PAC) Manager will serve as a
generalist in support of our corporate efforts to create an environment in which our
business, across all categories, can grow unencumbered, with a particular focus on the
sparkling category.

3.1.3 Hardware Interfaces

Coca-Cola Company has been using all six hardware categories, such as,
Input, Output and Storage devices, central processing unit, telecommunications and
connecting devices. Every of these categories is very important and can’t be isolated.
3.1.4 Software Interfaces

Coca-Cola Enterprises is the world’s largest marketer, producer, and
distributor of Coca-Cola products. Using Microsoft Online Services technologies, CCE
is able to save travel expenses through online meeting tools and collaboration platforms
that span time zones and geographies. Another Important software used is STATISTICA
data miner to analyze, organize and understand the raw data it collects from its different
sources.
3.1.4.1 Microsoft SQL Server 7

The system must use SQL Server as its database component.

Communication with the DB is through ODBC connections. The system must provide
SQL data table definitions to be provided to the company DBA for setup.A key point
to remember is that you do NOT want to specify software here that you think would be
good to use. This is only for customer-specified systems that you have to interact
with. Choosing SQL Server 7 as a DB without a customer requirement is a Design
choice, not a requirement. This is a subtle but important point to writing good
requirements and not over-constraining the design.
3.1.5 Communications Interfaces

Specify the various interfaces to communications such as local network
protocols, etc. These are protocols you will need to directly interact with. If you happen
to use web services transparently to your application then do not list it here. If you are
using a custom protocol to communicate between systems, then document that protocol
here so designers know what to design. If it is a standard protocol, you can reference an
existing document or RFC.

3.2 Functional Requirements

Functional requirements should include functions performed by specific
screens, outlines of work-flows performed by the system, and other business or
compliance requirements the system must meet.
3.2.1 Administrator Login

3.2.1.1 Introduction
This functional feature deals with the end-user (can also be used by the
administrator) and is facilitated by the interface of the Larvae system. Users login in the
system to use their account and perform some different operations on it. A user may post
a tweet or re tweet or delete a post.
3.2.1.2 Inputs
User Information – user email id, user password and may be some user name.
System Information – provide information to user that the user wants from system.
3.2.1.3 Processing
The system decides whether the user wants to login into the system is the valid
user or not. System accepts or rejects the user on the behalf of user id or password. If
user use valid id or password then accepts otherwise reject.
3.2.1.4 Outputs

- System accepts or rejects the user id or password

- User is valid or not
3.2.1.5 Error Handling

If user is not valid or enter wrong password or email id then inform to user the
email id or passwords is incorrect reenter your password and email id.
3.2.2 View Account

This feature will allow the user or administrator to view details about the account that
have been submitted, and the progress of the execution of the account.
3.2.2.2 Input
Email id and password of user use as input to enter in the account
3.2.2.3 Processing
Show all the available user options that the user performs by using their account.
3.2.2.4 Output
User view all the available options that system available to user.

If user performs any function that the system will not allow to user then an error generate
and say this function is not in your range.
3.2.3 Product Information

This feature provides function to user to provide the information about the
product.If any user get information of product. And may be user’s buy product
according to information.
3.2.3.2 Input
User gets data about product to system
.
3.2.3.3 Processing
System process the product information.
3.2.3.4 Output
User get product successfully.s

If any error occurs when product not available .

3.2.4 Updated Account

This website from which you are accessing these terms of Use (“Site”)is created and
maintained by the Coca-Cola Company (referred to below as “Coca-Cola”,”we”,and “us”).
3.2.3.2 Input
Email id and password to ensure that the appropriate user is able to update the account.
3.2.3.3 Processing
Update the data of the user from the databases.
3.2.3.4 Output
When update data from databases and the account of user will be update then show
message to user that the account or post deleted successfully.

If any error occurs when update any post or account the system control it and
show appropriate message to user an error occurred due to some reason wait until the
error remove from system.

3.2.5Registration
If customer wants to buy the product then she/he must be check the product
must be registered, unregistered.
3.2.5.2 Inputs
The user must be check the product if she/he wants to purchase the any product. It is
necessary to enter the code of product.
3.2.5.3 Processing
The customer, product and buyer information should be stored on database.
3.2.5.4 Outputs
If he/she successfully check the product will be original then he will able to get the
items if counterfeiting product field’s message displayed.

The without code product are not allowed.
3.2.6User check Products and Brands

This website in our concentrate operations, we typically generate net operating
revenues by selling concentrates and syrups to authorized bottling and canning operations (to
which we typically as our “bottlers” or our “bottling partners”).

3.2.6.2 Input
Our finished product operation consists primarily of our Company-owned or
controlled bottling,sales and distribution operation.
3.2.6.3 Processing
Consumer demand determines the optional menu of Company product offering.
3.2.6.4 Output
Generally, finished product operations generate higher net operating revenues but
lower gross profit margins than concentrate operations.
3.2.7Payment
For customer there are many type of safe billing will be prepaid as debit or
credit card, postpaid as after shipping, check or bank draft. The security will provide
by the third party like Pay-Pal etc.
3.2.7.2 Inputs
The customer should give her/his bank account number, check and debit or
credit card information to make payment possible.
3.2.7.3 Processing
Verifies the user account no. and credit card to check is it is legal or valid and
have enough balance to pay about her/his purchase.

3.2.7.4 Outputs
If the customer’s credit card account number details is correct and have
balance according to her/his purchase then she/he should be able to buy product
otherwise error occur.
3.2.8Administrator Logout
Administrator logout from the system after use their account and perform some
different operations on it.
3.2.8.2 Inputs
Administrator click on the logout button to log out from the system
3.2.7.3 Processing
All the administrator account detail will be hide from site
3.2.8.4 Outputs
Administrator can successfully logout from the system

3.2.9: Contact Us
Users can also contact us by clicking on Contact us option. in this page fax no,
contact number, mailing address is available through this user can contact.
3.2.9.2 Inputs
User can click on the contact us page
3.2.9.3 Processing
Contact us page will be ready to opened for the user
3.2.9.4 Outputs
Contact us page will be successfully opened
3.2.9.5Error Handling
If any error occurs when opening contact us page system control it and show
appropriate message to user an error occurred due to some reason wait until the error
remove from system.
3.3 Use Cases

This section contains use cases of the OCCCMS system .It is a methodology of
system analysis to identify and clarify and organize system requirements. The use case is
made up of a set of possible sequences of interactions between systems and users in a
particular environment and related to a particular goal.

3.3.1 Login
System
login
User User
Administrator customer Administrator customer

Steps Post Precon Act
conditio dition or
n
SRS Document 1.0

3.3.2 Search Product
1. User Ad
click mini
strat
s the or,
login Cust
ome
optio
r
n
User
Page 32 of 84
and will be
enter login or User
redirecte wants to
s the d to login.
ID login
page.
and
pass
word
.
2. Syste
m
chec
05/08/24
System
search Product
user
user
1.
2.
3.
4.
3.3.3 Search Product By Id

System
search product by ID
User
User
1.
2.
3.
3.3.4 View Details

System
view details
customer
customer

3.3.5 Online Order
System
login
<<include>>
online order
User <<include>>
logout
3.3.6 Registration

System
login
<<include>>
Registration
customer
<<include>>
logout
1.
2.
3.
4.
3.3.7 Payment

System
login
<<include>>
payment
customer customer
<<include>>
logout
1.
2.
3.
4.
5.
3.3.8 Add Product

System
login
<<include>>
Add product
Administrator customer
<<include>>
logout
inistr
Adm
syste
Prec
want
ondi
Prod
tion
new
ator
uct.
add
s to
the
of
m
1.
2.
3.
3.3.9 Delete Product

System
login
<<include>>
Delete Product
Administrator
<<include>> customer
logout
3.3.10 Update Product Details

System
login
<<include>>
Update Product Details
Administrator User
<<include>>
logout
1.
2.
3.
3.3.11 Cancel Registration

System
login
<<include>>
cancel registration
customer customer
<<include>>
logout
1.
2.
3.
4.
3.3.12 Special Offers

System
login
<<include>>
special offers
<<include>>
logout
1.
2.
3.
3.3.13 Add ads

System
login
<<include>>
Add Adds
<<include>>
logout
1.
2.
3.
3.3.14 User Feedback

System
User Feedback
customer Administrator
1.
2.
3.
3.3.15 Contact Us

System
Contact Us
customer 1. customer
2.
3.
3.3.16 Send Email to Customer

System
login
<<include>>
Send Email
<<include>>
logout
1.
2.
3.
4.
3.3.17 Logout
System
logout
User User

1.
2.
3.4 Classes / Objects 3.
A class diagram in the Unified Modeling Language (UML) is a type of
static structure diagram that describes the structure of a system by showing the system's
classes, their attributes, operations (or methods), and the relationships among objects.
The purpose of this diagram is to show how objects within the OCCCMS will interact
with each other in order to achieve the functionality required by the Use Case diagrams.
This section contains major classes of the Online Coca Cola Company Management
System
3.4.1 Login Credentials

LoginCredentials
+username
-password
-phoneNumber
-emailId
+login()
+logout()
+forgetPassword()
+resetPassword()
3.4.2 Registration

Registration
+userName
-userId
-phoneNumber
-nicNumber
+gender
+address
+dateTime
+durationOfRegistration
+signUp()
+confirmRegistration()
+cancelRegistration()
3.4.3 User
User
+userName
+userType
-userId
+userAddress
+userLogin()
+userRegistration()
+viewSearchresults()
+viewProducts()

3.4.3 Database
Database
+userName
+password
+databaseName
+phpAddress
+insertRecord()
+deleteRecord()
+searchRecord()
+updateRecord()
+fetchRecord()
3.4.3 Administrator
Administrator
+name
-Password
-phoneNumber
+email
+login()
+addProduct()
+deleteProduct()
+updateProduct()
+sendEmail()
+specialOffers()
+logout()

3.4.4 Product

Product
+pName
+pId
+pCode
+pDescription
+price
+getcode()
+setcode()
+getdescription()
+setdescription()
+addproduct()
+deleteproduct()
+specialoffers()
+updateproduct()
3.4.5 Soft Drink

SoftDrink
+name
+price
+size
+category
+expiryDate
+manufacturingDate
+order()
+deleteOrder()
+calculatePrice()
+changeOrder()
3.4.6 Coca-Cola
CocaCola
+price
+size
+order()
+deleteOrder()
+calculatePrice()
+changeOrder()
3.4.7 Fanta

Fanta
+price
+size
+order()
+deleteOrder()
+calculatePrice()
+changeOrder()
3.4.8 Sprite
Sprite
+price
+size
+order()
+deleteOrder()
+calculatePrice()
+changeOrder()
3.4.8 Juice

Juice
+name
+price
+size
+category
+expireDate
+manufacturingDate
+order()
+deleteOrder()
+calculatePrice()
+changeOrder()
3.4.9 Simply Orange
Simply Orange
+price
+size
+order()
+deleteOrder()
+calculatePrice()
+changeOrder()
3.4.10 Minute Maid

Minute Made
+price
+size
+order()
+deleteOrder()
+calculatePrice()
+changeOrder()
3.4.11 Water
Water
+name
+price
+size
+category
+expireDate
+manufacturingDate
+order()
+deleteOrder()
+calculatePrice()
+changeOrder()
3.4.11 Dasani

Dasani
+price
+size
+order()
+deleteOrder()
+changeOrder()
+calculatePrice()
3.4.11 vitamin Water
Vitamin Water
+price
+size
+order()
+deleteOrder()
+changeOrder()
+calculatePrice()

3.4.12 Customer
Customer
+firstName
+lastName
-phoneNumber
-cnic
+email
-customerId
+address
+login()
+logout()
+registration()
+visitWebsite()
+viewReviews()
+giveReviews()
+payMoney()

3.3.13 Order
Order
-orderId
-customerId
-customerName
-shippingDate
-productid
+productPrice
+totalPrice
+getOrder()
+setOrder()
+getCustomerName()
+setCustomerName()
+getCustomerId()
+setCustomerId()
+getshipingDate()
+setshippingDate()
+getPrice()
+setPrice()
+calculatePrice()
3.3.14 Payment

Payment
+productId
+userId
+userName
+accountNumber
+signUp()
+confirmPayment()
+transactionFailed()
3.4.15 Account Details
AccountDetails
+userId
-cardNumber
+cardExpirationDate
+viewAccount()
+updateAccount()
+viewAccountDetails()

3.4.16 Feedback
Feedback
+productId
+userId
+userName
+dateTime
+sendFeedback()
+cancelFeedback()
3.4.17 Reporting
Reporting
+reportTitle
+dateTime
+category
+lastYearsignUp()
+lastYearCustomerResponces()
+currentYearCustomerResponce()
+lastYearProductSale()
+currentYearProductSale()

3.3.18 Shipping
Shipping
+customerName
+location
+customerEmail
+quantity
+orderTime
+deliveryDate
+shipping()
+shippingCharges()
+addShippingDetails()
+deleteShippingDetails()
+updateShippingDetails()
3.3.19 Supplier
Supplier
+supplierId
+supplierName
-supplierPhoneNumber
+workArea
+supplyItem()
+takePayment()
+deleteSuplyDetails()
+addSupplyDetails()
+updateSupplyDetails()

3.5 Non-Functional Requirements

Non-functional requirements are the constraints or restrictions under which the
developed system (Software) must operate. Non-functional requirements are also known as
quality attributes .Nonfunctional requirements of Coca-Cola‟s Management Accounting
Information system are as follows.
3.5.1 Performance
OCCCMS Performance will be as high as possible. 90% of transaction shall be
processed in less than a second. System will responses with in time take less processing
time and will have high response time. System will not be slowed down if multiple user
accesses it at same time
3.5.2 Reliability
OCCCMS will take initial loading time depending on internet speed. The
performance will depend upon hardware components of the client/customer. System will
have lesser mean time to recover (MTR) and have high mean time between failure
(MTBF).
3.5.3 Availability
The system will be available to the user 24 hours a day 7 days a week as per
internet connection. System’s downtime may not exceed 5 minute per day, > 30 day
MTBF value. In case of any failure or database corruption backups of database can be
retrieved.

3.5.4 Security
The system must be secure for the users. The system’s back-end can only be
accessible by authenticated administrator that can login by providing ID and password.
Customer can have access only to view her/his account by logging in to the system.
3.5.5 Maintainability
The system must be maintainable. In case of any error in the system, it will be
repaired as soon as possible. Software design is being done with modularity so that its
maintainability can be done efficiently.
3.5.6 Portability
An OCCCMS is a web based system so its user end is portable. End user can use this
system on any operating system i.e. Linux or Windows having internet connection.

3.7 Logical Database Requirements

4. Analysis Models
Sequence Diagram shows how events move from object to object to object. How
events cause flow from one object to another in the time period. Sequence diagram is a
short representation of use case activities. Once a complete sequence diagram has been
developed, all of the events that cause transitions between system objects can be collated
into a set of input events and output events (from an object).
4.1.1 Administrator’s Login, logout, Add, Delete, Update Product Details
: Administrator : LoginCredentials : Product : Database
1 : Login()
2 : verifyLogin()
3 : FetchRecord()
5 : LoginSuccessfully() 4 : RecordExist
6 : AddProductDetails()
7 : InsertRecord()
8 : RecordInserted
9 : DeleteProductDetails()
10 : DeleteRecord()
11 : RecordDeleted
12 : UpdateProductDetails()
13 : RecordUpdate()
14 : RecordUpdated
15 : Logout()
16 : LogoutSuccessfully

4.1.2 Customer Registration Login and Logout
: Customer : Registration : LoginCredentials : Database
1 : SignUp()
2 : InsertRecord()
4 : Confirmation 3 : AcknowlegementOfRegistration
5 : Login() 6 : VerifyLogin()
7 : FetchRecord()
8 : LoginSuccessfully 9 : RecordExist
10 : Logout()
11 : LogoutSuccessfully

4.1.3 Place Order
: Customer : LoginCredentials : Order
1 : Login()
2 : VerifyLogin()
3 : LoginSuccessfully
4 : PlaceOrder()
5 : ConfirmOrder()
6 : DisplayForm
7 : FillUpForm()
8 : SubmitForm()
9 : PlaceOrderSuccessfully
10 : Logout()
11 : logoutSuccessfully

4.1.4 Payment

: Customer : Payment : AccountDetails : Database
1 : SignUp()
2 : VerifyAccountDetails()
3 : FetchRecord()
5 : PaymentPaidSuccessfully 4 : RecordExist

4.1.5Manage Database
: Administrator : Login : Database
1 : Login()
2 : verify login()
3 : Login successfully
4 : Manage Database()
5 : Manage Database()
6 : Manage Database Successfully
7 : LogOut()
8 : Logout successfully

4. Data Flow Diagrams (DFD)

Diagram that is used to show the data flow between external sources and
processes and data store with in a system. It is consists three levels Level 1, Level 2 and
Level 3.
4.2.1DFD Level: 0

DFD Level: 2

DFD Level: 3

7 State-Transition Diagrams (STD)

State diagram is a graph in which nodes correspond to states and arcs
correspond to transitions labeled with event names. A state diagram combines states and
events in the form of a network to model all possible objects.
7.1 Login
Enter Id and Password
Get Details
verify Details
False True
Rejected Login
7.1.2View Details and Select Product

Login View Product Details
Select Product
Check Availability
Select For New Item

Not Available
Available
Select Successfully
No
Logout
7.1.3 Payment

Select View Products
If User Wants To Purchase Product
Login
Request For Purchase Product
Fill The Form
After Fill Up Form
Make Payment
select Product
On Click Place Order
Confirm Order Place Order

7.1.4 View Record in Database
Login
Click View Record In Database
Enter User Id
Check Existance
Not Exist
Exist
Show Results

7.1.5 Update Database
Login
Get User Id
Get User Data Store in Database
Error Check Constraints
No error
storred succesfully

4.3.7 Logout
Click On Logout No
Yes
Logout Successfullyy

Online Coca Cola Company Management System SRS

Uploaded by

Copyright:

Available Formats

Online Coca Cola Company Management System SRS

Uploaded by

Document Information

Original Title

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

Online Coca Cola Company Management System SRS

Uploaded by

Copyright:

Available Formats

Online coca cola company Management System

Online Coca Cola Company Management System

Software Requirements Specification Document

[Sheeba Noureen RollNo 183211]

SRS Document 1.0 Page 1 of 84 05/08/24

Signature Printed Name Title Date

SRS Document 1.0 Page 2 of 84 05/08/24

SRS Document 1.0 Page 3 of 84 05/08/24

SRS Document 1.0 Page 4 of 84 05/08/24

SRS Document 1.0 Page 5 of 84 05/08/24

SRS Document 1.0 Page 6 of 84 05/08/24

SRS Document 1.0 Page 7 of 84 05/08/24

3.2.18.5 Error Handling 23

SRS Document 1.0 Page 8 of 84 05/08/24

3.3.7 Manage Orders 3

SRS Document 1.0 Page 9 of 84 05/08/24

SRS Document 1.0 Page 10 of 84 05/08/24

4.2.2 Context Diagram of Online coca cola company 62

4.2.3 Level 1 Diagram of Online coca cola company 63

4.2.2 Context Diagram of Online coca cola company 62

4.2.3 Level 1 Diagram of Online coca cola company 63

4.3 State Transition Diagram 64

4.3.1 State Transition Diagram of Registration 64

SRS Document 1.0 Page 11 of 84 05/08/24

SRS Document 1.0 Page 12 of 84 05/08/24

SRS Document 1.0 Page 13 of 84 05/08/24

1.3 Definitions,Acronyms,and Abriviations:

PHP A sever scripting language used by Drupal

ERD Entity Relationship Diagram

SRS Document 1.0 Page 14 of 84 05/08/24

OCCCMS Online Coca Cola Company Management System

ERD Entity Relationship Diagram

IEEE STD-830-1998, “IEEE Recommended practice for software requirement

SRS Document 1.0 Page 15 of 84 05/08/24

2.The Overall Description

2.1 Product Perspective

SRS Document 1.0 Page 16 of 84 05/08/24

2.2 Product Functions

All bottling partners work closely with customers--grocery stores, restaurants,

SRS Document 1.0 Page 17 of 84 05/08/24

2.3 User Characteristics

2.4 General Constraints

SRS Document 1.0 Page 18 of 84 05/08/24

will be enough so that no training is required by customers or administrators. Software will

2.5 Assumptions and Dependencies

SRS Document 1.0 Page 19 of 84 05/08/24

3.1 External Interface Requirements

3.1.1 System Interfaces

SRS Document 1.0 Page 20 of 84 05/08/24

3.1.3 Hardware Interfaces

3.1.4 Software Interfaces

3.1.4.1 Microsoft SQL Server 7

SRS Document 1.0 Page 21 of 84 05/08/24

The system must use SQL Server as its database component.

3.1.5 Communications Interfaces

SRS Document 1.0 Page 22 of 84 05/08/24

3.2 Functional Requirements

3.2.1 Administrator Login

SRS Document 1.0 Page 23 of 84 05/08/24