Colleage of engineering and technoloage

Department of software engineering

course title : requerment engineering
project title: online shopping ssystem
Name Id
1. Melkamu Enyew ……………………….…0630
2. Wagaye Bililgn ……….…………………..0886
3. Haymanot wondmagegn ……. ….…… ..0499
4. TadesE Birara … ………………..….…...0802
5. Guadnew Moges … …..…...………..... o9o2
6. Minibel Girma … ……………………..……0907

Summitted to Elisabet Mekonen(MSC)

Table of Contents
ABSTRACT ......................................................................................................................................... 2
1. INTRODUCTION ............................................................................................................................. 2
1.1 introduction to online shopping systems.................................................................................. 2
1.2 PURPOSE OF THE PROJECT ....................................................................................................... 3
1.3PROBLEM IN EXISTING SYSTEM ................................................................................................. 4
1.4 SOLUTION OF THESE PROBLEMS .............................................................................................. 4
2. SYSTEM ANALYSIS ...................................................................................................................... 5
2.1 INTRODUCTION ....................................................................................................................... 5
2.2 ANALYSIS MODEL ..................................................................................................................... 5
2.3 STUDY OF THE SYSTEM ............................................................................................................ 6
2.4 HARDWARE SPECIFICATIONS HARDWARE REQUIREMENTS: ..................................................... 7
2.5 PROPOSED SYSTEM .................................................................................................................. 8
2.6 INPUT AND OUTPUT ................................................................................................................ 9
3. feasibility study of the system ................................................................................................... 9
3.1. Technical Feasibility .............................................................................................................. 10
3.2. Operational Feasibility .......................................................................................................... 10
3.3. Economic Feasibility.............................................................................................................. 11
4. SOFTWARE REQUIREMENT SPECIFICATION .............................................................................. 12
4.1 INTRODUCTION ..................................................................................................................... 12
4.2 FUNCTIONAL REQUIREMENTS: ............................................................................................... 12
4.3 NON_FUNCTIONAL REQUIREMENTS ...................................................................................... 13
5. SYSTEM DESIGN ........................................................................................................................... 14
5.1 INTRODUCTION ..................................................................................................................... 14
5.2 SYSTEM WORKFLOW.............................................................................................................. 15
6. INTRODUCTION TO TESTING ........................................................................................................ 18
6.1 STRATEGIC APPROACH TO SOFTWARE TESTING ..................................................................... 19
6.2 Unit Testing ........................................................................................................................... 19
6.2.1 WHITE BOX TESTING ....................................................................................................... 19
6.2.2 BASIC PATH TESTING ....................................................................................................... 20
6.2.3 CONDITIONAL TESTING ................................................................................................... 20
6.2.4 DATA FLOW TESTING ...................................................................................................... 20
6.2.5 LOOP TESTING................................................................................................................. 20
7. SYSTEM SECURITY ........................................................................................................................ 21

1
 7.1 Introduction ........................................................................................................................... 21
7.2 SECURITY IN SOFTWARE......................................................................................................... 21
7.2.1 CLIENT SIDE VALIDATION................................................................................................. 22
7.2.2 SERVER SIDE VALIDATION................................................................................................ 22
8. CONCLUSION ............................................................................................................................... 23
8.1 BENEFITS: .............................................................................................................................. 24
8.2 LIMITATIONS OF EXISTING SYSTEM : ...................................................................................... 25
9. References .................................................................................................................................. 26

ABSTRACT
The Online Shopping System Software requirements Specification (SRS) report outlines the
essential specifications and requirements needed to develop a dependable and user friendly
online shopping platform. In the current digital era, e-commerce has become an essential
part of the retail environment. This SRS document offers the framework for creating an
efficient and user-friendly online purchasing experience for both administrators and
customers. This project's main goal is to design, develop, and implement an online shopping
system that satisfies the diverse demands of modern consumers. This system will offer a wide
range of products, user-friendly interfaces, secure payment options, and efficient order
management for clients. It will also give administrators access to comprehensive inventory
and sales administration tools.

