COMPANY’S PROFILE

Apex TG India Pvt. Ltd. focuses on delivering sophisticated technology-enabled solutions,

consulting and Training to maximize complex business needs. Founded in 2007 and based in
New Delhi NCR Noida.

Apex TG India Pvt. Ltd. deals in IT Consulting, Training and Development services and
providing substantial and concrete results to the clients from across the globe. Apex TG India
Pvt. Ltd. Provides technical, management and personal skills development, focused on
developing better brains for better business. Company work on the principal that unique high
quality portfolio, builds skills in five inter-related areas:

 Management & Leadership Essentials: The essential skills required to be a successful

manager and leader.

 Learn, Absorb and Understand: Learn more efficiently, take better notes, think and
plan effectively and be well informed.

 Write, Speak and influence: Make a positive impression, be remembered, build

relationships and influence effectively – in every interaction.

 Creative Thinking and Innovation: Generate new perspectives and ideas, solve real
problems and enhance decision making and team working.

 Engagement and personal balance: Enhance engagement and motivation, reduce stress
levels and improve performance.

APEX TG INDIA PVT. LTD DEALS WITH THE FOLLOWING:

 Development

 Software Development

 Web Development

 Ecommerce web development

  2.Web Design

 3. .Net Industrial Training

 4. Java Industrial Training

 5. Software Testing Training

 6. SEO/SMO Training

 7. Web Designing Training

 8. Digital Marketing Training

DEALS WITH FOLLOWING TECHNOLOGIES:

 .Net 4.5.2

 Java 8

 PHP 5.6

 Oracle 11G

 Cloud Computing

 SAS

 IBM Mainframe

 Embedded System

 Software testing

 C and C++ programming

 Android

 Data Ware house

 RedHat Linux

 ERP
 INTRODUCTION

The Shop Cool (Online Shopping) is the part of the sample application that provides customers
with online shopping. Through a Web browser, a customer can browse the catalog, place
items to purchase into a virtual shopping cart, create and sign in to a user account, and purchase
the shopping cart contents by placing an order with a credit card.

Our Shop Cool (Online Shopping) will use shopping cart - this is our virtual trolley into which
we can place items then take them to the checkout when we want to pay. The checkout must be
in a secure server in order for our transaction to be secure.

In our Shop Cool (Online Shopping) all electronic records will maintained in password protected
archives. Our records are maintained so we can send you details of promotions or services, in
which we may be interested. However, each time we send you something you have the
opportunity to request that no further information be sent to me. Our personal information will
then be deleted from our records.

To enable us to provide our services to me, we need to collect personal information from me –
usually your name and email address. We may also choose to tell us our preferences and country
of origin when searching Shop Safe web sites. We may also choose to provide us with our
mobile phone number. Our electronic information systems are password protected to prevent
unauthorized access. Our staff are trained and required to protect the privacy of our personal
information.
All service providers will be informed of the importance we place on protecting our privacy and
their role in helping us to do this and we will ask them to undertake to maintain the
confidentiality of our personal information. Any use of our personal information by them will be
subject to the Privacy Act and the Principles.

By integrating information and improving processes, Shop Cool will help improve enterprise-
wide decision support and operational efficiency. Improved efficiency translates into:

 More resources to support the enterprise.

 Improved customer service
  Web-based and more user friendly interfaces to buyers.

PROBLEMS/NEEDS:

 Time Consuming process

 Difficulty to finding the products
 Inconvenient
 Difficult to compare prices
 High Price
 Limited Products
 Limited operation period
 Less information about the product.

SOLUTIONS/APPROACH:
 These steps will be considered to solve above mentioned problems
 Do not have to spend time to travel.
 Easy to find any product you want by simply browsing the website.
 Convenience
 Easy to compare product and prices
 Discounts are available
 Available 24x7
 Broader product Range
 Quality of information about the product.

Objectives:

Our objective was to look at online retail from a customer’s point-of-view and determine which
of the biggest US-based ecommerce sites was providing the best customer experience.

A secondary aim was to zero in on key trends and identify opportunities for high-impact and

 Customer experience improvements.

 Products categories must be well thought out, and intuitive.
  There must be effective decision support tools to guide you through the exploration
process.
 The product must be clearly displayed with appropriate visualization tools.
 If customer I have been to the site before, it must remember me and personalize
customer’s subsequent experience?
 It is easy to keep track of things customer want to buy.
 To shop while in the comfort of your own home, without having to step out of the door.
 To be able to easily save money and compare prices from website to website.
 Online resellers tent to sell at a lower price due to less overhead expenses.
 Customer need to register in order to make a purchase or access certain content.
Our objective is also satisfied to our clients because almost all merchants want to see that their
clients are satisfied with their purchases. It is simply good business. On many occasions, after-
sales difficulties arise when communication breaks down.

If we are having difficulty communicating with a merchant who is listed on Shop Safe, all we
have to do is ask us and we will do our best to contact that merchant on our behalf.

If our complaint is reasonable, we will attempt to secure a satisfactory resolution for you. We
make no warranties of any kind in this regard but we will do our best to achieve a satisfactory
outcome for me.

Always Ensure:

 Always ensure that we know what we are buying and that we do want the goods.
 Find out what the shipping costs are before you commit to purchase.
 Calculate the full cost including shipping of the goods we are buying.
 Find out how long it will take for the goods to be delivered.
 Ensure that the delivery address we provide is valid and that somebody will be available
to receive the goods.
 SYSTEM ANALYSIS

Review of Existing System:

The existing trade of the market is that the goods manufactured by the company are first received
by the dealer which ultimately is responsible for the sale of the goods to the end user. The
dealers acting as middleware (between company and consumer) consumes a lot of money and
therefore the market prices of the goods are very high till it reaches consumer. Now with the help
of the Web-Sites developed for such consumer goods the market price can be controlled to a
large extent bringing relief to the consumers to some extent.

 In the existing system all transactions, dealings of products, purchasing of products were
done manually which is time consuming.
 Reports are prepared manually as and when needed. Maintaining of reports is very
tedious task.
 To buy any product user has to collect information about it either by visiting the shop or
asking people which is the better one.
 There is no computer system to handling all payments. All calculations are performed
manually which may not be correct always.
 Any internet user can use this existing website to search for any kind of products, select
particular products from a wide range of products.
 Once they make their minds to purchase any particular item, they can place an order and
can make payments through various available payment options.

Requirement of proposed System:

Under various groups of products and categories of items, the selling companies will registers
and enter the particulars and specifications of their products together with prices. The consumers
will registers with bank details and other particular for viewing/searching the available products
and for buying them.

Once the consumers confirms the buying transactions the systems prompts him to enter the bank
details for processing and debit the amount. Through the authorized gateways the debit so raised
will be sent for credits to company’s account for selling. A receipt for transaction conformation
is generated by the system for consumer with a copy to the respective company for delivery of
the goods.

 Online Shopping Portal is a specific requirement of the client that integrates the buying
and selling services specifically to their customers.
 Need for the new system is due to major drawbacks of existing system.
 Reports can be generated at any time within few seconds, so that manual labour is not
required, and also analysis can be performed much more frequently which helps in taking
decision.
 The details regarding all users, products can also be maintained as their information is
very helpful and sometimes becomes a critical requirement.
 Allows user to get registered from their places and transact for the required product.
 To overcome these problems in existing system we develop “ShopCool” (online
shopping).
 PROBLEM ANALYSIS

BUSINESS RULES AND REQUIREMENTS:

Sr. NO Description Notes

1 User Requirements Step by step Report: Excellent Planning.
Organization and management. To avoid
the conflicts you can analyse the effects
easily in response to particular action.

2 Functional requirements a. Modules for admin to handle the

administration task.
b. Module for user to manage user
information.
c. Modules to manage product
category and information
d. Module for managing roles and
menus.
e. Module to Place online order
f. Modules for users to slect the
products, add products to the cart,
make payments.
3 Reporting Requirements Users can get reports of the ordered
products from the admin as a mail.
4 Security Requirements Data Security: Proper Backup of data
 The access to the system must be
through the secure and
authenticated login, authorizations,
etc.
 5 Non-Functional  Secure access of confidential by
requirements using roles based authentication.
 24 X 7 availability.
 Better component design to get
better performance at peak.

