I.
Project Description
And Objective
1
1. Problem Statement
The existing system works manually. The existing system has got lot of intricacies within itself
and need lot of human effort and paper works. All of the above data needs to be maintained on
ledgers and maintaining this is a tedious and risky process. As the transactions increases, so the
data too. So the task of maintaining them increases exponentially. To view a data may need lot of
paper to be searched.
Some of the negative aspects of the existing system are as follows:
1) Course of action is time consuming. Wherever a need for search arises, the process evolves
search through paper records.
2) Readability of records is constrained. All the records may not be handled or written by the
same person. So the format and style of records differ and hence it is difficult to understand.
3) Paper records are easily damaged in course of time. The life time of paper record is unreliable
and it easily gets spoiled.
4) Expenditure is high. Manual system heeds added man power.
5) Prone to corruption by unauthorized users. Securing of manual system is not fully guaranteed.
Inaccuracy can be expected. Data can get easily scratched.
6) Techniques used are more complicated. Proper techniques are not exposed, so the functioning
is intricate.
7) To overcome these, the proposed system has been suggested.
2. Background
The proposed system is a computerized one which has greater accuracy and efficiency. It takes
only limited time for calculation.
The proposed system can be used to efficiently maintain the HR Department schedule of any
type of company. In larger organizations employees are large,at that time also the proposed
system is useful and helpful. HR Management System is not only a desire of the company but it
is the need of the company.
2
3. Objective of the project
Our objective is to look at online retail from a customers point of view and determine which of
the biggest US-based e-commerce sites was providing the best customer experience. Our
secondary aim was to zero in on a key trend and identify opportunities for high-impact customer
experience improvements.
4. Stakeholders
The following are the stakeholders in this project:
Admin Admin or administrator will be a single or group of person in an organization
that are given access by the company heads to deal with critical data of the organization
and take due action on this data. Helping general users in getting their issues resolved.
They are given full access to handle any data from the back-end.
General Users These are the target and bulk user of the system. System is being
developed for these users only. Other stakeholders are just to support these users. They
are given basic training on how to use this application. Their access level is restricted,
mostly pertaining to their own tasks only.
5. Functionality
The user gets into the system using user name and a unique password. Each user has his/her own
accessibility permission to accomplish his/her task flawlessly.
Advantages of the proposed system are
1) Easy access to the data.
2) The new system is more user friendly, reliable and flexible.
3) Pop-up menus to carry out transactions for a new user, and for other alert messages.
4) Timely report generation.
3
4
1. Introduction
An extremely powerful marketing tool, e-marts ability to suggestively sell alternate and
complementary products; e.g. if a customer selects the standard version of a product, you can
recommend that they also consider the pro version or if your customer chooses a pair of pants,
you can suggest that they also consider a belt and socks.
1.1. Purpose
The purpose of this document is to present a detailed description of the Shopping Cart. It will
explain the purpose and features of the system, the interfaces of the system, what the system will
do, the constraints under which it must operate and how the system will react to external stimuli.
The final product will be having only features mentioned in this document and assumptions for
any additional functionality/feature should not be made by any of the parties involved in
developing/testing/implementing/using this product. This document is intended for both the
stakeholders and the developers of the system and will be used for further development of the
software as a legal agreement.
1.2 Scope of Project
An extremely powerful marketing tool, e-marts ability to suggestively sell alternate and
complementary products; e.g. if a customer selects the standard version of a product, you can
recommend that they also consider the pro version, or if your customer chooses a pair of pants,
you can suggest that they also consider a belt and socks.
1.3 Definitions, Acronyms and Abbreviations
User: These are the general user using the shopping cart application for shopping purpose.
Stakeholders: Administrator, Users, Developers and the intended company for which the
Shopping Cart is developed,and have some sort of stake in this web-application software.
Administrator: The person responsible for managing the whole system. In our case he/she is the
head or an appointee in the admin department or IT department of the company. Note that there
can be multiple users (both admin/normal users).
Developer: The persons who builds the software. In the Shopping Cart, developer is the
company/organization/person who has developed the system.
1.4. References
5
Books on Online Order Processing & Payment System (Shopping Cart).
IEEE recommended practice for Software Requirements Specifications.
1.5. Overview
The category screen shows all of the products available for a particular category. The product
screen shows all of the items in a particular product. Product screens left column of the list
shows the price of the item, and includes a link labeled Add to Cart. This link, which also
appears on screen for the corresponding item, allows the customer to add the item to the cart
without looking at the item details. The Add to Cart link, when clicked, adds an order for the
item to the shopping cart, and then shows the shopping cart contents.
The cart screen lists the items currently in the cart, allows the customer to change the quantity of
each item ordered, and shows a title. It also includes a link to remove the item from the cart, and
a link Proceed to Checkout which, when clicked, shows the order information screen if the
user is signed in and reaches PayPal for checkout for completion of the transaction.
The sign in screen allows an existing customer to sign in as an existing user, and a new
customer to create an account. An existing customer enters a user name and password, and the
application displays the Order Information screen . A new customer enters a user name and
password and clicks the button Create New Account. The application creates a user with the
requested password. If user creation succeeds, the application displays the Account
Information screen. The account information screen, collects information about a new
customer, including contact information, a credit card, and personal preferences. This is also the
screen displayed whenever the customer clicks the Account link at the top right corner of the
screen (beneath the Search box).
The Order Information screen allows the user to enter the billing and shipping address.
Default values for address comes from the contact information of the currently signed-in
customer. This information is transmitted to the application when the user clicks Submit. The
application creates a new order, sends it to the order processing center, and displays the Order
Complete screen. The Order Complete screen verifies to the user that the order has been
placed. The screen includes the transaction number.
2. Overall Description
2.1. Product Perspective
6
Our objective is to look at online retail from a customers point of view and determine
which of the biggest US-based e-commerce sites was providing the best customer
experience.Our secondary aim was to zero in on the key trends and identify
opportunities for high-impact customer experience improvements.
We examined the entire experience. Unlike some studies that focus only on browsing,
we looked at the entire experience from the first moment on the site through selection,
purchase, shipping and returns.
We combined objective measurement with expert subjective analysis. Metrics have
a strong appeal, but in something that involves as many intangibles as the computer
experience measurement can only take you so far. With this in mind, we split our
analysis between straightforward objective grading and the expert opinions of our
panelists.
2.1.1. User Interface:
The system is provided with click and go type of graphical user interface with buttons and
links that can be easily understood by the user so that the errors in the entering the date in
appropriate fields can be reduced.
The system is designed in such a way that a user without any computer knowledge can also use
the system with the aid of a help file that is also called as user manual. A menu interface has
been provided to the client that is compatible with windows environment and is designed to be
user friendly.
The client is provided with an introductory help about the client interface and the user
documentation has been developed through help menu. The system is user-friendly and the
system can be implemented on any software environment.
2.1.2. Hardware Interfaces:
Main Processor Pentium IV
Hard-disk Capacity 8 GB
RAM 256 MB
Clock Speed 2.8 Hz
Floppy Drive 1.44 MB
Keyboard 104 Keys
7
Software Requirement
Operating System - Window 8
Back End Tool - MySQL 5.7.14
Front End Tool - PHP 7
2.1.3. Software Interfaces:
Database : MySQL 5.7.14
IDE : Sublime Text 3
Language : PHP 7
Framework : J-Query, AJAX
Server : WAMPSERVER 3.0.6
2.1.4. Communication Interfaces: None.
2.1.5. Memory Constraints:
Hard Disk Space: 8 GB or more.
RAM: 256 MB or more.
2.1.6. Operations: None.
2.1.7. Project Adaptation Requirements:
The work-station will have to support the hardware and software interface specified in above
sections.
2.2. Product Functions
8
The system will allow access only to authorized personnel with specific roles (Administrator,
Users). Depending upon the users role, he/she will be able to access only specific modules of
the system. A summary of the major functions that the software will perform is given below:
User (Administrator, users) will be able to log into the online application by entering
their credentials on the log-in page.
User (Administrator, Users) will be able to see a customized homepage according to
their respective roles in the system.
Admin will be able to see a list of all the issues raised by several users in the company
in a data-grid format and can manage these issues from the screen itself.
Admin will be able to see list of all notices by the control in a data-grid and can manage
these notices from the screen itself.
2.3. User Classes and Characteristics
There are various kinds of users for a product. Usually web products are visited by various
users for different reasons. The users include:
Developer: This is not a user of the system in particular,this is the developer of the
system who uses the system to check whether the system developed is correct or not.
Administrator: The task of Administrator consists of all tasks of the Shopping Cart
Application which allows it to manage all products along with other functionality of a
normal user.
Users: Users can access the products from the company through the site, he/she can
browse according his/her own choice.
Characteristics:
Developer:
1. They have full knowledge about the Shopping Cart application and have complete
access over the software and can make necessary changes to the server-side coding of
the web-application developed.
2. They can make changes to the database internally and can create or drop database at
will.
Administrator:
9
1. They have full knowledge about Shopping Cart application and have complete
access over the software.
2. They cannot make changes to the database internally.
3. They manage all the items of the system.
4. They have access to view data of all other products and monitor their activity.
Users:
1. They just deal with specific task related to themselves.
2. These users are present in bulk in the system and are inclined towards their own ease
to manage organizational tasks.
3. They cant create a new user for the system.
2.4. Constraints
Users at company will have to implement a security policy to safeguard their status information
from being modified by unauthorized users (by gaining access to the back-end database).
2.5. Assumption and Dependencies
Only a limited number of features are considered while development of this Shopping
Cart as it is only intended to be used by small companies with small work force.
The product needs no third party products pre- installed on the workstation. But do
requires a standard browser like IE, Firefox, etc. that can effectively handle the web UI
of the application.
2.6. Apportioning of Requirement Not Required.
3. Specific Requirements
This section contains the software requirements to a level of detail which would be
sufficient to enable the designer to design the system, and the tester to test that system.
10
11
12
13
