Bca Project

A PROJECT REPORT
ON
“ONLINE TRANSACTION FOR SUPER MARKET”
A Dissertation submitted in partial fulfillment of the requirements for the award of

degree of
BACHELORS OF COMPUTER APPLICATIONS

Of
BANGALORE UNIVERSITY
SUBMITTED BY
NAVYA BAI C.T
(196ESB7023)
Under the Guidance of

Prof. Prabhu. G
Dept. of BCA
Department of Computer Applications
BANGALORE INSTITUTE OF MANAGEMENT STUDIES

NO.35, MYSORE ROAD, BANGALORE -59
MARCH 2022
A PROJECT REPORT
ON
“ONLINE TRANSACTION FOR SUPER MARKET”
A Dissertation submitted in partial fulfillment of the requirements for the award of

degree of
BACHELORS OF COMPUTER APPLICATIONS

Of
BANGALORE UNIVERSITY
SUBMITTED BY
NAVYA BAI C.T
(196ESB7023)
BHARATHI K.S
(196ESB7005)
Under the Guidance of

Prof. Prabhu. G
Dept. of BCA

MARCH 2022
CERTIFICATE
This is to certify that Ms. NAVYA BAI C T & BHARATHI K S has completed
FIFTH semester project work entitled “ONLINE TRANSACTION FOR
SUPER MARKET” as a partial fulfillment for the award of Bachelors of
Computer Applications degree, during the academic year 2022 under our joint
supervision.
Signature of Guide Head of the Department

