SYSTEM REQUIRMENT SPECIFICATIONS FOR

eCommerce Application
PURPOSE OF THE SYSTEM
eCommerce Application is used to assist people making purchases online.
The Business-to-Customer aspect of electronic commerce (e-commerce) is the most
visible business use of the World Wide Web. The primary goal of an e-commerce site is
to sell goods and services online.
E-commerce is fast gaining ground as an accepted and used business paradigm. More
and more business houses are implementing web site providing functionality for
performing commercial transactions over the web. It is reasonable to say that the
process of shopping on the web is becoming commonplace.
Shopping Cart feature allows online shopping customers to place items in the
cart. Upon checkout the software calculates as total for the order including shipping
and handling postage, packing and taxes, if applicable.

The Shopping Cart is very

important feature used in e-commerce to assist people making purchases products

online. It provides the user a catalog of different products available in the system. In
order to purchase a shopping cart is provided to the user. The shopping cart application
has been developed to allow business grows larger and faster.

This site will let

customers to view and order products online from any part of the world. Under this
website many products and services can be ordered. The shopping cart is expanded
permanently through new products and services in order to offer a product portfolio
corresponding to the market.
PROBLEMS IN THE EXISTING SYSTEM:

It is limited to a single system.

It is less user-friendly.

It is having lots of manual work (Manual system does not mean that you are working
with pen and paper, it also include working on spread sheets and other simple
software's).

The present system is very less secure.

It is unable to generate different kinds of report.

User must go to shop and order products.

It is difficult to identify the required product.

Description of the product obtained only on manually.

Accuracy not guaranteed.

Not in reach of distant users.

SOLUTION OF THESE PROBLEMS

The development of the new system contains the following activities, which try to
automate the entire process keeping in view of the database integration approach.

User friendliness is provided in the application with various controls.

The system makes the overall project management much easier and flexible.

It can be accessed over the Internet.

Various classes have been used to provide file upload and mail features.

There is no risk of data mismanagement at any level while the project development is
under process.

Report generation feature is provided using Crystal Reports to generate different

kinds of reports like bar graphs, pie charts and table type charts etc.

It provides high level of security using different protocols like https etc.
STUDY OF THE SYSTEM
In the flexibility of the uses the interface has been developed a graphics concept in
mind, associated through a browses interface. The GUIS at the top level have been
categorized as
1. Administrative user interface
2. The operational or generic user interface
The administrative user interface concentrates on the consistent information that is
practically, part of the organizational activities and which needs proper authentication for
the data collection. The interfaces help the administrations with all the transactional
states like Data insertion, Data deletion and Data updating along with the extensive data
search capabilities.

The operational or generic user interface helps the users upon the system in transactions
through the existing data and required services. The operational user interface also
helps the ordinary users in managing their own information helps the ordinary users in
managing their own information in a customized manner as per the assisted flexibilities.
Number of Modules
The system after careful analysis has been identified to be presented with the following
modules and roles.
The modules involved are:
1.

Administrator

2.

Users

3.

Search

4.

Reports

Administrator:The administrator is the super user of this application. Admin only access to enter
into this admin page. Admin had all privileges to give authenticate to user and gives
privileges that which portion they can access. The administrator has all the information
about all the users and about all products.
This module is divided into different sub-modules.
1. Manage Category
2. Manage Products
3. Manage Users
4. Manage Orders History
5. Reports
1. Manage Category:
a. Add Category:

The shopping cart project contains different kind of products. The products can be
classified into different categories. Admin can add new category into the existing
system.
b. Edit Category:
Based on the market analysis admin can update a category. He can change the
category of a particular product.
c. Delete Category:
Admin has privilege to delete a category from the existing system.
d. View Category:
All existing categories can view by the administrator. The administrator can keep
track on categories.
2. Manage Products:
a. Add Products:
The shopping cart project contains different kind of products. The products can be
classified into different categories. Admin can add new products into the existing system
and he can map with the category.
b. Edit Products:
Based on the market position admin will modify the product details like price,
quantity, packing etc.
c. Delete Products:
Administrator can delete the products based on the category.

d. View Products:
Administrator can view the product details. He can watch the products prices and
contents of the products.
3. Manage Users:
a. View Users:

Admin can view the user details which are registered in his system. Because he
must know how many users entered his site and purchase products. So he can
keep track on users information.
b. Edit Users:
Admin has privileges to edit a particular user information, which is requested by
the users.
b. Delete Users:
Administrator has a right to delete user information with out intimation.
4. Manage Order History:
a. View the Order History:
Administrator can view the Order History which is generated by the user. He can
verify the products and their prices.
b. Generate Bill For History:
Administrator generates the bill for order list which is prepared by the users.
c. Set Status:
Admin can set the status for the Order list which is given by the user. The status
can be different types as follows.
o
o
o
o

Shifted
Delivered
Cancelled
Rejected

USERS:1. View Products:

User can view the list of products based on their categories. A detailed description
of a particular product can be displayed to the user, products details, manufactured by,
price and date of manufacture etc
2. Select Order Products:
After verifying the products details users select some required products.
3. Generate Order Products:

When ever user completes his selection of product, he can add these selected
products into shopping cart, for this he must be an authenticated person. If he is not an
authenticated person his selected products should not add into shopping cart. Then he
needs to register himself. If he is registered person he can directly generates the Order
Products.
4. Registration:
A registered user only can purchase products from online. So that if a user want
to purchase products he must be fill his registration form an must obtain a valid user
name and password which is provided by the administrator.
5. View Shopping Cart:
If a user generates an Order List after that he may watch which products selected
by himself, mode of delivery etc The user can also view previous shopping cart which
is generated by him.
5. Billing:
After submit his shopping cart user must pay his bill which is generated by the
administrator. The mode of billing is Credit Card only. User gives his proper
information about credit card then only he can get shopping cart, other wise his
order of shopping cart will be rejected.
Reports:Reports can be generated by the admin for various purposes. Based on the reports
admin take decisions of the system. Different kinds of reports can be generated they
are
1. Shopping Trends:
These reports based on which product is selected by large no users.
favorite product under which category it contains like that..

What is

2. Items Ordered on a given date/date range:

Admin will generate Orders lists which is selected by the users based on a selected
date or particular date range.

INPUTS & OUTPUTS

The main inputs, outputs and major functions of the system are as follows.
Inputs:
Admin enters his or her user id and password.
Users enter his or her user id and password.
User searches the products.
User selects the products.
Admin can view, add, edit and delete the products.
Admin can view, add, edit and delete products and map into categories.
Users generate the shopping cart.
Users view his shopping cart.
Users pay bills on basis of credit card manner.
Outputs:

Admin allocate user id and password to the users.

Different products displayed to user.

Shopping Cart generates for users.

Displays search result.

Users pay bills was accepted.

SCOPE OF THE PROJECT

This Document plays a vital role in the development life cycle (SDLC) as it describes the
complete requirement of the system. It is meant for use by the developers and will be
the basic during testing phase. Any changes made to the requirements in the future will
have to go through formal change approval process.
WATER FALL MODEL was being chosen because all requirements were known
beforehand

and

the

objective

of

our

software

development

computerization/automation of an already existing manual working system.

is

the

Changed
Requirements
Communicated
Requirements

Requirements
Engineering

Requirements
Specification

Design
Specification

Design

Programming

Executable
Software
Modules

Process
Integration

Product

Product
Output

Input

Maintenance

Integrated
Software
Product

Delivery

Delivered
Software
Product

Fig 2.2: Water Fall Model

The developer is responsible for:

Developing the system, which meets the SRS and solving all the requirements of the
system?

Demonstrating the system and installing the system at client's location after the
acceptance testing is successful.

Submitting the required user manual describing the system interfaces to work on it
and also the documents of the system.

Conducting any user training that might be needed for using the system.

Maintaining the system for a period of one year after installation.

INPUT DESIGN
Input design is a part of overall system design.

The main objective during the input

design is as given below:

To produce a cost-effective method of input.

To achieve the highest possible level of accuracy.

To ensure that the input is acceptable and understood by the user.

INPUT STAGES:
The main input stages can be listed as below:
Data recording
Data transcription
Data conversion
Data verification
Data control
Data transmission
Data validation
Data correction
INPUT TYPES:
It is necessary to determine the various types of inputs. Inputs can be categorized as
follows:
External inputs, which are prime inputs for the system.
Internal inputs, which are user communications with the system.
Operational, which are computer departments communications to the system?
Interactive, which are inputs entered during a dialogue.
INPUT MEDIA:
At this stage choice has to be made about the input media. To conclude about the
input media consideration has to be given to;
Type of input
Flexibility of format

 Speed
Accuracy
Verification methods
Rejection rates
Ease of correction
Storage and handling requirements
Security
Easy to use
Portabilility
Keeping in view the above description of the input types and input media, it can be said
that most of the inputs are of the form of internal and interactive. As
Input data is to be the directly keyed in by the user, the keyboard can be considered to
be the most suitable input device.
OUTPUT DESIGN
Outputs from computer systems are required primarily to communicate the results of
processing to users. They are also used to provide a permanent copy of the results for
later consultation. The various types of outputs in general are:

External Outputs, whose destination is outside the organization.

Internal Outputs whose destination is with in organization and they are the

Users main interface with the computer.

Operational outputs whose use is purely with in the computer department.

Interface outputs, which involve the user in communicating directly with

OUTPUT DEFINITION
The outputs should be defined in terms of the following points:

Type of the output

Content of the output

Format of the output

Location of the output

Frequency of the output

Volume of the output

Sequence of the output

It is not always desirable to print or display data as it is held on a computer. It should be

decided as which form of the output is the most suitable.
For Example

Will decimal points need to be inserted

Should leading zeros be suppressed.

OUTPUT MEDIA:
In the next stage it is to be decided that which medium is the most appropriate for the
output. The main considerations when deciding about the output media are:

The suitability for the device to the particular application.

The need for a hard copy.

The response time required.

The location of the users

The software and hardware available.

Keeping in view the above description the project is to have outputs mainly coming

under the category of internal outputs. The main outputs desired according to the
requirement specification are:

The outputs were needed to be generated as a hot copy

and as well as queries to be viewed on the screen. Keeping in view these outputs, the
format for the output is taken from the outputs, which are currently being obtained after
manual processing. The standard printer is to be used as output media for hard copies.

CONTEXT DIAGRAM
Users/cu
stomers

User
Information

User
Billing

Billing
report

User
Report

Admin
Information

Admin

Billing
request
Admin
Report
Order
details

Generate
Order
List

Order List
Report

SHOPPING
CART
Products
Information

Authentication
Report

Authen
tication

Product
Reports

Select
Product
s

Authentication
Information

Reports

PERFORMANCE REQUIREMENTS:

Performance is measured in terms of the output provided by the application.

Requirement specification plays an important part in the analysis of a system. Only when
the requirement specifications are properly given, it is possible to design a system,
which will fit into required environment. It rests largely in the part of the users of the
existing system to give the requirement specifications because they are the people who
finally use the system. This is because the requirements have to be known during the

initial stages so that the system can be designed according to those requirements. It is
very difficult to change the system once it has been designed and on the other hand
designing a system, which does not cater to the requirements of the user, is of no use.
The requirement specification for any system can be broadly stated as given
below:

The system should be able to interface with the existing system

The system should be accurate

The system should be better than the existing system

The existing system is completely dependent on the user to perform all the duties.
ADVANTAGES:

The project is identified by the merits of the system offered to the user. The merits
of this project are as follows:

Its a web-enabled project.

This project offers user to enter the data through simple and interactive forms. This is
very helpful for the client to enter the desired information through so much simplicity.

The user is mainly more concerned about the validity of the data, whatever he is
entering. There are checks on every stages of any new creation, data entry or
updating so that the user cannot enter the invalid data, which can create problems at
later date.

Sometimes the user finds in the later stages of using project that he needs to update
some of the information that he entered earlier. There are options for him by which
he can update the records. Moreover there is restriction for his that he cannot change
the primary data field. This keeps the validity of the data to longer extent.

User is provided the option of monitoring the records he entered earlier. He can see
the desired records with the variety of options provided by him.

From every part of the project the user is provided with the links through framing so
that he can go from one option of the project to other as per the requirement. This is
bound to be simple and very friendly as per the user is concerned. That is, we can sit
that the project is user friendly which is one of the primary concerns of any good
project.

Data storage and retrieval will become faster and easier to maintain because data is
stored in a systematic manner and in a single database.

Decision making process would be greatly enhanced because of faster processing of

information since data collection from information available on computer takes much
less time then manual system.

Allocating of sample results becomes much faster because at a time the user can see
the records of last years.

Easier and faster data transfer through latest technology associated with the
computer and communication.

Through these features it will increase the efficiency, accuracy and transparency.

DISADVANTAGES:

There are some limitations for the current system to which solutions can be provided as
a future development:
1. The system is not configured for multi- users at this time. The concept of transaction
can be used to achieve this.
2. The Website is not accessible to everyone. It can be deployed on a web server so that
everybody who is connected to the Internet can use it.
3. Credit Card validation is not done. Third party proprietary software can be used for
validation check.
FEASIBILITY REPORT
Preliminary investigation examine project feasibility, the likelihood the system will
be useful to the organization. The main objective of the feasibility study is to test the
Technical, Operational and Economical feasibility for adding new modules and debugging
old running system. All system is feasible if they are unlimited resources and infinite
time. There are aspects in the feasibility study portion of the preliminary investigation:

Technical Feasibility

Operation Feasibility

Economical Feasibility

Technical Feasibility
The technical issue usually raised during the feasibility stage of the investigation includes
the following:

Does the necessary technology exist to do what is suggested?

Do the proposed equipments have the technical capacity to hold the data required
to use the new system?

Will the proposed system provide adequate response to inquiries, regardless of the
number or location of users?

Can the system be upgraded if developed?

Are there technical guarantees of accuracy, reliability, ease of access and data
security?

Earlier no system existed to cater to the needs of Secure Infrastructure Implementation

System. The current system developed is technically feasible. It is a web based user
interface for audit workflow at NIC-CSD. Thus it provides an easy access to the users.
The databases purpose is to create, establish and maintain a workflow among various
entities in order to facilitate all concerned users in their various capacities or roles.
Permission to the users would be granted based on the roles specified. Therefore, it
provides the technical guarantee of accuracy, reliability and security. The software and
hard requirements for the development of this project are not many and are already
available in-house at NIC or are available as free as open source. The work for the
project is done with the current equipment and existing software technology. Necessary
bandwidth exists for providing a fast feedback to the users irrespective of the number of
users using the system.
Operational Feasibility
Proposed projects are beneficial only if they can be turned out into information system.
That will meet the organizations operating requirements. Operational feasibility aspects
of the project are to be taken as an important part of the project implementation. Some
of the important issues raised are to test the operational feasibility of a project includes
the following:

Is there sufficient support for the management from the users?

Will the system be used and work properly if it is being developed and
implemented?

Will there be any resistance from the user that will undermine the possible
application benefits?

This system is targeted to be in accordance with the above-mentioned issues.

Beforehand, the management issues and user requirements have been taken into
consideration. So there is no question of resistance from the users that can undermine
the possible application benefits.
The well-planned design would ensure the optimal utilization of the computer resources
and would help in the improvement of performance status.
Economic Feasibility
A system can be developed technically and that will be used if installed must still be a
good investment for the organization. In the economical feasibility, the development cost
in creating the system is evaluated against the ultimate benefit derived from the new
systems. Financial benefits must equal or exceed the costs. The system is economically
feasible. It does not require any addition hardware or software. Since the interface for
this system is developed using the existing resources and technologies available at NIC,
There is nominal expenditure and economical feasibility for certain.