CHAPTER 1

PROJECT DESCRIPTION
1.1 INTRODUCTION

This project is online cameras shopping and purchasing using Payment Gateway. Using
this software, companies can improve the efficiency of their services. Online Shopping is one of
the applications to improve the marketing of theCompany’sproducts. This Web application
involves all the features of the online shopping. Camera, their features, and new updates easily. It
is designed such a way that one can view all the updates of the mobile from any place through
online. The software will help in easy maintaining and updating products in the website for the
administrator. Also quick and easy comparison of different products for the customers. The
system will reduce the manual operation required to maintain all the records of booking
information. And also generates the various reports for analysis. Main concept of the project is to
enter transaction reports and to maintain customer records. Hence this software can be used in
any camera showroom to maintain their record easily. Though photography is prohibited in
museums, historical monuments, temples, user tend to capture images of these sites secretly,
which is not significant? Considering the piracy at theatres, Indian film industry suffers heavy
losses due to it. To avoid such problems, there is a need to develop a system which will detect
any digital (DSLR) camera and then neutralize image or video taken by that camera. Film
industry also suffers 1/3 loss due to movie piracy. Hence, there arises a need to prevent this
undesired photography, to avoid this heavy loss. This Project will be useful for detecting and
deactivating digital cameras in photography prohibited areas. It consists of two parts. The first
part is camera detection unit. The second part is digital image deactivating unit. Camera
detection unit includes camera interfaced with Raspberry . There is a camera in the photography
prohibited area which is used to capture the image in that prohibited area. When there is any
digital camera appears in the photography prohibited area, then that digital camera is detected by
using the image processing algorithms. In our proposed system, a method for identifying and
harming video nature of advanced cameras in photography restricted zones in view of picture
handling is composed. The system will comprise of two sections: Camera location unit and
Camera deactivating unit. Camera location unit incorporates web cam interfaced with. Web cam
will be utilized to catch the pictures of precluded zone. The situation of the camera focal point
will be observed by distinguishing and following the focal point. Discovery and Position of the
focal point of camera will be followed by Picture preparing Control motion from camera
recognition part will be created and sent through serial correspondence to microcontroller. IR
transmitter will be utilized to lessen the nature of the caught picture.

1.2 EXISTING SYSTEM

This project is a web based shopping system for an existing shop. The project objective is
to deliver the online shopping application into android platform. Physical design produces the
working system by defining the design specifications

DISADVANTAGES

 Delay in delivery.
 Lack of significant discounts in online shops.
 Lack of touch and feel of merchandise in online shopping.
 Interactivity in online shopping.
 Lack of shopping experience.
 Close examination in online shopping.
 Frauds in online shopping.

1.3 PROPOSED SYSTEM

The proposed system is based on the camera based product identification for blind
persons. They will not be familiarized with smart camera and cannot use the applications
installed in it to recognize the corresponding objects by barcode detection. And the QR code
reader is especially for scanning and billing purpose which also cannot be used by visually
impaired ones. In order to overcome the limitations of existing system we proposed a new
system, which is, Aspects. Here the visually impaired people have to wear spectacles and keep
the object they wish to purchase in front of the specs. It will recognize the barcode and retrieve
the corresponding details of the object from it. The details of this object will be given to them as
an audio output through head phones. The details include the prize of the said object alongside
the name of the object helping in comparison of same product from different brands.
ADVANTAGES

 It will help to stop capturing images in camera restricted areas.

 This system can be installed easily anywhere; it is very portable.
 Maintenance of this system is easy.
 Low cost cameras are required therefore this could be very affordable for all.
1.3.1 HARDWARE REQUIREMENTS
 Processor : Dual core processor 2.6.0 GHz
 RAM : 1GB
 Hard disk : 160 GB
 Compact Disk : 650 MB
 Keyboard : Standard keyboard
 Monitor : 15 inch color monitor

1.3.2 SOFTWARE SPECIFICATION

 Front End : .NET
 IDE : dream weaver
 Back End : My SQL

