TITLE OF THE TECHNICAL SEMINAR

Technical Seminar Report submitted to

Jawaharlal Nehru Technological University Hyderabad
in partial fulfillment for the award of degree of

Bachelor of Technology
in
Electronics and Communication Engineering
by

NAME OF THE STUDENT

Roll No:XXXXXXXXXX

Under the Guidance of

Mr. Name of the guide with designation

DEPARTMENT OF ELECTRONICS AND COMMUNICATION ENGINEERING

SRI INDU INSTITUTE OF ENGINEERING &TECHNOLOGY

(Affiliated to JNTUH, Hyderabad, Approved by AICTE, New Delhi)
Sheriguda (V), Ibrahimpatnam (M), R.R.Dist., Telangana- 501510.

2015-2016
 SRI INDU INSTITUTE OF ENGINEERING &TECHNOLOGY
(Affiliated to JNTUH, Hyderabad, Approved by AICTE, New Delhi)
Sheriguda (V), Ibrahimpatnam (M), R.R.Dist., Telangana- 501510.

DECLARATION

I,NAME OF THE STUDENT bearing Roll No XXXXXXXXXX, hereby declared that the

dissertation entitled “TITLE OF THE PROJECT /TOPIC”, carried out under the guidance of Mr.

name of the internal guide, Designation is submitted to Jawaharlal Nehru Technological

University Hyderabad in partial fulfillment of the requirements for the award of the degree of

Bachelor of Technology in Electronics and Communication Engineering. This is a record of

bonafide work carried out by me and the results embodied in this dissertation have not been

reproduced or copied from any source. The results embodied in this dissertation have not been

submitted to any other University or Institute for the award of any other degree.

Date: NAME OF THE STUDENT

Roll No: XXXXXXXXXX

 SRI INDU INSTITUTE OF ENGINEERING &TECHNOLOGY
(Affiliated to JNTUH, Hyderabad, Approved by AICTE, New Delhi)
Sheriguda (V), Ibrahimpatnam (M), R.R.Dist., Telangana- 501510.

DEPARTMENT OF ELECTRONICS AND COMMUNICATION ENGINEERING

This is to certify that the dissertation entitled “TITLE OF THE PROJECT /TOPIC”, being

submitted by NAME OF THE STUDENT, bearing Roll No: XXXXXXXXXX, to Jawaharlal

Nehru Technological University Hyderabad in partial fulfillment of the requirements for the

award of the degree of Bachelor of Technology in Electronics and Communication Engineering, is

a record of bonafide work carried out by him. The results of investigations enclosed in this report

have been verified and found satisfactory. The results embodied in this dissertation have not been

submitted to any other University or Institute for the award of any other degree or diploma.

INTERNAL GUIDE HEAD OF THE DEPARTMENT

PRINCIPAL
 ACKNOWLEDGEMENT

With great pleasure I take this opportunity to express my heartfelt gratitude to all the persons
who helped me in making this project work a success.

First of all I am highly indebted to Principal, Dr. I. SATYANARAYANA for giving me the
permission to carry out this project.

I would like to thank Mr. SURESH BALLALA, Professor & Head of the Department
(ECE), for giving support throughout the period of my study in SIIET. I am grateful for his valuable
suggestions and guidance during the execution of this project work.

My sincere thanks to project guide Mr. XXXXXXXXX, DESIGNATION for potentially

explaining the entire system and clarifying the queries at every stage of the project.

My whole hearted thanks to the staff of Electronics and Communication Engineering who
co-operated us for the completion of project in time.

Last but not the least, I express my sincere thanks to Mr. R. VENKAT RAO, Secretary, Sri
Indu Group of Institutions, for his continuous encouragement.

I also thank my parents and friends who aided me in completion of the project.

NAME OF THE STUDENT

ROLL NO.XXXXXXXXXX

i
ABSTRACT

ii
 CONTENTS
Page No
Acknowledgement i
Abstract ii
Table of contents iii
List of Figures vi
List of Screens vii

1. INTRODUCTION
1.1 Motivation 2
1.2 Problem definition 2
1.3 Objective of Project 2
1.4 Limitations of project 3
1.5 Organization of project 3