Table 1-Business Rules and Requirements

EXCLUSIONS COST:
 Cost:
 The cost management and budgeting is not to be considered in the current release.
 If the Project is to be extended on large scale then the cost factor on the resources will
be included but has been excluded for the time being.

FOUNDATION AND IMPACT:

 Assumptions:
 It has been assumed that the system will provide an interface for the user which is
easy to understand and implement.
 It is assumed that end user have at least basic knowledge of using computer based
applications.
 Issues and constraints:
 Security Requirements for the user i.e. authenticated and authorized access.
 Unauthorized access is prohibited.
 User related information should be in valid format.
 Risk Assessments:
 Lack/Unavailability of resources at the time of Survey.
 Conflict in time management
 REQUIREMENT ANALYSIS

Upon evaluating current problems and desired information (input and output), the analyst begins to
synthesize one or more solution. To begin, the data objects, processing function, and behavior of
the system are defined in detail. Once this information has been established basic architecture of
implementation are considered. A client –server approach would seem to be appropriate but does
the software support this architecture fall within the scope outlined in the software plan? A
database management system would seem to be required, but is the user/customers need for
associating justified? The process of evaluation and synthesis continues until both analyst and
customer feel confident that software can be adequately specified for subsequent development
steps.

Throughout evaluation and solution, synthesis, the analyst’s primary focus is on “What”, not
“How”. What data does the system produce and consume, What function must the system
perform, What behaviors does the system exhibits, What interface are defined and What
constraint apply?

Keeping in mind the problem with requirement gathering, a number of independent investigators
have developed a team oriented approach to requirement gathering that applied during early
stages of analysis and specifications called facilitated application specification technique
(FAST).

This approach encourages the creation of a join team of customers and developers who work
together identify the problem, propose elements of the solution, negotiate different approach and
specify preliminary set of solution requirements has been used predominantly by the information
system community, but the technique offers potential for improved communication in application
of all kinds.

Many different approaches of fast have been proposed. Each makes use of a slightly different
scenario but all apply variation on the following basic guide lines.

 A meeting is conducted at a neutral site and attended by both software engineers and
customers.
 Rule for preparation and participation are established.
 An agenda is suggested that is formal enough to cover all important points but
informal enough to encourage the free flow of ideas.
 A “facilitator” (can be a customer, a developer, or an outsider) control the meeting.
 A “definition mechanism” (can be work sheets, flip charts, or wall stickers or an
electronic bulletin board, chat room or virtual form) is used.
 The goal is to identify the problem, propose elements of the solutions, negotiate
different approaches, and specify a preliminary set of solution requirements and
atmosphere i.e. conductive to the accomplishment of the goal.
 FEASIBILITY STUDY
Feasibility is the determination of whether or not a project is worth doing. The process followed
in making this determination is called a feasibility study. This type study determines if a project
can and should be taken. Once it has been determined that a project is feasible, the analyst can go
ahead and prepare the project specification which finalizes project requirements. Generally,
feasibility studies are undertaken within tight time constraints and normally culminate in a
written and oral feasibility report. The contents and recommendations of such a study will be
used as a sound basis for deciding whether to proceed, postpone or cancel the project. Thus,
since the feasibility study may lead to the commitment of large resources, it becomes necessary
that it should be conducted competently and that no fundamental errors of judgment are made.An
important outcome of the preliminary investigation is the determination that system is feasible or
not. In the conduct of feasibility study, there are three major distinct and interrelated areas were
taken into consideration. They are as follows:

Technical Feasibility:
The System of operation which was functioning earlier was totally manual, with no kind of
automation or computerization. All the departments were maintaining separate registers for
keeping various records. The computerized system is technically feasible as it is efficient, less
time consuming, can produce outputs faster, can input large amount of data in limited time scale
and easier to use in operation.
This is concerned with specifying equipment and software that will successfully satisfy the user
requirement. The technical needs of the system may vary considerably, but might include:
 The facility to produce outputs in a given time.
 Response time under certain conditions.
 Ability to process a certain volume of transaction at a particular speed.
 Facility to communicate data to distant location.
In examining technical feasibility, configuration of the system is given more importance than the
actual make of hardware. The configuration should give the complete picture about the system’s
requirements: How many work station’s are required, how these units are interconnected so that
they could operate and communicate smoothly. What speeds of input and output should be
achieved at particular quality of printing. This can be used as a basis for the tender document
against which dealers and manufacturers can later make their equipment bids. Specific hardware
and software products can then be evaluated keeping in view with the logical needs. At the
feasibility stage, it is desirable that two or three different configurations will be pursued that
satisfy the key technical requirements but which represent different levels of ambition and cost.
Investigation of these technical alternatives can be aided by approaching a range of suppliers for
preliminary discussions. Out of all types of feasibility, technical feasibility generally is the most
difficult to determine.

Operational Feasibility:

The ultimate users i.e. the people who are supposed to use the system are trained for a period of
time so as to get familiar with the new system and its operation. They are taught about the new
skills and the new technology and how the technology will be useful to them in their functioning.
Operational feasibility is concerned with human, organizational and political aspects.

It is mainly related to human organizational and political aspects. The points to be considered
are:

 What changes will be brought with the system?

 What organizational structures are distributed?

Generally project will not be rejected simply because of operational infeasibility but such
considerations are likely to critically affect the nature and scope of the eventual
recommendations. This feasibility study is carried out by a small group of people who are
familiar with information system techniques, who understand the parts of the business that are
relevant to the project and are skilled in system analysis and design process.

Economical Feasibility:
The computerized system is economically feasible in the sense the cost of the hardware and
software and the cost to training of personnel of the company to operate the system and the
installation cost is less than the cost of maintaining the registers.
This is the most frequently used technique for evaluating the effectiveness of a proposed system.
More commonly known as cost/benefit analysis; the procedure is to determine the benefits and
savings that are expected from a proposed system and compare them with costs. If benefits
outweigh costs, a decision is taken to design and implemented the system. Otherwise, further
justification or alternative in the proposed system will have to be made if it is to have a chance of
being approved. This is an ongoing effort that improves in accuracy at each phase of the system
life cycle.

SOCIAL FEASIBILITY:

Social feasibility is a determination of whether a proposed project will be acceptable to the

people or not. This determination typically examines the portability of the project being accepted
by the group directly affected by the proposed system change.

LEGAL FEASIBILITY:

Legal feasibility is a determination of whether a proposed infringes on known Acts, Status, as

well as any pending legislation. Although in some instances the project might appear sound, on
closer investigation it may be found to infringe on several legal areas.

TIME FEASIBILITY:

Time feasibility is a determination of whether a proposed project can be implemented fully

within a stipulated time frame. If a project takes too much time it is likely to be rejected.
 SOFTWARE REQUIREMENT SPECIFICATIONS
Requirements specification involved coming up with a detailed documentation of what the propo
sed system was supposed to do. All the functionalities of the new system are described indetail.
It involves description of the user requirements into structures that can be automated.They
prescribe a reduced level of abstraction.

System Analysis is the application of the system approach to the study and solution of the
problems using computer-based system. An activity encompasses most of the tasks collectively
called as “Computer System Engineering”. Analysis is a detailed study of the various operation
performed by a system and their relationship within and outside of the system. This involves
gathering information and using structured tool for analysis such as DFD (data flow diagram),
Decision Tree etc. During analysis data are collected on the available files, decision points and
transactions handled by the present system. The fact finding and information gathering for
proposed system is the key part of system analysis. Information is gathered from sources both
internal and external to the organization. The external sources include vendors, supplier
professional journals and other similar systems. The primary internal sources include the system
users, system documentation existing programs, and reports. Analysis is the process of
diagnosing situations, done with a defiant aim, with the system kept in mind to produce a report
based on the findings. Analysis is a fact of finding technique where studies like the system
requirement specifications, boundaries of feasibility analysis and cost benefit analysis are carried
out. The requirements of both the system and the software are document and reviewed with the
user.

Requirements analysis is a software engineering task that bridges the gap between system level
requirement engineering and software design. Requirement engineering activities result in the
specification of software’s interface with other system elements, and establish constraints that
software interface with other system elements, and establish constraints that software must meet.
Requirements analysis allows the software engineer to refine domains that will be treated by
software. Requirement analysis provides the software designer with a representation of
information, function, and behavior that can be translated to data, architectural, interface, and
component-level designs. Finally, the requirements specification provides the developer and the
customer with the means to assess quality once software is built.

