Академический Документы
Профессиональный Документы
Культура Документы
I have undertaken training at New Holland Fiat (India) Pvt. Ltd., Greater Noida
from July 2010 – Dec. 2010 and worked on Transaction and Report Modules
for the Common Business Unit (CBU) System.
As with any project, documentation forms an integral part of this
project too. Documentation plays a vital role in the Software Engineering
Process in satisfying the future queries of the user and in the efficient
maintenance of the application. Hence this report serves as a detailed
documentation for this system.
It has been taken care that this document elicits the system
development process in a lucid and an understandable manner. The
contents have been divided into segments, all of which have been explained
in detail in the following pages. I have tried my best to elucidate all the
relevant details of the project to be included in the report. While in the
beginning I have given a general view of the project, to make it clearer, in
the later stages, I have included the portion that was specifically assigned to
me and also described where that part is actually being used.
1
Prashant Tanwar
ACKNOWLEDEGMENT
Unless you venture into the real world you never know, how lame and in
fecund efforts could be without the help of the various people and, how
tough the real world environment is, and, even tougher work is enumerating
and enlisting all the individuals whose contributions went into the making of
this project. I owe a sense of gratitude to all those who helped me color the
mosaics of this project with the heights of their knowledge, precious time
and expertise.
I am grateful to New Holland Fiat (India) Pvt. Ltd. for providing me with an
opportunity to work with them and be an active team member of a project of
such value.
2
Last but not least, I would like thank my family member and my
friends who helped me by giving moral information for completing my
industrial project.
Prashant Tanwar
Chapter
Brief Overview
1.1 Training Overview
1.2 Abstract
1.3 Development Environment
3
1.1 Training Overview
4
1.2 Abstract
1.2.1 CBU System
Central Business Unit (CBU) System relates to the business criteria of the
industry. CBU system describes the economical view of the industry
products.CBU includes the system that enable financial institution
customers, individuals or businesses, transact business, or obtain
information on financial products and services through a public or private
network.
1.2.1 .1 Modules
The following modules used in the CBU System are:
• Masters
• Transactions
• Reports
• BI Reports
1.2.1.2 Services
The required features of the System are
5
• Insert Zone, CBU, Location and Dealers if required
• Sales order
• View Current status of the dealer
• Annual Operating Plan
• Customer feedback
• Event Planning
• Field Activity
• Event Activity Report
• Pay amount online through cheque
• Reporting of loss of Password
6
1.3 The Development Environment
1.3.1 Hardware
• Pentium IV 1.2 GHz
• 512 KB Cache
• 512 MB RAM
• VGA card with 512 MB built-in RAM
• 40 GB Hard Disk
• 15” SVGA Color Monitor
• 1 Parallel and 2 Serial Ports
• Ethernet card (10/100 Mbps)
1.3.2 Software
• Application Development : Microsoft Visual Studio
7
• Application server : Microsoft .Net Framework
• Web server : IIS
• Database : SQL Server 2008.
Chapter
8
Company Profile
2.1 Company Perspectives
2.2 History
2.3 About: NHI Plant
2.4 Manpower Sourcing
2.5 Services Offered
2.6 Major Milestones
2.7 Products of Company
2.8 Present Status of Organisation
9
mission--the mission of a truly global company, present around the world
through its production plants, research and development centers, industrial
and commercial joint ventures, and worldwide dealer network. New Holland
offers one of the widest, most flexible ranges of agricultural machinery and
industrial equipment. This outstanding commitment stems directly from its
worldwide industrial and design skills, and a market approach which begins
and ends with the customers.
2.2 History
New Holland N.V. is one of the world's leading manufacturers and
distributors of agricultural equipment and a major producer of construction
equipment. The company is the market leader in Europe and many parts of
Latin America and Asia and ranks third in the North American tractor market.
New Holland was formed through the 1991 merger of Fiat Geotech S.p.A.
and Ford New Holland, Inc., both of which had grown into industry giants
over nearly a century of product and sales expansion and timely
acquisitions. Fiat Geotech S.p.A. continues to hold a 69 percent ownership
interest in New Holland, having sold the other 31 percent in a 1996 initial
public offering. New Holland currently operates 18 production sites in 24
countries, as well as 13 engineering centers around the world. More than 1.5
million New Holland machines are now engaged in agricultural and industrial
work somewhere on Earth.
10
New Holland's roots can be traced back to 1895, when handyman Abe
Zimmerman made his first feed mill at his New Holland, Pennsylvania repair
shop. Zimmerman soon began making other agricultural products as well.
He called his operation the New Holland Machine Company and incorporated
it in 1903, the same year Henry Ford incorporated the automobile company
he had started up in Detroit. Ford came out with the prototype for the
world's first mass produced agricultural tractor in 1907, and ten years later
the tractor, known as the Fordson Model F, went into actual production.
Decades later, these two fledgling operations would become linked.
Meanwhile, across the Atlantic, Italian auto maker Fiat was developing a
tractor of its own. That company's efforts resulted in the development of the
702, Fiat's first mass produced tractor, which hit the market in 1919. In
Belgium, another company, Claeys, was entering the picture. Founded in
1906, Claeys began manufacturing harvesting equipment in 1910. Back in
the United States, Zimmerman's New Holland company was also thriving. It
continued to do well until about 1930, when the Great Depression began to
hit rural America hard. As farm income plummeted, so did New Holland's
revenue.
11
In 1947 New Holland Machine Company was acquired by electronics
specialist Sperry Corporation, creating a subsidiary dubbed Sperry New
Holland. In the years that followed, Sperry New Holland developed and
manufactured a large number of agricultural machines. In particular, the
company carved out a niche as a producer of high-quality harvesting
equipment. Things were also developing quickly in the European agricultural
equipment industry during this period. In 1952 Claeys unveiled the first
European self-propelled combine harvester. By the early 1960s, Claeys was
one of the biggest combine manufacturers in Europe. Sperry New Holland
bought a major interest in Claeys in 1964. The same year, Sperry New
Holland made a major breakthrough in hay harvesting technology with the
introduction of the haybine mower-conditioner, model 460. This machine
was capable of performing tasks that previously required two or three
separate pieces of equipment. New Holland would go on to revolutionize
harvesting equipment in 1974, with the introduction of the world's first twin
rotor combine.
12
consolidated all of its agricultural machinery manufacturing under the
umbrella of Fiatagri, the new name for Fiat Trattori.
In 1986 Ford purchased Sperry New Holland and merged it with its Ford
Tractor Operations to create a new company, Ford New Holland, Inc. By this
time New Holland had grown to become one of the best performing
companies in the farm equipment business, with 2,500 dealers and more
than 9,000 employees of its own, working in 100 different countries. The
merger was part of an overall consolidation taking place in the farm
equipment industry at the time, a period that saw Tenneco, the parent
company of the J.I. Case tractor and farm implement operation, take over
the farm implement business of International Harvester. With combined
annual sales of $2 billion, the new company made Ford the third largest
farm equipment manufacturer in the world. Most of Ford Tractor's executives
and managers were moved over to New Holland's Pennsylvania offices,
which became Ford New Holland's corporate headquarters. Within months of
this merger, Ford New Holland added on the agricultural division of Versatile
Farm and Equipment Co., an agricultural equipment manufacturer that had
13
been founded in Canada in 1947. The combination of Ford's tractors, New
Holland's harvesters, and Versatile's large four-wheel-drive machines
created a company that produced a wide spectrum of agricultural
equipment, and, best of all, there was almost no overlap in what the three
entities manufactured and, therefore, little pruning to be done once they
were united. One of the few major changes at New Holland was the gradual
elimination of its company-store system. Between 1987 and 1989, New
Holland's 53 company-owned outlets were sold off or closed, in favor of a
dealer development program that provided training and assistance for
independent dealers.
Back in Europe, changes were also taking place at Fiat. In 1988 the activities
of Fiat-Allis and Fiatagri were merged to form a new company, FiatGeotech
S.p.A., which now encompassed Fiat's entire farm and earthmoving
equipment sector. By the end of the 1980s, Fiat was Europe's leading
manufacturer of tractors and hay and forage equipment. FiatGeotech's
revenue for 1989 was $2.3 billion.
14
in London, instantly became the world's largest producer of tractors and
haying equipment, the second largest producer of combines, and one of the
largest producers of diesel engines.
New Holland made the completion of its integration process official at its
1994 worldwide convention, at which the company unveiled its new
corporate identity and logo. For that year, the company reported net income
of $355 million on sales of $4.7 billion. Fiat eventually acquired the other 20
percent of New Holland previously owned by Ford, and in 1995, the 100th
anniversary of the New Holland brand name, Ford New Holland was
rechristened New Holland North America.
15
2.2.4 An IPO in 1996
By 1996 New Holland was selling about 280 different products in 130
countries around the world. Globally, 5,600 dealers were selling the
company's agricultural equipment and 250 were peddling its construction
machinery. During the last quarter of that year, Fiat sold 31 percent of New
Holland's stock, 46.5 million common shares, to the public at $21.50 per
share, to raise capital to bolster its sagging core automobile business. On
November 1, the first day New Holland stock was traded on the New York
Stock Exchange, it was the most heavily traded stock on the market.
In July 1997, the 25,000th New Holland Twin Rotor combine rolled off the
company's Grand Island, Nebraska assembly line. As the year continued, the
company announced the creation of a new Boomer line of light diesel
tractors, including four brand new models. Building on its longstanding
16
philosophy of manufacturing products close to where they are sold, the
company moved production of the light tractors from Japan to a new facility
in Dublin, Georgia. The launch of the Boomer line reflected New Holland's
commitment to the production of the kind of compact but powerful machines
sought by customers for a variety of off-highway uses. The company is
determined to continue developing new products designed to meet the ever-
changing needs expressed by its dealers and customers.
17
2.3.1 Production system
NHI adopts the assembly line production system for manufacturing of all kind
of models. The assembly lines are flexible and can produce various kinds of
models at constant rate with almost zero inventories between the lines. The
plant layout is one of the best in Asia. The plant layout and coloring scheme
was proposed by FIAT Engineering, Italy.
• The NHI team in India is over 800 strong, with some of the brightest young
technicians, engineers and executives in Indian industry.
• They are striving with a spirit of dedication & teamwork to establish the
best international standards of customer satisfaction for the Indian Farmer,
infused with the Core Values & Guiding Principles of CNH Group worldwide.
• The Company prides itself for having an open and transparent work culture
aimed at providing a challenging yet conducive work environment.
1. ENGINE ASSEMBLY
2. MACHINE SHOP(CNC MACHINING)
3. PTO ASSEMBLY LINE
4. DRIVE LINE
5. TRACTOR ASSEMBLY LINE BEFORE PAINTING
6. TRACTOR ASSEMBLY LINE AFTER PAINTING
7. TOOL ROOM
8. FRONT AXLE SUB ASSEMBLY LINE
9. STORE AREA
10. FINISHING LINE
18
11. TESTING
12. MAJOR REWORK
13. OK TO SHIP LINE
14. TYRE SUB ASSEMBLY LINE
15. CED PAINT SHOP
16. TYRE YARD
To meet such requirements New Holland India has a self reliant Design
& Engineering centre, which steers the organization towards serving the
consumer better by providing global products tailored to suit Indian needs
bearing most optimum price-tag. Also to ensure that the advantage trickles
down to the consumers indirectly NHI D&E works towards supporting
production technology to find the most efficient ways of manufacturing the
19
products to achieve the highest production standards, the fastest rates of
production with the lowest cost of manufacture.
It is this capability and people resource due to which NHI has been able to
develop and launch successful products year after year. To cite an example,
“the new 42hp model which is totally designed and developed in India with
Global Engineering support has been launched in flat 22 months from the
start of the program."
DESIGN
TESTING
VALUE ENGINEERING
ENGINEERING SERVICES
DESIGN:
20
TESTING:
- Component Testing
- Vehicle Testing
VALUE ENGINEERING:
ENGINEERING SERVICES:
FUNCTIONS:
21
• Providing Engineering support to the D & E relating to Global
models.
Other than this they also do a hard closing in the month of September each
year which is a closing up to September each year. Consequently they have
three audits each year.
22
• Support IT skill enhancement for its employee.
• Support IT infrastructure installed at all locations of NHI.
• Support the processes of the company by IT.
• Identify and implement relevant IT in NHI.
Applications:
2.3.3.5 Manufacturing
Tractor assembly
23
Painting
• Body Tractor
• Sheet Metal Parts
• Assembly
• Testing
Machining
24
• Transmission Case
• Axle Casing
• Trumpets (4 types)
• Front Axle support
• Rear Cover
• Hydraulic Lift Body
• Final Drive Cover
• Master Clutch Housing 42 HP
• Front Support 42 HP
2.3.3.6 PURCHASE
New Holland’s Purchasing philosophy is to obtain for our customers goods
and services with maximum total value. The elements of total value include
more than quality and delivery. Technical innovation, assured supplies, cost
reduction initiatives are also taken care of.
STRATEGIC OBJECTIVES:
25
1. Supplier development
2. Part Approval Process (PAP/ISIR)
3. Performance evaluation
4. Management of major non conformities arising during production
5. Corrective actions follow up
6. Sales and Marketing
Service department is committed to provide high standards of after sales
service support to our esteemed customers through our dedicated dealer
network resulting into a positive word of mouth by way of product
performance, customer retention & generating strong referrals.
To NHI
To Dealers
To Customers
The New Holland plant is the most modern tractor factory in India, with a
number of advanced features. It has:
26
• CED (Cathodic Electro Deposition) painting system for the sheet
metal components – a first in the Indian tractor industry – giving
excellent finish and durability.
• Assembly lines featuring the very latest equipment for ensuring high
quality and productivity.
• New Holland has also implemented and integrated Supply Chain ERP
system (BAAN), which gives extremely flexible and controlled
material management.
All production staff and workers are technically qualified, and many of them
have been trained in New Holland plants abroad to ensure international
standards of quality and productivity.
27
objective of this programme is to prepare new recruits to take up their
responsibilities and be effective in their roles from day one.
28
share their views and opinions at open forums, which in turn are used to
shape people policies. This non-biased measure ensures that they stay
people-friendly and continue to build people centric policies within the
organization.
Initiatives like TQM, Kaizen, Quality Circles and Suggestion Schemes in their
units have enabled them to tap latent creativity among organizational
members.
29
Excellence is a way of life at New Holland India that has been manifested in
every aspect of our life. The mission to excel in every way has been
translated into designing and developing products of world-class standards,
delivering enhanced values through brand building, distribution and
customer relationship. In all this they appreciate the fact that people are
their prime resource in establishing market leadership. Therefore, they value
integrity and the long-term association they share with our people. They
believe in the continuous professional and personal development of their
people.
30
➢ CNH power components
➢ Parts and Services
For whatever task, however tough, wherever in the world, every component
in one’s equipment must be able to work with uncompromising quality,
relentless performance and rugged durability. Designed, tested and
operated in their own products, one can benefit from a dramatic reduction in
one’s development time and costs for all of the components or assemblies -
from complete power trains and drivelines to axle assemblies, gearboxes
and cabs.
31
And it doesn't stop there. Their truly global parts and service network is
never more than a phone call away when one needs service, repair- or a
little more Power Components know-how.
Customers can rely on CNH Parts & Service and its state-of-the-art
distribution facilities to provide the right products and service to help them
keep their equipment up, running and profitable. The dealers employ the
best trained technicians and have access to the full line of CNH Original Parts
as well as the latest tools and equipment for performing diagnostics,
maintenance and repair.
Combined with innovative programs for making routine maintenance
convenient, the dealers offer flexible scheduling, early morning parts
delivery and service in the field.
32
1996 New Holland India established.
33
Indian market. One of its leading products is the newly launched sugarcane
harvester which has been awarded great acclaims from the agricultural
community.
2. Harvesting Equipments
4. Supporting Attachment
New Holland Agriculture, Greater Noida has more than 700 employees, with
all production staff being properly technically trained. Many of these staff
members have also received training in other New Holland plants outside of
India to ensure standardization of quality products in all New Holland plants
across the globe.
34
Armed with some of the latest CAD tools and CNC, 5the factory has an
excellent machining center. Its CED equipment provides high quality
polyester paint. Moreover it has an integrated supply chain ERP system
which allows smooth and efficient functionality of major processes. The
company emphasizes on quality and hence earned ISO 9001:2000 and
14001:2004 certification.
35
Chapter
36
Statement of Work
3.1 CBU Components
3.2 Design Process
3.3 Architectural Goals
37
• Administrator
• CBU Manager
• Finance
• Dealer
38
for the various business functions. Eg. In sales modules, Payment at
different level like Zone, CBU, Dealer. Visual Studio .NET v1.0 would be used
to develop the application front-end, while SQL Server 2008 would be used
as database. Only the authorized person who has the Admin Role can
access the admin screens to add, modify and delete the content of the
intranet site dynamically.
➢ Validation logic
➢ Form Aliases
39
3.3 Architectural Goals
The architecture goals for the application could be outlined as follows:
40
Chapter
Project Plan
4.1 Modular breakdown Structure
4.2 Processor Logic For Modules
4.3 Technical Facts
4.4 Self Contribution
4.5 Development Methodology
4.6 Project Mentors
41
4.1 Modular breakdown Structure
The project titled CBU has been further divided into 4 modules and further
divided into many sub-modules. Various modules that constitute the overall
project are:
• Masters
• Transactions
• Reports
• BI Reports
Transactions
Masters
CBU
System
Reports 42 BI Reports
4.2 Processor Logic for Modules
• Master Module (MM)
• Transactions (TM)
• Reports (RM)
• BI Reports (BIRM)
This module will only allow the administrator to change and view the details
about all the zones, CBUs, dealers, locations and models to with the
organization deals. The masters that will be handled by the module are:
43
Zone Master: -
44
• Detailed view of all dealers in particular CBU.
• Insert additional location in particular CBU as per requirement.
The facilities that will be provided by administrator to users the w.r.t to this
module will be:
• A Zone manager will be able to view the enlisted summary of all the
zones. For each zone, the zone manager can view the information
regarding zone code, zone name, creation date etc.
• A CBU manager will be able to view the enlisted summary of all the
CBUs related to particular zone. For each CBU, the CBU manager can
view the information regarding CBU code, CBU name, city, CBU head
etc.
• Location master can be accessed by zone manager and CBU master.
This sub-module enlists the summary of all the dealers in the
particular zone and cbu. Contains the information regarding dealer
code, dealer name, cbu code, city etc.
• The Model Master module enlists the information regarding all the
product series of NHT like model name, model no., segment, HP, axle,
transmission, hydraulic etc.
Transaction Services
Following Transaction services will be provided through CBU System: -
• Annual Operating Plan (AOP) Locking Status
• Dealer Payment
• Event Planning
• Field Activity
45
• Dealer Payment Details
• Customer Feedback
• Sales Order Approval
46
This module will allow the user to view various types of reports . The various
reports options are as follows:
• Plan
• Payment
• Dispatches
• Sales Order
• Depot
• Monthly Dashboard
• Field Services
• Model Feedback
• Dealer Details
• Market Share etc.
47
4.3 Technical Facts
Microsoft .NET Compact Framework
48
Visual Basic.NET and C# as development languages out of the box. Support
for other languages is planned in near future. Microsoft is creating a set of
extensions for Visual Studio .NET called Smart Device Extensions that will
allow Visual Studio .NET developers to program for .NET Compact
Framework. This means that developers familiar with Visual Studio.NET can
start developing for mobile devices almost instantly.
Features of .NET
Now that we know some basics of .NET, let us see what makes .NET a
wonderful
platform for developing modern applications.
• OOPs Support
The advantages of Object Oriented programming are well known. .NET
provides a fully object oriented environment. The philosophy of .NET is –
“Object is mother of all.” Languages like Visual Basic.NET now support many
of the OO features that were lacking traditionally. Even primitive types like
integer and characters can be treated as objects – something not available
even in OO languages like C++.
49
• Multi-Language Support
Generally enterprises have varying skill sets. For example, a company might
have people with skills in Visual Basic, C++, and Java etc. It is an experience
that whenever a new language or environment is invented existing skills are
outdated. This naturally increases cost of training and learning curve. .NET
provides something attractive in this area. It supports multiple languages.
This means that if you have skills in C++, you need not throw them but just
mould them to suit .NET environment. Currently four languages are available
right out of the box namely – Visual Basic.NET, C# (pronounced as C-sharp),
Jscript.NET and Managed C++ (a dialect of Visual C++). There are many
vendors that are working on developing language compilers for other
languages (20+ language compilers are already available). The beauty of
multi language support lies in the fact that even though the syntax of each
language is different, the basic capabilities of each language remain at par
with one another.
• Multi-Device Support
Modern lift style is increasingly embracing mobile and wireless devices such
as PDAs, mobiles and handheld PCs. . . .NET provides promising platform for
programming such devices. .NET Compact Framework and Mobile Internet
Toolkit are step ahead in this direction.
50
configuring COM+ application right from your source code. Your COM+
knowledge still remains as a valuable asset.
• Security
Windows platform was always criticized for poor security mechanisms.
Microsoft has taken great efforts to make .NET platform safe and secure for
enterprise applications. Features such as type safety, code access security
and role based authentication make overall application more robust and
secure.
51
4.3.1 Understanding the .NET Platform and its
layers
Here in this section we will be covering what the .NET Platform is made up of
and we will define its layers. To start, .NET is a framework that covers all the
layers of software development above the Operating System. It provides the
richest level of integration among presentation technologies, component
technologies, and data technologies ever seen on Microsoft, or perhaps any,
platform. Secondly, the entire architecture has been created to make it easy
to develop Internet applications, as it is to develop for the desktop.
52
4.4 Self Contribution
I am working as a Team Member in e-Banking Project. I am assigned with
following Modules:
TM (Transaction Module)
RM (Reports Module)
53
4.5 Development Methodology
Development
Capturing
User &application
Developing
Requirement
Integration
System
Design specifying
of HLD &&code
Analysis Project
LLD &for
Unit Testing
Construction
Acceptance
(HLD
Testing
Specification
& LLD)
enhancements
Requirements
54
This project has been based on the Iterative Water Fall model.
3) Construction:
This includes the real development of the module. All the designed
components are developed in specified technology.
4) Unit testing:
It involves the testing of each component separately.
5) Integration Testing:
The whole Module is tested with dependency to each component.
6) System Testing:
The Inter modules dependency is tested with the complete system.
55
7) User Acceptance:
Finally user acceptance testing takes place to make sure that user is
ready to accept the application.
Chapter
56
Abstract
This is the requirements document for the CBU project. The system to be
developed will enable the customers to avail the various facilities of the
company through internet, in an easy and convenient way. He will be able to
maintain his plan, payment and can view dispatches, Depot Aging, Dealer
Details and so on. This document follows the IEEE standard for the
requirements specification document with some variations.
5.1 Introduction
5.1.1 Purpose
57
The purpose of this document to describe the essential requirements for a CBU
system along with the description of the various interfaces required for the
proposed system.
5.1.2 Scope
This document is the only one that will describe the requirements of the
proposed system. It is meant for use by the developers and will be the basis
for validating the final delivered system. Any changes made to the
requirements in the future will have to go through a formal approval
process. The developer is responsible for asking for clarifications wherever
necessary.
58
5.2.2 Product Functions Overview
The software will enable the registered dealers to avail the various facilities :
• The dealer can view the summary of the purchased items, view the
details of their transactions etc.
• The dealer can pay his payments online after getting registered from
the list of payers having collaboration with the plant.
• The dealers can give their feedback rating about the product.
• User can plan for yearly and monthly collection.
The main users of this system will be the dealers, who should be having little
expertise with the basic functionalities of the computer system along with
the knowledge of surfing the Internet.
5.3Specific Requirements
59
1. Before a user can use the facilities of CBU System he will have to login
using the User Id and login password provided by the company
authorities during the registration process.
2. The user after logging on to the system should be able to view the
enlisted summary of all his account according to the user type.
60
Fig: Desired output as per requirement
3. For a particular module selected the user should be able to view the
history as well as user details.
4. The users should be able to view their AOP and MOP plan.
61
Fig: Desired output as per requirement
5. The users should be able to view the MOP daywise plan for their term
Plan Reports.
62
Fig: Desired output as per requirement
6. The users should be able to view the payments, give their feedback
about the product they purchased, and sales order pending Approval.
7. The users should be able to view the summary of his accounts, details
of holding and personal information.
8. The user should be able to update his Annual Operating plan in
advance and view his status.
9. Some users should have the permissions to view MOP marketing plan
year wise for sales of domestic as well as exports zones.
10. The cbu user should be able to plan for AOP of the dealer if he has
registered in that cbu area.
63
Fig: Desired output as per requirement
11.The dealer should be able to add his payment details of the product he
purchased by entering his necessary details like amount, transaction
type etc.
64
Fig: Desired output as per requirement
12. The user should be able to add his MOP-Daywise Plan according to his
cbu zone
65
13.1 The user should be able to view MOP according to dealer and model
wise.
13.2 And he should be able to edit the details and can add new variant
by clicking on the dealer code link.
66
Fig: Desired output as per requirement
14.The customer should be able to give his feedback about the product
he purchased.
67
Fig: Desired output as per requirement
68
Fig: Desired output as per requirement
16.The user should be able to view his YTD and MTD collection.
69
Fig: Desired output as per requirement
70
Fig: Desired output as per requirement
18.The user should be able to view report about sales order status wise.
71
Fig: Desired output as per requirement
19.The user should be able to the stock aging of depots and plant.
72
20.The user should be able to view his market-share of all months in the current
and previous year.
➢ Feedback Messages
➢ Appropriate Error messages
5.3.3 Design constraints
a) Software Constraints:
The system is to run under the Windows Operating System, Internet Explorer
6.0 or higher.
b) Hardware Constraints:
73
5.3.4 Acceptance Criteria
Before accepting the system the developer must demonstrate that the
system works in compliance with the requirements of the proposed system.
The developer will have to show through test cases that all conditions are
satisfied.
Chapte
r
74
6.1 Proposed system
The salient features of the proposed system include:
• No queuing
• Plan for Annual Operating Plan
• Allows the customer to control his/her finances on a day-to-day basis
• No need to interrupt DBA every time for every detail
• Access to the account 24 hours, 7 days a week (some accounts do close for
maintenance during the working time)
• Reporting of loss of Password
• Prevention of late penalties on bill payments
• Access to the account from anywhere (depending on the user)
• Better financial management
• Completely Secure transactions
• Access anywhere, anytime
75
CBU System is a Client-Server based distributed Application. The most important
aspect of distributed applications is the logical partitioning of an application into
three fundamental layers:
➢ Presentation
➢ Business logic
➢ Data Source
A simple distributed application model consists of a client that
communicates with the middle layer, which itself consists of the application
server and an application containing the business logic. The application, in
turn, communicates with a database that supplies and stores data.
The following sections describe the functionality of the each layer in detail:
➢ Presentation
Also called the Client tier, this layer consists of the front end user interfaces,
which act as a medium between the system and the user. These screens have
very high user interaction and hence must have a good look-n-feel and ease of
navigation. Web clients use a browser to access the middle tier over an HTTP
connection such as the Internet. Included in this tier are any applets that
execute on the client’s machine.
➢ Business logic
This layer constitutes the middle tier containing the Application Server
consisting of reusable asp Components. This tier contains both the presentation
logic and the business rules that define a Web site.
asp servlets: Sun ONE Active Server Pages 4.0 implements some of the
interfaces and classes in the javax.servlet and javax.servlet.http packages.
This means that Java objects designed for use in Java Server Pages (JSPs) can
now be integrated into a Sun ONE ASP script. The ASP servlet interface
implemented in this release is not a full-fledged servlet container, but instead
provides a mapping between servlet container objects and ASP objects.
asp pages: Active Server Pages (ASP), also known as Classic ASP or ASP
Classic, was Microsoft's first server-side script-engine for dynamically-generated
web pages. Initially released as an add-on to Internet Information Services (IIS)
76
via the Windows NT 4.0 Option Pack (ca 1998), it was subsequently included as
a free component of Windows Server (since the initial release of Windows 2000
Server). ASP.NET has superseded ASP. Programmers write most ASP pages
using C#, but any other Active Scripting engine can be selected instead
with the @Language directive or the <script language="language"
runat="server"> syntax. JScript (Microsoft's implementation of
ECMAScript) is the other language that is usually available. PerlScript (a
derivative of Perl) and others are available as third-party installable
Active Scripting engines.
➢ Data Source
This layer represents the data storage and data access features, and will
host SQL Server 2008 consisting of physical database and logical objects
• Storage of data
• Retrieval of data
• Maintenance of data
• Integrity of data
Layers are independent of each other.
77
This three-tier architecture offers several advantages:
78
The tiers, or even components of the tiers, can be distributed across multiple
hardware systems to improve system scalability and performance.
The middle tier shields clients from the complexities of accessing the Enterprise
data store.
The asp Servlet API defines Web applications as being composed of asp servlets,
asp pages, static content such as HTML pages, and any other application
resources.
The component architecture allows you to distribute application development
across your development group. For example, asp Servlet developers are
typically concerned with information presentation rather than with
implementing business rules. Conversely, asp developers are concerned with
data access and manipulation but not with presentation.
79
1.3 Context Diagram
80
81
6.4Database Design
6.4.1Table Structure
paycode varchar(20) N Y N
empname varchar(50) N N N
active char(1) Y N N
LoginType char(3) Y N N
cbuCode varchar(20) Y N N
mobileno varchar(20) Y N N
emailId varchar(50) Y N N
JobType varchar(50) Y N N
Dept_hrms varchar(200) Y N N
zoneCode varchar(30) Y N N
SendMail char(1) Y N N
82
Column Name Data Type Allow Null PK FK
MCBU_CBUCode varchar(50) N Y N
MCBU_CBUDescription nvarchar(50) Y N N
MCBU_ZoneCode varchar(20) Y N N
MCBU_RegionCode int N N N
MCBU_MAST_Region_Code int Y N N
MCBU_Address1 nvarchar(50) Y N N
MCBU_Address2 nvarchar(50) Y N N
MCBU_Address3 nvarchar(50) Y N N
MCBU_City nvarchar(50) Y N N
MCBU_Depot varchar(8) Y N N
MCBU_State nvarchar(50) Y N N
MCBU_PinCode nvarchar(15) Y N N
MCBU_Country nvarchar(50) Y N N
MCBU_CBUHead nvarchar(50) N N N
MCBU_EmailID nvarchar(50) Y N N
MCBU_Tel_Num nvarchar(50) Y N N
MCBU_FaxNumr nvarchar(50) Y N N
MCBU_Remarks nvarchar(100) Y N N
MCBU_Status char(10) Y N N
MCBU_CreatedBy nvarchar(50) N N N
MCBU_CreatedOn datetime N N N
MCBU_ModifiedBy nvarchar(50) Y N N
83
MCBU_ModifiedOn datetime Y N N
MDL_DealerCode varchar(15) N Y N
MDL_DealerName nvarchar(100) N N N
MDL_CBUCode char(10) N N N
MDL_LocationCode int N N N
MDL_Credit_Limit money Y N N
MDL_Credit_Effdt datetime Y N N
MDL_Avail_Credit_Limit money Y N N
MDL_Capital money Y N N
MDL_Address1 nvarchar(255) Y N N
MDL_Address2 nvarchar(255) Y N N
MDL_Address3 nvarchar(50) Y N N
MDL_City nvarchar(50) Y Y N
MDL_State nvarchar(50) Y N N
MDL_PinCode nvarchar(50) Y N N
MDL_Country nvarchar(50) Y N N
MDL_Tel_Number nvarchar(50) Y N N
MDL_Fax_Num nvarchar(50) Y N N
MDL_ContactPerson nvarchar(50) Y N N
84
MDL_EmailID nvarchar(50) Y N N
MDL_StdDelDuration int Y N N
MDL_Remarks nvarchar(100) Y N N
MDL_Status char(10) N N N
MDL_CreatedBy nvarchar(50) N N N
MDL_CreatedOn datetime N N N
MDL_ModifiedBy nvarchar(50) Y N N
MDL_ModifiedOn datetime Y N N
MDL_BG_Limit money Y N N
MDL_BG_Actual money Y N N
MDL_Credit_Period int Y N N
MDL_SecurityDeposit int Y N N
MDL_DepotCode char(6) Y N N
MDL_CMSAcceptance varchar(10) Y N N
MDL_ChequeAcceptance varchar(10) Y N N
MDL_BGNumber varchar(50) Y N N
MDL_ValidUpTo datetime Y N N
MDL_YesNo varchar(50) Y N N
MDL_Mobile varchar(50) Y N N
MDL_Partner varchar(250) Y N N
MDL_LegalEntity varchar(50) Y N N
MDL_LOIDate datetime Y N N
MDL_ClosureDate datetime Y N N
85
MDL_TinNo varchar(20) Y N N
MDL_PANNo varchar(20) Y N N
MDL_AgreementDate datetime Y N N
MDL_ValidityDate datetime Y N N
MDL_AOC nvarchar(255) Y N N
MDL_Sub_status varchar(50) Y N N
MDL_District varchar(50) Y N N
MDL_FinanceRank int Y N N
MDL_SaleRank int Y N N
MDL_Agreement char(1) Y N N
MDL_prefloc varchar(10) Y N N
MDL_plant_pcode varchar(3) Y N N
MDL_depot_pcode varchar(3) Y N N
MDL_STATEID varchar(3) Y N N
MDL_TAX_RATE decimal(5, 2) Y N N
MDL_MTDFINC money Y N N
MDL_TODAYFINC money Y N N
MDL_PDSO money Y N N
MDL_MTDBILL money Y N N
MDL_TODAYBILL money Y N N
MDL_CHNFIN_OS money Y N N
MDL_AltCode varchar(50) Y N N
86
Table Name: TM_LOCATION
MLOC_LocationCode int N Y N
MLOC_LocationName nvarchar(50) N N N
MLOC_CBUCode char(10) N N N
MLOC_Status char(10) Y N N
MLOC_CreatedBy nvarchar(50) N N N
MLOC_CreatedOn datetime N N N
MLOC_ModifiedBy nvarchar(50) Y N N
MLOC_ModifiedOn datetime Y N N
MLOC_LocationCode int N N N
MMOD_ModelCode nvarchar(16) N N N
MMOD_ModelName nvarchar(50) N N N
MMOD_Description nvarchar(100) Y N N
MMOD_ModelNo nvarchar(16) N Y N
MMOD_TyreSize nvarchar(50) Y N N
MMOD_Detail nvarchar(50) N N N
MMOD_Segment nvarchar(50) N N N
MMOD_Type nchar(20) Y N N
MMOD_Rtyre nchar(20) Y N N
87
MMOD_Ftyre nchar(20) Y N N
MMOD_CLUT nchar(30) Y N N
MMOD_SEGG nchar(30) Y N N
MMOD_Drive nchar(20) Y N N
MMOD_AXLE varchar(30) Y N N
MMOD_HYDRAULIC varchar(30) Y N N
MMOD_TRANSMISSION varchar(30) Y N N
MMOD_PTOTYPE varchar(30) Y N N
MMOD_FRONTWHEEL varchar(30) Y N N
MMOD_REARWHEEL varchar(30) Y N N
MMOD_ROPS varchar(30) Y N N
MMOD_TOWHOOK varchar(30) Y N N
MMOD_DRAWBAR varchar(30) Y N N
MMOD_CANOPY varchar(30) Y N N
MMOD_Cost money N N N
MMOD_Status char(10) N N N
MMOD_MfgName varchar(50) Y N N
MMOD_YearOfIntro datetime Y N N
MMOD_SellingPrice numeric(18, 0) Y N N
MMOD_CreatedBy nvarchar(50) N N N
MMOD_CreatedOn datetime N N N
MMOD_ModifiedBy nvarchar(50) Y N N
MMOD_ModifiedOn datetime Y N N
88
MMOD_Category varchar(50) Y N N
ZoneCode varchar(20) N Y N
ZoneName varchar(20) N N N
Description varchar(50) Y N N
CreatedBy varchar(20) Y N N
CreatedOn datetime Y N N
Active char(10) Y N N
DPD_PaymentID numeric(10, 0) N Y N
DPD_DealerCode varchar(15) N Y N
DPD_DateOfIntimation datetime Y N N
DPD_DateOfEntry datetime N N N
DPD_Mode char(3) N N N
DPD_CMSNumber nvarchar(50) Y N N
DPD_CMSDate datetime Y N N
DPD_ChequeOrDDNo nvarchar(50) Y N N
DPD_ChequeOrDDDate datetime Y N N
DPD_Amount money N N N
89
DPD_Status nvarchar(50) N N N
DPD_Remark nvarchar(100) Y N N
DPD_YBy nvarchar(50) Y N N
DPD_YDate datetime Y N N
DPD_Y_Remark nvarchar(100) Y N N
DPD_Finance_Date datetime Y N N
DPD_Finance_Remarks nvarchar(50) Y N N
DPD_Cancel_Date datetime Y N N
DPD_Cancel_Remarks nvarchar(50) Y N N
DPD_TransactionType nvarchar(10) Y N N
DPD_FLAG char(1) Y N N
DPD_CreatedBy nvarchar(50) N N N
DPD_CreatedOn datetime N N N
DPD_ModifiedBy nvarchar(50) Y N N
DPD_ModifiedOn datetime Y N N
DPD_FI varchar(50) Y N N
DPD_Bank varchar(50) Y N N
DPD_Place varchar(50) Y N N
DPD_PlaceCode varchar(50) Y N N
DPD_BaaNEntry int Y N N
DPD_DealerPayment varchar(50) Y N N
DPD_BaaNCtrl int Y N N
DPD_ProductCategory int Y N N
90
Table Name: DISPTCH_DETAILS_SALES
From_DepotCode char(6) Y N N
DISP_DealerCode varchar(15) N N N
DISP_Invoice_Number nvarchar(50) N Y N
DISP_Invoice_Date datetime N N N
DISP_ModelCode nvarchar(15) N N N
DISP_Truck_Number nvarchar(50) Y N N
DISP_Tractor_Number nvarchar(50) N Y N
DISP_Engine_Number nvarchar(50) N Y N
DISP_GRLR_Num nvarchar(50) Y N N
DISP_GRLR_Date datetime Y N N
DISP_TrptrName nvarchar(50) Y N N
DateOfRemoval datetime Y N N
DISP_SalesOrderRef nvarchar(50) N N N
DISP_BaanOrderRef nvarchar(50) N Y N
DISP_Status nvarchar(50) Y N N
DISP_Price money Y N N
Disp_Discount numeric(18, 0) Y N N
DISP_Manfact_Date datetime Y N N
DISP_BaaNItemCode nvarchar(16) Y N N
DISP_DispatchDate datetime Y N N
91
Disp_Insurance numeric(18, 0) Y N N
Disp_Freight numeric(18, 0) Y N N
DISP_CSTNo varchar(30) Y N N
DISP_LSTNo varchar(30) Y N N
Disp_CSTDate datetime Y N N
Disp_LSTDate datetime Y N N
DepotOperatingExp numeric(18, 0) Y N N
InvoicePrinted char(1) Y N N
DISP_CCHP char(3) Y N N
CSt_LST_AMT numeric(18, 2) Y N N
ModeOfTransport varchar(30) Y N N
CancellationRef nvarchar(50) Y N N
ModifiedBy varchar(30) Y N N
ModifiedOn datetime Y N N
pk_planid int N N N
dealercode varchar(20) N Y N
planmonth int N Y N
planyear int N N N
amount money N N N
PRODTYPE int Y N N
92
Table Name: CB_DISPATCH_PLAN
pk_planid int N Y N
dealercode varchar(20) N Y N
planmonth int N Y N
planyear int N Y N
planvalue int N N N
Chapter
Testing
7.1 Objective And Scope
93
7.1 Objective And Scope
The objective of the different testing phases is to test in such a way, that the
system being developed for CBU fulfils the requirements (both functional
and non-functional) as specified in the Business requirement. The objective
also includes testing all main functions / services within the system and the
interfaces connecting different functionalities to the maximum extent
possible.
The scope involves identifying all the components that need to be tested
along with the various functions that form the component. The following is a
summary of the Scope of the different testing phases:
➢ Unit Testing
Unit testing will be a white box testing of various modules. Team member
responsible for the development of the module will carry it out.
94
➢ Sub-System Testing
This includes business functionality testing of all the components
taking into consideration all the interfaces.
➢ Integration Testing
This testing would include testing the technical integration of
various components.
This will not involve any business functionality testing but
only technical integration testing.
➢ System Testing
This would include:
End – to – End functionality testing which includes integration
testing with all third party interfaces.
Performance Testing that aims to determine whether a
system meets the performance requirements within the
physical limitation of the computing environment (CPU
process speed, memory capacity and number of users etc.) of
the system.
➢ Pre-Acceptance Testing
○ This would include selected Business Functionality to be
tested for the Client.
95
Figure: Levels of Testing
96
The Automated Testing Lifecycle Methodology (ATLM)
This structured test methodology involves a multi-stage process, supporting
the detailed and interrelated activities that are required to introduce and
utilize an automated test tool:
Develop test design.
Develop and execute test cases.
Develop and manage test data and the test environment.
Document, track, and obtain closure on issue/trouble reports.
The ATLM implementation takes place in parallel with the system
development lifecycle. For software professionals to make a successful leap
to automated testing, they must embrace structured approaches to testing.
The following sections describe each primary process, as well as the
subordinate processes contained within each primary process.
97
Phase 1: Decision to Automate Testing
The decision to automate testing represents the first phase of the ATLM. This
phase covers the entire process that goes into the automated testing
decision. During this phase, it's important for the test team to manage
automated testing expectations and to outline the potential benefits of
automated testing when implemented correctly. A test tool proposal needs
to be outlined, which will be helpful in acquiring management support.
98
Plans for user involvement are assessed, and test team personnel skills are
analyzed against test requirements and planned test activities. Early test team
participation is emphasized, supporting refinement of requirement specifications
into terms that can be adequately tested while also supporting test team
understanding of application requirements and design.
b) Test Tool Consideration
The test tool consideration process includes steps that investigate whether
incorporation of automated test tools that have been brought into the
company without a specific project in mind now would be beneficial to a
specific project, given the project testing requirements, available test
environment, personnel resources, user environment, platform, and product
features of the application under test. Schedule is reviewed to ensure
sufficient time for test tool setup and development of requirements
hierarchy; potential test tools and utilities are mapped to test requirements,
test tool compatibility with the application and environment is verified, and
workaround solutions are investigated for incompatibility problems that
surfaced during compatibility tests.
99
b) Test Design
The test design component addresses the need to define the number of
tests to be performed, the ways that testing will be approached (paths,
functions), and the test conditions that need to be exercised. Test design
standards need to be defined and followed.
Step Description
1 Test Architecture Review. The test team reviews the test architecture
in order to identify the test techniques that apply.
100
designed in further detail within a detailed test design file or document.
Test procedure detailed design may consist of pseudo-code of
algorithms, preliminary test step definition, or pseudo-code of test
automation programs.
Test Development
For automated tests to be reusable, repeatable, and maintainable, test
development standards need to be defined and followed.
After performing test analysis and design, the test team is now ready to perform
test development.
Module (Unit) Design module Perform test planning and test environment
Development from setup.
requirements.
101
Conduct Verify that system is scalable and will meet
performance performance requirements.
testing.
Integration Build system by Combine unit test scripts and add new scripts
connecting that demonstrate module interconnectivity. Use
modules. test tool to support automated integration
Integration-test testing.
connected
modules.
Review trouble
reports.
System Test Review trouble Integrate automated test scripts into system-
reports. level test procedures where possible, and
develop additional system-level test procedures.
Execute system test and record test results.
102
The test team needs to obtain and modify test databases necessary to
exercise software applications, and develop environment setup scripts and
test bed scripts. The test team perform product reviews and validation of all
test source materials. The location of the test environment for each project
or task is defined within the test plan for each project. Early identification of
the test site is critical to cost-effective test environment planning and
development.
103
various steps necessary for test program review and assessment are
outlined below.
Following test execution, the test team needs to review the performance of
the test program to determine where changes can be implemented to
improve the test program performance on the next project.
The focus of the test program review includes an assessment of whether the
application satisfies acceptance criteria and is ready to go into production.
Chapter
104
Conclusion
105
CONCLUSION DRAWN
I feel truly satisfied by the fact that though getting a chance to work in such
a real live application project is rare still I managed to get it. I have exploited the
opportunity that came my way to the fullest extent by increasing my technical
know-how and also gaining the valuable work experience from the esteemed
organization.
The program will provide customers easy and secure access to EBS services
through the Internet, any time and from any place in a manner that best suits the
customers.
106
REPORTING
SERVICES
107
SQL SERVER 2005 REPORT GENERATING SYSTEM
SQL Server 2005 Reporting Services is a key component of SQL Server 2005.
Reporting Service provides customers with an enterprise-capable reporting
platform with a comprehensive environment for authoring, managing, and
delivering reports to the entire organization.
There are a few simple steps to get started with his application in SQL 2005
1. Go to the start menu, programs, Microsoft SQL Server 2005, SQL Server
business intelligence development studio.
2. Once the visual studio window is opened, go to File option and select
project from the new menu option. On doing so, a new report will be made
as shown below;
108
3. Select the Report Server Project option from the window. On doing so, a
new report will be added to the recent projects column.
4. Go to the project option in the menu bar and select add new option. On
doing so, the following window will be seen;
109
TYPES OF REPORTS
There are in all eight types of reports, out of which the important three are
discussed below. These reports are most frequently used and implemented
on a large scale.
PARAMETERIZED REPORTS
When you are using reports, you need to have parameters that narrow down
your report for better analysis. You will often see that you need to have
more than one parameter, where the second parameter may depend on the
first parameter, which many require you to refresh the second parameter
depending on the first parameter. In addition, you may have parameters
110
with multiple and/or default values. These reports are called parameterized
reports. The following steps will help us to know about it in a better way.
1. Click on the report option in the window and an entirely new window
opens up;
2. Next we select the <New Dataset> option in the dataset bar and the
window looks like as follows;
111
3. Name the dataset, and click on the edit button near connection string. On
doing so, a new window pops up;
112
4. Specify the server name, then select ‘Use SQL Server authentication’ and
fill in the user name and password , check the save password check box,
specify a database name and finally click on the ‘Test Connection’ button. A
small message box saying the connection is successfully made is shown.
5. Next, on closing all the windows in the visual studio, we see the new
window as shown below;
6. Now, we click on the ‘edit selected dataset’ option near the dataset box;
113
7. Next, we give the correct command type and the query name, and then
click OK.
8. Now, we go to the solution explorer window, right click on the shared data
sources option, and make the connection as done earlier.
114
9. Now, if we click the Run button, the specified query is executed. For
example,
10. Right above the bar containing the dataset name and the run button, we
have three options; data, layout and preview. Till now we were working on
the data. Now, we will work on the layout of our report, by clicking on the
layout button.
115
11. Next, we click on the toolbar option at the very left of the window. From
there we select the tool we need for our report. For example
116
12. Now, we fill the required information from the database option given
below the toolbar option. Our layout is ready.
117
13. Finally, we click on the preview option and the report is generated.
14. On making changes in the properties of the table in the layout section,
we can give our report a better look.
118
LINKED REPORTS
119
below are the steps one should use to deploy a report and then create a
linked report.
2. In the TargetServerURL column, write the URL address, and select OK.
3. A security window asking for the username and password of the given
URL address will be seen. Enter the required information, and the report will
be deployed.
4. Open the internet explorer and in the address bar type the URL address
given earlier. Another security box will emerge. Fill in the username and
password and proceed. The SQL Server Reporting Services Homepage will
be opened.
120
5. Select the project and open the report you want to link to and click on the
properties tab. The general properties page opens up.
121
6. Fill in the required information and click Create Linked Report. The linked
report is created.
122
DRILL DOWN REPORTS
Occasionally, you may want to place items on a report but hide them from
view when the report is rendered. You can also cause a report item to toggle
between visible and hidden when the user clicks on another report item, or
you can hide a report item based on the contents of another report item.
You can hide any report item, including groups, columns, or rows in a table
or matrix.
The primary use of hidden items is to provide a report that shows summary
data but also provides a way for the user to drill down into detail data. To
create this drilldown effect, select the group, column, or row to hide, set its
hidden state to True, and then set the toggle item to the name of a text box
in a containing group. When the report is rendered, the user can click the
text box to expand and collapse the detail data. Initial stages of the drill
down report is similar to the above two reports.
1. Once the project is opened, create two reports and set their data and
parameters as needed.
123
3. Right click on the header of the column that you want to drill down and
select properties.
4. In the properties window, under the navigation tab, select jump to report
option, select the other report and click OK.
124
5. In the preview section, right click on the first report and select build. Do
the same with the second report.
7. In the preview section, when you click on the column that is drilled down,
the next hidden report is shown.
125
126
INTEGRATING THE DEPLOYED REPORTS IN ASP.NET
In the previous sections, we learnt how to make various kinds of reports and
deploy them on the server. These reports are now made to be seen by users
and clients and use it in their applications. This is done by using the
Microsoft Visual Studio Application.
127
128
Once the application opens, the following steps would create an integrated
report in ASP.NET.
1. Go to the files option in menu bar and select New, then Web Site.
129
3. This is the ASP.NET code window that appears. It contains all the general
specifications needed for an ASP.NET application to run on the server.
130
4. In the tool box, select the report viewer, and click on the report viewer
that appears on the design window.
131
5. The code window opens up, where we can add more specifications, like
parameters, default values, buttons etc.
6. Finally, on executing this, one can see the integrated report on the server.
132
CONCLUSION
In the eight years since release of Microsoft's previous SQL Server product
(SQL Server 2000), advancements have been made in performance, the
client IDE tools, and several complementary systems that are packaged with
SQL Server 2005. These include: an ETL tool (SQL Server Integration
Services or SSIS), a Reporting Server, an OLAP and data mining server
(Analysis Services), and several messaging technologies, specifically Service
Broker and Notification Services.
The SQL SERVER 2005 introduces a lot of user friendly features. SQL Server
2005 introduced "MARS" (Multiple Active Results Sets), a method of allowing
usage of database connections for multiple purposes. SQL Server 2005
introduced DMVs (Dynamic Management Views), which are specialized views
133
and functions that return server state information that can be used to
monitor the health of a server instance, 61
diagnose problems, and tune performance. This project deals mainly with
the SQL SERVER REPORTING SYSTEM. This feature comes in the package of
the Microsoft SQL Server 2005. This helps a lot as far as the administration
in an organization is concerned. With the passage of time, this feature is
getting better.
134