This is a project with the objective to develop a basic website where a consumer is provided
with a shopping cart application and also to know about the technologies used to develop
such an application. This document will discuss each of the underlying

1. INTRODUCTION
1.1 introduction to online shopping systems

2
E-commerce is fast gaining ground as an accepted and used business paradigm. More and
more business houses are implementing web sites 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.

The objective of this project is to develop a general purpose e-commerce store where any
products can be bought from the comfort of home through the Internet. However, for
implementation purposes, this paper will deal with an online Shopping Cart.
The Shopping Cart is a virtual store on the Internet where customers can browse the catalog
and select products of interest. The selected items may be collected in a shopping cart. At
checkout time, the items in the shopping cart will be presented as an order. At that time,
more information will be needed to complete the transaction. Usually, the customer will be
asked to fill or select a billing address, a shipping address, a shipping option, and payment
information such as credit card number. An e- mail notification is sent to the customer as
soon as the order is placed.
The Shopping Cart is expanded permanently through new products and services in order to
offer a product portfolio corresponding to the market. Private customer and business
customers can order the selected products of the Shopping Cart service online quickly and
comfortably.
Target groups of customer of the Shopping Cart are. The customers can have a payment
option through credit card only. In order to use the load writing procedure, the customer
registers itself and receives a login for its purchases name. It is an Internet application.
Electronic Commerce (e-commerce) applications support the interaction between different
parties participating in a commerce transaction via the network as well as the management
of the data involved in the process.

1.2 PURPOSE OF THE PROJECT

The Shopping Cart needs to sell different types of products to customer living in any part of
the world. The website will show all products in categorized manner. Customer can browse

3
any product for its price and other details and can order the product. Orders needs to
accompany with shipping & billing details. Customer has to pay order amount online through
credit cards. Products can be managed by operators from admin panel. Operator can be
created by admin. Admin can keep track of orders through admin panel. The main purpose of
the system is to enable customers to browse and order from any part of the world and hence
increasing business scope.

1.3PROBLEM IN EXISTING SYSTEM

 The existing system is manual system. Needs to be converted into automated
system.
 Risk of mismanagement of data.
 Less Security.
 No proper coordination between different Applications and Users.
 Fewer Users - Friendly.
 Accuracy not guaranteed.
 Not in reach of distant users.

1.4 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.

1. User friendliness is provided in the application with various controls.

2. The system makes the overall project management much easier and flexible.
3. There is no risk of data mismanagement at any level while the project
development is under process.
4. It provides high level of security with different level of authentication.
5. Users from any part of the world can make use of the system.
6. New system will process accurate results.
7. New system will be much better in performance as compared to existence one.

4
 2. SYSTEM ANALYSIS

2.1 INTRODUCTION

After analysing the requirements of the task to be performed, the next step is to analyse the
problem and understand its context. The first activity in the phase is studying the existing
system and other is to understand the requirements and domain of the new system. Both the
activities are equally important, but the first activity serves as a basis of giving the functional
specifications and then successful design of the proposed system. Understanding the
properties and requirements of a new system is more difficult and requires creative thinking
and understanding of existing running system is also difficult, improper understanding of
present system can lead diversion from solution.

2.2 ANALYSIS MODEL

The model that is basically being followed is the WATER FALL MODEL, which states that the
phases are organized in a linear order. First of all the feasibility study is done. Once that part
is over the requirement analysis and project planning begins. If system exists one and
modification and addition of new module is needed, analysis of present system can be used
as basic model.
The design starts after the requirement analysis is complete and the coding begins after the
design is complete. Once the programming is completed, the testing is done. In this model
the sequence of activities performed in a software development project are: -

 Requirement Analysis
 Project Planning
 System design

5
  Detail design
 Coding
 Unit testing
 System integration & testing

WATER FALL MODEL was being chosen because all requirements were known beforehand
and the objective of our software development is the computerization/automation of an
already existing manual working system.

2.3 STUDY OF THE SYSTEM