Software requirements analysis may be divided into five areas of effort:

 Problem recognition.
 Evaluation and synthesis.
 Modeling.
 Specification.
 Review.
Initially, the analyst studies the System Specification and the Software Project Plan. It is
important to understand software in a System context and to review the software scope that was
used to generate planning estimates so that problem recognition is ensured. The goal is
recognition of the basic problem elements as perceived by the customer/users.

Problem evaluation and solution synthesis is the next major area of effort for analysis. The
analyst must define all externally observable data objects, evaluated the flow and content of
information, define and elaborate all software function, understand software behavior in the
context of events that affect the system, establish system interface characteristics, and uncover
additional, and uncover additional design constraints. Each of these tasks serves to describe the
problem so that an overall approach or solution may be synthesized.

SYSTEM OVERVIEW:

Generally, the system represented by this report is meant to offer seven main functionalities:

 Buying and ordering items online

 Paying of items online
 Admin managing shop store
 Secure records of customers
 Manage transaction of customers.
 Generate reports of the shops to management(admin)
 Easy to use and user friendly interface
FUNCTIONAL SPECIFICATIONS:

 Users should registered before buying or ordering products online to make the
transaction secure.
 Once the user register and have an account he/she can be able to buy or order product
online.
 Admin must be able to view the transaction made by the customers buy viewing of
reports when logged in.
 Admin must be able to view the transaction made by the customers buy viewing of
reports when logged in.
 The user transaction should be secure. That is authentication mechanism
will be built into the application to prevent unauthorized persons from accessing another
customers’ account.
 Admin should be able to manage the stock in the store through editing, removing and
adding.

PRODUCTS SPECIFICATIONS:
It consists of these modules:
 Authentication and Authorization.
 Login and session.
 User authentication.
 Roles assign by admin user.
 Roles assign user wise.
 Order the product
 View the product
 Select the product
 Add to cart
 Fill users detail and address
 Place order
 Make Payment
  Password recovery
 Change password

 ADMINSTRATOR
These are the users who use to manage (Controls) whole website and its contents. They
have the privileges to manage the database. Few of the administrator modules are as
follows:
 Insert the product details
 Add/Remove products
 Manage other users.
 Access and maintain all users.
 USERS
There are other users who are created by admin user and assign role and responsibility,
according assigned role other user will use the website and make work more efficient.
These are the users for whom we are making this website. After registration procedure
they will be registered to use our website and who is not part of institute they can’t
allowed to purchase from our website, for this they must be registered with us.

TECHNICAL REQUIREMENTS:

FRONT END

 Presentation Layer: Java Server Pages

 User friendly
 Separation of work(design and coding)
 Write once and run anywhere
 Middle tier: Java Beans and Servlet.
 Database Layer: MySql
 Web development language: HTML5, CSS, and BOOTSTRAP.

Software Requirements:

 Operating System : WindowsXP/windows7/windows8 and above

  User Interface : HTML, CSS
 Client-side Scripting : JavaScript
 Programming Language : Java
 Web Applications : JDBC, Servlets, JSP
 IDE/Workbench : NetBeans 8.x
 Database : MySql
 Server Deployment : Tomcat 6.x

Hardware Requirements:

 Processor : Pentium IV

 Hard Disk : 40GB

 RAM : 256MB
SOFTWARE DEVELOPMENT LIFE CYCLE:
Software development organization follows some process when developing a software product.
A key component of any software development process is the life cycle model on which the
process is based. The particular life cycle model can significantly affect overall life cycle costs
associated with a software product. Life cycle of the software starts from concept exploration
and at the retirement of the software.
 Fig: - Software Development Life Cycle

PHASES OF SOFTWARE DEVELOPMENT LIFE CYCLE:

The software development life cycle is classically thought of as the set of activities that analysts,
designers and users carry out to develop and implement an information system.
The system development life cycle consists of the following activities:
 Feasibility Study
 Requirement Analysis
 Designing
 Coding
 System Testing
 Implementation and Maintenance.
Feasibility Study: An important outcome of the preliminary investigation is the determination
that system is feasible or not. In the conduct of feasibility study, there are three major distinct
and interrelated areas were taken into consideration. They are as follows:
 Technical Feasibility: The System of operation which was functioning earlier was
totally manual, with no kind of automation or computerization. All the departments
were maintaining separate registers for keeping various records. The computerized
system is technically feasible as it is efficient, less time consuming, can produce
outputs faster, can input large amount of data in limited time scale and easier to use
in operation.
 Operational Feasibility: The ultimate users i.e. the people who are supposed to
use the system are trained for a period of time so as to get familiar with the new
system and its operation. They are taught about the new skills and the new
technology and how the technology will be useful to them in their functioning.
Operational feasibility is concerned with human, organizational and political
aspects.
 Economical Feasibility: The computerized system is economically feasible in the
sense the cost of the hardware and software and the cost to training of personnel of
the company to operate the system and the installation cost is less than the cost of
maintaining the registers.
Requirements analysis: Analysis of requirements includes studying the existing system and
collecting data. During analysis, data are collected on the available files, decision points and
transaction handled by the present system. Once the structured analysis is completed, the analyst
has affirmed understanding of what is to be done.

System Designing: The design of an information system produces the details that clearly
describe how a system will meet the requirements identified during system analysis. System
analysts begin the design process by identifying reports and other outputs system will produce.
The system design also describes the data to be input, calculated or stored.

Coding: This is the phase in which computer based system is constructed from the specifications
prepared in the design phase. Equipment is acquired and installed during the development phase.
All necessary procedure, manuals software specifications, and other documentation are
completed. The staff is trained.

System Testing: During system testing, the system is used experimentally to ensure that the
software does not fail. In other words we can say that it will run according to its specifications
and in the way users expect. Special test data are input for processing, and the result examined.

Implementation, Evaluation and Maintenance: Implementation is the process of having

systems personnel check out and put new equipments into use, train users, install the new
application and construct any files of data needed to use it.
Evaluation of the system is performed to identify its strength and weaknesses. Maintenance is
necessary to eliminate errors in the working system during its working life and to tune the system
to any variations in its working environment. The importance of maintenance is to continue to
bring the new system to standards.
 SYSTEM DESIGN

System design refers to the technical specification that will be applied in implementing the
candidate system. This involves input/output, file and processing design. System design is a
solution, a “how to” approach to the creation of new system. This important phase is composed
of several steps. It provides the understandings and procedural details necessary for
implementing the system recommended in feasibility study. Emphasis is on translating the
performance requirements into design specifications. Design goes through logical and physical
stages of development. Logical design reviews the present physical system; prepares input and
output specification; makes edit, security, and control specifications details the implementation
plan; and prepares a logical design walkthrough. The physical design means out the details of the
physical system, plans the system implementation, devises a test and implementation plan, and
specifies any new H/W or S/W.

Several development activities are carried out during structured design. They are data base
design, implementation planning, system test preparation, and system interface specification and
user documentation.

Data base design:

This activity deals with the design of the physical database. A key is to determine how the access
paths are to be implemented. A physical path is derived from logical paths.

Program design:

In conjunction with the database design is a decision on programming language to be used and
the flowcharting, coding, and debugging procedure prior to conversion.

System and programs test preparation:

Each aspect of the system has separate test requirement. System testing is done after all
programming and testing is completed. The test cases cover every aspect of the candidate system
actual operations, user interface and so on
DATA FLOW DIAGRAM:

A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system modelling, its process aspects. Often they are a preliminary step used to
create an overview of the system which can later be elaborated. DFDs can also be used for the
visualization of data processing (structured design).
A DFD shows what kinds of information will be input to and output from the system, where the
data will come from and go to, and where the data will be stored. It does not show information
about the timing of processes, or information about whether processes will operate in sequence
or in parallel (which is shown on a flowchart).
DFDs are an important technique for modelling, a system’s high –level detail by showing how
input data is transformed to output results through a sequence of functional transformations.
DFDs consist of four major components: entities, processes, data stores, and data flows. The
symbols used to depict how these components interact in a system are simple and easy to
understand; however, there are DFD models to work from, each having its own symbol. DFD
syntax does remain constant by using simple verb and noun constructs.
Such a syntactical relationship of DFDs makes them ideal for object-oriented analysis and
parsing functional specifications into precise DFDs for the systems analyst.
When it comes to conveying how information data flows through systems (and how the data is
transformed in the process), data flow diagrams (DFDs) are the method of choice over technical
descriptions for three principle reasons.
 DFDs are easier to understand by technical and non technical audiences.
 DFDs can provide a high level system overview, complete with boundaries and