2. LITERATURE SURVEY
2.1 Introduction 5
2.2 Existing System 5
2.2.1 Drawbacks in existing system 5
2.3 Proposed System 6
2.4 Feasibility study 6
2.5 Features of the project 7
2.6 Conclusion 8

3. ANALYSIS
3.1 Introduction 10
3.2 Requirement Specification 10
3.2.1 User requirements 10
3.2.1.1 Functional requirements 11
3.2.1.2 Non-functional requirements 11
3.2.2 Software and Hardware Requirements 12
3.3 Context Diagrams 13
3.4 Conclusion 17

iii
4. DESIGN
4.1 Introduction 19
4.2 UML diagrams 19
4.2.1 Use case Diagrams 19
4.2.2 Class Diagram 23
4.2.3 Sequence Diagram 24
4.2.4 Collaboration Diagram 27
4.2.5 State Chart Diagram 30
4.2.6 Activity Diagrams 31
4.2.7 Component Diagram 32
4.3 Module design and organization 32
4.4 Conclusion 33

5. IMPLEMENTATION
5.1 Introduction 35
5.2 Key functions 35
5.3 Method of Implementation 36
5.3.1 Forms/Tables 37
5.3.2 Output Screens 42
5.3.3 Result Analysis 47
5.4 Conclusion 47

6. TESTING, VALIDATION AND RESULTS

6.1 Introduction 49
6.2 Testing Methodologies 50
6.3 Design of test cases and scenarios 53
6.4 Validation 54
6.5 Result analysis 54
6.6 Conclusion 54

7. CONCLUSION
7.1 Conclusion 57
7.2 Future Enhancement 57
iv
APPENDIX
A. Symbols & Acronyms 59

BIBLIOGRAPHY 61

v
 LIST OF FIGURES

Following are the list of figures used in this project documentation at various locations.
 vi
SAMPLE DOCUMENTATION(IEEE format)
Enclosed in the following pages
Introduction
Online analytical processing (OLAP)
and Data mining represents some of the latest
trends in computing environment and I.T
applications to large scale processing and
analysis of data
Data Warehouse along with OLAP
tools are being increasingly developed to
analyze historical data to identify past patterns
or trends which may be useful in forecasting
future.
What is Data warehousing?
A data warehouse is an integrated store
of information collected from other systems
that becomes the foundation for decision
support and data analysis. Although there are
many types of data warehouses, based on
different design methodologies and
philosophical approaches, they all have these
common traits:
 Information is organized around the
major subjects of the enterprise (for
example, customers, products, sales, or
vendors), reflecting a data-driven
design. Raw data is gathered from
nonintegrated operational and legacy
applications, cleansed, and then
summarized and presented in a way
that makes sense to end users.
 Based on feedback from end users and
discoveries in the data warehouse, the
data warehouse architecture will
change over time, reflecting the
iterative nature of the process.
 The data warehousing process is
inherently complex and, as a result, is
costly and time-consuming.
Why to build a data warehouse?
Business strategy requires answers to
questions in business and future strategy. This
means that the decisions are to be taken quickly
and correctly using all the available data. As
the data size increases continuosly and data is
required to be processsed faster and faster the
need for data warehousing technology arises in
terms of ability to organise, maintain large data
and also be able to analyse in few seconds in
the manner and depth required.There are
conventional information systems which didn’t
succeed in meeting these requirements.
Conventional and data warehousing tackle two
different activity domains-OLTP & OLAP.
Besides this conventional information
system is not capable of analyzing a large
number of past transactions or large number of
data records.
The cost of processing the data also
increases as the volume of data increases .As a
result the analyst finds data mart extremely
useful for fast and easy analysis. Since the
data flows into data mart (from the Data
Warehouse), the department which owns it can
easily customize the data.
Data marts are of 2 types:
1. Multi dimensional OLAP (MOLAP)
2. Relational OLAP (ROLAP)
Data Warehousing Framework
The goal of the Data Warehousing
Framework is to simplify the design,
implementation, and management of data
warehousing solutions. This framework has
been designed to provide:
 Open architecture that is easily