GUI’S

In the flexibility of the uses the interface has been developed a graphics concept in mind,
associated through a browser interface. The GUI’S 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 Date updation 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:

 This project is divided into 9 modules:

6
 1. Registration Module
2. Products Browse Module
3. Products Search Module
4. Shopping cart Module
5. Shipping & Billing Module
6. Payment Module
7. Admin User Management Module
8. Admin Catalog Management Module
9. Admin Order Management Module

 Entities Involved in the Project:

1) Customer
2) Product
3) Website Administrator
4) Operator
5) Order

Customer: The target user of the system. A Customer is responsible for registering them to
the site, browsing site, placing orders and making payments.
Product: Product is the entity, a customer looking for. A Product will be sold to the customer.
Website Administrator: An entity responsible for managing users, roles and roles privileges.
Operator: Operator is a person (entity) responsible for managing products and orders.
Order: Order is an entity which describes the business transaction.

 Provide an environment for upgradation of application for newer versions that are
available in the same domain as web service target.

2.4 HARDWARE SPECIFICATIONS HARDWARE REQUIREMENTS:

 PIV 2.8 GHz Processor and Above
 RAM 512MB and Above
 HDD 20 GB Hard Disk Space and Above SOFTWARE REQUIREMENTS:
 WINDOWS OS

7
  Visual Studio .Net 2005 Enterprise Edition
 Internet Information Server 5.0 (IIS)
 Visual Studio .Net Framework (Minimal for Deployment)
 SQL Server

2.5 PROPOSED SYSTEM

To debug the existing system, remove procedures those cause data redundancy, make
navigational sequence proper. To provide information about audits on different level and also
to reflect the current work status depending on organization/auditor or date.Required to
build strong password mechanism.

FUNCTIONAL FEATURES OF THE MODEL

As far as the project is developed the functionality is simple, the objective of the proposal is
to strengthen the functioning of Audit Status Monitoring and make them effective and
better. The entire scope has been classified into five streams knows as Coordinator Level,
management Level, Auditor Level, User Level and State Web Coordinator Level. The proposed
software will cover the information needs with respect to each request of the user group viz.
accepting the request, providing vulnerability document report and the current status of the
audit.
WORKING OF THE SYSTEM
The entire scope has been classified into five streams known as: -
Coordinator Level
(Addressing the information management needs of coordinator)
Management Level
(Addressing the information management needs of management)
Auditor Level
(Addressing the information management needs of auditors)
User Level
(Addressing the information management needs of the user group)
State Web Coordinator level
(Addressing the needs of coordinator of the state)

8
2.6 INPUT AND OUTPUT
The main inputs, outputs and major functions of the system are as follows
INPUTS:

 Customer enters his or her user id and password.

 Operators enter his or her user id and password.
 Admin enter his or her user id and password.
 User requests the product description.
 User requests the product search.
 User orders product.
 System requests shipping & billing address.

OUTPUTS:

 Customer receives personal and order details.

 Operator receives the personal details.
 Admin receives order details.
 Users receive requested product details.
 Users receive orders.
 System processes orders.

3. feasibility study of the system

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

9
3.1. 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 database’s
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.

3.2. Operational Feasibility

10
Proposed projects are beneficial only if they can be turned out into information system. That
will meet the organization’s 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.

3.3. 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 normal
expenditure and economical features for certain.

11
 4. SOFTWARE REQUIREMENT SPECIFICATION
4.1 INTRODUCTION
Purpose: The main purpose for preparing this document is to give a general insight into the
analysis and requirements of the existing system or situation and for determining the
operating characteristics of the system.

Scope: This Document plays a vital role in the development life cycle (SDLC) and 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.
DEVELOPERS RESPONSIBILITIES OVERVIEW:
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.

4.2 FUNCTIONAL REQUIREMENTS:

User Registration and Authentication: Users should be able to create accounts, log in, and log
out securely.

Product Catalog: The system should display a list of products with details such as name,
description, price, and images.