Signature of Examiners
Examiner-1:_______________ Examiner-2:_________________
DECLARATION
We, NAVYA BAI C.T & BHARATHI K.S student of 5TH semester BCA, BANGALORE INSTITUTE OF
MANAGEMENT STUDIES, Bangalore, bearing REG 196ESB7023 & 196ESB7005 hereby declare
that the project entitled “ONLINE TRANSACTION FOR SUPER MARKET” has been carried under
the guidance of Prof. Prabhu. G, Dept. of BCA, Bangalore Institute of Management Studies and
submitted in partial fulfillment of the requirements for the award of the Degree of Bachelors of
Computer Applications by the Bangalore University during the academic year 2022.
Name: NAVYA BAI C T
BHARATHI K S
Signature:
ACKNOWLEDGEMENT
We have taken efforts in this project. However, it would not have been possible without the
kind support and help of many individuals and organizations. We would like to extend our
sincere thanks to all of them.
We express sincere thanks to Prof. Prabhu. G, HOD, Dept of BCA for his immense support
and guidance throughout the project.
We are highly indebted to our project internal guide, Prof. Prabhu. G, Professor
Department of BCA, Bangalore Institute of Management Studies, who provided valuable
guidance and support during the Project.
It`s our pleasure to extend our gratitude to all the lecturers of BCA department for their
valuable guidance, suggestions and encouragement throughout this work.
We express immense pleasure to Mrs. Sumathi Srinivas (MINDTREE) Project Manager,

she has helped us in channeling my efforts in the right direction. She has guided us to
meticulously carry out phases of the project
Last but not the least we thank almighty, our beloved Parents and Friends for their
constant encouragement without which this assignment would have not been possible.
Thanking you,
NAVYA BAI C.T

(196ESB7023)
BHARATHI K.S
(196ESB7005)
CONTENTS OF THE TABLE
SL.NO CHAPTER PAGE .N

O
01 INTRODUCTION 01
1.1 Basic Introduction of Project 02
1.2 Objective and Scope 03
1.3 Project Category 03
1.4 Tools and Technologies used 04
1.5 Introduction to C# 05
1.6 Introduction to ASP.NET 06
1.7 Introduction to SQL Server2005 08
1.8 Internet Information Server [IIS] 09
02 SYSTEM ANALYSIS 11
2.1 Preliminary analysis &Information 12
gathering
03 SRS 14
3.1 Hardware interface 15
3.2 Software interface 15
3.3 Communication interface 15
3.4 Functional Requirements 16
3.5 Software Engineering model used 19
3.6 Project Schedule 21
04 SYSTEM DESIGN 23
4.1 System Design 24
4.2 Database Design 25
4.3 Data flow Diagram 26
4.4 ER Diagram 30
4.5 Use Case Diagram 32
4.6 sequence Diagram 34
4.7 Class Diagram 37
4.8 Object Diagram 39
05 TESTING 40
5.1 Purpose & Types of Testing 41
5.2 Levels of Testing 42
5.3 Regression Testing 44
06 IMPLEMENTATION 45
07 CONCLUSION AND FUTURE 47
ENHANCEMENT
08 ANNEXURE 49
09 REFERENCE 55
ONLINE
TRANSACTION
FOR
SUPERMARKET
ONLINE TRANSCATION FOR SUPERMARKET
CHAPTER-1
INTRODUCTION
DEPT OF BCA 1
CHAPTER-1
INTRODUCTION
1.1 Basic introduction of Project

A supermarket is a self-service shop offering a wide variety of food and household products,
organized into aisles. It is larger and has a wider selection than a traditional grocery store, but is
smaller and more limited in the range of merchandise than a hypermarket or big-box market.
The supermarket typically comprises meat, fresh produce, dairy, and baked goods aisles, along
with shelf space reserved for canned and packaged goods as well as for various non-food items
such as kitchenware, household cleaners, pharmacy products and pet supplies. Some
supermarkets also sell a variety of other household products that are consumed regularly, such as
alcohol (where permitted), medicine, and clothes, and some stores sell a much wider range of
non-food products: DVDs, sporting equipment, board games, and seasonal items (e.g., Christmas
wrapping paper in December).
The traditional supermarket occupies a large amount of floor space, usually on a single level. It is
usually situated near a residential area in order to be convenient to consumers. The basic appeal
is the availability of a broad selection of goods under a single roof, at relatively low prices. Other
advantages include ease of parking and frequently the convenience of shopping hours that extend
into the evening or even 24 hours of the day. Supermarkets usually allocate large budgets to
advertising, typically through newspapers. They also present elaborate in-shop displays of
products.
Supermarkets typically are chain stores, supplied by the distribution centers of their parent

companies thus increasing opportunities for economies of scale. Supermarkets usually offer
products at relatively low prices by using their buying power to buy goods from manufacturers at
lower prices than smaller stores can. They also minimize financing costs by paying for goods at
least 30 days after receipt and some extract credit terms of 90 days or more from vendors.
Certain
DEPT OF BCA 2
products (typically staple foods such as bread, milk and sugar) are very occasionally sold as loss

leaders so as to attract shoppers to their store. Supermarkets make up for their low margins by a
higher overall volume of sales, and with the sale of higher-margin items bought by the intended
higher volume of shoppers. Customers usually shop by placing their selected merchandise
into shopping carts (trolleys) or baskets (self-service) and pay for the merchandise at the check-
out. Many supermarket chains are attempting to further reduce labor costs by shifting to self-
service check-out machines, where a single employee can oversee and assist multiple customers
at a time.
A larger full-service supermarket combined with a department store is sometimes known as

a hypermarket. Other services offered at some supermarkets may include those
of banks, cafés, childcare centers/creches, insurance (and other financial services), Mobile
Phone services, photo processing, video rentals, pharmacies and/or petrol stations.
1.2 Objective and Scope
The main objective of this application is to ease the process of shopping in super markets.
1.3 Project Category

A web based application is software package that can be accessed through the web browser. The
software and the database reside on a central server rather than being installed in the desktop
system and is accessed over the network. In computing, a web application or web App is a client-
server software application which the client (or user interface) runs in a web browser. Web
applications are popular due to the ubiquity of web browsers, and the convenience of using a
web browser a client to update and maintain web applications without disturbing and installing
software on potentially thousands of client computers is a key reason for their popularity, as is
the inherits supports for cross-platform compatibility.
DEPT OF BCA 3
1.4 Tools and Technologies used

.NET Framework
The .NET Framework is the infrastructure for the overall .NET Platform. It includes base
class libraries, like ADO.NET and ASP.NET, as well as a common language runtime.
Fig: MICROSOFT .NET FRAMEWORK
Web Services:
A Web Service is a unit of application logic providing data and services to other pplications.
Applications access Web Services via ubiquitous Web protocols and data formats such as HTTP,
XML, and SOAP.
The .NET Framework is an environment for building, deploying, and running Web
Services and other applications. It is the infrastructure for the overall .NET Platform. The
framework consists of three main parts: the Common Language Runtime, the class libraries, and
ASP.NET.
The Common Language Runtime and class libraries, including Windows Forms,
ADO.NET, and ASP.NET, combine together to provide services and solutions that can be easily
integrated within and across a variety of systems. The .NET Framework provides a fully
DEPT OF BCA 4
managed, protected, and feature-rich application execution environment, simplified development
and deployment, and seamless integration with a wide variety of languages.
Common Language Runtime
Despite its name, the runtime actually has a role in both a component's runtime and
development time experiences. While the component is running, the runtime is responsible for
managing memory allocation, starting up and stopping threads and processes, and enforcing
security policy, as well as satisfying any dependencies that the component might have on other
components. At development time, the runtime's role changes slightly; because it automates so
much (for example, memory management); the runtime makes the developer's experience very
simple, especially when compared to COM today. In particular, features such as reflection
dramatically reduce the amount of code a developer must write in order to turn business logic
into a reusable component.
Unified programming classes

The framework provides developers with a unified, object-oriented, hierarchical, and
extensible set of class libraries (APIs). Currently, C++ developers use the Microsoft Foundation
Classes; Java developers use the Windows Foundation Classes. The framework unifies these
disparate models and gives Visual Basic programmers access to class libraries as well. By
creating a common set of APIs across all programming languages, the .NET Framework runtime
enables cross-language inheritance, error handling, and debugging. All programming languages,
from ECMA Script to C++, have similar access to the framework and developers are free to
choose the language that they want to use.
1.5 Introduction to C#:
C# (pronounced as ‘C Sharp’) is a new computer-programming language developed by

Microsoft Corporation, USA. C# is a fully object-oriented language like Java and is the first
Component-oriented language. It has been designed to support the key features of .NET
Framework, the new development platform of Microsoft for building component-based software
solutions. It is a simple, efficient, productive and type-safe language derived from the
DEPT OF BCA 5
popular C and C++ languages. Although it belongs to the family of C/C++, it is a purely
object-oriented, modern language suitable for developing Web-based applications.
C# is designed for building robust, reliable and durable components to handle real-world
applications. Major highlights of C# are:
 It is a brand new language derived from the C/C++ family.
 TIt simplifies and modernizes C++.
 It is the only component-oriented language available today.
 It is the only language designed for the .NET Framework.
 It is a concise, lean and modern language.
 It combines the best features of many commonly used languages: the productivity of
Visual Basic, the power of C++ and the elegance of Java.
 It is intrinsically object-oriented and web-enabled.
DEPT OF BCA 6
 It has a lean and consistent syntax.
 It embodies today’s concern for simplicity, productivity and robustness.
 It will become the language of choice for .NET programming.
 Major parts of .NET Framework are actually coded in C#.
1.6 INTRODUCTION TO ASP.NET
ASP.NET is a unified Web development model that includes the services necessary for
you to build enterprise-class Web applications with a minimum of coding. ASP.NET is part of the
.NET Framework, and when coding ASP.NET applications you have access to classes in
the .NET Framework. You can code your applications in any language compatible with the
common language runtime (CLR), including Microsoft Visual Basic, C#, JScript .NET, and J#.
These languages enable you to develop ASP.NET applications that benefit from the common
language runtime, type safety, inheritance, and so on. ASP.NET includes:
 A page and controls framework

 The ASP.NET compiler
 Security infrastructure
 State-management facilities
 Application configuration
DEPT OF BCA 7
 Health monitoring and performance features
 Debugging support
 An XML Web services framework
 Extensible hosting environment and application life cycle management
 An extensible designer environment
Ado.Net - Database Connectivity:
Most applications need data access at one point of time making it a crucial component when
working with applications. Data access is making the application interact with a database, where
all the data is stored. Different applications have different requirements for database access.
ASP.NET uses ADO .NET (Active X Data Object) as its data access and manipulation protocol
which also enables us to work with data on the Internet.
ADO.NET Data Architecture
Data Access in ADO.NET relies on two components: Data Set and Data Provider.
1. Data Set
The dataset is a disconnected, in-memory representation of data. It can be considered as a local

copy of the relevant portions of the database. The Data Set is persisted in memory and the data in
it can be manipulated and updated independent of the database. When the use of this Data Set is
finished, changes can be made back to the central database for updating. The data in Data Set can
be loaded from any valid data source like Microsoft SQL server database, an Oracle database or
from a Microsoft Access database.
2. Data Provider
DEPT OF BCA 8
The Data Provider is responsible for providing and maintaining the connection to the database. A
Data Provider is a set of related components that work together to provide data in an efficient
and performance driven manner. The .NET Framework currently comes with two Data
Providers: the SQL Data Provider which is designed only to work with Microsoft's SQL Server
7.0 or later and the OleDb Data Provider which allows us to connect to other types of databases
like Access and Oracle. Each Data Provider consists of the following component classes:
The Connection object which provides a connection to the database. The Command
object which is used to execute a command. The Data Reader object which provides a forward-
only, read only, connected record set. The Data Adapter object which populates a disconnected
Data Set with data and performs update.
1.7 Introduction to SQL Server 2005:
Microsoft SQL Server is a full-featured relational database management system (RDBMS) that
offers a variety of administrative tools to ease the burdens of database development, maintenance
and administration. In this article, we'll cover six of the more frequently used tools: Enterprise
Manager, Query Analyzer, SQL Profiler, Service Manager, Data Transformation Services and
Books Online.
Enterprise Manager is the main administrative console for SQL Server installations. It provides
you with a graphical "birds-eye" view of all of the SQL Server installations on your network.
You can perform high-level administrative functions that affect one or more servers, schedule
common maintenance tasks or create and modify the structure of individual databases.
Query Analyzer offers a quick and dirty method for performing queries against any of your SQL
Server databases. It's a great way to quickly pull information out of a database in response to a
user request, test queries before implementing them in other applications, create/modify stored
procedures and execute administrative tasks.
DEPT OF BCA 9
SQL Profiler provides a window into the inner workings of your database. You can
monitor many different event types and observe database performance in real time. SQL Profiler
allows you to capture and replay system "traces" that log various activities. It's a great tool for
optimizing databases with performance issues or troubleshooting particular problems.
Service Manager is used to control the MS SQL Server (the main SQL Server process),
MSDTC (Microsoft Distributed Transaction Coordinator) and SQL Server Agent processes. An
icon for this service normally resides in the system tray of machines running SQL Server. You
can use Service Manager to start, stop or pause any one of these services.
Data Transformation Services (DTS) provide an extremely flexible method for importing

and exporting data between a Microsoft SQL Server installation and a large variety of other
formats. The most commonly used DTS application is the "Import and Export Data" wizard
found in the SQL Server program group.
1.8 Internet Information Server [IIS]:
IIS server includes a broad range of administrative features for managing web sites and
the web server. With programmatic features like ASP, ASP.NET, you can create and deploy
scalable, flexible web applications.
Features of IIS:
Support of Internet standards:
The features include HTTP support and standard internet services such as:
 World Wide Web (WWW): It supports HTTP allowing users to publish content to the
internet. Files can be placed in folders in our websites so the users can view with a web
browser. We can install business applications and publish in HTML.
DEPT OF BCA 10
 File Transfer Protocol: It is an industry standard protocol used for transferring files
between computers on a TCP/IP network. FTP enables to use one computer to host
multiple domain names.
 Simple Mail Transfer Protocol (SMTP): It is a standards-based, secure and scalable email
server. It supports a distributed email server using SMTP and Post Office Protocol
(POP3).
DEPT OF BCA 11
CHAPTER-2
SYSTEM ANALYSIS
DEPT OF BCA 12
CHAPTER-2
SYSTEM ANALYSIS
2.1 Preliminary analysis & Information gathering

Preliminary analysis is defined as the initial process at the start of a project that
determines whether the concept is viable. It looks at economic, market, industry and social trends
that influence the success of business endeavors associated with a proposed strategy. Preliminary
analysis is repeated in situations where primary investigations trigger updates to plans.
Conducting a preliminary analysis of a business strategy allows the organization to see the
viability of an intended goal. It creates a comprehensive idea of the enterprise objective and
states how the outcome is meant to be expressed.
The next step after envisioning the endgame is to verify that it is obtainable. Preliminary
analysis looks at necessary funding, environmental, social and legal factors that weigh on the
ability of a business to fully execute a plan. Any snag is caught at this stage and remedied,
allowing the organization to proceed with confidence that the overall vision is one that is safe to
pursue.
Risk analysis and cost assessments are critical parts of the preliminary analysis phase.
This gives leaders an idea of where the major concerns lie in a project. As it is impossible to rule
out all problems in the project management life cycle, it is important to anticipate as many of
these factors as possible with preliminary analytics.
INFORMATION GATHERING
It is the process of collecting information about something. Allow plenty of time
for information gathering as well as for making necessary applications for financial support.
Information gathering is carried out by surveying information about the similar applications:
DEPT OF BCA 13
The Commodities Price Extracting for Shop Online

As the shop online and its usage develop very fast, the content, structure, and usage data, and the
Web mining get more and more useful in everywhere such as e-supermarkets and e-commerce.
Many theories and algorithms are reported for Web mining. This paper shows a novel idea for
the commodities price extracting of shop online. The MVC design model and the Bottle
Formwork are opted to build the application system. The opened developing tools: Python
language and MySQL database are used to code the system program and construct the system
database respectively. The system architecture and the commodity classified are introduced. The
functions coded by Python are designed for implantation the commodities price extracting,
comparative analyzing, and system management.
Some of them are described in detail. Experiment demonstrates its performance and proves this
case is meaningful and useful for the storekeeper online.
 Memory Zones for Online Supermarket Shopping
Problems occur for users when they attempt to navigate or purchase items from a virtual
shopping environment that has to correlate in the physical world. These problems arise in part,
because online shoppers do not have the benefit of external memory provided by the physical
world. The memory zones idea attempts to solve these problems by providing an online parallel
to this external memory. The system reported uses a profile of previous purchases and a
representation of the physical environment of the actual shop to recommend Items to shoppers,
that they may have otherwise forgotten because of the lack of suitable external memory.
DEPT OF BCA 14
CHAPTER-3
SOFTWARE REQUIREMENTS
SPECIFICATION
DEPT OF BCA 15
CHAPTER-3
SOFTWARE REQUIREMENTS SPECIFICATION
3.1 Hardware Interface
Processor : i3 +
RAM : 4GB
Hard Disk : 80GB
Speed : 1.2 GHz+
3.2 Software Interface

Operating System : Windows 7 or Higher
IDE : Visual Studio 2010
Language : C#
Framework : ASP.NET 4.0
Back End : MS SQL Server
3.3 Communication Interface

HTTP Protocol
The Hypertext Transfer Protocol (HTTP) is an application protocol for distributed,

collaborative, hypermedia information systems. HTTP is the foundation of data communication
DEPT OF BCA 16
for the World Wide Web. Hypertext is structured text that uses logical links (hyperlinks)
between nodes containing text. HTTP is the protocol to exchange or transfer hypertext.
HTTP (Hypertext Transfer Protocol) is the set of rules for transferring files (text, graphic
images, sound, video, and other multimedia files) on the World Wide Web. As soon as a Web
user opens their Web browser, the user is indirectly making use of HTTP. HTTP is an
application protocol that runs on top of the TCP/IP suite of protocols (the foundation protocols
for the Internet).
HTTP concepts include (as the Hypertext part of the name implies) the idea that files can
contain references to other files whose selection will elicit additional transfer requests. Any Web
server machine contains, in addition to the Web page files it can serve, an HTTP daemon, a
program that is designed to wait for HTTP requests and handle them when they arrive. Your
Web browser is an HTTP client, sending requests to server machines. When the browser user
enters file requests by either "opening" a Web file (typing in a Uniform Resource Locator
or URL) or clicking on a hypertext link, the browser builds an HTTP request and sends it to the
Internet Protocol address (IP address) indicated by the URL. The HTTP daemon in the
destination server machine receives the request and sends back the requested file or files
associated with the request. (A Web page often consists of more than one file.)
3.4 Functional Requirements
In software engineering and systems engineering, a functional requirement defines a function of

a system or its component. A function is described as a set of inputs, the behavior, and outputs. It
should include descriptions of data to be entered into the system, operations performed by each
system, work-flows performed by the system and also how the system meets applicable
regulatory requirements.
Admin
1. Login
Admin can login to the application by providing the credentials like username and password.
2. Manage Category
DEPT OF BCA 17
Admin will be managing the product categories.
3. Manage Products stock based on Category
Product stocks based on the category will be managed by the admin.
4. Manage staff
Admin will be managing the supermarket staffs.
5. Manage Customers
Admin will be managing the customers.
6. View Requested Products
Admin can view the requested products.
7. Dispatch Products Requested by Customers
The dispatching of the products requested by the customers will be carried out by the admin.
8. View feedback
Admin can view the feedback posted by the customers.
9. Logout
Staff
1. Login
Staff can login to the application by providing the required valid credentials.
2. Check Admin Request
Staff can view the request of the products given to the admin.
3. Dispatch the product to respected customers
The products will be dispatched to the respective customers by the staff.
4. Edit profile
Staff can edit their profile.
DEPT OF BCA 18
5. Logout
Customer
1. Register
Customers have to first get registered to the application to access it.
2. Login
By providing the valid login credentials, customer can login to the application and access it.
3. View products based on category
Customer can view the products based on different categories.
4. Request the products
Customers can request for the product to admin as per their requirement.
5. View history
Customers can view the transaction history
6. Edit profile
Customers can edit their profile.
7. Post feedback
Customers can post feedback regarding the application and the transactions.
8. Logout
Visitor
1. Home
2. About Us
3. Contact Us
4. View products
DEPT OF BCA 19
Visitors can only view the products based on different categories.
3.5 Software Engineering Model Used

WATERFALL MODEL
Waterfall model is the earliest SDLC approach that was used for software development.
It is also referred to as a linear-sequential life cycle model. It is very simple to understand and
use. In a waterfall model, each phase must be completed before the next phase can begin and
there is no overlapping in the phases.
Following is a diagrammatic representation of different phases of waterfall model.
Fig: Waterfall Model
In "The Waterfall" approach, the whole process of software development is divided into
separate phases. In Waterfall model, typically, the outcome of one phase acts as the input for the
next phase sequentially. The sequential phases in Waterfall model are:
 Requirement Gathering and analysis:
All possible requirements of the system to be developed are captured in this phase and
documented in a requirement specification doc
DEPT OF BCA 20
 System Design:
The requirement specifications from first phase are studied in this phase and system
design is prepared. System Design helps in specifying hardware and system requirements and
also helps in defining overall system architecture.
 Implementation:
With inputs from system design, the system is first developed in small programs called
units, which are integrated in the next phase. Each unit is developed and tested for its
functionality which is referred to as Unit Testing.
 Integration and Testing:
All the units developed in the implementation phase are integrated into a system after
testing of each unit. Post integration the entire system is tested for any faults and failures.
 Deployment of system:
Once the functional and non-functional testing is done, the product is deployed in the
customer environment or released into the market.
 Maintenance:
 There are some issues which come up in the client environment. To fix those issues
patches are released. Also to enhance the product some better versions are released.
Maintenance is done to deliver these changes in the customer environment.
All these phases are cascaded to each other in which progress is seen as flowing steadily
downwards (like a waterfall) through the phases. The next phase is started only after the defined
set of goals are achieved for previous phase and it is signed off, so the name "Waterfall Model".
In this model phases do not overlap.
DEPT OF BCA 21
3.7 Project schedule
The project schedule is the tool that communicates what work needs to be performed, which
resources of the organization will perform the work and the timeframes in which that work needs
to be performed. The project schedule should reflect all of the work associated with delivering
the project on time.
DEPT OF BCA 22
CHAPTER-4
SYSTEM DESIGN
DEPT OF BCA 23
CHAPTER-4
SYSTEM DESIGN
4.1 System Design

The purpose of the design phase is to plan a solution of the problem specified by the
requirements document. This phase is the first step in moving from the problem domain to the
solution domain. In other words, starting with what is needed; design takes us toward how to
satisfy the needs. The design of a system is perhaps the most critical factor affecting the quality
of the software; it has a major impact on the later phases particularly testing and maintenance.
The design activity often results in three separate outputs –
 Architecture design.
 High level design.
 Detailed design.
Architecture Design:
Architecture focuses on looking at a system as a combination of many different components, and

how they interact with each other to produce the desired result. The focus is on identifying
components or subsystems and how they connect. In other words, the focus is on what major
components are needed.
High Level Design:
In high level design identifies the modules that should be built for developing the system and the
specifications of these modules. At the end of system design all major data structures, file
format, output formats, etc., are also fixed. The focus is on identifying the modules. In other
words, the attention is on what modules are needed.
DEPT OF BCA 24
Detailed Design: In the detailed design the internal logic of each of the modules is specified.
The focus is on designing the logic for each of the modules. In other words how modules can be
implemented in software is the issue. A design methodology is a systematic approach to creating
a design by application of a set of techniques and guidelines. Most methodologies focus on high
level design.
4.2 Database Design
DEPT OF BCA 25
4.3 Data flow diagram
A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system. DFDs can also be used for the visualization of data processing (structured
design). On a DFD, data items flow from an external data source or an internal data store to an
internal data store or an external data sink, via an internal process. A DFD provides no
information about the timing of processes, or about whether processes will operate in sequence
or in parallel. It is therefore quite different from a flowchart, which shows the flow of control
through an algorithm, allowing a reader to determine what operations will be performed, in what
order, and under what circumstances, but not what kinds of data will be input to and output from
the system, nor where the data will come from and go to, nor where the data will be stored (all of
which are shown on a DFD).
Symbols used in DFD’s:
Processes:
A process transforms data values. The lowest processes are our functions without side effects.
Data Flows:
A data flow connects the output of an object or process to the input of another object or process.
It represents the intermediate data values within the computation. It is draws as an arrow between
the procedure and the consumer of the data value. The arrow is labeled with the description of
the data, usually its name or type.
Actors:
An actor is an active object that drives the data flow graph by producing or consuming values.
Actors are attached to the inputs and the outputs of a dataflow graph. In sense, the actors lie on
the
boundary of the flow graph but terminate the flow of data as sources and sinks of data, and so are
sometimes called terminators.
DEPT OF BCA 26
Data Store:
A data store is a passive object within a data flow diagram that stores data for later access.
Unlike an actor, a data store does not generate any operations on its own but merely responds to
requests to store and access data.
Context data flow diagram:
It is common practice to draw a context-level data flow diagram first, which shows the
interaction between the system and external agents which act as data sources and data sinks. On
the context diagram (also known as the 'Level 0 DFD') the system's interactions with the outside
world are modeled purely in terms of data flows across the system boundary. The context
diagram shows the entire system as a single process, and gives no clues as to its internal
organization. This context-level DFD is next "exploded", to produce a Level 1 DFD that shows
some of the detail of the system being modeled. The Level 1 DFD shows how the system is
divided into sub-systems (processes), each of which deals with one or more of the data flows to
or from an external agent, and which together provide all of the functionality of the system as a
whole. It also identifies internal data stores that must be present in order for the system to do its
job, and shows the flow of data between the various parts of the system.
CONTEXT FLOW DIAGRAM
DEPT OF BCA 27
DATA FLOW DIAGRAM
Fig: DFD for Admin
DEPT OF BCA 28
Fig: DFD for Staff
Fig: DFD for Customer
DEPT OF BCA 29
4.4 ER diagram
An entity relationship diagram (ERD) shows the relationships of entity sets stored in a
database. An entity in this context is a component of data. In other words, ER diagrams illustrate
the logical structure of databases.
In entity–relationship model (ER model) describes inter-related things of interest in a

specific domain of knowledge. An ER model is composed of entity types (which classify the
things of interest) and specifies relations. In software engineering an ER model is commonly
formed to represent things that a business needs to remember in order to perform business
processes. Consequently, the ER model becomes an abstract data model that defines a data or
information structure that can be implemented in a database, typically a relational database
relationships that can exist between instances of those entity types. Entity–relationship modeling
was developed for database design by Peter Chen and published in a 1976 paper. However,
variants of the idea existed previously. Some ER modelers show super and subtype entities
connected by generalization-specialization relationships, and an ER model can be used also in
the specification of domain-specific ontologies.
An entity–relationship model is usually the result of systematic analysis to define and

describe what is important to processes in an area of a business. It does not define the business
processes; it only presents a business data schema in graphical form. It is usually drawn in a
graphical form as boxes (entities) that are connected by lines (relationships) which express the
associations and dependencies between entities.
Entities may be characterized not only by relationships, but also by additional properties
(attributes), which include identifiers called "primary keys". Diagrams created to represent
attributes as well as entities and relationships may be called entity-attribute-relationship
diagrams, rather than entity-relationship models.
An ER model is typically implemented as a database. In a simple relational database

implementation, each row of a table represents one instance of an entity type, and each field in a
table represents an attribute type. In a relational database a relationship between entities is
DEPT OF BCA 30
implemented by storing the primary key of one entity as a pointer or "foreign key" in the table of
another entity
Benefits of ER diagrams
ER diagrams constitute a very useful framework for creating and manipulating databases.
First, ER diagrams are easy to understand and do not require a person to undergo extensive
training to be able to work with it efficiently and accurately. This means that designers can use
ER diagrams to easily communicate with developers, customers, and end users, regardless of
their IT proficiency. Second, ER diagrams are readily translatable into relational tables which
can be used to quickly build databases. In addition, ER diagrams can directly be used by
database developers as the blueprint for implementing data in specific software applications.
Lastly, ER diagrams may be applied in other contexts such as describing the different
relationships and operations within an organization.
Fig: ER Diagram
DEPT OF BCA 31
4.5 USE CASE DIAGRAM
Use case diagrams model the functionality of a system using actors and use cases. Use
cases are services or functions provided by the system to its users. Use case diagrams are
usually referred to as behavior diagrams used to describe a set of actions (use cases) that some
system or systems (subject) should or can perform in collaboration with one or more external
users of the system (actors). Each use case should provide some observable and valuable result
to the actors or other stakeholders of the system.
Use cases:
A use case describes a sequence of actions that provide something of measurable value to
an actor and is drawn as a horizontal ellipse.
Actors:
An actor is a person, organization, or external system that plays a role in one or more
interactions with your system. Actors are drawn as stick figures.
Associations:
Associations between actors and use cases are indicated in use case diagrams by solid
lines. An association exists whenever an actor is involved with an interaction described by a use
case.
System boundary boxes:
You can draw a rectangle around the use cases, called the system boundary box, to
indicate the scope of your system. Anything within the box represents functionality that is in
scope.
DEPT OF BCA 32
Fig: Use case Diagram for Admin
Fig: Use case Diagram for Staff
DEPT OF BCA 33
Fig: Use case Diagram for Customer
4.6 Sequence diagram

The Sequence Diagram models the collaboration of objects based on a time sequence. It shows
how the objects interact with others in a particular scenario of a use case. With the advanced
visual modeling capability, you can create complex sequence diagram in few clicks. Besides,
Visual Paradigm can generate sequence diagram from the flow of events which you have defined
in the
use case description. The sequence diagram models the collaboration of objects based on a time
sequence. It shows how the objects interact with others in a particular scenario of a use case. It
depicts the objects and classes involved in the scenario and the sequence of messages exchanged
between the objects needed to carry out the functionality of the scenario.
Lifelines:
A sequence diagram shows, as parallel vertical lines (lifelines), which indicates different
processes or objects that live simultaneously.
Message:
DEPT OF BCA 34
Messages written with horizontal arrows with the message name written above them,
display interaction. The messages are written in the order in which they occur. This allows the
specification of simple runtime scenarios in a graphical manner.
Object/Activation Box/Process:
Activation boxes, or method-call boxes, are opaque rectangles drawn on top of lifelines to
represent that processes are being performed in response to the message.
Fig: Sequence Diagram for Admin
Fig: Sequence Diagram for Staff
DEPT OF BCA 35
Fig: Sequence Diagram for Customer
4.7 Class diagram

A class diagram models the static structure of a system. It shows relationships between classes,
objects, attributes, and operations.
Classes
Classes represent an abstraction of entities with common characteristics. Associations represent

the relationships between classes.
Illustrate classes with rectangles divided into compartments. Place the name of the class in the
first partition (centered, bolded, and capitalized), list the attributes in the second partition (left-
aligned, not bolded, and lowercase), and write operations into the third.
DEPT OF BCA 36
Active Classes
Active classes initiate and control the flow of activity, while passive classes store data and serve
other classes. Illustrate active classes with a thicker border.
Visibility
Use visibility markers to signify who can access the information contained within a class. Private
visibility, denoted with a - sign, hides information from anything outside the class partition.
Public visibility, denoted with a + sign, allows all other classes to view the marked information.
Protected visibility, denoted with a # sign, allows child classes to access information they
inherited from a parent class.
DEPT OF BCA 37
Associations
Associations represent static relationships between classes. Place association names above, on, or
below the association line. Use a filled arrow to indicate the direction of the relationship. Place
roles near the end of an association. Roles represent the way the two classes see each other.
Multiplicity (Cardinality)
Place multiplicity notations near the ends of an association. These symbols indicate the number
of instances of one class linked to one instance of the other class. For example, one company will
have one or more employees, but each employee works for just one company.
DEPT OF BCA 38
4.8 Object diagram
An object diagram in the Unified Modeling Language (UML), is a diagram that shows a

complete or partial view of the structure of a modeled system at a specific time.
In the Unified Modeling Language (UML), an object diagram focuses on some particular set

of objects and attributes, and the links between these instances. A correlated set of object
diagrams provides insight into how an arbitrary view of a system is expected to evolve over time.
In early UML specifications the object diagram is described as:
Object diagrams and class diagrams are closely related and use almost identical notation. Both
diagrams are meant to visualize static structure of a system. While class diagrams show classes,
object diagrams display instances of classes (objects). Object diagrams are more concrete
than class diagrams. They are often used to provide examples or act as test cases for class
diagrams. Only aspects of current interest in a model are typically shown on an object diagram.
DEPT OF BCA 39
CHAPTER-5
TESTING
DEPT OF BCA 40
CHAPTER-5
TESTING
Software testing is performed to verify that the completed software package functions
according to the expectations defined by the requirements/specifications. The overall objective is
not to find every software bug that exists, but to uncover situations that could negatively impact
the customer, usability and/or maintainability.
5.1 PURPOSE OF TESTING
 Finding defects which may get created by the programmer while developing the
software.
 To prevent defects.
 To make sure that the end result meets the business and user requirements.
 To ensure that it satisfies the BRS that is Business Requirement Specification and SRS
that is System Requirement Specifications.
 To gain the confidence of the customers by providing them a quality product.
TYPES OF TESTING
DEPT OF BCA 41
There are two types of testing. They are:
1. White Box Testing
2. Black Box Testing
WHITE BOX TESTING
It is a software testing method in which the internal structure/design/implementation of

the item being tested is known to the tester. The tester chooses inputs to exercise paths through
the code and determines the appropriate outputs. Programming know-how and the
implementation knowledge is essential. This method is named so because the software program,
in the eyes of the tester, is like a white/transparent box; inside which one clearly sees. Internal
software and code working should be known for this type of testing. Tests are based on coverage
of code statements, branches, paths, conditions. Also known as structural testing and Glass box
Testing.
BLACK BOX TESTING
Internal system design is not considered in this type of testing. Tests are based on requirements
and functionality. This method is named so because the software program, in the eyes of the
tester, is like a black box; inside which one cannot see. Black box testing is a testing technique
that ignores the internal mechanism of the system and focuses on the output generated against
any input and execution of the system. It is also called functional testing.
5.2 LEVELS OF TESTING
There are four levels of software testing.
1. UNIT TESTING
Unit Testing is a level of the software testing process where individual units/components of a
DEPT OF BCA 42
software/system are tested. The purpose is to validate that each unit of the software performs as
designed.
2. INTEGRATION TESTING
Integration Testing is a level of the software testing process where individual units are combined
and tested as a group. The purpose of this level of testing is to expose faults in the interaction
between integrated units.
3. SYSTEM TESTING
System Testing is a level of the software testing process where a complete, integrated
system/software is tested. The purpose of this test is to evaluate the system’s compliance with the
specified requirements.
System Testing is a level of the software testing process where a complete, integrated
system/software is tested. The purpose of this test is to evaluate the system’s compliance with
the specified requirements.
4. ACCEPTANCE TESTING
Acceptance Testing is a level of the software testing process where a system is tested for
acceptability. The purpose of this test is to evaluate the system’s compliance with the business
requirements and assess whether it is acceptable for delivery.
Acceptance testing or User Acceptance Testing (UAT) is a level of the software testing
process where a system is tested for acceptability. The purpose of this test is to evaluate the
system’s compliance with the business requirements and assess whether it is acceptable for
delivery.
User Acceptance Testing (UAT) is performed by Users or on behalf of the users to ensure that
the Software functions in accordance with the Business Requirement Document. UAT focuses
on the following aspects:
DEPT OF BCA 43
 All functional requirements are satisfied.
 All performance requirements are achieved.
 Other requirements like transportability, compatibility, error recovery etc. are satisfied.
 Acceptance criteria specified by the user is met.
5.3 REGRESSION TESTING
The purpose of regression testing is to confirm that a recent program or code change has
not adversely affected existing features. Regression testing is nothing but full or partial selection
of already executed test cases which are re-executed to ensure existing functionalities work fine.
This testing is done to make sure that new code changes should not have side effects on the
existing functionalities. It ensures that old code still works once the new code changes are done.
Regression testing is the process of testing changes to computer programs to make sure
that the older programming still works with the new changes. Regression testing is a normal part
of the program development process and, in larger companies, is done by code testing specialists.
Test department coders develop code test scenarios and exercises that will test new units of code
after they have been written. These test cases form what becomes the test bucket. Before a new
version of a software product is released, the old test cases are run against the new version to
make sure that all the old capabilities still work. The reason they might not work is because
DEPT OF BCA 44
changing or adding new code to a program can easily introduce errors into code that is not
intended to be changed.
CHAPTER-6
IMPLEMENTATION
DEPT OF BCA 45
CHAPTER-6
IMPLEMENTATION
This application is implemented using object-oriented programming language. Object oriented

programming is an approach that provides a way of modularizing programs by creating
partitioned memory area for both data and functions that can be used as templates for creating
copies of such modules on demand.
Features of Object-Oriented paradigm:
 Emphasis is on data rather than procedure.
 Programs are divided into what are known as objects.
 Data structures are designed such that they characterize the objects.
 Methods that operate on the data of an object are tied together in the data structure.
 Objects may communicate with each other through methods.
DEPT OF BCA 46
 New data and methods can be easily added whenever necessary.
 Follows bottom-up approach in program design.
 Data is hidden and cannot be accessed by external functions.
CHAPTER-7
DEPT OF BCA 47
CONCLUSION AND
FUTURE ENHANCEMENT
DEPT OF BCA 48
CHAPTER-7
CONCLUSION AND FUTURE ENHANCEMENT
Conclusion:
Supermarkets make up for their low margins by a higher overall volume of sales, and with the
sale of higher-margin items bought by the intended higher volume of shoppers. Customers
usually shop by placing their selected merchandise into shopping carts (trolleys) or baskets (self-
service) and pay for the merchandise at the check-out. Many supermarket chains are attempting
to further reduce labor costs by shifting to self-service check-out machines, where a single
employee can oversee and assist multiple customers at a time.
This web-based application helps customers to choose their daily needs and add products to the
cart. Admin will send the list provided by the customers to the staff. Customers provide their
complete detail of address and contact number and they get their chosen products in their home.
Future Enhancements:
In future this application can be enhanced in different ways:
 Notifications to users can be sent by the supermarkets regarding the special offers or
discounts they are providing for the products.
 Supermarkets can advertise the products which are in demand to the users and increase
the productivity of the products.
DEPT OF BCA 49
CHAPTER-8
ANNEXURE
CHAPTER-8
ANNEXURE
DEPT OF BCA 50
DEPT OF BCA 51
DEPT OF BCA 52
DEPT OF BCA 53
DEPT OF BCA 54
DEPT OF BCA 55
CHAPTER-9
REFERENCE
DEPT OF BCA 56
CHAPTER-9
REFERENCE
 https://en.wikipedia.org/wiki/.NET_Framework
 https://www.asp.net/
 https://dotnetfoundation.org/
 https://www.tutorialspoint.com/csharp/
 https://www.guru99.com/c-tutorial.html
 “Programming in C#, 3E” by Bal Guruswamy Tata McGraw-Hill Education, 2010
 “Begin ASP.NET 2.0 with visual C#.NET”, Wrox, By Chris Ullman.
 Software Engineering, Ian Summerville, Sixth Edition, Pearson Education Ltd, 2001
 Ian Sommerville, Software Engineering, Pearson Education, Sixth Edition
 ASP.net complete reference - Pearson Publication
DEPT OF BCA 57

Bca Project

Uploaded by

Document Information

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

Bca Project

Uploaded by

Copyright:

Available Formats

A PROJECT REPORT

A Dissertation submitted in partial fulfillment of the requirements for the award of

BACHELORS OF COMPUTER APPLICATIONS

Under the Guidance of

Department of Computer Applications

BANGALORE INSTITUTE OF MANAGEMENT STUDIES

A Dissertation submitted in partial fulfillment of the requirements for the award of

BACHELORS OF COMPUTER APPLICATIONS

Under the Guidance of

BANGALORE INSTITUTE OF MANAGEMENT STUDIES

BANGALORE INSTITUTE OF MANAGEMENT STUDIES

NO.35, MYSORE ROAD, BANGALORE -59

Department of Computer Applications

Signature of Guide Head of the Department

Name: NAVYA BAI C T

We express immense pleasure to Mrs. Sumathi Srinivas (MINDTREE) Project Manager,

NAVYA BAI C.T

SL.NO CHAPTER PAGE .N

1.1 Basic introduction of Project

Supermarkets typically are chain stores, supplied by the distribution centers of their parent

products (typically staple foods such as bread, milk and sugar) are very occasionally sold as loss

A larger full-service supermarket combined with a department store is sometimes known as

1.2 Objective and Scope

1.3 Project Category

1.4 Tools and Technologies used

Fig: MICROSOFT .NET FRAMEWORK

Common Language Runtime

Unified programming classes

1.5 Introduction to C#:

C# (pronounced as ‘C Sharp’) is a new computer-programming language developed by

 It is a brand new language derived from the C/C++ family.

 TIt simplifies and modernizes C++.

 It is the only component-oriented language available today.

 It is the only language designed for the .NET Framework.

 It is a concise, lean and modern language.

Visual Basic, the power of C++ and the elegance of Java.

 It is intrinsically object-oriented and web-enabled.

 It has a lean and consistent syntax.

 It embodies today’s concern for simplicity, productivity and robustness.

 It will become the language of choice for .NET programming.

 Major parts of .NET Framework are actually coded in C#.

1.6 INTRODUCTION TO ASP.NET

 A page and controls framework

Ado.Net - Database Connectivity:

ADO.NET Data Architecture

The dataset is a disconnected, in-memory representation of data. It can be considered as a local

1.7 Introduction to SQL Server 2005:

Data Transformation Services (DTS) provide an extremely flexible method for importing

1.8 Internet Information Server [IIS]:

2.1 Preliminary analysis & Information gathering

The Commodities Price Extracting for Shop Online

SOFTWARE REQUIREMENTS SPECIFICATION

3.1 Hardware Interface

Hard Disk : 80GB

Speed : 1.2 GHz+

3.2 Software Interface

IDE : Visual Studio 2010

Framework : ASP.NET 4.0

Back End : MS SQL Server

3.3 Communication Interface

The Hypertext Transfer Protocol (HTTP) is an application protocol for distributed,

3.4 Functional Requirements

In software engineering and systems engineering, a functional requirement defines a function of

3. Manage Products stock based on Category