integrated with and extended by third-
party vendors.
 Heterogeneous data import, export,
validation, and cleansing services with
optional data lineage.
 Integrated metadata for data
warehouse design, data
extraction/transformation, server
management, and end-user analysis
tools.
 Core management services for
scheduling, storage management,
performance monitoring, alerts/events,
and notification.
  Methods of loading and transforming
data from operational systems to the
data warehouse.

Data Warehousing Framework

Components

Building the data warehouse requires

a set of components for describing the logical
and physical design of the data sources and
their destinations in the enterprise data
warehouse or data mart.
Determining Business, User, and Technical To conform to definitions laid out
Requirements during the design stage, operational data must
Before a data warehouse can be built, a pass through a cleansing and transformation
detailed project and implementation plan stage before being placed in the enterprise
should be written. The project and data warehouse or data mart. This data staging
implementation plan includes: process can be many levels deep, especially
with enterprise data warehousing
 Building a business case.
 Gathering user requirements.
Architectures, but is necessarily simplified in
 Determining the technical this illustration.
requirements.
 Defining standard reports required by
users. End-user tools, including desktop
 Analyzing client application tools productivity products, specialized analysis
being used. products, and custom programs, are used to
gain access to information in the data
Building the business case involves warehouse. Ideally, user access is through a
determining the business needs solved by the directory facility that enables end-user searches
project, the costs of the project, and the return for appropriate and relevant data to resolve
on the investment. questions and that provides a layer of security
The user requirements determine: between the end users and the data warehouse
 Data requirements (level of systems.
granularity). Finally, a variety of components can
 Operational systems within the come into play for the management of the data
enterprise containing the data. warehousing environment, such as for
 Business rules followed by the data. scheduling repeated tasks and managing
 Queries required providing the users multiserver networks.
with data. OLE DB provides for standardized,
high-performance access to a wide variety of
The technical requirements may involve data, and allows for integration of multiple data
determining: types.
 Hardware architecture and Microsoft Repository provides an
infrastructure. integrated metadata repository that is shared by
 Backup and recovery mechanisms. the various components used in the data
 Security guidelines. warehousing process. Shared metadata allows
for the transparent integration of multiple
products from a variety of vendors, without the
need for specialized interfaces between each of
the products:
 Mainframe indexed sequential access
method/virtual storage access method
(ISAM/VSAM) and hierarchical
databases
 E-mail and file system stores
 Text, graphical, and geographical data
 Custom business objects
Data Warehousing Architecture
Many methodologies have been
proposed to simplify the information technology
efforts required to support the data warehousing
process on an ongoing basis. This has led to
debates about the best architecture for delivering
data warehouses in organizations.
Two basic types of data warehouse
architecture exist: enterprise data warehouses and
data marts.
The enterprise data warehouse contains
enterprise-wide information integrated from
multiple operational data sources for
consolidated data analysis. Typically, it is
composed of several subject areas, such as
customers, products, and sales, and is used for
both tactical and strategic decision making. The
enterprise data warehouse contains both detailed
point-in-time data and summarized information,
and can range in size from 50 gigabytes (GB) to
more than 1 terabyte. Enterprise data warehouses
can be very expensive and time-consuming to
build and manage. They are usually created from
the top down by centralized information services
organizations.
Enterprise data warehouses and data
marts are constructed and maintained through the
same iterative process described earlier.
Furthermore, both approaches share a similar set
of technological components.
Data Marts
A data mart is typically defined as a
subset of the contents of a data warehouse,
stored within its own database. A data mart
tends to contain data focused at the department
level, or on a specific business area. The data
can exist at both the detail and summary levels.
The data mart can be populated with data taken
directly from operational sources, similar to a
data warehouse, or data taken from the data
warehouse itself. Because the volume of data in
a data mart is less than that in a data warehouse,
query processing is often faster.
Characteristics of a data mart include
 Quicker and simpler implementation.
 Lower implementation cost.
 Needs of a specific business unit or
function met.
 Protection of sensitive information
stored elsewhere in the data
warehouse.
 Faster response times due to lower
volumes of data.
 Distribution of data marts to user