Search and Filtering: Users should be able to search for products and filter results based on
categories, price range, ratings, etc.

12
Shopping Cart: Users should be able to add, update, and remove products from their
shopping cart.

Checkout Process: The system should support a seamless checkout process, including order
review, payment processing, and order confirmation.

Payment Gateway Integration: The system should integrate with multiple payment gateways
to process payments securely.

Order Management: Users should be able to view their order history, track orders, and
receive notifications about order status.

User Profile Management: Users should be able to update their personal information, such as
address and payment details.

Product Reviews and Ratings: Users should be able to leave reviews and ratings for products
they have purchased.

Admin Panel: Administrators should have access to a dashboard to manage products, orders,
users, and view analytic

4.3 NON_FUNCTIONAL REQUIREMENTS

Non-functional requirements (NFRs) are crucial for the success of an online shopping
platform. They define the system's quality attributes and ensure it meets user expectations.
Here are some key NFRs for an online shopping platform:

1. Performance: The system should handle a large number of users and transactions
simultaneously without significant delays. This includes fast page load times, quick search
results, and efficient checkout processes.

2. Scalability: The platform should be able to scale up or down based on the number of users
and transactions. This ensures that the system can handle peak shopping periods, such as
Black Friday or holiday sales, without crashing.

13
3. Security: Protecting user data is paramount. The platform should implement strong
encryption, secure payment gateways, and regular security audits to prevent data breaches
and fraud.

4. Usability: The user interface should be intuitive and easy to navigate. This includes clear
product categories, a simple checkout process, and accessible customer support.

5. Reliability: The system should be available and operational 24/7. This includes having
backup systems and disaster recovery plans in place to minimize downtime.

6. Maintainability: The platform should be easy to update and maintain. This includes
modular code, comprehensive documentation, and automated testing to ensure that new
features or fixes do not disrupt the system.

7. Compliance: The platform should comply with relevant laws and regulations, such as data
protection laws standards .
8. Compatibility: The system should work seamlessly across different devices and browsers.
This ensures that users have a consistent experience whether they are shopping on a
desktop, tablet, or smartphone.

These non-functional requirements ensure that the online shopping platform is efficient,
secure, and user-friendly, ultimately leading to a better shopping experience for customers.

5. SYSTEM DESIGN

5.1 INTRODUCTION

Software design sits at the technical kernel of the software engineering process and is
applied regardless of the development paradigm and area of application. Design is the first
step in the development phase for any engineered product or system. The designer’s goal is
to produce a model or representation of an entity that will later be built. Beginning, once

14
system requirement have been specified and analysed, system design is the first of the three
technical activities -design, code and test that is required to build and verify software.
The importance can be stated with a single word “Quality”. Design is the place where quality
is fostered in software development. Design provides us with representations of software
that can assess for quality. Design is the only way that we can accurately translate a
customer’s view into a finished software product or system. Software design serves as a
foundation for all the software engineering steps that follow. Without a strong design we risk
building an unstable system – one that will be difficult to test, one whose quality cannot be
assessed until the last stage.
During design, progressive refinement of data structure, program structure, and procedural
details are developed reviewed and documented. System design can be viewed from either
technical or project management perspective. From the technical point of view, design is
comprised of four activities – architectural design, data structure design, interface design and
procedural design.

5.2 SYSTEM WORKFLOW

(Logging Via Crusted)

|
Product Search/ Listing
|
Selecting a Particular Product
|
Selection through Checkbox ---------> Temp order record record
|
Billing/ Shipping Info ----------> Recording Customer's Data
|
Shipping + Product Price Calculated ----> If shipped via 3rd party then charge is
calculated from their linked server
Order Confirmation & Accept Order ----> Entry into main database including temp
| records. * Delete temp record CCard/ PayPal/ Offline Pay
Process

15
 |
|
| ----------- ----------- --------- ViaEmail ViaEmail ViaEmail ----------- ----------
- ---------
|
|
| Invoice to Seller Charge Customer Invoice Amount (in
case of 3rd party seller as Ebay)