connections to other systems.
 DFDs can provide a detail representation of system components.
DFD’s help system designers and others during initial analysis stages visualize a current system
or one that may be necessary to meet new requirements. Systems analysts prefer working with
DFDs, particularly when they require a clear understanding of the boundary between existing
systems and postulated systems. DFDs represent the following:
 External devices sending and receiving data
 Processes that change that data
  Data flows themselves
 Data storage locations
The hierarchical DFD typically consists of a top-level diagram (Level 0) underlain by cascading
lower level diagrams (Level 1, Level 2…) that represent different parts of the system.
DFD Notations:
The DFD may be partitioned into levels that represent increasing formation flow and functional
details. Four simple notations are used to complete a DFD.
These notations are given below:-
 Data flow
 Process
 External Entity
 Data Store
 Output
Data Flow:
The data flow is used to describe the movement of information from one part of the system to
another part. Flows represent data in motion. It is a pipe line through which information flows.

Process:
A circle or bubble represents a process that transforms incoming data to outgoing data. Process
shows a part of the system that transforms inputs to outputs.
External Entity:
A square defines a source or destination of system data. External entities represent any entity that
supplies or receive information from the system but is not a part of the system.

Data Store:
The data store represents a logical file. A logical file can represent either a data store symbol
which can represent either a data structure or a physical file on disk. The data store is used to
collect data at rest pr a temporary repository of data. It is represented by open rectangle.

Output:
The output symbol is used when a hard copy is produced and the user of the copies can not be
clearly specified or there are several users of the output.
CONTEXT LEVEL DFD:
FIRST LEVEL DFD (ADMIN):
SECOND LEVEL DFD (ADMIN):
SECOND LEVEL DFD (MEMBER):
SECOND LEVEL DFD (VISITOR)
SECOND LEVEL DFD (ORDER TRACK)
USE CASE DIAGRAM:

Use Case diagrams are used to chart out the user requirements. This diagram represents the
different use cases, actors in a system with their relationships.

USE CASE OF SHOPCOOL:

MAINTAINING THE SHOPPING CART (ADMIN) MODULE:
MAINTAIN ACCOUNT(USER):
EXPLORE CATALOG:

MAKE PAYMENT:
FLOW CHART:
Flow Charts are the Pictorial representations of the flow of the data of the Travel with Glance
System. In flowcharts the Start/Stop is represented by eclipse, Input/output is shown by
rectangles, operations are shown in parallelogram, and diamonds represents the Decision box.

LOGIN MODULE:
FLOW CHART FOR THE SYSTEM:

Fig.Flow Chart Of The ShopCool

ENTITY RELATIONSHIP DIAGRAM:

Entity – Relationship model (ER model) in software engineering is an abstract way to describe a
database. This article refers to the techniques proposed in Peter Chen's 1976 paper. However,
variants of the idea existed previously, and have been devised subsequently such as super type
and subtype data entities and commonality relationships.

An ER model is an abstract way to describe a database. Describing a database usually starts with
a relational database, which stores data in tables. Some of the data in these tables point to data in
other tables - for instance, our entry in the database could point to several entries for each of the
phone numbers that are ours.

The ER model would say that we are an entity, and each phone number is an entity, and the
relationship between us and the phone numbers is 'has a phone number'. Diagrams created to
design these entities and relationships are called entity–relationship diagrams or ER diagrams.

Using the three schema approach to software engineering, there are three levels of ER models
that may be developed.

LEVELS OF E-R MODEL:

The Conceptual Data Model:

 This is the highest level ER model in that it contains the least granular detail but
establishes the overall scope of what is to be included within the model set.
 The conceptual ER model normally defines master reference data entities that are
commonly used by the organization.
 Developing an enterprise-wide conceptual ER model is useful to support documenting
the data architecture for an organization. A conceptual ER model may be used as the
foundation for one or more logical data models.
 The purpose of the conceptual ER model is then to establish structural metadata
commonality for the master data entities between the set of logical ER models.
 The conceptual data model may be used to form commonality relationships between ER
models as a basis for data model integration.
The Logical Data Model:

 A logical ER model does not require a conceptual ER model especially if the scope of the
logical ER model is to develop a single disparate information system. The logical ER
model contains more detail than the conceptual ER model.

 In addition to master data entities, operational and transactional data entities are now
defined. The details of each data entity are developed and the entity relationships between
these data entities are may be defined as a thing which is recognized as being capable of
an independent existence and which can be uniquely identified.

 An entity is an abstraction from the complexities of a domain. When we speak of an

entity, we normally speak of some aspect of the real world which can be distinguished
from other aspects of the real world.

 An entity may be a physical object such as a house or a car, an event such as a house sale
or a car service, or a concept such as a customer transaction or order. Although the term
entity is the one most commonly used, following Chen we should really distinguish
between an entity and an entity-type. An entity-type is a category.

The Physical Model:

 One or more physical ER models may be developed from each logical ER model. The
physical ER model is normally developed to be instantiated as a database. Therefore,
each physical ER model must contain enough detail to produce a database and each
physical ER model is technology dependent since each database management system is
somewhat different.

 The physical model is normally forward engineered to instantiate the structural metadata
into a database management system as relational database objects such as database tables,
database indexes such as unique key indexes, and database constraints such as a foreign
key constraint or a commonality constraint.

 The ER model is also normally used to design modifications to the relational database
objects and to maintain the structural metadata of the database. The first stage of
 information system design uses these models during the requirements analysis to describe
information needs or the type of information that is to be stored in a database.

 The data modeling technique can be used to describe any ontology (i.e. an overview and
classifications of used terms and their relationships) for a certain area of interest. In the
case of the design of an information system that is based on a database, the conceptual
data model is, at a later stage (usually called logical design), mapped to a logical data
model, such as the relational model; this in turn is mapped to a physical model during
physical design. Note that sometimes, both of these phases are referred to as "physical
design".

ER-Modeling:

The building blocks are:

 Entities

 Attributes

 Relationships

Entities:

In a database model, each object that you wish to track in the database is known as an entity.
Normally, each entity is stored in a database table and every instance of an entity corresponds to
a row in that table. In an ER diagram, each entity is depicted as a rectangular box with the name
of the entity contained within it.

They would then repeat the process to create a rectangular box for each entity in the data model.

Here's a depiction of the Person entity in that format.

That covers the "Entity" part of Entity-Relationship diagrams. Now let's take a look at displaying
data relationships.

Relationship:
Relationships are normally given names that are verbs, while attributes and entities are named
after nouns. This convention makes it easy to express relationships. For example, if we name our
Person/City relationship "Lives In", we can string them together to say "A person lives in a city."
We express relationships in E-R diagrams by drawing a line between the related entities and
placing a diamond shape that contains the relationship name in the middle of the line. Here's how
our Person/City relationship would look:

Attributes:

Each of these attributes is depicted in an E-R diagram as an oval, as shown in the figure below:

Notice that the text in the attribute ovals is formatted slightly differently. There are two text
formatting features used to convey additional information about an entity's attributes

Cardinality in E-R Model:

In data modeling, the cardinality of one data table with respect to another data table is a critical
aspect of database design. Relationships between data tables define cardinality when explaining
 how each table links to another. In the relational model, tables can be related as any of: many-to-
many, many-to-one (rev. one-to-many), or one-to-one.

E-R DIAGRAM:

Order-id
Prod_id
Prod_id
Prod_Name
U_name qty
address
Add Price
1 M ORDER M M Product
User place Has
Email
1
Category-Id
date
Cntct_No 1 M
Has
Has

Date
Remarks Has Category_Name
M 1 1

Order-Id DELIVERY M
CATEGORY
Are STOCK
Category-id

Sale-id Stock-id Prod_id

M Delivery_Qty

SALE

Prod_id
Date
DATA DICTIONARY:

