company profile1
TRANSCRIPT
Xelos Technology
Introduction
1 Blue Shop System
Xelos Technology
1.1 Company profile
Xelos Technologies is a leading provider of online solutions specializing in
corporate web development, graphic and logo design, digital marketing and
search engine optimization. Xelos Technologies was established in the Pune
in 2008. Our specialties are the creation of commercial corporate websites,
content management systems and complex database & software development
for businesses of all sizes.Xelos Technologies is geared up by Enterprising
Entrepreneurs with a
goal to make a difference in Information Technology Industry, Solving &
Providing the most complex Business System Requirements. We aim to
enhance the Lives and Businesses of Companies in all Sectors by providing
End-to-End Enterprise Level Solutions. We are involved in providing In-House
and On-Client-Site ERP for Technological Solutions, Planning and
Implementation, ERP Technical Support, Customized ERP Packages,
Development and Customization, Knowledge Process Outsourcing {KPO},
Business Process Outsourcing {BPO},Microsoft Share Point projects
Development etc
2 Blue Shop System
Xelos Technology
Team:
Xelos Technologies have proud on its team, At Xelos Technologies we believe
that people are the key for providing high level innovative software solutions
and more importantly, an ongoing relationship with our clients Xelos has a
clear policy of employing only the best in their field. At Xelos we have highly
experienced IT professionals in core IT Industry, to mould the technology as
per client requriments.Most of them hold MCA/M-Tech/B.E degrees in
technology and Science some are PhD holder in computer Science in
computers Science.
Vision:
To develop a strong client base with an equally effective support Structure
which acts as a catalyst for effective development of Futuristically complete
and crediable IT solution
We strive to achieve this by focusing individually on each project tand build a
healthy relationship with our clients:-
To be flexible to our client’s changing needs , requirements and
deadlines
To deliver superior services and solutions to our clients on time at
Optimum cost
3 Blue Shop System
Xelos Technology
Mission:
We are highly motivated and adhesives towards towards being
globalize software services provider customized Application and high End
software Development Xelos has kept its eye firmly on the future and
advanced Technology, which is resulted in Firm , dynamic and technically
competent organization It dream Team consists of experienced dedicated
professionals, expert in the areas of software design and development,
testing, and maintenance. Team members have been highly trained for all its
products and services Offshore dedicated center Xelos long- term
commitment to establish and operate managed software ,Engineering facility
on the basic of Xelos that is tailored to client’s IT and business practices,
methodologies and culture.
Some of our leading software/products
Tours and ERP
Site Automation
Service Center Automation
Medical store management Syste
4 Blue Shop System
Xelos Technology
1.2 Existing System:
Time consuming:
The existing system was not so time consuming for customer as Well as
owner of the shopping because every time customer hasto come
shopping then choose the product also billing counter there consuming
.Due to exiting system ,there was limited time to shopping at Blue
Shopping system means only in the day time customer Can do
shopping.
Communication Gap:
In existing system, there was communication gap between Customer
and owner of shopping mall. If customer is having Problem regarding
his order or delivery of product so it was too difficult to communication
to owner.
Owner was having same problem, if owner want tell to customer about
payment details or new product scheme at that owner had to do
advertising of new product scheme at that owner had to call to customer
via phone other media.
5 Blue Shop System
Xelos Technology
More Paper Work:
There was more paper work in system, because it was manual System
so everything was stored on the paper. Owner had to store and
maintains the all paper from the starting of shopping mall otherwise the
proper report was not getting. To do these paper work owner had to
appoint one or more employees so that’s why extra expanses was there
Lack of Products Stock Maintenance:
In existing system , there was lack of product maintenance of stock,
missed stock, expired stock , defective stock, due to lack of product
stock the accounts of the department was getting problemat the end of
year.The actual stock was different from available stock, expire stock
that’s why customer was getting these type of products.
No Global Shopping:
There was no global shopping means customer had to come only at
Blue shop and he was not able to give order from his home in existing
system customer had to do shopping when blue shop is open on
holiday Sunday and other day when shopping get holiday on these
day customer couldn’t do shopping so there wasno global shopping.
6 Blue Shop System
Xelos Technology
Less Advertising:
In today’s world Advertising is the most important because if Owner
don’t do the advertising of any product and scheme then Customer will
not get product and scheme so in existing system there was less
advertising
7 Blue Shop System
Xelos Technology
1.3 Scope of System:
This system will helps in maintaining and monitoring the whole Blue
Shopping system that involves
Maintaining master records of product, Empolyee,scheme
Sales Forecasting
Provides facility placing online shopping to customer.
There are different modes of payment
Keeping track of the group of quantity of products to be sold to
customer.
Online report generation
Gathering and maintaining of all the data record centrally in system
manner.
Manage a customer’s “Shopping Cart”
Confirm Orders
8 Blue Shop System
Xelos Technology
Have an unambiguous interface to assist in browsing the categories
and products
1.4 Operating Environment Software and Hardware:
Software Requirement
Web Server : Tomcat5.0
Server Side Scripting : Servlet
Database : Oracle 10g
Client Side scripting : Jsp, Javascript,
HTML
Operating System : Windows XP
Web Browser : Internet Explorer,
Mozilla Firefox
Software : Eclipse
9 Blue Shop System
Xelos Technology
Hardware Requirement:
Processor : P4 and Above.
RAM : 1 GB RAM(Min.)
Hard Disk : 2GB
1.5 DETAILED DISCRIPTION OF TECHNOLOGY
Java is a programming language originally developed by James Gosling at
Sun Microsystems (which is now a subsidiary of Oracle Corporation) and
released in 1995 as a core component of Sun Microsystems' Java platform.
The language derives much of its syntax from C and C++ but has a simpler
object model and fewer low-level facilities. Java applications are typically
compiled to bytecode (class file) that can run on any Java Virtual Machine
(JVM) regardless of computer architecture. Java is a general-purpose,
concurrent, class-based, object-oriented language that is specifically designed
to have as few implementation dependencies as possible. It is intended to let
application developers "write once, run anywhere". Java is currently one of the
most popular programming languages in use, and is widely used from
application software to web applications.[9][10]
The original and reference implementation Java compilers, virtual machines,
and class libraries were developed by Sun from 1995. As of May 2007, in
compliance with the specifications of the Java Community Process, Sun
relicensed most of its Java technologies under the GNU General Public
License. Others have also developed alternative implementations of these
10 Blue Shop System
Xelos Technology
Sun technologies, such as the GNU Compiler for Java, GNU Classpath, and
Dalvik.
Feature of Java:
1.Platform Independent:
The concept of Write-once-run-anywhere (known as the Platform
independent) is one of the important key feature of java language that
makes java as the most powerful language. Not even a single language is
idle to this feature but java is more closer to this feature. The programs
written on one platform can run on any platform provided the platform must
have the JVM.
2.Simple
There are various features that makes the java as a simple language.
Programs are easy to write and debug because java does not use the
pointers explicitly. It is much harder to write the java programs that can
crash the system but we can not say about the other programming
languages. Java provides the bug free system due to the strong memory
11 Blue Shop System
Xelos Technology
management. It also has the automatic memory allocation and deallocation
system.
Object Oriented
To be an Object Oriented language, any language must follow at least
the four characteristics.
Inheritance : It is the process of creating the new classes and using
the behavior of the existing classes by extending them just to reuse
the existing code and adding the additional features as needed.
Encapsulation: It is the mechanism of combining the information and
providing the abstraction.
Polymorphism: As the name suggest one name multipleform,
Polymorphism is the way of providing the different functionality by the
functions having the same name based on the signatures of the
methods.
Dynamic binding : Sometimes we don't have the knowledge of
objects about their specific types while writing our code. It is the way of
providing the maximum functionality to a program about the specific
type at runtime. As the languages like Objective C, C++ fulfills the
above four characteristics yet they are not fully object oriented
12 Blue Shop System
Xelos Technology
languages because they are structured as well as object oriented
languages But in case of java, it is a fully Object Oriented la nguage
because object is at the outer most level of data structure in java. No
stand alone methods, constants, and variables are there in java
Everything in java is object even the primitive data types can also be
converted into object by using the wrapper class.
Robust
Java has the strong memory allocation and automatic garbage
collection mechanism. It provides the powerful exception handling
and type checking mechanism as compare to other programming
languages. Compiler checks the program whether there any error and
interpreter checks any run time error and makes the system secure
from crash. All of the above features makes the java language robust.
Distributed
The widely used protocols like HTTP and FTP are developed in java.
Internet programmers can call functions on these protocols and can get
access the files from any remote machine on the internet rather than writing
codes on their local system.
Portable
The feature Write-once-run-anywhere makes the java language portable
provided that the system must have interpreter for the JVM. Java also have
the standard data size irrespective of operating system or the processor.
These features makes the java as a portable language.
13 Blue Shop System
Xelos Technology
Dynamic
While executing the java program the user can get the required files
dynamically from a local drive or from a computer thousands of miles away
from the user just by connecting with the Internet.
Secure
Java does not use memory pointers explicitly. All the programs in java are
run under an area known as the sand box. Security manager determines the
accessibility options of a class like reading and writing a file to the local disk.
Java uses the public key encryption system to allow the java applications to
transmit over the internet in the secure encrypted form. The bytecode
Verifier checks the classes after loading.
Performance
Java uses native code usage, and lightweight process called threads. In the
beginning interpretation of bytecode resulted the performance slow but the
advance version of JVM uses the adaptive and just in time compilation
technique that improves the performance.
Multithreaded
As we all know several features of Java like Secure, Robust, Portable,
dynamic etc; you will be more delighted to know another feature of Java
which is Multithreaded.
Java is also a Multithreaded programming language. Multithreading means
a single program having different threads executing independently at the
same time. Multiple threads execute instructions according to the program
code in a process or a program. Multithreading works the similar way as
multiple processes run on one computer.
14 Blue Shop System
Xelos Technology
Multithreading programming is a very interesting concept in Java. In
multithreaded programs not even a single thread disturbs the execution of
other thread. Threads are obtained from the pool of available ready to run
threads and they run on the system CPUs. This is how Multithreading works
in Java which you will soon come to know in details in later chapters.
Interpreted
We all know that Java is an interpreted language as well. With an
interpreted language such as Java, programs run directly from the source
code.
The interpreter program reads the source code and translates it on the fly
into computations. Thus, Java as an interpreted language depends on an
interpreter program.
The versatility of being platform independent makes Java to outshine from
other languages. The source code to be written and distributed is platform
independent.
Another advantage of Java as an interpreted language is its error debugging
quality. Due to this any error occurring in the program gets traced. This is
how it is different to work with Java.
Architecture Neutral
The term architectural neutral seems to be weird, but yes Java is an
architectural neutral language as well. The growing popularity of networks
makes developers think distributed. In the world of network it is essential
that the applications must be able to migrate easily to different computer
systems. Not only to computer systems but to a wide variety of hardware
architecture and Operating system architectures as well. The Java compiler
does this by generating byte code instructions, to be easily interpreted on
any machine and to be easily translated into native machine code on the fly.
15 Blue Shop System
Xelos Technology
The compiler generates an architecture-neutral object file format to enable a
Java application to execute anywhere on the network and then the compiled
code is executed on many processors, given the presence of the Java
runtime system. Hence Java was designed to support applications on
network. This feature of Java has thrived the programming language.
JSP:
JavaServer Pages (JSP) is a Java technology that helps software
developers serve dynamically generated web pages based on HTML, XML,
or other document types. Released in 1999 as Sun's answer to ASP and
PHP, JSP was designed to address the perception that the Java
programming environment didn't provide developers with enough support for
the Web.
Java Server Pages or JSP for short is Sun's solution for developing dynamic
web sites. JSP provide excellent server side scripting support for creating
database driven web applications. JSP enable the developers to directly
insert java code into jsp file, this makes the development process very
simple and its maintenance also becomes very easy. JSP pages are
efficient, it loads into the web servers memory on receiving the request very
first time and the subsequent calls are served within a very short period of
time.
In today's environment most web sites servers dynamic pages based on
user request. Database is very convenient way to store the data of users
and other things. JDBC provide excellent database connectivity in
heterogeneous database environment. Using JSP and JDBC its very easy
to develop database driven web application.
16 Blue Shop System
Xelos Technology
Java is known for its characteristic of "write once, run anywhere." JSP
pages are platform independent. Your port your .jsp pages to any
platform.
Architecturally, JSP may be viewed as a high-level abstraction of Java
servlets. JSP pages are loaded in the server and operated from a structured
special installed Java server packet called a Java EE Web Application, often
packaged as a .war or .ear file archive.
JSP allows Java code and certain pre-defined actions to be interleaved with
static web markup content, with the resulting page being compiled and
executed on the server to deliver an HTML or XML document. The compiled
pages and any dependent Java libraries use Java bytecode rather than a
native software format, and must therefore be executed within a Java virtual
machine (JVM) that integrates with the host operating system to provide an
abstract platform-neutral environment.
JSP syntax is a fluid mix of two basic content forms: scriptlet elements and
markup. Markup is typically standard HTML or XML, while scriptlet elements
are delimited blocks of Java code which may be intermixed with the markup.
When the page is requested the Java code is executed and its output is
added, in situ, with the surrounding markup to create the final page. JSP
pages must be compiled to Java bytecode classes before they can be
executed, but such compilation is needed only when a change to the source
JSP file has occurred.
Java code is not required to be complete (self contained) within its scriptlet
element block, but can straddle markup content providing the page as a whole
is syntactically correct (for example, any Java if/for/while blocks opened in one
scriptlet element must be correctly closed in a later element for the page to
successfully compile). This system of split inline coding sections is called step
17 Blue Shop System
Xelos Technology
over scripting because it can wrap around the static markup by stepping over
it. Markup which falls inside a split block of code is subject to that code, so
markup inside an if block will only appear in the output when the if condition
evaluates to true; likewise markup inside a loop construct may appear multiple
times in the output depending upon how many times the loop body runs.
The JSP syntax adds additional XML-like tags, called JSP actions, to invoke
built-in functionality. Additionally, the technology allows for the creation of JSP
tag libraries that act as extensions to the standard HTML or XML tags. JVM
operated tag libraries provide a platform independent way of extending the
capabilities of a web server. Note that not all commercial Java servers are
Java EE specification compliant.[which?]
Starting with version 1.2 of the JSP specification, JavaServer Pages have
been developed under the Java Community Process. JSR 53 defines both the
JSP 1.2 and Servlet 2.3 specifications and JSR 152 defines the JSP 2.0
specification. As of May 2006 the JSP 2.1 specification has been released
under JSR 245 as part of Java EE 5. As of Dec 10, 2009 the JSP 2.2
specification has been released as a maintenance release of JSR 245.
JSP architecture
JSPs are built on top of SUN Microsystems' servlet technology. JSPs are
essential an HTML page with special JSP tags embedded. These JSP tags
can contain Java code. The JSP file extension is .jsp rather than .htm or .html.
The JSP engine parses the .jsp and creates a Java servlet source file. It then
compiles the source file into a class file,this is done the first time and this why
18 Blue Shop System
Xelos Technology
the JSP is probably slower the first time it is accessed. Any time after this the
special compiled servlet is executed and is therefore returns faster.
Steps required for a JSP request:
1. The user goes to a web site made using JSP. The user goes to a JSP
page (ending with .jsp). The web browser makes the request via the
Internet.
2. The JSP request gets sent to the Web server.
19 Blue Shop System
Xelos Technology
3. The Web server recognises that the file required is special
(.jsp),therefore passes the JSP file to the JSP Servlet Engine.
4. If the JSP file has been called the first time,the JSP file is
parsed,otherwise go to step 7.
5. The next step is to generate a special Servlet from the JSP file. All the
HTML required is converted to println statements.
6. The Servlet source code is compiled into a class.
7. The Servlet is instantiated,calling the init and service methods.
8. HTML from the Servlet output is sent via the Internet.
9. HTML results are displayed on the user's web browser.
The web server needs a JSP engine ie. container to process JSP pages. The
JSP container is responsible for intercepting requests for JSP pages. This
tutorial makes use of Apache which has built-in JSP container to support JSP
pages development.
20 Blue Shop System
Xelos Technology
A JSP container works with the Web server to provide the runtime
environment and other services a JSP needs. It knows how to understand the
special elements that are part of JSPs.
Following diagram shows the position of JSP container and JSP files in a Web
Application.
JSP Processing:
The following steps explain how the web server creates the web page using
JSP:
As with a normal page, your browser sends an HTTP request to the
web server.
The web server recognizes that the HTTP request is for a JSP page
and forwards it to a JSP engine. This is done by using the URL or JSP
page which ends with .jsp instead of .html.
The JSP engine loads the JSP page from disk and converts it into a
servlet content. This conversion is very simple in which all template text
21 Blue Shop System
Xelos Technology
is converted to println( ) statements and all JSP elements are converted
to Java code that implements the corresponding dynamic behavior of
the page.
The JSP engine compiles the servlet into an executable class and
forwards the original request to a servlet engine.
A part of the web server called the servlet engine loads the Servlet
class and executes it. During execution, the servlet produces an output
in HTML format, which the servlet engine passes to the web server
inside an HTTP response.
The web server forwards the HTTP response to your browser in terms
of static HTML content.
Finally web browser handles the dynamically generated HTML page
inside the HTTP response exactly as if it were a static page
Servlet:
A Servlet is a Java class in Java EE that conforms to the Java Servlet API, a
protocol by which a Java class may respond to HTTP requests. They are not
tied to a specific client-server protocol, but are most often used with this
protocol. The word "Servlet" is often used in the meaning of "HTTP Servlet". [1]
Thus, a software developer may use a servlet to add dynamic content to a
Web server using the Java platform. The generated content is commonly
HTML, but may be other data such as XML. Servlets are the Java counterpart
to non-Java dynamic Web content technologies such as CGI and ASP.NET.
Servlets can maintain state in session variables across many server
transactions by using HTTP cookies, or URL rewriting.
The servlet API, contained in the Java package hierarchy javax.servlet,
defines the expected interactions of a Web container and a servlet.[1] A Web
container is essentially the component of a Web server that interacts with the
servlets. The Web container is responsible for managing the lifecycle of
22 Blue Shop System
Xelos Technology
servlets, mapping a URL to a particular servlet and ensuring that the URL
requester has the correct access rights.
A Servlet is an object that receives a request and generates a response based
on that request. The basic servlet package defines Java objects to represent
servlet requests and responses, as well as objects to reflect the servlet's
configuration parameters and execution environment. The package
javax.servlet.http defines HTTP-specific subclasses of the generic servlet
elements, including session management objects that track multiple requests
and responses between the Web server and a client. Servlets may be
packaged in a WAR file as a Web application.
Servlets can be generated automatically from JavaServer Pages (JSP) by the
JavaServer Pages compiler. The difference between Servlets and JSP is that
Servlets typically embed HTML inside Java code, while JSPs embed Java
code in HTML. While the direct usage of Servlets to generate HTML (as
shown in the example below) is relatively rare nowadays, the higher level
MVC web framework in Java EE (JSF) still explicitly uses the Servlet
technology for the low level request/response handling via the FacesServlet. A
somewhat older usage is to use servlets in conjunction with JSPs in a pattern
called "Model 2", which is a flavour of the model-view-controller pattern.
A Servlet, in its most general form, is an instance of a class which implements
the javax.servlet.Servlet interface. Most Servlets, however, extend one of the
standard implementations of that interface, namely
javax.servlet.GenericServlet and javax.servlet.http.HttpServlet. In this tutorial
we'll be discussing only HTTP Servlets which extend the
javax.servlet.http.HttpServlet class.
In order to initialize a Servlet, a server application loads the Servlet class (and
probably other classes which are referenced by the Servlet) and creates an
instance by calling the no-args constructor. Then it calls the Servlet's
23 Blue Shop System
Xelos Technology
init(ServletConfig config) method. The Servlet should performe one-time setup
procedures in this method and store the ServletConfig object so that it can be
retrieved later by calling the Servlet's getServletConfig() method. This is
handled by GenericServlet. Servlets which extend GenericServlet (or its
subclass HttpServlet) should call super.init(config) at the beginning of the init
method to make use of this feature. The ServletConfig object contains Servlet
parameters and a reference to the Servlet's ServletContext. The init method is
guaranteed to be called only once during the Servlet's lifecycle. It does not
need to be thread-safe because the service method will not be called until the
call to init returns.
When the Servlet is initialized, its service(ServletRequest req,
ServletResponse res) method is called for every request to the Servlet. The
method is called concurrently (i.e. multiple threads may call this method at the
same time) so it should be implemented in a thread-safe manner. Techniques
for ensuring that the service method is not called concurrently, for the cases
where this is not possible, are described in section 4.1.
When the Servlet needs to be unloaded (e.g. because a new version should
be loaded or the server is shutting down) the destroy() method is called. There
may still be threads that execute the service method when destroy is called,
so destroy has to be thread-safe. All resources which were allocated in init
should be released in destroy. This method is guaranteed to be called only
once during the Servlet's lifecycle.
24 Blue Shop System
Xelos Technology
Apache Tomcat:
Apache Tomcat (or Jakarta Tomcat or simply Tomcat) is an open source
servlet container developed by the Apache Software Foundation (ASF).
Tomcat implements the Java Servlet and the JavaServer Pages (JSP)
25 Blue Shop System
A typical Servlet lifecycle
Xelos Technology
specifications from Sun Microsystems, and provides a "pure Java" HTTP web
server environment for Java code to run.
Tomcat should not be confused with the Apache web server, which is a C
implementation of an HTTP web server; these two web servers are not
bundled together. Apache Tomcat includes tools for configuration and
management, but can also be configured by editing XML configuration files.
Catalina
Catalina is Tomcat's servlet container. Catalina implements Sun
Microsystems' specifications for servlet and JavaServer Pages (JSP). In
Tomcat, a Realm element represents a "database" of usernames, passwords,
and roles (similar to Unix groups) assigned to those users. Different
implementations of Realm allow Catalina to be integrated into environments
where such authentication information is already being created and
maintained, and then utilize that information to implement Container Managed
Security as described in the Servlet Specification.[2]
Coyote
Coyote is Tomcat's HTTP Connector component that supports the HTTP 1.1
protocol for the web server or application container. Coyote listens for
incoming connections on a specific TCP port on the server and forwards the
request to the Tomcat Engine to process the request and send back a
response to the requesting client.
Jasper
Jasper is Tomcat's JSP Engine. Tomcat 5.x uses Jasper 2, which is an
implementation of the Sun Microsystems's JavaServer Pages 2.0
specification. Jasper parses JSP files to compile them into Java code as
26 Blue Shop System
Xelos Technology
servlets (that can be handled by Catalina). At runtime, Jasper detects changes
to JSP files and recompiles them.
Jasper 2
From Jasper to Jasper 2, important features were added:
JSP Tag library pooling - Each tag markup in JSP file is handled by a
tag handler class. Tag handler class objects can be pooled and reused
in the whole JSP servlet.
Background JSP compilation - While recompiling modified JSP Java
code, the older version is still available for server requests. The older
JSP servlet is deleted once the new JSP servlet has finished being
recompiled.
Recompile JSP when included page changes - Pages can be inserted
and included into a JSP at runtime. The JSP will not only be recompiled
with JSP file changes but also with included page changes.
JDT Java compiler - Jasper 2 can use the Eclipse JDT (Java
Development Tools) Java compiler instead of Ant and javac.
Features
Tomcat 5.x
Implements the Servlet 2.4 and JSP 2.0 specifications
Reduced garbage collection, improved performance and scalability
Native Windows and Unix wrappers for platform integration
Faster JSP parsing
Deployment
Experienced users can build and install Tomcat manually from source code
after installing such dependencies as the Java Development Kit and the
Apache Ant build tool.
27 Blue Shop System
Xelos Technology
Depending on the usage requirements, Tomcat may either be deployed as a
standalone pure-Java web server or as a component in a more complex
configuration in which it serves as a back-end which handles requests passed
to it from a general purpose web server such as Apache, using a connector
such as mod_jk supplied by the Apache Tomcat team, or mod_proxy an
optional module for the Apache HTTP Server supplied by the Apache HTTP
Server team.
History
Tomcat started off as a servlet reference implementation by James Duncan
Davidson, a software architect at Sun Microsystems. He later helped make the
project open source and played a key role in its donation by Sun to the
Apache Software Foundation. The Apache Ant software build automation tool
was developed as a side-effect of the creation of Tomcat as an open source
project.
Davidson had initially hoped that the project would become open sourced and,
since many open source projects had O'Reilly books associated with them
featuring an animal on the cover, he wanted to name the project after an
animal. He came up with Tomcat since he reasoned the animal represented
something that could fend for itself. Although the tomcat was already in use for
another O'Reilly title, his wish to see an animal cover eventually came true
when O'Reilly published their Tomcat book with a snow leopard on the cover.
Eclipse (software):
28 Blue Shop System
Xelos Technology
Eclipse is a multi-language software development environment comprising an
integrated development environment (IDE) and an extensible plug-in system.
It is written mostly in Java and can be used to develop applications in Java
and, by means of various plug-ins, other programming languages including
Ada, C, C++, COBOL, Perl, PHP, Python, Ruby (including Ruby on Rails
framework), Scala, Clojure, and Scheme. The IDE is often called Eclipse ADT
for Ada, Eclipse CDT for C/C++, Eclipse JDT for Java, and Eclipse PDT for
PHP.
The initial codebase originated from VisualAge.[1] In its default form it is meant
for Java developers, consisting of the Java Development Tools (JDT). Users
can extend its abilities by installing plug-ins written for the Eclipse software
framework, such as development toolkits for other programming languages,
and can write and contribute their own plug-in modules.
Released under the terms of the Eclipse Public License, Eclipse is free and
open source software. It was one of the first IDEs to run under GNU Classpath
and it runs without issues under IcedTea.
Oracle Database:
The Oracle Database (commonly referred to as Oracle RDBMS or simply as
Oracle) is an object-relational database management system (ORDBMS)[2]
produced and marketed by Oracle Corporation.
Larry Ellison and his friends and former co-workers Bob Miner and Ed Oates
started the consultancy Software Development Laboratories (SDL) in 1977.
SDL developed the original version of the Oracle software. The name Oracle
comes from the code-name of a CIA-funded project Ellison had worked on
while previously employed by Ampex.[3]
29 Blue Shop System
Xelos Technology
Physical and logical structures
An Oracle database system—identified by an alphanumeric system identifier
or SID[4]—comprises at least one instance of the application, along with data
storage. An instance—identified persistently by an instantiation number (or
activation id: SYS.V_$DATABASE.ACTIVATION#)—comprises a set of
operating-system processes and memory-structures that interact with the
storage. Typical processes include PMON (the process monitor) and SMON
(the system monitor).
Users of the Oracle databases refer to the server-side memory-structure as
the SGA (System Global Area). The SGA typically holds cache information
such as data-buffers, SQL commands, and user information. In addition to
storage, the database consists of online redo logs (or logs), which hold
transactional history. Processes can in turn archive the online redo logs into
archive logs (offline redo logs), which provide the basis (if necessary) for data
recovery and for some forms of data replication.
If the Oracle database administrator has implemented Oracle RAC (Real
Application Clusters), then multiple instances, usually on different servers,
attach to a central storage array. This scenario offers advantages such as
better performance, scalability and redundancy. However, support becomes
more complex, and many sites do not use RAC. In version 10g, grid
computing introduced shared resources where an instance can use (for
example) CPU resources from another node (computer) in the grid.
The Oracle DBMS can store and execute stored procedures and functions
within itself. PL/SQL (Oracle Corporation's proprietary procedural extension to
SQL), or the object-oriented language Java can invoke such code objects
and/or provide the programming structures for writing them.
Storage:
30 Blue Shop System
Xelos Technology
The Oracle RDBMS stores data logically in the form of tablespaces and
physically in the form of data files ("datafiles").[5] Tablespaces can contain
various types of memory segments, such as Data Segments, Index
Segments, etc. Segments in turn comprise one or more extents. Extents
comprise groups of contiguous data blocks. Data blocks form the basic units
of data storage.
There is also a partioning feature available on newer versions of the database,
which allows tables to be partitioned based on different set of keys.
Oracle database management tracks its computer data storage with the help
of information stored in the SYSTEM tablespace. The SYSTEM tablespace
contains the data dictionary—and often (by default) indexes and clusters. A
data dictionary consists of a special collection of tables that contains
information about all user-objects in the database. Since version 8i, the Oracle
RDBMS also supports "locally managed" tablespaces which can store space
management information in bitmaps in their own headers rather than in the
SYSTEM tablespace (as happens with the default "dictionary-managed"
tablespaces).
Disk files:
This section requires expansion.
At the physical level, data files comprise one or more data blocks, where the
block size can vary between data files.
Data files can occupy pre-allocated space in the file system of a computer
server, utilize raw disk directly, or exist within ASM logical volumes.[6]
[edit] Control files
The following parameters govern the size of the control files:
31 Blue Shop System
Xelos Technology
* maxlogfile
* maxlogmembers
* maxloghistory
* maxinstances
* control_file_record_keep_time
Database Schema
Oracle database conventions refer to defined groups of object ownership
(generally associated with a "username") as schemas.
Most Oracle database installations traditionally came with a default schema
called SCOTT. After the installation process has set up the sample tables, the
user can log into the database with the username scott and the password
tiger. The name of the SCOTT schema originated with Bruce Scott, one of the
first employees at Oracle (then Software Development Laboratories), who had
a cat named Tiger.[7]
Oracle Corporation has de-emphasized the use of the SCOTT schema, as it
uses few of the features of the more recent releases of Oracle. Most recent
examples supplied by Oracle Corporation reference the default HR or OE
schemas.
Other default schemas[8][9] include:
SYS (essential core database structures and utilities)
SYSTEM (additional core database structures and utilities, and
privileged account)
OUTLN (utilized to store metadata for stored outlines for stable query-
optimizer execution plans.[10]
32 Blue Shop System
Xelos Technology
2. PROPOSED SYSTEM
2.1 Proposed System:
Proposed online Blue Shopping maintains and deliversproduct and also
online order . This system enable to administrator to
33 Blue Shop System
Xelos Technology
generate proper report generation, it also bridges the gap between
administrator ,employeeand customer as well as reduces time consuming
problems and maintains account for each department
Convenience
Online stores are usually available 24 hours a day, and many consumers
have Internet access both at work and at home.
Information and reviews
Online stores must describe products for
sale with text, photos, and multimedia files, whereas in a physical retail store,
the actual product and the manufacturer's packaging will be available for
direct inspection (which might involve a test drive, fitting, or other
experimentation
Price and selection
One advantage of shopping online is being able to quickly seek out
deals for items or services with many different vendors
Online shopping every user will have a unique id that can distinguish
him/her from other user will have a unique id
that distingwish him /her from oter user. The user of this
system can mainly be of three types
Administrator
Employee
Customer
Aministrator:
34 Blue Shop System
Xelos Technology
The Administrator here is prime impotantance as he/she is responsible
maintaining department and their product maintenance and schemes
Administrator also responsible for granting. He is able to get aill report
regarding system means he has authority
to as the entire payment process ,sales,delivery etc Information as per
the date and department.
Administrator has to give answer to employee also send any new
scheme details to customer so this process bridges the communication
gap between customer or employee. Administrator is one of the
employees of the shopping system so that’s why administrator can do
employee work.
Employee:
Employee is one of the system but he has less authority than
administrator and without administrator and permission employee
can’t
Register his profile.
Employee is responsible for to handle customer order, billing and
delivery. Even employee can communicate with other user of
system.
Customer:
35 Blue Shop System
Xelos Technology
The main user of system is customer because system has been
developed for customer satisfaction. Customer can search differen t
product and shchemes
As per department can search different product and get Stock
availability without registration.
Customer Registration:
In This form customer will register himself to system by giving
personal details,residential details and contact details so that
delivery will be properly deliveryed and update his profile if any
contact details is changed
A customer visits the online Blue shopping. A customer may buy
item or just visit the page
and logout. The customer can select a segment, then a category,
and brand to get the different products in the desired brand. The
customer can select the product for purchasing. The process can
be repeated for more items. Once the customer finishes selecting
the product/s the cart can be viewed , If the customer wants to
edit the final cart it can be done here.
Shopping :
Shopping is very important feature of the system because it’s
online Blue shopping. This is very important part of the system in
that only registered customer can do shopping on the system,
while shopping customer must get all product details after
completing shopping he will get modes of payment. System must
provide online
36 Blue Shop System
Xelos Technology
2.2 Objective Of System:
This system will helps in maintaining and monitoring the whole
Blue Shopping system that involves
Maintaining master records of product, Empolyee,scheme
Sales Forcasting
Provides facility placing online shopping to customer.
There are different modes of payment
Keeping track of the group of quantity of products to be sold to
customer.
Online report generation
Gathering and maintaining of all the data record centrally in
system manner.
Manage a customer’s “Shopping Cart”
Confirm Orders
37 Blue Shop System
Xelos Technology
Have an unambiguous interface to assist in browsing the
categories and products
2.3 User Requriment:
To remove time consuming system:
The traditional system was so time consuming as well as owner of the
Bule shopping shopping system because every time customer has to come
Bule Shopping then choose the product also billing counter there where time
consuming.
To fill the communication gap:
In traditional system, there was communication gap between Customer
and owner of shopping mall. If customer is having Problem regarding
his order or delivery of product so it was to difficult to communication to
owner.
Owner was having same problem ,if owner want tell to customer about
payment details or new product scheme at that owner hadto do
advertising of new product scheme at that owner had to call to customer
via phone other media.
Computerization:
38 Blue Shop System
Xelos Technology
There was more paper work in system ,because it was manual System
so everything was stored on the paper . Owner had to store and
maintains the all paper from the starting of shopping mall otherwise the
proper report was not getting.
To do these paper work owner had to appoint one or more employees
so that’s why extra expanses was there
Global Shopping:
There was global shopping means customer had to come only at Blue
shop and he was not able to give order from his home in existing
system customer had to do shopping when blue shop is open on
holiday Sunday and other day when shopping get holiday on these
day customer could do shopping so there was global shopping.
39 Blue Shop System
Xelos Technology
2.4 Feasibility Study
While developing any computerized system it is necessary to examine
whether the developed computerized system is feasible in the point of view
operational, technical and financial.
In the most commercial software development there are also some
activities performed before the requirement analysis take place. These can be
combined into a feasibility analysis and a business proposal is put forth. With
a very general plan for the project and some cost estimates. For feasibility
analysis, some understanding of the major requirements of the system is
essential. Once the business proposal is accepted or the contract is awarded,
the development begins with the requirement analysis phase:
The cases are categorized as follows:
A. Operational Feasibility
B. Technical Feasibility
C. Economical Feasibility
40 Blue Shop System
Xelos Technology
2.4.1.A. Technical Feasibility
Technical feasibility is the study of cost benefit analysis of the system
and study of the hardware and software requirements i.e. technical
requirements of the system in order to inform management and user for
particular system designing this much technical sources are required, in order
to know user and management view, regarding the technical resources. By
studying the technical study the actual cost of the system designing is known.
To know the total system cost, it is essential for any management to know the
actual expense of the system and what are the output of the system.
For technical feasibility, organization can provide what is minimum required.
41 Blue Shop System
Xelos Technology
2.4.1.B. Economic feasibility
Economic feasibility study is the actual cost and benefit of the system.
Actual cost of the system is calculated in the economic study so as to inform
the user and management that this mush cost will be required to develop the
system. Because system cost id the first cost before starting system
designing.
So actual cost of the system is important before starting the design of
the system. After how many years proposed system will prove beneficial for
the organization is studied in economical study. The design system will
provide tangible as well as intangible benefits.
The organization is already equipped with all the latest software and is
also has self-sufficient hardware setup. System is designed so as to fit in the
current software present in the organization. And if all purchasing new
software is required for the long run and hence no overhead. So system is
economically feasible.
2.4.1.C. Operational Feasibility
42 Blue Shop System
Xelos Technology
Training program will be required to the user. A group of user will be
trained during the training period. It focuses on the willingness and the ability
of the user. A proposed system requires special efforts to educate the staff on
new way on conducting ways.
The system incorporates user friendly interface, default processing
and required validations. These all are done keeping in view the individual
with minimum computer knowledge
43 Blue Shop System
Xelos Technology
ANALYSIS & DESIG
44 Blue Shop System
Xelos Technology
Data Flow Diagram (DFD)
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).
45 Blue Shop System
Xelos Technology
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).
Data Flow Diagrams show the flow of data from external entities into the
system,
and from one process to another within the system. There are four symbols for
drawing a
DFD:
1. Rectangles representing external entities, which are sources or destinations
of
data.
2. Ellipses representing processes, which take data as input, validate and
process it
and output it.
3. Arrows representing the data flows, which can either, be electronic data or
physical items.
4. Open-ended rectangles or a Disk symbol representing data stores,
including
electronic stores such as databases or XML files and physical stores such as
filing
cabinets or stacks of paper.
46 Blue Shop System
Xelos Technology
Figures 3 - 14 are the Data Flow Diagrams for the current system. Each
process within
the system is first shown as a Context Level DFD and later as a Detailed DFD.
The
Context Level DFD provides a conceptual view of the process and its
surrounding input,
output and data stores. The Detailed DFD provides a more detailed and
comprehensive
view of the interaction among the sub-processes within the system.
47 Blue Shop System
Xelos Technology
Context Level DFD:
48 Blue Shop System
Xelos Technology
1.0 Master Creation Process:
49 Blue Shop System
Xelos Technology
2.0 Registration Process:
50 Blue Shop System
Xelos Technology
51 Blue Shop System
Xelos Technology
3.0 Login Process:
3.0Login
Process
Administrator
Employee
Customer
Administrator Table
Employee Table
Customer Table
Enter Admin Login details
Admin Login details
Enter Emp Login details Emp Login details
Enter Customer Login DetailsCustomer Login
details
52 Blue Shop System
Xelos Technology
4.0 Department Process:
53 Blue Shop System
Xelos Technology
5.0 Product Process:
5.0Product Process
AdninistratorReq. For Add New Product
ProductAdd New Product
Req For Delete Product
Delete Product
Req. For Update Product
Delete Scheme
Add New Product
Update Product
Add New Product
Delete Product
Update Product
Update Product
54 Blue Shop System
Xelos Technology
6.0 Scheme process:
6.0Scheme Process
AdninistratorReq. For Add New Scheme
SchemeAdd New Scheme
Req For Delete Scheme
Delete Scheme
Req. For Update Scheme
Update Scheme
Delete Scheme
Add New Scheme
Update Scheme
Update Scheme
Delete Scheme
Add New Scheme
55 Blue Shop System
Xelos Technology
7.0 Stock Process:
7.0Stock Process
AdninistratorReq. For Check Defective Stock
StockCheck Defective Stock
Req For Check Avaibility Stock
Check Avaibility Stock
Check Avaibility StockAvaibility Stock
Check Defective Stock
Defective Stock
Req For Check Missed Stock
Check Missed Stock
Missed Stock
Missed Stock
Check Expried Stock
Expried StockReq. for Check Expried Stock
Expried Stock
56 Blue Shop System
Xelos Technology
8.0 Customer Process:
8.oProcess ByCustomer
Customer
Order Table
Delivery Table
CustomerTable
Req for order
Req forBill
order details
Product Add to cart
Bill details
Bill details
Bill details
Req. for Delivery of Product
Delivery of Product details
Delivery of Product details
Product Delivery
Req. Update Profile
Bill Table
order details
Customer order
Update Profile details
Update Profile Update Profile
Product Table
Req for Add to cart product
Product Add to cart
Add to cart product
Add to cart product
FeedbackTable Give Feedback Feedback Details
57 Blue Shop System
Xelos Technology
9.0 Employee Process:
9.oProcess ByEmployee
Employee
Order Table
Delivery Table
Employee Table
Req for view Customer order
Generate Bill
Customer order details
Product Add to cart
Bill details
Bill details
Bill details
Req. for Delivery of Product
Delivery of Product details
Delivery of Product details
Product Delivery
Req. Update Profile
Bill Table
Customer order details
Customer order
Update Profile details
Update Profile Update Profile
58 Blue Shop System
Xelos Technology
10.0 Report Generation:
59 Blue Shop System
Xelos Technology
3.2 Functional Decomposition Diagram:
A decomposition diagram shows a top-down functional decomposition of
asystem and exposes the system's structure. The objective of the Functional
Decomposition is to break down a system step by step, beginning with the
main function of a system and continuing with the interim levels down to the
level of elementary Functions. The diagram is the starting point for more
detailed process diagrams, such as
data flow diagrams (DFD). Figure shows the Functional Decomposition
Diagram forthis project.
60 Blue Shop System
Xelos Technology
ER Diagram:
an entity-relationship model (ERM) is an abstract and conceptual
representation of data. Entity-relationship modeling is a database modeling
method, used to produce a type of conceptual schema or semantic data
model of a system, often a relational database, and its requirements in a top-
down fashion. Diagrams created by this process are called entity-
relationship diagrams, ER diagrams, or ERDs.
The first step in designing a database is to develop an Entity-Relation
Diagram (ERD). The ERD serves as a blue print from which a relational
database maybe deduced. Figure 1 shows the ERD for the project and later
we will show the transformation from ERD to the Re lational model.
Figure 1 Entity Relationship Diagram (
entity A matches exactly one record in entity B and every record in B matches
exactly one record in A. One to many means that every record in A matches
zero or more records in B and every record in B matches exactly one record in
A. If there is a one to many relationship between two entities, then these
entities are represented as Associative Entities. In the Relational Database
model, each of the entities will be transformed into a table. The tables are
shown below along with the attributespresent the
relationship between
61 Blue Shop System
Xelos Technology
Employee Customer Feedback
Department
Bill
Stock
Product
Scheme
SchemeDetails
Delivery
Customer OrderDetails
Epried Stock
Defective Stock
MissedStock
GeneratesSend to
Has
Belong to Belong to
Get
Belong to
Show status of
GivesAccepts
Is A
Customer Order
Places
Belong to
Belong to
62 Blue Shop System
Xelos Technology
Table Design
63 Blue Shop System
Xelos Technology
3.5 Data Dictionary:
Field Name Data
Type
size Constraint Description
Admin_id Varchar2 20 Primary
key
Unique id of
administration
Admin_Name Varchar2 20 Not Null Name of administration
Admin_password Varchar2 20 Not Null Administration password
Dept_id Varchar2 10 Pk Unique id of department
Dept_name Varchar2 20 Not Null Name of department
Dept_date Date Not Null Date of entry
Emp_id Varchar2 10 Pk Unique id of Empolyee
Emp_fname Varchar2 20 Not Null Frist name of employee
Emp_lname Varchar2 20 Not Null Last name of employee
Emp_gender Varchar2 10 Not Null Gender of employee
Emp_sal Float 8 Not Null Salary of employee
Emp_add1 Varchar2 50 Not Null Address 1of employee
Emp_add2 Varchar2 50 Not Null Address2 of employee
Emp_city Varchar2 20 Not Null City of employee
Emp_state Varchar2 20 Not Null State of employee
Emp_pin Number 15 Not Null Pin of employee
Emp_phone Number 10 Not Null Phone of employee
Emp_mobile Number 10 Not Null Mobile of employee
Emp_email Varchar2 15 Not Null Email of employee
Emp_doj Date Not Null Date of joining of
employee
Emp_dob Date Not Null Date of birth of
employee
64 Blue Shop System
Xelos Technology
Emp_password Varchar2 20 Not Null Password of employee
Pr_id Varchar2 10 PK Unique id of Product
Pr_name Varchar2 20 Not Null Name of Product
Pr_brand Varchar2 10 Not Null Brand of Product
Pr_doe Date Not Null Date of entry of Product
Pr_mno Varchar2 30 Not Null Model no of Product
Pr_feature Varchar2 50 Not Null Feature of Product
Pr_color Varchar2 10 Not Null Color of Product
Pr_image Varchar2 30 Not Null Image of Product
Pr_size Varchar2 10 Not Null Size of of Product
Pr_avail Number 10 Not Null Available of Product
Cust_id Varchar2 10 Pk Unique id of customer
Cust_fname Varchar2 20 Not Null Frist name of customer
Cust_lname Varchar2 20 Not Null Last name of customer
Cust_gender Varchar2 10 Not Null Gender of customer
Cust_dor Date Not Null Date of registration
Cust_add1 Varchar2 50 Not Null Address 1of customer
Cust_add2 Varchar2 50 Not Null Address2 of customer
Cust_city Varchar2 20 Not Null City of customer
Cust_state Varchar2 20 Not Null State of customer
Cust_pin Number 15 Not Null Pin of customer
Cust_phone Number 10 Not Null Phone of customer
Cust_mobile Number 10 Not Null Moblile of customer
Cust_email Varchar2 15 Not Null Email of customer
Cust_occuption Varchar2 20 Not Null Occupation of customer
Cust_dob Date Not Null Date of Birth of
customer
Cust_password Varchar2 20 Not Null Password of customer
Missed_Stock_id Varchar2 10 pk Missed_stock_id
Missed_qty Number 10 Not Null Missed quantity
Missed_date Date Not Null Product missed date
65 Blue Shop System
Xelos Technology
Missed_Description Varchar2 50 Not Null Product missed
description
Expired_Stock_id Varchar2 10 Pk Expried stock id
Expried_qty Number 10 Not Null Expried quantity
Expired date Date Not Null Expired date of product
Defect_Stock_id Varchar2 10 Pk Defective stock id
Defect_qty Number 10 Not Null Defective quantity
Return_to Varchar2 30 Not Null Name of who will
receivied
Scheme_id Varchar2 10 Pk Scheme id
Discount Float 8 Not Null Discount of scheme
Buy Number 9 Not Null Quantity to buy
Get Number 9 Not Null Quantity which is free
Order_id Varchar2 10 Pk Customer order id
Cust_id Varchar2 10 Fk Customer id
Order_date Date Not Null Date of customer order
Total_amt Float 9 Not Null Availbale stock till date
Feedback_id Varchar2 10 Pk Feedback id
Feedback Varchar2 100 Not Null Feedback message
From Varchar2 35 Not Null Feedback from
cust/emp
To Varchar2 35 Not Null Feedbak from cust /emp
Bill_id Varchar2 10 Pk Bill id
Bill_date Date Not Null Bill Date
Delivery_id Varchar2 10 Pk Delivery id
Delivery_date Date Not Null Delivery date
66 Blue Shop System
Xelos Technology
3.6 Table Design:
Table Name: Login
Table Description: This table holds the Login Id and Password
67 Blue Shop System
Xelos Technology
Field Name Data
Type
size Constration
Userid Varchar
2
20 Primary key
User_Name Varchar
2
20 Not Null
User_password Varchar
2
20 Not Null
Table Name: Department_Master
Table Description: This table contains details of department
Field Name Data Type size Constraint
Dept_id Varchar2 10 Pk
Dept_name Varchar2 20 Not Null
Dept_date date Not Null
Table Name: Stock
Table Description: This table contains details of new stock and used by
administrator module
68 Blue Shop System
Xelos Technology
Field Name Data Type size Constraint
Stock_id Varchar2 20 Pk
Pr_id Varchar2 10 Fk
Pr_qty Number 20 Not Null
Date Date Not Null
Table Name: Missed Stock
Table Description: This table holds the details of missing stock
Field Name Data Type size Constraint
Missed_Stock_id Varchar2 10 Pk
Stock_id Varchar2 20 Fk
Pr_id Varchar2 10 Fk
Missed_qty Number 10 Not Null
Missed_date Date Not Null
Missed_Description Varchar2 50 Not Null
69 Blue Shop System
Xelos Technology
Table Name: Expired Stock
Table Description: Expired stock is maintained by this table
Field Name Data Type size Constraint
Expired_Stock_id Varchar2 10 Pk
Stock_id Varchar2 20 Fk
Pr_id Varchar2 10 Fk
Expried_qty Number 10 Not Null
Expired date Date Not Null
Table Name: Defective Stock
Table Description: Defective stock is maintained by this table
Field Name Data Type size Constraint
Defect_Stock_id Varchar2 10 Pk
Stock_id Varchar2 20 Fk
Pr_id Varchar2 10 Fk
Defect_qty Number 10 Not Null
Return_to Varchar2 30 Not Null
Date Date Not Null
Description Vachar2 50 Not Null
70 Blue Shop System
Xelos Technology
Table Name: Product_master
Table Description: This table holds the details of product
Field Name Data Type size Constraint
Pr_id Varchar2 10 PK
Pr_name Varchar2 20 Not Null
Pr_brand Varchar2 10 Not Null
Pr_doe Date Not Null
Pr_mno Varchar2 30 Not Null
Pr_feature Varchar2 50 Not Null
Pr_color Varchar2 10 Not Null
Pr_image Varchar2 30 Not Null
Pr_size Varchar2 10 Not Null
Pr_avail Number 10 Not Null
Pr_price Float Not Null
Table Name: Scheme_Master
Table Description: This used to add new scheme
Field Name Data Type size Constraint
71 Blue Shop System
Xelos Technology
Scheme_id Varchar2 10 Pk
Pr_id Varchar2 10 Fk
Discount Float 8 Not Null
Buy Number 9 Not Null
Get Number 9 Not Null
Table Name: Product Scheme details
Table Description: This holds the product scheme details
Field Name Data Type size Constraint
Scheme_id Varchar2 10 Fk
Pr_id Varchar2 10 Fk
Table Name: Employee_Master
Table Description: Details of employee is maintained by this table used by
administrator module
Field Name Data Type size Constraint
Emp_id Varchar2 10 Pk
Dept_id Varchar2 10 Fk
Emp_fname Varchar2 20 Not Null
Emp_lname Varchar2 20 Not Null
Emp_gender Varchar2 10 Not Null
72 Blue Shop System
Xelos Technology
Emp_sal float 8 Not Null
Emp_add1 Varchar2 50 Not Null
Emp_add2 Varchar2 50 Not Null
Emp_city Varchar2 20 Not Null
Emp_state Varchar2 20 Not Null
Emp_pin Number 15 Not Null
Emp_phone Number 10 Not Null
Emp_mobile Number 10 Not Null
Emp_email Varchar2 15 Not Null
Emp_doj Date Not Null
Emp_dob Date Not Null
Emp_password Varchar2 20 Not Null
Table Name: Customer_Master
Table Description: This table contains Detail of Customer
Field Name Data Type size Constraint
Cust_id Varchar2 10 Pk
Cust_fname Varchar2 20 Not Null
Cust_lname Varchar2 20 Not Null
Cust_gender Varchar2 10 Not Null
Cust_dor Date Not Null
Cust_add1 Varchar2 50 Not Null
73 Blue Shop System
Xelos Technology
Cust_add2 Varchar2 50 Not Null
Cust_city Varchar2 20 Not Null
Cust_state Varchar2 20 Not Null
Cust_pin Number 15 Not Null
Cust_phone Number 10 Not Null
Cust_mobile Number 10 Not Null
Cust_email Varchar2 15 Not Null
Cust_occuption Varchar2 20 Not Null
Cust_dob Date Not Null
Cust_password Varchar2 20 Not Null
Table Name:Customer Order
Table Description: This table is used to store detail of customer Order
Field Name Data Type size Constraint
Order_id Varchar2 10 Fk
Cust_id Varchar2 10 Fk
Order_date Date Not Null
Total_amt Float 9 Not Null
74 Blue Shop System
Xelos Technology
Table Name: Customer Order detail
Table Description: This table is used to store details of customer Order
Field Name Data Type size Constraint
Order_id Varchar2 10 Pk
Pr_id Varchar2 10 Fk
Pr_qty Number 9 Not Null
Pr_price Float 8 Not Null
Table Name: Feedback
Table Description: This is used to store the feedback
Field Name Data Type size Constraint
Feedback_id Varchar2 10 Pk
Feedback Varchar2 100 Not Null
75 Blue Shop System
Xelos Technology
Cust_id Varchar2 10 Fk
Emp_id Varchar2 10 Fk
Date Date Not Null
Table Name: Billing
Table Description: This used to store the Billing details
Field Name Data Type size Constraint
Bill_id Varchar2 10 Pk
Order_id Varchar2 10 Fk
Emp_id Varchar2 10 Fk
Bill_date Date Not Null
Bill_amount Float Not Null
Table Name: Delivery
Table Description: This used to store the Delivery details
Field Name Data Type size Constraint
Delivery_id Varchar2 10 Pk
Order_id Varchar2 10 Fk
Bill_id Varchar2 10 Fk
Delivery_date Date Not Null
Site Map:
76 Blue Shop System
Xelos Technology
Administrator:
Inbox
Product
Department
Scheme
Stock
Employee
Report
Employee:
Inbox
Billing
Delivery Form
All Feedback
77 Blue Shop System
Xelos Technology
Report
Profile
Customer:
Inbox
Compose
My cart
Pervious order
Profile
All Feedback
78 Blue Shop System
Xelos Technology
Menu Screen
79 Blue Shop System
Xelos Technology
Home:
Task: Accessing the Home page
Step: Type the Blue Shop instance URL in browser.
Description: Below is the layout Main Page This is primary interface of the
user. Once user type URL this page is response Back to user
80 Blue Shop System
Xelos Technology
Login
Task: Login into Blue Shop
Step: Type the Blue Shop instance url in browser.
Description: Below is the layout of Blue Shop System’s Main Page.
81 Blue Shop System
Xelos Technology
Registration:
Task: New customer wants to register
Step: Go To> Registration> fill Registration form>Blue Shop System
Description: Below is the layout of Registration in Blue Shop System’s If
new customer wants to get registered then can do same by using this page .
82 Blue Shop System
Xelos Technology
Item List:
Task: Show the list of item
Step: Go To> product /item page
Description: Below is the layout of Item list in Blue Shop System’s. This
page contains the list of shopping items. Customer can be order product
83 Blue Shop System
Xelos Technology
View Cart:
Task: View cart
Step: Go To> cart page
Description: Below is the layout of It cart in Blue Shop System’s. This
page contains the details of view cart shopping items. Customer can be
order product
84 Blue Shop System
Xelos Technology
Product Detail:
Task: View product details the
Step: Go To> product details>Blue Shop System
Description: Below is the layout of Product details in Blue Shop
System’s. This page contains the product details of shopping items.
85 Blue Shop System
Xelos Technology
Customer Order:
Task: View the customer Order
Step: Go To> Customer order
Description: Below is the layout of Customer Order in Blue Shop
System’s. This page contain Customer order When customer finishes its
shopping and make payment from this part
86 Blue Shop System
Xelos Technology
Employee registration
Task: New Employee wants to register
Step: Go To> Registration> fill Registration form>Blue Shop System
Description: Below is the layout of Employee Registration in Blue Shop
System’s If new employee wants to get registered then can do same by
using this page .
87 Blue Shop System
Xelos Technology
Department:
Task: Add/delete/update/search/modify department
Step: Go To> Department > Blue Shop System
Description: Below is the layout of Department information in Blue
Shop System’s. Administrator can use this page to
add/delete/search/modify department
88 Blue Shop System
Xelos Technology
Product Entry:
Task: Show the product entry such that add/delete/modify /search product
Step: Go To> product /item page
Description: Below is the layout of Product Entry list in Blue Shop System’s.
Administrator can use this page to add/delete/search/modify product Entry
89 Blue Shop System
Xelos Technology
Mail Box:
Task: Show mail box
Step: Go To> mail box
Description: Below is the layout of Mail box in Blue Shop System’s. This
page is used to view mail send by customer
90 Blue Shop System
Xelos Technology
91 Blue Shop System
Xelos Technology
Reports
Product Report:
Report for Schemes
Description: : This is Summary report for showing all the product
92 Blue Shop System
Xelos Technology
Scheme report:
Report for Schemes
Description: This is Summary report for showing all the schemes
93 Blue Shop System
Xelos Technology
Sales Report:
Report for Sales
Description: This is Summary report for showing all the sales
94 Blue Shop System
Xelos Technology
Bill Report:
Report for Bill
Description: This is Summary report for showing all the Bills
95 Blue Shop System
Xelos Technology
Customer Order Report:
Report for Customer Order
Description: This is Summary report for showing all the customer Order
96 Blue Shop System
Xelos Technology
97 Blue Shop System
Xelos Technology
Test Procedures and Implementation
Test procedure & Implementation:
Software testing is an investigation conducted to provide stakeholders with
information about the quality of the product or service under test.[1] Software
testing also provides an objective, independent view of the software to allow
the business to appreciate and understand the risks of software
implementation. Test techniques include, but are not limited to, the process of
executing a program or application with the intent of finding software bugs.
98 Blue Shop System
Xelos Technology
Software testing can also be stated as the process of validating and verifying
that a software program/application/product:
1. meets the business and technical requirements that guided its design
and development;
2. works as expected; and
3. can be implemented with the same characteristics.
Software testing, depending on the testing method employed, can be
implemented at any time in the development process. However, most of the
test effort occurs after the requirements have been defined and the coding
process has been completed. As such, the methodology of the test is
governed by the software development methodology adopted.
Different software development models will focus the test effort at different
points in the development process. Newer development models, such as
Agile, often employ test driven development and place an increased portion of
the testing in the hands of the developer, before it reaches a formal team of
testers. In a more traditional model, most of the test execution occurs after the
requirements have been defined and the coding process has been completed
Overview
Testing can never completely identify all the defects within software. Instead, it
furnishes a criticism or comparison that compares the state and behavior of
the product against oracles—principles or mechanisms by which someone
might recognize a problem. These oracles may include (but are not limited to)
specifications, contracts,[2] comparable products, past versions of the same
99 Blue Shop System
Xelos Technology
product, inferences about intended or expected purpose, user or customer
expectations, relevant standards, applicable laws, or other criteria.
Every software product has a target audience. For example, the audience for
video game software is completely different from banking software. Therefore,
when an organization develops or otherwise invests in a software product, it
can assess whether the software product will be acceptable to its end users,
its target audience, its purchasers, and other stakeholders. Software testing is
the process of attempting to make this assessment.
Type checking:
Type checking is the processes of identifying errors in
A program based on explicitly or implicitly stated type information a tractable
syntactic framework for classifying phrases according to the kinds of values
they compute . A type system associates types with each computed value. By
examining the flow of these values, a type system attempts to prove that no
type errors can occur. The type system in question determines what
constitutes a type error, but a type system generally seeks to guarantee that
operations expecting a certain kind of value are not used with values for which
that operation does not make sense.
Any Data item should be of some type user should be prevented from entering
other type of data
Length Checking:
Length checking of the data items should be checked as most of the data
items have some valid length as one of the their constraints.
100 Blue Shop System
Xelos Technology
Control Design:
The application begin a GUI application should provide the user to enter the
data in the order they prefer to enter, except to certain key data items. Even
though existence tests have to be done on these.
Testing Model:
1. Unit Testing:
The term unit testing refers to the individual testing of separate units of a
software system
unit testing is a method by which individual units of source code are tested to
determine if they are fit for use. A unit is the smallest testable part of an
application. In procedural programming a unit may be an individual function or
procedure. In object-oriented programming a unit is usually a method Unit
tests are created by programmers or occasionally by white box testers during
the development process.
Integrating testing:
Objective of Integration testing is to make sure that the interaction of two or
more components produces results that satisfy functional requirement. In
integration testing, test cases are developed with the express purpose of
exercising the interface between the components. Integration testing can also
be treated as testing assumption of fellow programmer
Validation Testing :
Verification and validation is the process of checking that a product, service,
or system meets specifications and that it fulfills its intended purpose. These
are critical components of a quality management system such as ISO 9000.
101 Blue Shop System
Xelos Technology
Sometimes preceded with "Independent" (or IV&V) to ensure the validation is
performed by a disinterested third party.
Output Testing:
Output testing involves the checking of output from the software from dummy
input. If the provides is an expeceped,then the S/W can be considered to be
given the desired output for the given input
User Accepting Testing:
acceptance testing is black-box testing performed on a system (for example: a
piece of software, lots of manufactured mechanical parts, or batches of
chemical products) prior to its delivery.[1] It is also known as functional testing,
black-box testing, QA testing, application testing, confidence testing, final
testing, validation testing, or factory acceptance testing.
Alpha testing
Alpha testing is simulated or actual operational testing by potential
users/customers or an independent test team at the developers' site. Alpha
testing is often employed for off-the-shelf software as a form of internal
acceptance testing, before the software goes to beta testing.[30]
102 Blue Shop System
Xelos Technology
Beta testing
public to increase the feedback field to a maximal number of future users Beta
testing comes after alpha testing and can be considered a form of external
user acceptance testing. Versions of the software, known as beta versions,
are released to a limited audience outside of the programming team. The
software is released to groups of people so that further testing can ensure the
product has few faults or bugs. Sometimes, beta versions are made available
to the open
103
Blue Shop System
Xelos Technology
Test cases
User Login and password verification.
Test case Id: Login001
Test case Name:Login_Test_Cases
104 Blue Shop System
Xelos Technology
105 Blue Shop System
Test
Case
Name
Test case
Description
Steps/Input Expected
Result
Actual
Result
Remark
Validate
Login
1.To verify
That login
Name on
login page
must be
greater than 3
characters
1.Enter Login
name less
than 3 chars.
&password
click submit
button
2.Enter Login
Name 4
chars.
&password
click submit
button
An error
message “login
not less than 3
characters”
must be
displayed
Login
successfully or
An error
message
displayed
Invalid login
Name or
password
Respective
user Home
page should
displayed
Pass
2 To verify
That login
Name on
login page
Does not take
special
charaters
Enter login
name with
special chars.
Password
and click
submit button
An error
message
“special chars.
Not allowed in
login” must be
displayed
Invalid login
Name or
password
validate
Password
1.To verify
That
password on
login page
must be
greater than
1.Enter
password
less than 6
chars. And
login name
and clicn
An error
message
“password not
less than
characters”
must be
Invalid
password
Xelos Technology
Test Case Id:Department002
Test Case Name: Add _Dept _Test_Case
106 Blue Shop System
Department
Test
Case name
Test case
description
Step/Input Expected
Result
Actual
result
Remark
Validate
Department
1.To verify
department
Id and
name
1.Enter valid
department
Id& name
2.Enter
department
Name &Id,
description
User
successfully
add
department
User
successfully
add
department
Respective
user
department
display
Respective
user
department
display
pass
3.Enter
invalid
department
name and Id
4.Do not
Error
message
display
Invalid user
type
Invalid
user type
Show error
Xelos Technology
Product Information:
Test Case Id :prod inf003
Test Case Name: Add_prod_Test_Cases
Test case
Name
Test case
Description
Step/Input Expected
Result
Actual
Result
Remark
Valid
product Id,
Departmen
t
Id
To verify
Product
Id ,product
name,
Departmen
t
Id
1.Enter
valid
product Id
2.Enter
product
Name
3.Enter
departmen
t
User
successfull
y Add the
product
information
In their
Respective
modules
And
respective
table
Product
successfull
y Add
pass
Do not
enter name
,id and
description
To verify
Product
Id ,product
name,
Departmen
t
Id
1.Do not
enter
product
information
2.Click
AddButton
Error
message
Display with
the enter
the details
information
frist
Error
Message
Enter
proper
information
of product
107 Blue Shop System
Test
Case name
Test case
description
Step/Input Expected
Result
Actual
result
Remark
Validate
Department
1.To verify
department
Id and
name
1.Enter valid
department
Id& name
2.Enter
department
Name &Id,
description
User
successfully
add
department
User
successfully
add
department
Respective
user
department
display
Respective
user
department
display
pass
3.Enter
invalid
department
name and Id
4.Do not
Error
message
display
Invalid user
type
Invalid
user type
Show error
Xelos Technology
Cart verification:
Test Case Id: verefi004
Test Case Name:Verefication_Test_Cases
Test
Case
Name
Test
Description
Step/Input Expected
Result
Actual
Result
Remark
Valid
Quantit
y
Verify
Quantity
1.Enter
the
Quantity
User
successfully
Add the
product
In cart
User add
successfully
Add the
product
Quantity in
cart
Pass
Do not
Enter
Quantit
y
2.Do not
Enter
quantity
Error
message
display with
the give the
all details
information
Error
message
display
108 Blue Shop System
Xelos Technology
USER MANUAL:
109 Blue Shop System
Xelos Technology
Introduction
Java Shop is a web based order tracking tool for companies and
Organizations which want to accelerate sales with minimal manual work. Blue
Shop System helps to do online shopping at easy Blue Shop. The online
Shopping maintains & delivers product an Also Online order and payment
done by cheque or on the delivery. This System enables to administrator to
generate proper report generation. Also bridges the gap between
administrator and customer as well as reduces time consuming problems, it
maintains account for each department
Internet has a very bright future. If you want to increase your business and
cross the boundaries of region you need to take help of internet. Without going
online you can’t think about your progress worldwide. In this regard you can
see all large scale business. Big brand, big shopping store are online. Online
shopping is the demand of today’s modern time. Time and quality is the main
subject of online shopping. Today everybody is running to save time and who
saves time automatically save money. Day to day needed item
now available on internet and people prefer to shop online.
1. Seaching product and their scheme :
Any user of the system can search product and their scheme andOther
details. We have placed two links for that on home page called Product
and scheme. This features can be accessed can be any user Without
registration We have given some selection criteria to search like
departmentWise, price, range, brand wise, size wise, color wise.
2.Customer Registration:
110 Blue Shop System
Xelos Technology
The main intension of system is online shopping but forthat
customer has to register him to system for online shopping. We placed
linkregister on home page when customer has to give some personal
information, contact details, security details such as id and password which
helps to login. In registration form some fields has Asterisk(*) it means these
field are compulsory every has validation so customer cannot provide invalid
data
3.Inbox/compose:
As other mailing site after login every user gets inbox and compse Message
for the other user, this can used to communicate to other user and viceversa.
Inbox ,user gets message which sent by other user o system.
Every message will have radio button used To selected message to Show
there is a button when user click on show button then system will show the
selected message. In compose ,user can send amessage to other user. We
have provide one feature i.e user cane select old message and save his time
of typing. User will just click only message from feedback list and send it to
other user. If user wants to send new message then he has his message and
system will give Id to that message
4. Customer Login:
When customer register to system then he gets Id and password that Id is
unique to all user that’s why every user can be identified uniquely. When
customer login to system if the login is successful then Customer will
gets his screen in that at the top screen shows name of the user with sign out
button.
Shopping cart is used to place the order when customer apply for The
shopping cart, he has select to select product which to be buy. In product list
every product has on button to select product which is Used to add product in
shopping cart. There another button to select product. When user click on
111 Blue Shop System
Xelos Technology
confirm order button system ask for payment. Payment will done by payment
will done by on the delivery or by cheque Then only system places order and
customer gives delivered details
Report :
Customer will get to reports frist is previous order and previous
Feedback. In previous order customer has to select order id and click
on show Button the customer will get details of that selected order In
previous feedback ,the list of all feedback, which is sent by Other
customer can use these feedback to send and save time of typing
5.Employee:
Employee cannot register to system if any new employee is Appointed
then administrator register him and give Id and save Id and password
after that he can update his profile.
Billing:
In billing employee will get all customer and every customer order Will
have one radio button when employee selects radio button and On show
order details then employee click on create bill button the System
generates bill of that order stores with employee Id.
112 Blue Shop System
Xelos Technology
Delivery:
After the billing employee deliver the order to correspondingCustomer
fills the delivery challan in database
Report:
Employee can have three types of reports. These reports are Billing
report, Delivery report, feedback report. Report is important for
employeefor the getting details about work.
In billing report, employee will get the all bills which are generate by that
particular employee who is accessing the billing report. In This report
employee will not get bills which are generate by the Other employee .when
employee request for the billing report he Will get the bill.
Id combo box in that employee has to select bill Id then he will get the The
all details of bill. In delivery report, employee will get the all the delivery
challan which Are delivered by that particular employee who is accessing
the deliver report. In this report employee who is accessing the deliver
challan which are delivery by the other employee requests for the delivery
report he will get the delivery Id then he will get the all details of delivery.
In previous feedback, the list of all feedback which sent byother customer
can uses these feedback to send and save time of typing.
6. Administrator:
Administrator is user who has whole authority regarding system . In this
system there is only one administrator who maintains all the master database
113 Blue Shop System
Xelos Technology
registering new employee . Administrator is also one the employees so he will
have record in the employee tables and can perform employee so will have
record in the employee work is maintaining master database these are as
follows.
Department:
In Java Shop there are different department and every department Has
many product. Administrator can add new department name By giving
department name by giving department id but he cannot Change
department Id because system uses department Id for every
Product. Administrator can change department as well as he can delete
department.
Product:
The product is mandatory thing of any shopping system, every Shopping
system must be maintain product in better manner So we differentiate all
the product in the department so that every Product has one department id.
Before inserting any product its Department must be inserted into
department table. Every product has some attribute like name, image,
price, color, size and product Id. These attributes help to find products list
as per the customer requirement.
Scheme:
In today’s generation every shopper ‘s given new schemes to
114 Blue Shop System
Xelos Technology
Customer so that’s why we added schemes in system. It handles all
schemes in the database.
Administration is only person who has add new schemes and
attach these schemes to any product. Also we have provided
facility to administrator i.e. if any existing schemes want to
attach with product then need enter scheme just attach scheme id to that
product.
Stock:
In other online java Shop, customer has to given order then
System gives availability of the product if product is not available Then
customer delete that product from order so its time consuming. We
overcome that drawbacks by giving availability at the time of Selection of
the product. For this administrator maintains stock, as per customer order
the quantity reduces.
Administrator has to maintain missed stock, defective stock,
Expired stock because if the does not maintain this stock then It is
considered as stock then it shows in the availability
115 Blue Shop System
Xelos Technology
Module Specification:
116 Blue Shop System
Xelos Technology
Module Specification:
Login:
Module Name Login
User Administrator,Employee,End
User
Trigger The User enters the correct
individual
User Id and password and
click
submit button
Preconditions The user has accessed the
login
screen of the system. The
117 Blue Shop System
Xelos Technology
user
Must be registered user and
he must
Know his username and
password
Basic Path
Post condition
1.The user must type the
system
URL in the address bar of the
Browser
2. The login page of the
system
Gets display
3.The user enters correct
user Id
4.the user is successfully
redirected in the System
The user is successfully
redirected
118 Blue Shop System
Xelos Technology
of the home page
Exception path The user enters incorrect
username
and /password any of the text
box
are kept blank
Other If user forgets the password
the
User can take new password
to
administrator.
Department:
Module Name Department
Trigger The user enter add and update , delete
department.
Search The department information
Precondition The user have accessed the
Department and Update
119 Blue Shop System
Xelos Technology
Basic path 1.The user must select the department
2. Then an add , update ,delete Buttons
gets display
3. The user enters correct department
Information and click on submit button
4. The user redirected to the same
page
Cart:
120 Blue Shop System
Exception Path Enter incorrect Information of
department ,it will get error message
Other
Xelos Technology
Module Name cart
Trigger End user enter add update and
Delete the product item of its cart
information
Precondition End user must be register before using
Cart module
Basic path 1.The user must select the item
add/update/delete form cart.
2. The add or update page of this
system gets display.
3. The user get message and redirect
to same page.
Post Conditions User is successfully redirected of the
same page
Exception Path The user enters incorrect item quantity
It will get error message
Report:
121 Blue Shop System
Xelos Technology
Module Name Report
User Administrator, employee, end
user
Trigger Select the type of rport
Preconditions Knowledge about system
then user
can select the category of
report
Basic path 1.The user must select the
Report
Menu from menu bar
2.The add or update page of
the
System gets display.
3.The user select the type of
report
4. The user gets report.
Post Condition User can take the print out of
the
report
Exception The user enters incorrect
122 Blue Shop System
Xelos Technology
Drawbacks and Limitations
123 Blue Shop System
Xelos Technology
Drawbacks and Limitations:
The system has some limitations. These limitations do not hinder the System
as a whole. The limitations are:
1. Slow Web sites
2. Product not available (status provided)
3. Late delivery
4. Unable to track order status
5. Web site outages
124 Blue Shop System
Xelos Technology
6. Long wait for customer services
7. Product not available (wasn't notified)
8. Order never arrived.
125 Blue Shop System
Xelos Technology
Proposed Enhancement
Proposed Enhancement:
126 Blue Shop System
Xelos Technology
Provide online credit card payment:
The system does not have online credit card payment. We are
planning to
implement online credit card payment which helps to
Administrator to give
payment online
Access on Mobile Device
Though this system contains many graphics this leads to the slow
access through
mobile. It will enhance so that it can be easily access through
mobile
127 Blue Shop System
Xelos Technology
Conclusion
128 Blue Shop System
Xelos Technology
Conclusion:
Finally I would like to conclude my project experience that I got While
development. I learnt new concept in Jsp, Servlet and oracle Database . I
have applied my experience to prepare this report is Prepare such a way so
that, one can easily understand about system.The introduction section all
basics Knowledge that is requiring understanding the system , and general
over view about the system.Then I have converted the main objective ,and
user requirements of the Proposed system.
129 Blue Shop System
Xelos Technology
BIBLIOGRAPHY
8. BIBLIOGRAPHY
Books Referred
Java,JSP References Books
130 Blue Shop System
Xelos Technology
Jsp Complete Reference – By Herbert Schidt
Core Servlet and JSP VOL 1 – By Hall and Brown
Java2 Complete Reference – By Herbert Schidt
Websites Referred
www.java.sun.com
www.jakarta.apache.org
www.google.com
WWW.Roseindia.net
www.ebay.com
www.w3c.org
131 Blue Shop System
Xelos Technology
132 Blue Shop System
Xelos Technology
133 Blue Shop System