Designing an online shopping system involves several key components to ensure it is

efficient, secure, and user-friendly. Here's a detailed overview:
1. User Interface (UI)
The UI is the front-end part of the system that users interact with. It should be intuitive,
responsive, and visually appealing. Key elements include:

 Homepage: Displays featured products, promotions, and navigation links.

 Product Pages: Show product details, images, prices, and reviews.
 Search and Filter: Allows users to search for products and filter results based on
categories, price, ratings, etc.
 Shopping Cart: Users can add, update, and remove products from their cart.
 Checkout Process: A seamless process for reviewing orders, entering shipping
information, and making payments.

2. Backend Server
The backend server handles the business logic and processes user requests. It includes:

 Application Server: Manages user sessions, processes orders, and handles business
logic.
 Database Server: Stores user information, product details, order history, and
transaction records.
 Web Server: Serves web pages to users and handles HTTP requests.

3. Database

16
A robust database is essential for storing and managing data. Common databases used
include MySQL, PostgreSQL, and MongoDB. Key data stored includes:

 User Data: Account information, addresses, payment details.

 Product Data: Product descriptions, prices, inventory levels
 Order Data: Order history, payment status, shipping details.

4. Payment Gateway
The payment gateway handles secure payment processing. It integrates with various
payment methods such as credit/debit cards, digital wallets, and bank transfers. Popular
payment gateways include PayPal, Stripe, and Square.

5. Security
Implementing strong security measures is crucial to protect user data and prevent fraud. This
includes:

 SSL Encryption: Ensures secure data transmission between users and the server.
 Secure Authentication: Uses techniques like two-factor authentication (2FA) to
verify user identities.
 Regular Security Audits: Identifies and fixes vulnerabilities in the system.
 Compliance: Adheres to data protection regulations like GDPR and PCI DSS.

6. Scalability
The system should be designed to handle increasing traffic and transactions, especially during
peak shopping periods. This involves:

 Scalable Infrastructure: Using cloud services like AWS or Azure to scale resources up
or down as needed.
 Load Balancing: Distributes incoming traffic across multiple servers to ensure no single
server is overwhelmed.
 Caching Mechanisms: Stores frequently accessed data in memory to reduce load on
the database.

7. APIs

17
Application Programming Interfaces (APIs) enable communication between different
components of the system and with third-party services. For example:

 Shipping Providers: Integrates with shipping services to calculate shipping costs and
track orders.
 Payment Gateways: Connects with payment processors to handle transactions.
 External Databases: Accesses additional product information or reviews from
external sources.

8. Content Management System (CMS)

A CMS allows administrators to manage website content, including product descriptions,
images, and promotional materials. Popular CMS platforms include WordPress, Magento, and
Shopify.
9. Analytics and Reporting
Implementing analytics tools helps track user behavior, sales performance, and other key
metrics. This data can be used to optimize the shopping experience and make informed
business decisions.
10. Customer Support
Providing efficient customer support is essential for a positive shopping experience. This can
include:

 Live Chat: Real-time assistance for users.

 Email Support: Handling customer inquiries and issues.
 FAQ Section: Answers to common questions and troubleshooting tips.

By integrating these components, an online shopping system can provide a seamless, secure,
and scalable platform for users to browse and purchase products.

6. INTRODUCTION TO TESTING

Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and coding. In fact, testing is the one step in the
software engineering process that could be viewed as destructive rather than constructive.

18
A strategy for software testing integrates software test case design methods into a well-
planned series of steps that result in the successful construction of software. Testing is the
set of activities that can be planned in advance and conducted systematically. The underlying
motivation of program testing is to affirm software quality with methods that can
economically and effectively apply to both strategic to both large and small-scale systems.

6.1 STRATEGIC APPROACH TO SOFTWARE TESTING

The software engineering process can be viewed as a spiral. Initially system engineering
defines the role of software and leads to software requirement analysis where the
information domain, functions, behavior, performance, constraints and validation criteria for
software are established. Moving inward along the spiral, we come to design and finally to
coding. To develop computer software we spiral in along streamlines that decrease the level
of abstraction on each turn.