Software description
What is .NET?
When .NET was announced in late 1999, Microsoft positioned the technology as a
platform for building and consuming Extensible Markup Language (XML) Web services. XML
Web services allow any type of application, be it a Windows- or browser-based application
running on any type of computer system, to consume data from any type of server over the
Internet. The reason this idea is so great is the way in which the XML messages are transferred:
over established standard protocols that exist today. Using protocols such as SOAP, HTTP, and
SMTP, XML Web services make it possible to expose data over the wire with little or no
modifications to your existing code.
Since the initial announcement of the .NET Framework, it's taken on many new and
different meanings to different people. To a developer, .NET means a great environment for
creating robust distributed applications. To an IT manager, .NET means simpler deployment of
applications to end users, tighter security, and simpler management. To a CTO or CIO, .NET
means happier developers using state-of-the-art development technologies and a smaller bottom
line. To understand why all these statements are true, you need to get a grip on what the .NET
Framework consists of, and how it's truly a revolutionary step forward for application
architecture, development, and deployment.
NET Framework
Now that you are familiar with the major goals of the .NET Framework, let's briefly
examine its architecture. As you can see in Figure 1-2, the .NET Framework sits on top of the
operating system, which can be a few different flavors of Windows and consists of a number of
components .NET is essentially a system application that runs on Windows.
Conceptually, the CLR and the JVM are similar in that they are both runtime infrastructures that
abstract the underlying platform differences. However, while the JVM officially supports only
the Java language, the CLR supports any language that can be represented in its Common
Intermediate Language (CIL). The JVM executes byte code, so it can, in principle, support many
languages, too. Unlike Java's byte code, though, CIL is never interpreted. Another conceptual
difference between the two infrastructures is that Java code runs on any platform with a JVM,
whereas .NET code runs only on platforms that support the CLR. In April, 2003, the
International Organization for Standardization and the International Electro technical Committee
(ISO/IEC) recognized a functional subset of the CLR, known as the Common Language
Interface (CLI), as an international standard.
This development, initiated by Microsoft and developed by ECMA International, a
European standards organization, opens the way for third parties to implement their own versions
of the CLR on other platforms, such as Linux or Mac OS X. For information on third-party and
open source projects working to implement the ISO/IEC CLI and C# specifications The layer on
top of the CLR is a set of framework base classes. This set of classes is similar to the set of
classes found in STL, MFC, ATL, or Java. These classes support rudimentary input and output
functionality, string manipulation, security management, network communications, thread
management, text management, reflection functionality, collections functionality, as well as
other functions.
 On top of the framework base classes is a set of classes that extend the base classes to
support data management and XML manipulation. These classes, called ADO.NET, support
persistent data management—data that is stored on backend databases. Alongside the data
classes, the .NET Framework supports a number of classes to let you manipulate XML data and
perform XML searching and XML translations. Classes in three different technologies (including
web services, Web Forms, and Windows Forms) extend the framework base classes and the data
and XML classes. Web services include a number of classes that support the development of
lightweight distributed components, which work even in the face of firewalls and NAT software.
These components support plug-and-play across the Internet, because web services employ
standard HTTP and SOAP.
Web Forms, the key technology behind ASP.NET, include a number of classes that allow
you to rapidly develop web Graphical User Interface (GUI) applications. If you're currently
developing web applications with Visual Interdev, you can think of Web Forms as a facility that
allows you to develop web GUIs using the same drag-and-drop approach as if you were
developing the GUIs in Visual Basic. Simply drag-and-drop controls onto your Web Form,
double-click on a control, and write the code to respond to the associated event. Windows Forms
support a set of classes that allow you to develop native Windows GUI applications. You can
think of these classes collectively as a much better version of the MFC in C++ because they
support easier and more powerful GUI development and provide a common, consistent interface
that can be used in all languages.
The Common Language Runtime
 Automatic memory management
 Cross-language debugging
 Cross-language exception handling

Inside the Common Language Runtime

The common language runtime enables code running in its execution environment to
have features such as security, versioning, memory management and exception handling because
of the way .NET code actually executes. When you compiled Visual Basic 6 forms applications,
you had the ability to compile down to native node or p-code. Visual Studio.net offers a rich set
of development tools that hide a lot of the complexity inherent in working with the .NET
Framework. This reduces time spent both learning the product and developing applications.
When Visual Studio .NET is installed, the CLR and the .NET Framework classes are also
installed. These are command line applications that are built without a graphical user interface
(GUI) and which can be executed from, and interact with, a DOS Window. In addition to their
intrinsic value, they can be particularly useful for testing sections of code to ensure proper
functionality

WINDOWS FORMS

 These are rich-client applications that are built around a GUI similar to desktop
applications written using Visual FoxPro 7.0. New features for client applications
developed in the .NET Framework include visual inheritance, code-free resizing,
automatic control updates, and new controls.

WEB FORMS

 These are browser-based applications that are built around a GUI with special controls.
Web form applications are written using ASP.NET.

XML WEB SERVICES

 These are applications that define XML Web services that can be consumed by other
XML Web services or applications either on a local network or exposed on the Internet.
Because they are based on HTTP and XML, the information they transfer can be passed
through firewalls.