organizations.
 Built from the bottom upward.
Building a Data Warehouse from Data
Marts
Data warehouses can be built using a
top-down or bottom-up approach. Top-down
describes the process of building a data
warehouse for the entire organization,
containing data from multiple, heterogeneous,
operational sources. The bottom-up approach
describes the process of building data marts for
departments, or specific business areas, and then
joining them to provide the data for the entire
organization. Building a data warehouse from
the bottom-up, by implementing data marts, is
often simpler because it is less ambitious.

A common approach to using data
marts and data a warehouse involves storing all
detail data within the data warehouse, and
summarized versions within data marts. Each
data mart contains summarized data per
functional split within the business, such as
sales region or product group, further reducing
the data volume per data mart.
Data Mart Considerations
Data marts can be useful additions or
alternatives to the data warehouse, but issues to
consider before implementation include:
 Additional hardware and software.
 Time required populating each data
mart regularly.
 Consistency with other data marts and
the data warehouse.
 Network access (if each data mart is
located in a different geographical
region).
OLAP:
Online Analytical Processing (OLAP)
systems, contrary to regular conventional OLTP
systems are capable of analyzing online a large
number of transactions or large number of data
records (ranging from mega bytes to tera
bytes).This type of data is usually multi
dimensionality is the key driven for OLAP
technology, which happens to be central to data
warehousing.
Any multidimensional data can’t be
processed by conventional SQL type DBMS.
For complex real world problems the data is
usually multi dimensional in nature.
SQL will not be capable of handling it
effectively even one can manage to put that data
in a conventional relational database in
normalized table
Integrated OLAP Analytical
Capabilities
OLAP is an increasingly popular
technology that can dramatically improve
business analysis. Historically, OLAP has been
characterized by expensive tools, difficult
implementation, and inflexible deployment.
OLAP Services is a new, fully featured OLAP
capability provided as a component of SQL
Server 7.0. OLAP Services includes a middle-
tier server that allows users to perform
sophisticated analysis on large volumes of data
with exceptional results. OLAP Services also
includes a client-side cache and calculation
engine called Microsoft PivotTable Service,
which helps improve performance and reduce
network traffic. PivotTable Service allows end
users to conduct analyses while disconnected
from the network.
OLAP Services is a middle-tier OLAP
server that simplifies user navigation and helps
improve performance for queries against
information in the data warehouse.
OLAP is a key component of data
warehousing, and OLAP Services provides
essential functionality for a wide array of
applications ranging from reporting to advanced
decision support. OLAP functionality within
SQL Server 7.0 helps make multidimensional
analysis much more affordable and bring the
benefits of OLAP to a wider audience, from
smaller organizations to groups and individuals
within larger corporations. Coupled with the
wide variety of tools and applications
supporting OLAP applications through
Microsoft OLE DB for OLAP, OLAP Services
helps increase the number of organizations that
have access to sophisticated analytical tools and
can help reduce the costs of data warehousing.
For more information about Microsoft
SQL Server OLAP Services, see SQL Server
Books Online.
Data Warehousing and OLAP
DTS can function independent of SQL
Server and can be used as a stand-alone tool to
transfer data from Oracle to any other ODBC or
OLE DB-compliant database. Accordingly, DTS
can extract data from operational databases for
inclusion in a data warehouse or data mart for
query and analysis.
In the illustration, the transaction data
resides on an IBM DB2 transaction server. A
package is created using DTS to transfer and
clean the data from the DB2 transaction server
and to move it into the data warehouse or data
mart. In this example, the relational database
server is SQL Server 7.0, and the data
warehouse is using OLAP Services to provide
analytical capabilities. Client programs (such as
Excel) access the OLAP Services server using
the OLE DB for OLAP interface, which is
exposed through a client-side component called
Microsoft PivotTable service. Client programs
using PivotTable service can manipulate data in
the OLAP server and can even change
individual cells.
Data warehousing Components
A data warehouse always consists of a
number of components, including:
 Operational data sources.
 Design/development tools.
 Data extraction and transformation
tools.
 Database management system
(DBMS).
 Data access and analysis tools.
 System management tools.