TABLES

TABLE1: ADMIN

TABLE2: USERS

TABLE3: PRODUCT CATEGORY

TABLE4: PRODUCT

TABLE 5: PRODUCTCOMPANY

TABLE 6: PAYMENTDETAILS

TABLE7: PURCHASE_HISTORY
TABLE 8: ADDRESS

TABLE 9: SHIPPING ADDRESS

TABLE10: SHIPPING_PRODUCT

TABLE11: CONTACT US
 TESTING

Software testing is an investigation conducted to provide information about the quality of the
product or service under test. Software testing can also provide an objective, independent view of
the software to allow the business to appreciate and understand the risks at the software
implementation. Software testing is any activity aimed at evaluating an attribute or capability of
a program or system and determining that it meets its required results. Software Testing is the
process of executing a program or system with the intent of finding errors. Software testing can
also be stated as the process of validating and verifying that a software
program/application/product:

FUNCTIONALITY ENGINEERING ADAPTABILITY

(EXTERIOR QUALITY) (INTERIOR QUALITY) (FUTURE QUALITY)

CORRECTNESS TESTABILITY DOCUMENTATION

EFFICIENCY REUSABILITY MAINTAINABILITY
FLEXIBILITY USABILITY INTEGRITY
RELAIABILITY STRUCTURE
Table 1: Typical Software quality factors

TESTING OBJECTIVES:

The main objectives of testing is to uncover a host of errors, systematically and with minimum
effort and time, starting formally, we can say,

 Testing is the process of executing a program with the intent of finding errors.
 A successful test is one that uncovers an as yet of finding errors.
 A good test case is one that has a high probability of finding errors, if it exits.
 The tests are independent to detect possible errors.
 The software more or less confirms to the quality and reliable standards.
LEVELS OF TESTING:

UNIT TESTING:

 Unit Testing is primarily carried out by the developers.

 It deals with the functional correctness and the completeness of individual program
units.
 Whit box testing methods are employed.

INTEGRATION TESTING

It deals when several program units are integrated.

 Regression Testing: Change of behaviour due to modification or addition is called

‘Regression’; it is used to bring changes from worst to least.
 Incremental Integration Testing: Checks out for bugs which encounter when a
module has been integrated to the existing.
 Smoke Testing: It is the battery of test which checks the basic functionality of
program. It fails then the program is not sent for further testing.

SYSTEM TESTING

It deals with testing the whole program system for its intended purpose.

 Recovery Testing: System is forced to fail and checked out how well the system
recovers the failure.
 Security Testing: Checks the capability of system to defend itself from hostile attack
on programs and data.
  Load and Stress Testing: The system is tested for max load and extreme stress points
are figured out.
 Performance Testing: Used to determine the processing speed.
 Installation Testing: Installation and uninstallation is checked out in the target
platform.

ACCEPTANCE TESTING

UAT ensures that the project satisfies the customer requirements.

 Alpha Testing: It is the test done by the client at the developer’s site.
 Beta Testing: It is the test done by the end user at the client’s site.
 Long Term Testing: Checks out for faults occurrence in a long term usage of the
product.
 Compatibility Testing: Determines how well the product is substantial to product
transition.

ALPHA TESTING

Alpha testing is testing of an application when development is about to complete. Minor

design changes can still be made as a result of alpha testing. Alpha testing is typically
performed by a group that is independent of the design team, but still within the company,
e.g. in-house software test engineers, or software QA engineers.

BETA TESTING

Beta testing is testing of an application when development and testing are essentially
completed and final bugs and problems need to be found before the final release. Beta
testing is typically performed by end-users or others, not programmers, software engineersor
test engineers.
TEST CASES:

TEST CASES FOR LOGIN FORM:

Test Suite: User Login Form Date of Creation:20-04-2018

Created By: Implemented On: 20-04-2018
Shravan
Pre-Requisites: Weblogic or Tom Cat server, MySql, Login Form, Google chrome,JDK 8
Mozilla Firefox 5.0
Required Field Validator: (User Name,
Validation: Password)
Valid Classes User Name (email id, Max length =100)
Password (A-Z, a-z,1234567890, Max length =20, Special character (~!
@#$%^&*_+=-
}{[]\|’;:”/.,<>?))
Invalid Classes User Name (Spaces, invalid email format)
Password (Spaces)
User Interface Login Form
User Name and As per the login person or as generated by in the database
Password
Test Case Id Description Expected Result Actual Result Rem
Arks

Leave all fields (User

TC-ULG-01 Name It should display Error message Pass
and password) empty and error message in displayed in
click on Login button. validation validation summary
“Enter User name
summary and
User ID and Password
Password
respectively.
TC-ULG-03 It accept Pass
Enter alphabets and It Alphabets and
Numbers in the should accept both numbers.
User Name field. values.

TC-ULG-04 Enter spaces in the User It should not It does not allows Pass
Name field. allow spaces. spaces to be entered
in the User Name
field.
TC-ULG-05 Enter special characters It should accept It does accepts Pass
in User Name field such special special characters in
as!@#$ %^&*()_+=- characters in User User Name field
 except invalid email
address.
Name field but
valid email address
only
{}|:”?><,\ /
TC-ULG-06 Check for maximum It should not It does not exceed Pass
length of characters for accept infinite the maximum length.
the User Name field. characters in User
Name field.
TC-ULG-07 Enter numeric values in It should accept It accepts the Pass
Alpha-numeric values
Along with
the User Name field. Alpha-numeric @example.com
Values followed by
@example.com (email id)
TC-ULG-08 It should display It displays an error Pass
an error message message “ User
Enter the Password field in validation Name field”
and leave the User summary
Name “Enter user name
field blank. field.

TC-ULG-09 Enter alphabets in the It should accept It accepts the Pass

Password field the alphabets in alphabets either they
(Both Capitals and Password field. are in capital letters
small). or small letters.
TC-ULG-10 Enter spaces in Password It should not It does not accept the Pass
Field. accept spaces in spaces in Password
the Password field.
field.
TC-ULG-11 Enter special characters It should accept It accepts special Pass
in Password field such special characters characters in
as!@#$ %^&*()_+=- in Password field. Password field.
{}|:”?><,\ /
TC-ULG-12 Check for maximum It should not It does not exceed Pass
length of characters for accept infinite the maximum length.
the Password field. characters in

Password field.
TC-ULG-13 Enter numeric values in It should accept It accepts the Pass
the Password field. numeric values numeric values.
also.
Enter invalid User Name
TC-ULG-14 and It should display It displays an error Pass
Password and click on an error message. message “
Login button. User Name and
password” is incorrect
TC-ULG-15 Enter valid User Id and Login should be Login successful and Pass
Password and click on successful. is redirected to the
Login button. page as per login.
TC-ULG-16 Click the Reset button It should clear all It clears the entered Pass
the entered fields fields.
prior to login

TEST CASES FOR FORGOT PASSWORD FIRST PAGE:

Test Suite: User Forgot Password

Form Date of Creation:20-04-2018
Created By: Implemented On: 20-04-2018
Shravan
 Weblogic or Tom Cat server, MySql, Login Form, Google chrome,JDK
Pre-Requisites: 8,
Mozilla Firefox 5.0
Validation: Required Field Validator: (User Name)
Valid Classes
User Name (valid email id, Max length =200)

Invalid Classes User Name (Spaces, ivalid email id)

User Interface Login Form

User Id and As per the login person or as generated by in the database
Password
Test Case Id Description Expected Result Actual Result Rem
Arks

TC-ULG-01 LeaveUser Name It should display Error message Pass

empty and error message in displayed
click on Next button.
“Enter User name”
User ID

required
TC-ULG-03 It accept Pass
Enter alphabets and Alphabets and
Numbers in the It numbers. Ie: email id
User Name field. Ie: should accept both only
email id values.
TC-ULG-04 Enter spaces in the User It should not It does not allows Pass
Name field. allow spaces. spaces to be entered
in the User Name
field.
TC-ULG-05 Enter special characters It should It does accepts Pass
in User Name field such accept special special characters in
User Name
field.Except invalid
as!@#$ %^&*()_+=- characters in User email id.
Name field. Except
{}|:”?><,\ / invalid email id.
TC-ULG-06 Check for maximum It should not It does not exceed Pass
length of characters for accept infinite the maximum length.
the User Name field. characters in User
Name field.