Overview of ASP.NET

ASP.NET is used to create programmable Web pages as part of Web form

applications. Not only can ASP.NET produce dynamic Web pages, but it can also tailor
them to the browser being used by the user. Development in ASP.NET is much easier
because it contains a wide range of object-oriented server-side controls ready for use in
applications. ASP.NET actually supports four different types of control:
HTML server controls

These are programmable HTML elements that are exposed to the server. HTML server
controls expose an object model that maps very closely to the HTML elements that they
render.

WEB SERVER CONTROLS

These controls have more built-in features than HTML server controls. Web server
controls include not only form-type controls, such as buttons and text boxes, but also
special-purpose controls, such as a calendar. Web server controls are more abstract than
HTML server controls in that their object model does not necessarily reflect HTML
syntax.

VALIDATION CONTROLS

These are controls that incorporate logic and that can be attached to an input control to
test what the user enters. Some validation controls check for a required field, a specific
value or pattern of characters, that a value falls within a specified range, and so on.

USER CONTROLS

These are custom controls created as Web Forms pages. Web Forms user controls can be
embedded in other Web Forms pages and provide an easy way to create menus, toolbars,
and other reusable elements.
 CHAPTER 2
LOGICAL DEVELOPMENT

2.1 DATA FLOW DIAGRAM

A two-dimensional diagram explains how data is processed and transferred in a system.

The graphical depiction identifies each source of data and how it interacts with other data
sources to reach a common output. Individuals seeking to draft a data flow diagram must identify
external inputs and outputs, determine how the inputs and outputs relate to each other, and
explain with graphics how these connections relate and what they result in.
Data flow Symbols:
Symbol Description

An entity. A source of data or a destination

for data.

A process or task that is performed by the

system.

A data store, a place where data is held

between processes.

A data flow.
 This type of diagram helps business development and design teams visualize how data is
processed and identify or improve certain aspects.
LEVEL 0

DFD Level 0 is also called a Context Diagram. It’s a basic overview of the whole system or
process being analyzed or modeled. It’s designed to be an at-a-glance view, showing the system
as a single high-level process, with its relationship to external entities. It should be easily
understood by a wide audience, including stakeholders, business analysts, data analysts and

Admin

Online camera shopping Customer

system

Database

Fig 2.1.1 level 0-DFD

LEVEL 1

DFD Level 1 provides a more detailed breakout of pieces of the Context Level Diagram.
You will highlight the main functions carried out by the system, as you break down the high-
level process of the Context Diagram into its sub – processes.
 1.0
Admin User
Register

2.0

Online payment

3.0
Database
View the user
details
2.2 ARCHITECTURAL DIAGRAM

This article will look at all forms of cameras, catering to all photography levels. The best
camera for architecture photography will have a full frame sensor. But there is a case to be made
of other camera types as well.
Smartphone’s continue to advance in quality. And Samsung and Apple products lead the way.
The ability to use them on a tripod, and even change the lenses makes them more versatile than
ever.

ONLINE CAMERA SHOPPING

Store

Admin

Database
Customer Register

Fig 2.2.1 architectural diagram

 CHAPTER 3
DATABASE DESIGN
3.1 DATA DICTIONARY

3.3 RELATIONSHIP DIAGRAM

An entity–relationship model (ER model for short) describes interrelated things of

interest in a specific domain of knowledge. A basic ER model is composed of entity types
(which classify the things of interest) and specifies relationships that can exist
between entities (instances of those entity types). In software engineering, an ER model is
commonly formed to represent things 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 which can be implemented in a database, typically a relational database.
Fig 3.3.3ER diagram
 CHAPTER 4
PROGRAM DESIGN
4.1 MODULES

4.1.1 ADMIN LOGIN

Admin is the one who manages the student details and the parent details. They had
permission to add the student and the parents to the database. They will intimate the user about
the timing of the student to the parents. Thus they will manage each and every details of the
student and the user.

4.1.2 REGISTRATION:

Student and the parents need to enter their details for verification purpose. The parents
should register their valid mobile number and mail id to sent the notifications to the parents. In
student registration parents details should be enrolled such that the intimation will be easily sent
to the parent.

4.1.3ADD PRODUCT

The shopping camera project contains different kind of products. The products can be classified
into different categories by name. Admin can add new products into the existing system with all
its details including an image.

4.1.4 VIEW USER

Admin will have a list view of all the user registered in the system. Admin can view all the
details of details of each user in the list except password.
 CHAPTER 5

SYSTEM TESTING

5.1 Testing