A strategy for software testing may also be viewed in the context of the spiral. Unit testing
begins at the vertex of the spiral and concentrates on each unit of the software as
implemented in source code. Testing progress by moving outward along the spiral to
integration testing, where the focus is on the design and the construction of the software
architecture. Talking another turn on outward on the spiral we encounter validation testing
where requirements established as part of software requirements analysis are validated
against the software that has been constructed. Finally we arrive at system testing, where the
software and other system elements are tested as a whole.

6.2 Unit Testing

Unit testing focuses verification effort on the smallest unit of software design, the module.
The unit testing we have is white box oriented and some modules the steps are conducted in
parallel.

6.2.1 WHITE BOX TESTING

This type of testing ensures that • All independent paths have been exercised at least once •
All logical decisions have been exercised on their true and false sides • All loops are executed

19
at their boundaries and within their operational bounds • All internal data structures have
been exercised to assure their validity.
To follow the concept of white box testing we have tested each form .we have created
independently to verify that Data flow is correct, All conditions are exercised to check their
validity, All loops are executed on their boundaries.

6.2.2 BASIC PATH TESTING

Established technique of flow graph with Cyclomatic complexity was used to derive test cases
for all the functions. The main steps in deriving test cases were: Use the design of the code
and draw correspondent flow graph.

6.2.3 CONDITIONAL TESTING

In this part of the testing each of the conditions were tested to both true and false aspects.
And all the resulting paths were tested. So that each path that may be generate on particular
condition is traced to uncover any possible errors.

6.2.4 DATA FLOW TESTING

This type of testing selects the path of the program according to the location of definition
and use of variables. This kind of testing was used only when some local variable were
declared. The definition-use chain method was used in this type of testing. These were
particularly useful in nested statements.

6.2.5 LOOP TESTING

In this type of testing all the loops are tested to all the limits possible. The following exercise
was adopted for all loops:

 All the loops were tested at their limits, just above them and just below them.
 All the loops were skipped at least once.
 For nested loops test the inner most loop first and then work outwards.
 For concatenated loops the values of dependent loops were set with the help
of connected loop.
 Unstructured loops were resolved into nested loops or concatenated loops
and tested as above.

20
Each unit has been separately tested by the development team itself and all the input have
been validated.

7. SYSTEM SECURITY

7.1 Introduction
The protection of computer based resources that includes hardware, software, data,
procedures and people against unauthorized use or natural Disaster is known as System
Security.
System Security can be divided into four related issues:

 Security
 Integrity
 Privacy
 Confidentiality

SYSTEM SECURITY refers to the technical innovations and procedures applied to the hardware
and operation systems to protect against deliberate or accidental damage from a defined
threat.

DATA SECURITY is the protection of data from loss, disclosure, modification and destruction.
SYSTEM INTEGRITY refers to the power functioning of hardware and programs,
appropriate physical security and safety against external threats such as eavesdropping and
wiretapping.
PRIVACY defines the rights of the user or organizations to determine what information they
are willing to share with or accept from others and how the organization can be protected
against unwelcome, unfair or excessive dissemination of information about it.
CONFIDENTIALITY is a special status given to sensitive information in a database to minimize
the possible invasion of privacy. It is an attribute of information that characterizes its need
for protection.

7.2 SECURITY IN SOFTWARE

System security refers to various validations on data in form of checks and controls to avoid
the system from failing. It is always important to ensure that only valid data is entered and

21
only valid operations are performed on the system. The system employees two types of
checks and controls:

7.2.1 CLIENT SIDE VALIDATION

Various client side validations are used to ensure on the client side that only valid data is
entered. Client side validation saves server time and load to handle invalid data. Some checks
imposed are:

 VBScript in used to ensure those required fields are filled with suitable data only.
Maximum lengths of the fields of the forms are appropriately defined.
 Forms cannot be submitted without filling up the mandatory data so that manual