TEST CASES FOR FORGOT PASSWORD NEXT PAGE:

Test Suite: User Forgot Password

Form Date of Creation:20-04-2018
Created By: Implemented On: 20-04-2018
Shravan
Weblogic or Tom Cat server, MySql, Login Form, Google chrome,JDK
Pre-Requisites: 8,
Mozilla Firefox 5.0
Validation: Required Field Validator: (User Name)
Valid Classes Valid EmailId( Max length =100)
Invalid Classes Emailid (Spaces)

Forgot Password
User Interface Next
User Id and As per the login person or as generated by in the database
Password
Test Case Id Description Expected Result Actual Result Rem
Arks

TC-ULG-01 Leave Email It should display Error message Pass

empty and error message in displayed
click on Submit button.
“Enter Email ID”
Email required

TC-ULG-03 It accept Pass

Alphabets and
It numbers with special
Enter proper email should accept character but in
format. proper email id proper format.
. values.

TC-ULG-04 Enter spaces in the It should not It does not allows Pass
Email Id field. allow spaces. spaces to be entered
in the Email ID field.
TC-ULG-05 Enter special characters It should It accepts Pass
 in Email Id field such accept special special characters in
as!@#$ %^&*()_+=- characters in Email ID.
{}|:”?><,\ / Email Id field.
TC-ULG-06 Check for maximum It should not It does not exceed Pass
length of characters for accept infinite the maximum length.
the Email ID field. characters in
Email ID field.

TEST CASES FOR USER SIGNUP:

Test Suite: Employee Details Date of Creation:20-04-2018

Created By: Implemented On:20-04-2018

Shravan

Pre- Weblogic or Tom Cat server, MySql, Login Form, Google chrome,JDK 8,
Requisites: Mozilla Firefox 5.0

Validation:

Required Field Validation: Name, Password, confirm password,

Email, Mobile no.
Functional Cases(Mozilla Firefox) Test

Name (A-z, a-z, spaces, Max length =30)

Valid
Classes Password (A-Z,a-z,special
 character,1234567890, Max length=20)
Confirm Password (A-Z,a-z,special
character,1234567890, Max length=20)

Email Id(special caharetr, alphabets and numeric

values, max character=100)

Mobile no(0-10, max length=10)