Testing is a series of different tests that whose primary purpose is to fully exercise the
computer based system. Although each test has a different purpose, all work should verify that
all system element have been properly integrated and performed allocated function. Testing is
the process of checking whether the developed system works according to the actual requirement
and objectives of the system. The philosophy behind testing is to find the errors. A good test is
one that has a high probability of finding an undiscovered error. A successful test is one that
uncovers the undiscovered error. Test cases are devised with this purpose in mind. A test case is
a set of data that the system will process as an input.

5.1.1 Types of Testing:

5.1.2 System testing

After a system has been verified, it needs to be thoroughly tested to ensure that every component
of the system is performing in accordance with the specific requirements and that it is operating
as it should including when the wrong functions are requested or the wrong data is introduced.

Testing measures consist of developing a set of test criteria either for the entire system or for
specific hardware, software and communications components. For an important and sensitive
system such as an electronic voting system, a structured system testing program may be
established to ensure that all aspects of the system are thoroughly tested.

Testing measures that could be followed include:

 Applying functional tests to determine whether the test criteria have been met
 Applying qualitative assessments to determine whether the test criteria have
been met.
 Conducting tests in “laboratory” conditions and conducting tests in a variety of
“real life” conditions.
  Conducting tests over an extended period of time to ensure systems can
perform consistently.
 Conducting “load tests”, simulating as close as possible likely conditions while
using or exceeding the amounts of data that can be expected to be handled in an
actual situation.
Test measures for hardware may include:

 Applying “non-operating” tests to ensure that equipment can stand up to expected levels
of physical handling.
 Testing “hard wired” code in hardware (firmware) to ensure its logical correctness and
that appropriate standards are followed.

Tests for software components also include:

 Testing all programs to ensure its logical correctness and that appropriate design,
development and implementation standards have been followed.
 Conducting “load tests”, simulating as close as possible a variety of “real life” conditions
using or exceeding the amounts of data that could be expected in an actual situation.
 Verifying that integrity of data is maintained throughout its required manipulation.

5.1.3 Unit testing

The first test in the development process is the unit test. The source code is normally divided into
modules, which in turn are divided into smaller units called units. These units have specific
behavior. The test done on these units of code is called unit test. Unit test depends upon the
language on which the project is developed.

Unit tests ensure that each unique path of the project performs accurately to the documented
specifications and contains clearly defined inputs and expected results. Functional and reliability
testing in an Engineering environment. Producing tests for the behavior of components (nodes
and vertices) of a product to ensure their correct behavior prior to system integration.
5.1.4 System testing

Several modules constitute a project. If the project is long-term project, several developers write
the modules. Once all the modules are integrated, several errors may arise. The testing done at
this stage is called system test. System testing ensures that the entire integrated software system
meets requirements. It tests a configuration to ensure known and predictable results. System
testing is based on process descriptions and flows, emphasizing pre-driven process links and
integration points. Testing a specific hardware/software installation. This is typically performed
on a COTS (commercial off the shelf) system or any other system comprised of disparate parts
where custom configurations and/or unique installations are the norm.

5.1.5 Integration testing

Testing is which modules are combined and tested as a group. Modules are typically code
modules, individual applications, source and destination applications on a network, etc.
Integration Testing follows unit testing and precedes system testing. Testing after the product is
code complete. Betas are often widely distributed or even distributed to the public at large in
hopes that they will buy the final product when it is release.

CHAPTER 6
CONCLUSION
 The project entitled “Online camera Shopping “is developed using ASP.Net as front end
and SQL Server database in back end to computerize the process of online buying and selling of
mobiles in a showroom. This project covers only the basic features required. However a lot of
features are already incorporated in this project. The main beneficiaries are both customers as
well as admin who consume more time while dealing with camera. Moreover extra features can
be identified and incorporated in the future In order to accommodate additional features it will
take longer time and effort to understand the requirement and converting it into computerized
system.

CHAPTER 7
REFERENCES
BIBLIOGRAPHY

Book reference:

[1]ASP.NET 3.5 Unleashed, by Stephen Walther. SAMS Publishing, ISBN

[2]Microsoft ASP.NET and AJAX: Architecting Web Applications, by Dino Esposito. Microsoft
Press, ISBN [3]SQL Server MVP Deep Dives, by Paul Nielson and 52 other MVPs.

[3]ASP.NET MVC Framework Unleashed, by Stephen Walther.

Nov 10, 2009

Web Reference:

https://www.itprotoday.com/web-application-management/top-books-aspnet-developers

https://www.sanfoundry.com/best-reference-books-asp-net/

CHAPTER 8
APPENDICES

8.1 – SOURCE CODE

8.2 _O/P SCREENS