mistakes of submitting empty fields that are mandatory can be sorted out at the
client side to save the server time and load.
 Tab-indexes are set according to the need and taking into account the ease of user
while working with the system.

7.2.2 SERVER SIDE VALIDATION

Some checks cannot be applied at client side. Server side checks are necessary to save the
system from failing and intimating the user that some invalid operation has been performed
or the performed operation is restricted. Some of the server side checks imposed is:

 Server side constraint has been imposed to check for the validity of primary key
and foreign key. A primary key value cannot be duplicated. Any attempt to
duplicate the primary value results into a message intimating the user about those
values through the forms using foreign key can be updated only of the existing
foreign key values.
 User is intimating through appropriate messages about the successful operations
or exceptions occurring at server side
 Various Access Control Mechanisms have been built so that one user may not
agitate upon another. Access permissions to various types of users are controlled
according to the organizational structure. Only permitted users can log on to the
system and can have access according to their category. User- name, passwords
and permissions are controlled o the server side

22
  Using server side validation, constraints on several restricted operations are
imposed.

8. CONCLUSION

The Internet has become a major resource in modern business, thus electronic shopping has
gained significance not only from the entrepreneur’s but also from the customer’s point of
view. For the entrepreneur, electronic shopping generates new business opportunities and
for the customer, it makes comparative shopping possible. As per a survey, most consumers
of online stores are impulsive and usually make a decision to stay on a site within the first few
seconds. “Website design is like a shop interior. If the shop looks poor or like hundreds of
other shops the customer is most likely to skip to the other site. Hence we have designed the
project to provide the user with easy navigation, retrieval of data and necessary feedback as
much as possible.

In this project, the user is provided with an e-commerce web site that can be used to buy
Products online. To implement this as a web application we used ASP.NET as the Technology.
ASP.NET has several advantages such as enhanced performance, scalability, built- in security
and simplicity. To build any web application using ASP.NET we need a programming language
such as C#, VB.NET, J# and so on. C# was the language used to build this application. For the
client browser to connect to the ASP.NET engine we used Microsoft’s Internet Information
Services (IIS) as the Web Server. ASP.NET uses ADO.NET to interact with the database as it
provides in-memory caching that eliminates the need to contact the database server
frequently and it can easily deploy and maintain an ASP.NET application. SQL Server was used
as back-end database since it is one of the most popular open source databases, and it
provides fast data access, easy installation and simplicity.

A good shopping cart design must be accompanied with user-friendly shopping cart
application logic. It should be convenient for the customer to view the contents of their cart
and to be able to remove or add items to their cart. The shopping cart application described

23
in this project provides a number of features that are designed to make the customer more
comfortable.

This project helps in understanding the creation of an interactive web page and the
technologies used to implement it. The design of the project which includes Data Model and
Process Model illustrates how the database is built with different tables, how the data is
accessed and processed from the tables. The building of the project has given me a precise
knowledge about how ASP.NET is used to develop a website, how it connects to the
database to access the data and how the data and web pages are modified to provide the
user with a shopping cart application.

It has been a great pleasure for me to work on this exciting and challenging project. This
project proved good for me as it provided practical knowledge of not only programming in
ASP.NET and C#.NET web based application and no some extent Windows Application and
SQL Server, but also about all handling procedure related with “PROJECT NAME”. It also
provides knowledge about the latest technology used in developing web enabled application
and client server technology that will be great demand in future. This will provide better
opportunities and guidance in future in developing projects independently.

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

 It’s 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
updation so that the user cannot enter the invalid data, which can create
problems at later date.

24
  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 sat 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,

8.2 LIMITATIONS OF EXISTING SYSTEM :

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.

25
9. References
Mohapatra, H., & Rath, A. K. (2020). Fundamentals of software engineering: designed to
provide an insight into the software engineering concepts. BPB Publications.

Search Engine:

www.qooqle.com

Online Tools:

https://app.smartdraw.com/editor

https://online.visual-paradiqm.com

https://creately.com

26