Name (0-10, (! @~#$%^&*()_+|}{[]\”:’;?><,./~))

Email(space and invalid email id)

Password(Spaces)
Invalid Mobile number(Alphabet and special character)
Classes

Test Case Id Description Expected Result Actual Result Rem

Arks

fields blank Display in the Error Please fill out the fields: Name,
 Message Right of the password, confirm password,
TC-ED-01 and Press control. email id and mobile number. Pass
Submit Button

TC-ED-02 Leave all Nothing should Nothing Will Happen. Pass

fields blank happen.
and Press
Reset Button

Error message displayes enter

TC-ED-03 valid email Id Pass
Enter invalid Should give error
email Id message

TC-ED-04 Enter Numeric It should Accept Numeric is Accepted. Pass

(1234) in the Numeric fields in
Name Field. Name Field.

TC-ED-05 Enter Special Special Characters Special Characters are not Pass
Characters (! should Accepted Accepted in Name Field.
@#$%^&*()_- Name Field.
<,>.?/~`) in
Name Field

TC-ED-06 Enter Alphabets Should Alphabets are Accepted in Pass

Alphabets (A- Accept in Name Name Field.
Z, a-z) in Field
Name Field.

TC-ED-07 Enter Spaces Spaces should Spaces are not Accepted in Pass
in Name Accept in Name Name Field.
Field. Field.

TC-ED-08 Leave the Error Message should Error Message “Enter First Pass
 Name Field displayed Name”
Blank and
Click On
submit Button

TC-ED-09 Enter Max length Must Give. Max length is given. Pass
Maximum It should not Accept
Alphabets in Infinite Characters in
The Name Name Field
Field.

TC-ED-10 Enter Numeric It should Accept Numeric is Accepted. Pass

(1234) in
password field the Numeric fields in
Password Field.

TC-ED-11 Enter Special Special Characters Special Characters are Pass

Characters (! should Accepted Accepted in password Field.
@#$%^&*()_- In password Field.
<,>.?/~`) in
password
Field.

TC-ED-12 Enter Alphabets Should Alphabets are Accepted in Pass

Alphabets (A- Accept in password Password Field.
Z, a-z) in
password field Field.

TC-ED-13 Enter Spaces Spaces should not Spaces are not Accepted in Pass
in password
field Accept in passwsord Password Field.
Field.

TC-ED-14 Leave the Error Message should Error Message displays in the Pass
password Field. display in the Error Message Summary ”Enter
 Blank and Message Summary The password”
Click On
submit Button

Enter max
length in
TC-ED-15 password Max length Must Give. Max length is given. Pass

TC-ED-16 Leave the Error Message should Error Message displays in the Pass
Email Field display in the Error Message Summary ” Enter
Blank and Message Summary Email”
Click On
submit Button

TC-ED-17 Enter Special Message should Message Displays in Email Pass

Characters (! Display in Email Field.
#$%^&*()_- Field.
<,>.?/~`)
In Email Field.

TC-ED-18 Enter Spaces Spaces should not Spaces are not Accepted in Pass
in Email Field. Accept in Email Field. Email Field.

TC-ED-19 Enter It should not Accept Alphabet is not Accepted in Pass

Alphabets in the alphabets in fields
mobile number in mobile number filed Mobile number field.

TC-ED-20 Enter Special Special Characters Special Characters are not Pass
 Accepted in Mobile number
Characters (! should not Accepted field
@#$%^&*()_- in Mobile number field
<,>.?~`)in
Mobile number
field

Enter another Should not accept other

value in value than password
confirm entered in tha previous Message displayed password
TC-ED-21 password field. did not matched. Pass

TC-ED-22 Enter Spaces Spaces should not Spaces are not Accepted in Pass
in mobile Accept in mobile
number number Mobile number

TC-ED-23 Enter It should Accept the Numeric is Accepted Contact Pass

Numeric(1234 Numeric fields in Number Field
) in Contact Contact Number Field
Number Field

TC-ED-24 Enter Special Special Characters Special Characters are not Pass
Characters (! should not Accepted Accepted in Contact Number
@#$%^&*()_- in Contact Number Field.
<,>.?~`) in Field.
Contact
Number Field

Reset button Should clear all fields. Cleared all fields

 after entering
the fields.
TC-ED-25

Press reset
without entering
values in filed. Should do nothing. Nothing happend
TC-ED-26

TEST CASES FOR USER CHANGE PASSWORD:

Test Suite: User Change Password

Form Date of Creation:20-04-2018
Created By: Implemented On: 20-04-2018
Shravan
Weblogic or Tom Cat server, MySql, Login Form, Google chrome,JDK
Pre-Requisites: 8,
Mozilla Firefox
5.0
Required Field Validator: (User Name, old
password, new password, confirm new
Validation: password)
Valid Classes Valid EmailId( Max length =100)
Old password(max length 20,A-Z,a-z,numbers and special characters)
new password(max length 20,A-Z,a-
z,numbers and special characters)
confirm new password(max length 20,A-Z,a-
 z,numbers and special characters)
Emailid (Spaces)
Old password(wrong entry of old password, spaces)
New password(spaces)
Invalid Classes Confirm new password(spaces)

User Interface Change password

User Id and As per the login person or as generated by in the database
Password
Test Case Id Description Expected Result Actual Result Rem
Arks

TC-ULG-01 Leave Email It should display Error message Pass

empty and error message in displayed
click on Submit button.
“Enter Email ID”
Email required

TC-ULG-03 It accept Pass

Alphabets and
It numbers with special
Enter proper email should accept character but in
format. proper email id proper format.
. values.

TC-ULG-04 Enter spaces in the It should not It does not allows Pass
Email Id field. allow spaces. spaces to be entered
in the Email ID field.
TC-ULG-05 Enter special characters It should It accepts Pass
in Email Id field such accept special special characters in
as!@#$ %^&*()_+=- characters in Email ID.
{}|:”?><,\ / Email Id field.

TC-ULG-06 Check for maximum It should not It does not exceed Pass
length of characters for accept infinite the maximum length.
the Email ID field. characters in
Email ID field.

TC-ULG-07 Enter wrong old It should not Display alert message Pass
password accept wrong current password did not
input of current matched.

password

TC-ULG-08 Enter special Shoul accept all Accept all the special Pass
characters in the special character
password field character
Such as ! @ # $
5 ^ & * ()<> ? / \
TC-ULG-09 Enter spaces in Should not New password field does Pass
password field accept spaces in not accept spaces
new password
field

TC-ULG-10 Enter diiferent Should not Give alert message Pass

value from new accept the password does not matched
password in different value.
confirm
password field.

TC-ULG-11 Click submit Should give alert Display alert to fill the Pass
button without about the field. empty fields.
filling the fields
TC-ULG-12 Click reset Should clear Clear all the fields. Pass
button after
all.
filling the fields

TC-ULG-13 Click reset Do nothing. Do not have any effect. Pass

button without
filling the fields.

TEST CASES FOR USER CHECKOUT:

Test Suite: User checkout Form Date of Creation:20-04-2018

Created By: Implemented On: 20-04-2018
Shravan
Weblogic or Tom Cat server, MySql, Login Form, Google chrome,JDK
Pre-Requisites: 8,
Mozilla Firefox 5.0
Required Field Validator: (User Name,
permanent address, shipping address, current
Validation: city,land mark, area code, state)
Valid Classes Valid EmailId( Max length =100)
Permanent address(max length 200,A-Z,a-z,numbers and special characters)
shipingaddress(max length 200,A-Z,a-
 z,numbers and special characters)
current city(max length 100,A-Z,a-z,numbers
and special characters)
state(max length=100,A-Z,a-
z,numbers,special character)
pincode(number max length=10)
land mark(alphabet, special character and
numbers, max length=100)
Emailid (Spaces)
Permanent address(do not exceed max caharacter)
Current city(do not exceed max character)
Invalid Classes Area code(A-Z,a-z,special character)

User Interface Check out

User Id and As per the login person or as generated by in the database
Password
Test Case Id Description Expected Result Actual Result Rem
Arks

TC-ULG-01 Leave Email It should display Error message Pass

empty and error message in displayed
click on Submit button.
“Enter Email ID”
Email required

TC-ULG-03 Enter proper email It It accept Pass

format. should accept Alphabets and
. proper email id numbers with special
 values. character but in
proper format.

TC-ULG-04 Enter spaces in the It should not It does not allows Pass
Email Id field. allow spaces. spaces to be entered
in the Email ID field.
TC-ULG-05 Enter special characters It should It accepts Pass
in Email Id field such accept special special characters in
as!@#$ %^&*()_+=- characters in Email ID.
{}|:”?><,\ / Email Id field.

TC-ULG-06 Check for maximum It should not It does not exceed Pass
length of characters for accept infinite the maximum length.
the Email ID field. characters in
Email ID field.

TC-ULG-07 Enter special characters It should accept Accept all the Pass
in permanent address special characters special characters in
As !@#$%^&*()+=- in permanent permanent adress
{}[]:;”><,/ address.
Accept spaces in

TC-ULG-08 Enter spaces in It should accept permanent adress Pass

permanent adress spaces in
permanent
address.

TC-ULG-09 Leave empty permanent It should display Display error Pass

 address error message message permanent
permanent address required.
address required.
TC-ULG-10 Enter special characters It should accept Accept all the
in shipping address special characters special characters in Pass
As !@#$%^&*()+=- in shipping shipping adress
{}[]:;”><,/ address.

Enter spaces in shipping It should accept

TC-ULG-11 address. spaces in shipping Accepts space in Pass

address. shipping address
Leave empty shipping It should display Display error

TC-ULG-12 address error message message shipping Pass

shipping address address required
required
Enter special characters It should accept Accept all the

TC-ULG-13 in city special characters special characters in Pass

As !@#$%^&*()+=- in city city
{}[]:;”><,/

TC-ULG-14 Enter spaces in city. It should accept Accepts space in city

spaces in city Pass
TC-ULG-15 Leave empty city It should display Display error
error message city message city Pass
Is empty required
TC-ULG-16 Enter special characters It should accept Accept all the Pass
in land mark As special characters special characters in
!@#$%^&*()+=- in landmark land mark
{}[]:;”><,/
TC-ULG-17 Enter spaces in landmark It should accept Accepts space in Pass
spaces in land land mark
 mark
TC-ULG-18 Leave empty land mark It should display Display error
error message message land mark Pass
land mark is required
empty

TC-ULG-18 Enter (1234567890) in should

landmark Accept alpha Accept alpha- Pass
numeric value in numeric values in
land mark land mark.
TC-ULG-19 Enter (1234567890) in should
area code Only accept Accept numbers in Pass
numeric value area code.
TC-ULG-20
Enter special characters Should not accept Give error message Pass
in Area code As special characters that special character
!@#$%^&*()+=- in area code not allowed.
{}[]:;”><,/
TC-ULG-21 Enter spaces in Area
code Should not accept Not accepted spaces Pass
spaces in area in area code
code
TC-ULG-22 Leave empty Area code
Give error message Pass
Should give error area code is empty
message not be
empty Area code
TC-ULG-23
Enter special characters Should be Accept special Pass
in State accepted characters in state
TC-ULG-24 Enter spaces in State
Should accept Accept spaces in Pass
spaces in state state

TC-ULG-25 Leave empty State

Shoul give error Give error message Pass
empty state. state is empty
TC-ULG-26
Leave empty all fields in Should give error Give error fields are Pass
checkout and click fields are empty empty
submit
TC-ULG-27
Click reset after filling Should clear all Clear all the fileds Pass
the fields fields
TC-ULG-28
Click reset during empty Should do Do not change Pass
fields. nothing. anything

TC-ULG-29 Enter maximum Pass

characters in permanent Max length must Max length is given
address give. It should not in the permanent
accept infinite address
characters in
permanent
address.
TC-ULG-30 Enter maximum Max length must Max length is given Pass
characters in shipping give. It should not in the shipping
address accept infinite address
 characters in
shipping address.
TC-ULG-31 Enter maximum Max length must Pass
characters in city give. It should not Max length is given
accept infinite in the city
characters in city.
TC-ULG-32 Enter maximum Max length must Max length is given Pass
characters in land mark give. It should not in the land mark
accept infinite
characters in land
mark
TC-ULG-33 Enter maximum Max length must Max length is given Pass
characters in area code give. It should not in the area code
accept infinite
characters in area
code
TC-ULG-34 Enter maximum Max length must Max length is given Pass
characters in state give. It should not in the state
accept infinite
characters in state
 IMPLEMENTATION AND MAINTENANCE

In system development life cycle, Implementation is the fourth phase. Implementation proceeds
just after the system development phase come into existence. Implementation refers to the final
process of moving the solution from development status to production status. Depending on your
project, this process is often called deployment, go-live, rollout or installation. The
implementation phase deals with issues of quality, performance, baselines, libraries, and
debugging. The end deliverable is the product itself. During the Implementation Phase, the
automated system/application is moved from development status to production status. The
process of implementation is dependent on the characteristics of the project and the IT solution,
and thus may be synonymous with installation, deployment, rollout, or go-live. If necessary, data
conversion, phased implementation, and training for using, operating, and maintaining the
system are accomplished during the Implementation Phase. From a system security perspective,
the final system must be certified and accredited for use in the production environment during
the Implementation Phase. The Implementation Phase ends with a formal decision to release the
final project into the Operations and Maintenance Phase.
DIRECT CONVERSION:
The old system is stopped and the new system replaces it immediately. It is a quick transition,
which may not be possible if the changes are large.
PHASE CONVERSION:
In this phase, only parts of a new application or only a few forms at a time are converted. A
phased conversion allows a gradual implementation process to take place within an organization.
PILOT CONVERSION:
In this type of conversion only one department or other work site serves as a test site. A new
system can be tried out at this site until developers feel it can be implemented throughout the
organization.
PARALLEL CONVERSION:
In this phase, both the old and the new system are operated until the project development team
and end user management agrees to switch completely over to the new system.
POST IMPLEMENTATION:
INTERNALIZATION:
Internalization means globalization. It is aimed at developers and team leaders wanting to create
applications which run in more than one language and region.

MULTILINGUAL
Multilingual means that the application supports the different languages. It is localization so it
can be helpful to various candidates who do not understand the English language.

MAINTENANCE:
The maintenance phase involves making changes to hardware, software, and documentation to
support its operational effectiveness. It includes making changes to improve a system's
performance, correct problems, enhance security, or address user requirements. Maintenance
includes all the activity after the installation of software that is performed to keep the system
operational. As we have mentioned earlier, software often has design faults. Once when the
customers starts using the developed system then the actual problems comes up and needs to be
solved from time to time. This process where the care is taken for the developed product is
known as maintenance.

MAINTENANCE IS OF THESE TYPES:

CORRECTIVE MAINTENANCE:
Corrective maintenance is a maintenance task or operation done in order to identify, isolate or
separate and rectify a particular fault. This is performed in order to restore the failed machine,
equipment or system to an operational condition. Corrective maintenance can be either planned
or unplanned.
Corrective maintenance performed due to a breakdown could be either planned or unplanned.It
improves equipment and its components so that preventive maintenance can be carried out
reliably. Equipment with design weakness must be redesigned to improve reliability or
improving maintainability.
Corrective maintenance refers to changes made to repair defects in the design, coding, or
implementation of the system. Most corrective maintenance problems surface soon after
installation.
When corrective maintenance problems surface, they are typically urgent and need to be resolved
to continue normal business activities.
Corrective maintenance adds little or no value to an organization; it simply focuses on removing
defects from an existing system without adding new functionality.

ADAPTIVE MAINTENANCE
Adaptive maintenance involves making changes to an information system to evolve its
functionality to changing business needs or to migrate to a different operating environment.
Adaptive maintenance adds enhancements to an operational system, such as new features,
increased capability, or changes that improve efficiency or maintainability. An adaptive
maintenance project is like a mini-SDLC project, and that adaptive maintenance can be even
more difficult than new systems development because the enhancements must work within the
constraints of an existing system.
Adaptive maintenance is usually less urgent than corrective maintenance because business and
technical changes typically occur over some period of time. Adaptive maintenance is generally a
small part of an organization’s maintenance effort, but does add Value to the organization.
Adaptive maintenance includes changes to the functionality of the system developed for specific
customer needs. Adaptive maintenance also implies the need for modifications of certain
functionalities, although the system works as expected and in this sense that there is no fault or
error in the system.

PERFECTIVE MAINTENANCE
Perfective maintenance involves making enhancements to improve processing performance,
interface usability, or to add desired, but not necessarily required, system features.
The objective of perfective maintenance is to improve response time, system efficiency,
reliability, or maintainability. During system operation, changes in user activity or data pattern
can cause a decline in efficiency, and perfective maintenance might be needed to restore
performance. Usually, the perfective maintenance work is initiated by the IT department, while
the corrective and adaptive maintenance work is normally requested by users.

PREVENTIVE MAINTENANCE
It is a daily maintenance, design to retain the healthy condition of system and prevent failure
through the prevention of deterioration, periodic inspection or equipment condition diagnosis, to
measure deterioration. It is further divided into periodic maintenance and predictive
maintenance. Just like human life is extended by preventive medicine, the equipment service life
can be prolonged by doing preventive maintenance.
Preventive maintenance involves changes made to a system to reduce the chance of future
system failure. An example of preventive maintenance might be to increase the number of
records that a system can process far beyond what is currently needed or to generalize how a
system sends report information to a printer so that so that the system can adapt to changes in
printer technology.
Preventive maintenance is less likely to occur as compared to corrective maintenance.

PROJECT LEGACY
CURRENT STATUS OF THE PROJECT
 This website is developed in 3-tier architecture so it is very flexible and very secure.
 Security is provided by roles.
 No direct queries are used only stored procedures are used in data base so it very fast.
 Environment is user friendly so any one can use it easily it is easy to understand.
 Every user gets his/her password by email so it provides security to the users.
 If any user can forget his password he can easily recover it.
 All menus are dynamic so it is easy to add/remove a new link.
 Master tables are used for future use.
 Users can easily view their profile.
FUTURE ENHANCEMENTS
 The system can be used as online shopping portal in ral life. Any one who wants to sale
their items online or wants to build online store, he/she can use this application for their
use.
 Uses of new controls of jsp into this website and fully responsive website.

TECHNICAL AND MANAGERIAL SKILLS LEARNT

We have learnt about Servlet, JSP, HTML, Bootstrap, MySql, and Java Scripts.
 In MySQL we have learned about stored procedures, Query Handling and some more
features of it.
 In JSP we have learned about various controls, validating data, stored data in the database
with the help of XML etc.
 In managerial skills we have learned about team work, Group Effort and coordination in
group and the way to work on the Live Projects.
 SNAPSHOT

HOME PAGE:
Description: This interface will show all the menus or operations that can be view and access
by users.
LOGIN

Description: This Interface will take the username and password and according to their roles
they will enter their user section.
CHANGE PASSWORD:

Description: By this interface, users can reset their password.

SIGN UP:

Description: This is a registration form for a user where they can fill the required
information and create an account on shopcool website. In this case they have to
fill simple details like- User Name, Valid Email Id, phone number, and have to
create password.
FORGET PASSWORD:

Description:

In this, If user have forgot the password then user can request his/her password in
their respective email by which user had registered. We have to enter his/her
respective email id in the field and submit. User can check the password in the
respective email inbox.
VIEW PRODUCTS:
ADD TO CART:

Description: user can add items to the cart by simply selecting items and have to
click add to cart. By signing in user can process further.
PROCESS TO CHECK

Description: User can process to check by simply click on process to check. Then
above shown page will be open. Here have to fill information about his Email Id,
Permanent Address, Shipping Address, Current city, Land Mark, Area Code, and
State. If incase entered wrong value then user can reset it by click on reset button.
PROCESS CHECKOUT:

Description: Here user can check the details about shipping and processed to place
order by pay now or cash on delivery.
ORDER DETAILS:

Description: Here user can get order details along with delivery address. And also
have option to continue shopping or finish shopping.
11. FINISH SHOPING
 FUTURE SCOPE

 This model can be enhanced and applied to similar product categories of special
operations like Groceries etc. and other B2C Ecommerce websites.
 A Web based application needs provision to support scalability to cater to growth. The
Architecture should support the constant continuous growth of operation.
 Dynamic and periodic updations of data information flow, operations of data information
flows, operation required.
 Security features, fraudulent transactions to be properly taken care off. Misuse of any
kind should be averted and system should have built in feature for prevention of such
things and protection.
 Faster processing of information as compared to the current system with high accuracy
and reliability.
 Automatic and error free report generation as per the specified format.
 Automatic calculation and generation of correct and precise Bills-thus reducing much of
the workload on the accounting staff and the errors arising due to manual calculations.
 Better vigilance of the Salesmen and tracking of carats is now possible.
 Better sales management is foreseen with the a few enhancements in this application.
A future application of this system lies in the fact that the proposed system would remain
relevant in the future. In case there be any additions or deletion of the products, addition or
deletion of any salesman in the any type of modification in future can be implemented easily.
 CONCLUSION

The “SHOP COOL” is a web-based application for online-shopping who provide customized
solutions .The software is developed using Java as front end and MySQL Server as back end.
The goals that are achieved by the software are:

 Instant access.
 Improved productivity.
 Optimum utilization of resources.
 Efficient management of records.

As evidence of the success of this mission, there are millions of items listed each day in
thousands of different categories. There are items for almost any interest that one could imagine,
from sheet music to automobiles to hand tools to real estate. And the variety doesn’t stop there.
Need a computer? One may find it listed in the proper category, in any configuration from very
old and obsolete to the latest greatest machine available. What about antiques? One can find an
antique quilt that is up for highest bid, or maybe an old violin, whose beautiful tones have
enchanted many though its years.

In this instance it may be true that on eBay, they have something for everybody, whatever their
tastes may be.
 BIBLIOGRAPHY

Core Java™ 2 Volume I – Fundamentals 7th Edition - Cay S. Hortsman

Core Java™ 2 Volume II – Advanced - Cay S. Hortsman

Head First Servlets & JSP - Eric Freeman

Java Database Best Practices - George Reese