Several years ago, Microsoft recognized
the need for a set of technologies that would
integrate these components. This led to the
creation of the Microsoft Data Warehousing
Framework, a roadmap not only for the
development of Microsoft products such as SQL
Server 7.0, but also for the technologies
necessary to integrate products from other
vendors.
Data warehousing Characteristics
A data warehouse can assist decision
support and online analytical processing
(OLAP) applications because it provides data
that is:
 Consolidated and consistent.
 Subject-oriented.
 Historical.
Consolidated and Consistent Data
A data warehouse consolidates
operational data from a variety of sources with
consistent naming conventions, measurements,
physical attributes, and semantics.
For example, in many organizations,
applications can often use similar data in
different formats: dates can be stored in Julian
or Gregorian format; true/false data can be
represented as one/zero, on/off, true/false, or
positive/negative.
Data should be stored in the data
warehouse in a single, acceptable format agreed
to by business analysts, despite variations in the
external operational sources. This allows data
from across the organization, such as legacy
data on mainframes, data in spreadsheets, or
even data from the Internet, to be consolidated
in the data warehouse, and effectively cross-
referenced, giving the analysts a better
understanding of the business.
Subject-oriented Data
Operational data sources across an
organization tend to hold a large amount of data
about a variety of business-related functions,
such as customer records, product information,
and so on. However, most of this information is
also interspersed with data that has no relevance
to business or executive reporting, and is
organized in a way that makes querying the data
awkward. The data warehouse organizes only
the key business information from operational
sources so that it is available for business
analysis.
Historical Data
Data in OLTP systems correctly
represents the current value at any moment in
time. For example, an order-entry application
always shows the current value of stock
inventory; it does not show the inventory at
some time in the past. Querying the stock
inventory a moment later may return a different
response. However, data stored in a data
warehouse is accurate as of some past point in
time because the data stored represents
historical information.
The data stored in a data warehouse
typically represents data over a long period of
time; perhaps up to ten years or more. OLTP
systems often contain only current data, because
maintaining large volumes of data used to
represent ten years of information in an OLTP
system can affect performance. In effect, the
data warehouse stores snapshots of a business’s
operational data generated over a long period of
time. It is accurate for a specific moment in time
and cannot change.
. This contrasts with an OLTP system
where data is always accurate and can be
updated when necessary
Designed Building a Data Warehouse and
OLAP System
The steps required to build a data
warehouse include:
 Determining business, user, and
technical requirements.
 Designing and building the
database.
 Extracting and loading data into
the data warehouse.
 Designing and processing
aggregations using OLAP tools.
 Querying and maintaining the data
warehouse and LAP databases.
Data Granularity
A significant difference between an
OLTP or operational system and a data
warehouse is the granularity of the data stored.
An operational system typically stores data at
the lowest level of granularity: the maximum
level of detail. However, because the data
warehouse contains data representing a long
period in time, simply storing all detail data
from an operational system can result in an
overworked system that takes too long to query.
A data warehouse typically stores data
in different levels of granularity or
summarization, depending on the data
requirements of the business. The different
levels of summarization in order of increasing
granularity are:
 useful for fast analysis rather than conventional
 Current operational data databases with OLTP.
 Historical operational data
 Aggregated data
 Metadata

Current and historical operational data are

taken, unmodified, directly from operational
systems.

Aggregated, or summary, data is a filtered

version of the current operational data.

Metadata does not contain any operational References:

data, but is used to document the way the data
warehouse is constructed. Data warehousing in Real World
--DENNIS MURRAY
--SAM ANAHORY
Process Flow Within A Data Data warehousing with Microsoft SQL Server
Warehouse --JAKE STURM
Data warehousing with Oracle
The processes are: --Sima Yazdani
1. Extract and load data. --Shirley S.Wons
2. Clean and transform data into a form
that can cope with large data volumes.
3. Back up and archive data.
4. Manage queries and direct them to
appropriate data source.

Conclusion:

So, Data Warehousing with OLAP

technology is useful for handling large amounts
of data .It is also useful for analyzing past data
for forecasting, and also for graphical analysis
and handling multidimensional data .This is