Project Report

126
PREFACE 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

Transcript of Project Report

Page 1: Project Report

PREFACE

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.

Prashant Tanwar

ACKNOWLEDEGMENT

1

Page 2: Project Report

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.

It was memorable experience for me to visit the industry. I don’t have

adequate word to express my profound gratitude to Project Manager Mr.

Deepak Kumar (Senior Manager) and Project Report Incharge Ms. Neha

Mishra for providing me such valuable opportunity training in New Holland

Fiat (India) Pvt. Ltd. Without their continuous help and motivation my

efforts would not have been able to be shaped into a tangible form. They

always inspired me towards learning and gaining knowledge and helped me

at all stages of the project by spending their invaluable time and effort.

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 Chapter 2

Page 3: Project Report

Brief Overview1.1 Training Overview

1.2 Abstract

1.3 Development Environment

1.1 Training Overview

3

Page 4: Project Report

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.

The main objective of the proposed solution (CBU) is to automate the various functions and activities of the business through Internet. The solution will facilitate to the industry employees, users and the dealers with different modules. The solution is very much necessary for the private sector business and the corporate sectors. Using this solution the users and the dealers will be able to access various kinds of features.

1.2.1 .1 Modules

The following modules used in the CBU System are:

Masters Transactions

4

Project Title CBU System & SQL Reporting Services

Student Name Prashant Tanwar

Internal Guide: Ms. Neha Mishra

Project Manager Mr. Deepak Kumar

Team Leader Mr. Deepak Kumar

Company Name New Holland Fiat (India) Pvt. Ltd

Company Address New Holland Fiat (India) Pvt. Ltd.

Tractor Division Plot No. 03, Udyog Kendra, Greater Noida – 201306Distt. Gautam Budh Nagar, U.P. India

Page 5: Project Report

Reports BI Reports

1.2.1.2 Services

The required features of the System are

Add more modules using application management 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

1.2.2 SQL Server Reporting Services

Microsoft SQL Server Reporting Services (SSRS) is an enterprise reporting platform supporting traditional paper-based reports and interactive reports delivered over the Web or through custom applications. SSRS is data-source independent. Multidimensional sources and hierarchical sources of reports can also be used.

The Report Server Service, which is the server-side component, hosts reports in a variety of formats, including Microsoft Excel Worksheets and Portable Document Format (PDF) files. The server component is managed through a Web services infrastructure accessible using Simple Object Access Protocol (SOAP). The client consuming the report might be as simple as a Web browser pointing to a Report Server URL. Reporting Services also has an API that allows reports to be embedded in other applications.

Reporting server - This is the New Holland Tractor (NHT) reporting database where performance metrics samples are gathered and aggregated over a period of time.

Reporting Services ArchitectureThe following figure gives a conceptual overview of the Reporting Services architecture showing how data is made available for report generation.

5

Page 6: Project Report

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 Application server : Microsoft .Net Framework Web server : IIS Database : SQL Server 2008.

6

Page 7: Project Report

1.3.3 Development Tools

Drag and Drop design IntelliSense features Database Excellent debugging tools. Integration with version control software such as Visual Source Safe (VSS) Easy project management

Chapter Chapter

Company Profile2.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

7

Page 8: Project Report

2.8 Present Status of Organisation

2.1 Company Perspectives

The mission: To be a customer-driven organization, flexible, agile and

innovative, with our people, dealers, suppliers and partners working

together with pride to be the best globally positioned company in the

agricultural and industrial equipment business. This is New Holland's

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

8

Page 9: Project Report

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.

2.2.1 Company Origins

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

9

Page 10: Project Report

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.

2.2.2 Sperry Takes Over in 1947

After about a decade of struggle, New Holland was purchased by a group of

four investors. The new owners were able to turn the company around

quickly by introducing a new product, the world's first successful automatic

pick-up, self-tying hay baler. The baler, invented by local thresherman Ed

Nolt, was an instant hit among farmers. It almost singlehandedly put New

Holland back on solid footing. In fact, the company has continued to

manufacture updated models of the baler ever since.

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.

As the 1960s continued, Fiat became increasingly active in the manufacture

of equipment for agriculture and construction. Late in the decade, that

10

Page 11: Project Report

company created a Tractor and Earthmoving Machinery Division. Fiat's

earthmoving segment was moved into its own subsidiary, Fiat Macchine

Movimento Terra S.p.A., in 1970. Fiat continued to move further into heavy

equipment through the 1970s. In 1974 Fiat Macchine Movimento Terra

launched a joint venture with American manufacturer Allis Chalmers

Corporation, called Fiat-Allis. That year also marked the creation of the

company's Fiat Trattori S.p.A. subsidiary. Fiat finally gained entry into the

North American market in 1977, with the acquisition of Hesston, a Kansas-

based manufacturer of hay and forage machinery. Fiat also purchased

Agrifull, a small-sized tractor manufacturer, that year. In 1984 Fiat

consolidated all of its agricultural machinery manufacturing under the

umbrella of Fiatagri, the new name for Fiat Trattori.

2.2.3 The 1980s Belong to Ford

All the while, Ford was also becoming a global force in agricultural

equipment. Its Ford Tractor division had been responsible for a number of

industry breakthroughs, including the use of rubber pneumatic tires, power

hydraulics, diesel engines, and the three-point hitch. Ford's inexpensive

tractors had been largely responsible for the replacement of horses and

mules by machines on United States farms over the first several decades of

the 20th century. By 1985 Ford Tractor had 9,000 employees, about one

third of them located in North America, and 5,000 dealers worldwide, again

about a third of them in the United States.

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

11

Page 12: Project Report

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 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.

2.2.4 1990s: The Fiat Era

By 1990 Ford New Holland had 17,000 employees, revenue of $2.8 billion,

and plants in the United States, Canada, Belgium, England, and Brazil, plus

joint ventures in India, Pakistan, Japan, Mexico, and Venezuela. In 1991 Fiat

purchased 80 percent interest in Ford New Holland. Ford New Holland was

12

Page 13: Project Report

merged with FiatGeotech to create a huge new industrial equipment entity

dubbed N.H. Geotech--though its North American operation kept the name

Ford New Holland for the time being. The purchase surprised nobody in the

industry, since Ford had been looking for a buyer for its tractor operation

for the better part of a decade. The new international behemoth,

headquartered 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.

Between 1991 and 1993, the company undertook a number of measures

designed to better integrate its many pieces into a coherent whole. Among

the goals of this group of projects were a reduction in the time needed to

bring new products to market and to focus manufacturing operations on

core components. The company's supply chain was also streamlined. N.H.

Geotech changed its name to New Holland N.V. in January 1993, although

the company's North American operation stuck with the Ford New Holland

moniker for two more years. The year 1993 also brought the introduction of

the company's Genesis line of 140- to 210-horsepower tractors. The Genesis

line proved so popular that it took only a little more than two years to sell

10,000 of them.

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.

Operating as a wholly owned subsidiary of Fiat, New Holland brought in

just more than $5 billion in sales in 1995. By this time, the company

controlled 21 percent of the world market for agricultural tractors, 17

percent of the world market for combines, 42 percent of the market for

13

Page 14: Project Report

forage harvesters, and significant shares of the world markets for just about

every other category of agricultural or construction equipment one could

name.

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 addition to the stock offering, 1996 also brought a number of

technological innovations and new product unveilings as well. New

Holland's new E-Series backhoe-loaders were chosen by Construction

Equipment magazine as one of the construction industry's 100 most

significant products. The company also introduced several new tractor lines,

four Roll-Best round balers, and two large self-propelled forage harvesters.

New Holland was also active in conducting research on futuristic, driverless

machines. Working with NASA and Carnegie Mellon University as part of

the NASA Robotics Engineering Consortium, New Holland created a

prototype of a self-propelled windrower that cuts, conditions, and puts

alfalfa into windrows without requiring a human operator. One further 1996

development at New Holland was the appointment of former U.S. Treasury

Secretary and Vice-Presidential candidate Lloyd Bentsen as its chairman of

the board.

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

14

Page 15: Project Report

tractors, including four brand new models. Building on its longstanding

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.

2.3 About: NHI Plant

15

Page 16: Project Report

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.

2.3.3 SECTIONS IN THE PLANT

1. ENGINE ASSEMBLY2. MACHINE SHOP(CNC MACHINING)3. PTO ASSEMBLY LINE4. DRIVE LINE5. TRACTOR ASSEMBLY LINE BEFORE PAINTING6. TRACTOR ASSEMBLY LINE AFTER PAINTING7. TOOL ROOM8. FRONT AXLE SUB ASSEMBLY LINE9. STORE AREA

10. FINISHING LINE11. TESTING12. MAJOR REWORK13. OK TO SHIP LINE14. TYRE SUB ASSEMBLY LINE15. CED PAINT SHOP16. TYRE YARD

16

Page 17: Project Report

2.3.3 DEPARTMENTS AT NHI PLANT

1). Design and engineering2). Finance and accounts3). Human resource4). Information system5). Manufacturing• Supply chain, logistics, PPC, procurement• SQA (Supply Quality Assurance)

6). Purchase7). Sales and marketing.

2.3.3.1 Design and engineeringIntroduction

To work towards achieving an undisputed & encyclopedic market leadership, basic thrust of NHI is on continuously upgrading the products and introducing new products to suit the ever-changing needs of its customers.

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 products to achieve the highest production standards, the fastest rates of production with the lowest cost of manufacture.

It is equipped with the most modern facilities for computer-aided engineering, stress & vibration analysis, prototype-build and test laboratories for metrology, chemical and metallurgical analysis, physical analysis, engine testing, specialized design testing and special track-testing. To comprehend, it has well established Product Development capability, driven by young , motivated & qualified engineers drawn from various functions to follow the modern concurrent engineering approach, endorsed with state of the art tools comprising latest computer software, modern testing facilities and proven design and developing methodologies.

17

Page 18: Project Report

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."

D&E can be subdivided into four sub-systems:

DESIGN

TESTING

VALUE ENGINEERING

ENGINEERING SERVICES

DESIGN:

Design department is bifurcated further into two competence groups:

CG I- Looking meagerly after Transmission, Hydraulics, Steering & Front Axle System

CG II- Taking care of Engine, Electrical System, Vehicle, Sheet metal, Linkages etc.

TESTING:

Testing department is further divided into two groups

- Component Testing

- Vehicle Testing

VALUE ENGINEERING:

Value Analysis provides the following services to the Tractor GPL

New Product Cost Estimates - Piece Cost & Supplier Investment Current Product Technical Cost Analysis of Piece Cost (Key Model) Engineering 'Elbow' Service (Best Cost Solution) New Parts Cost Target to Purchase - Piece Cost & Supplier Investment CPI / VIT Cost Control - Piece Cost & Investment

18

Page 19: Project Report

Current Product Piece Cost Change Analysis for Budget Current Product & New Product Supplier Investment Analysis for Budget

Competitive Model Tear down to achieve cost savings or avoidance.

ENGINEERING SERVICES:

FUNCTIONS:

It is responsible for releasing Engineering changes through CIDS Archiving of all drawings, standards, specifications Creating & Maintaining the Engineering Bill Of Material through

special software - "DBT" (Distente Base Technica) which collects and gives access to all models BOMs globally.

Providing Engineering support to the D & E relating to Global models.

2.3.3.2 Finance and accountsThe finance and accounts team at New Holland India working together as a winning team currently compromises of 19 members. They are primarily a support function for the rest of the company fulfilling the company’s financial requirements and managing the finances and also meeting the statutory requirements.

They work on calendar year accounting from January to December, keeping in line with international accounting requirements. In addition they also have a tax closing from April to march every year as per the Indian tax requirements.

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.

2.3.3.3 Human Resource

19

Page 20: Project Report

Human Resource is the most valuable asset for any organization any and they require utmost care,concern and recognition to be able to perform to

their fullest potential.

2.3.3.4 Information SystemRole:

To lead the organisation to be a highly IT oriented and Processed based organisation.

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:

ERP – BaaN ( Supply Chain) .NET framework ( Web Applications ) Group ware – Lotus Notes (Messaging & Workflows) New Holland India Intranet. Locally developed – Spare Parts Management System. Farm Training System Localization Control System.

2.3.3.5 ManufacturingTractor assembly

Pre Paint Assembly Post Paint Assembly

Front Axle sub Assembly Tyre sub Assembly

20

Page 21: Project Report

Painting

Body Tractor Sheet Metal Parts

Drive Line Assembly

Rear Axle Assembly Transmission Case Assembly Hydraulic Lift Assembly Trumpet Assembly

Engine Assembly (3 Cylinder & 4 Cylinder)

Assembly Testing

Machining

Transmission Case Axle Casing Trumpets (4 types) Front Axle support Rear Cover

21

Page 22: Project Report

Hydraulic Lift Body Final Drive Cover Master Clutch Housing 42 HP Front Support 42 HP

2.3.3.6 PURCHASENew 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.

We view the relationship with our suppliers as a business partnership in which both the parties work together and combine their talents to produce mutually profitable and consistently superior results. As in any partnership, this arrangement imposes obligations.

STRATEGIC OBJECTIVES:

– PRODUCT LAUNCH AT SHORTEST POSSIBLE TIME– AGGRESSIVE LOCALISATION TO REDUCE COSTS.– MAXIMISE OUTSOURCING.– COMPETITIVENESS THROUGH CONTROL OF PURCHASED – MATERIAL COSTS.– DEVELOP A SUPPLY BASE MEETING CNH GLOBAL STANDARDS.

SQA team manages several activities, mainly at supplier site:

Suppliers’ audits and certification

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 MarketingService department is committed to provide high standards of after sales service support to our esteemed customers through our dedicated dealer

22

Page 23: Project Report

network resulting into a positive word of mouth by way of product performance, customer retention & generating strong referrals.

To NHI

Raise product performance Establish strong customer loyalty Image enhancement Smooth network functioning Overall business growth

To Dealers

Infrastructure and system development Prompt warranty support on product concerns Increasing service business Raising technical skill level of manpower to avoid repeat problems

To Customers

Ensure minimum breakdown time Bring service network within easy reach. Measuring satisfaction through surveys ans providing service.

The New Holland plant is the most modern tractor factory in India, with a

number of advanced features. It has:

CED (Cathodic Electro Deposition) painting system for the sheet metal components – a first in the Indian tractor industry – giving excellent finish and durability.

Sophisticated high speed machining centres for machining critical castings and components to very close tolerances.

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.

23

Page 24: Project Report

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.

2.4 Manpower Sourcing

2.4.1 Internal Sourcing

They believe in rewarding talent and commitment amongst our own before

looking elsewhere. They therefore look for suitable talent first within the

organization by notifying vacancies internally.

2.4.2 Talent from Campus

They recruit young engineering graduates, CAs and MBAs from reputed

institutes around the country. They are then initiated into the organization

after a rigorous training, during which they are rotated through various

departments before being finally placed in their area of specialization. The

objective of this programme is to prepare new recruits to take up their

responsibilities and be effective in their roles from day one.

2.4.3 Lateral Recruitment

They have a ready pool of employees who join them from other companies from time to time. They provide mentoring for new inductees in the organization to enable them to settle down into our unique culture.

The combined force of existing talent and induction of fresh blood into the organization helps them to be competitive, in the face of increasing business complexities.

2.4.4 Continuous Learning and Development

They strive for organizational excellence through continuous investment for the growth and renewal of their people. There is an intense focus on continuously developing their abilities to respond to existing and future

24

Page 25: Project Report

business requirements. A detailed training and development plan is drafted and implemented each year, which comprises level-wise planned interventions as well as specific need-based interventions. The Training Need Analysis helps to equip people to excel in their current roles and prepare them for future roles. They also place emphasis on behavioral and attitudinal training apart from technical as well as on-the-job training.

2.4.5 Performance Management

At New Holland India, they have an effective Performance Management System, which provides opportunities for employees to explore their potential for professional growth and personal development. We are attempting to bring as much objectivity as possible in our assessments to recognize and reward performers.

2.4.6 Employee Involvement

They believe that employee involvement is the key to continuous improvement, sound decision-making and developing an open and transparent organization. They provide ample opportunities for employees to 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.

2.4.7 Sensitivity to Employee Expectations

25

Page 26: Project Report

Wherever New Holland India has created industry and employment, it has also provided educational, medical, recreational and spiritual support systems for its people. Be it subsidized transport facilities or availability of our product at concessional rates to our employees or quality education for their children, it is our constant endeavor to anticipate and exceed employees’ expectations to make them feel a part of the large New Holland India family. Our excellent employee relations are a manifestation of our employees’ integration with the organization.

The organization has also ensured and enforced equal employment opportunities to women. Their welfare has been especially catered for with support systems like medical and transport facilities.

2.4.8 Working at New Holland India

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.

2.5 Services Offered

Great products need great service. CNH provides full back-up for the customers and dealers of its world-leading agricultural and construction

26

Page 27: Project Report

equipment. Their commitment to serving their customers' success starts even before they buy a machine through the flexible finance schemes provided by CNH Capital.

On-line assistance is always there to help with any technical issue. Parts can be located and delivered when and where they are needed. It's all part of the all-encompassing service that they ensure.

The services which they provide are:

Financial CNH power components Parts and Services

2.5.1 Financial services

To help its customers and dealers grow, CNH offers a wide range of financial services and products. As a specialist in the construction and agricultural equipment businesses, they have a natural grasp of needs and trends in the sector that aids customers in planning their future. Throughout the world, CNH specialists provide flexible financing solutions tailored to local requirements and the individual needs of farmers, construction companies, dealers and contractors.

2.5.2 CNH power components service

CNH Power Components works with OEM companies to help them take advantage of the tremendous manufacturing and purchasing power of CNH when selecting components for their own vehicles or machines. 

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. 

27

Page 28: Project Report

CNH Power Component products are incorporated in machines working in such varied sectors as road construction, mining, soil preparation and harvesting, contributing to the success of OEM companies around the world. 

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. 

2.5.2 Parts and services

Signing a purchase or lease agreement at the dealership is only the beginning of the relationship between customers and Case New Holland. Acting as a business partner with our customers, CNH plays an active role in providing the right after-sales parts, service and support from the factory, both at the dealership and in the field.

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.

2.6 Major Milestones

1996 New Holland India established.

1997 Ground Breaking Ceremony of the Plant at Greater Noida.

1998 Inauguration of Training center

New Holland India launched the 5630 (70 HP Tractor)

28

Page 29: Project Report

1999 Plant Inauguration and Launch of 50 HP tractor New Holland 3630

2001 New Holland 3230 (42 HP Tractor) launched

2002 New Holland 3030 (35 HP Tractor) launched

2003 New Holland 3630 TX – 55 HP Launched

2005 Launched 3630 TX+, 3130, 3600 and 5500 & 7500 models in both 2 wheels and 4 wheel drive version.

2007 New Holland NX Series(35hp, 40Hp and 45 Hp category) launched

2008 100,000th Tractor Rolled Out. 3037 NX model launched

2.7 Products of the Company

New Holland offers a wide range of products in the industry ranging from Tractors, Harvesting equipment to hay equipment and supporting attachments. It manufactures tractors ranging from 30 to 75 HP for the Indian market. One of its leading products is the newly launched sugarcane harvester which has been awarded great acclaims from the agricultural community.

Products are of following categories:

1. Agricultural tractors - for Indian market (ranging from 30 to 75 HP)

for International market

2. Harvesting Equipments

3. Hay & Forage Equipment

29

Page 30: Project Report

4. Supporting Attachment

2.8 Present Status of Organisation

New Holland Agriculture , a subsidiary of the FIAT group is one of the major manufacturers of agricultural Equipments in the world today. Competing with other players such as Mahindra & Mahindra, Tractors and Farm Equipment’s Ltd.(TAFE), Sonalika, Punjab Tractor Ltd.(PTL), in India, New Holland has come to earn its reputation as one of the finest manufacturers of agricultural Equipment’s with promise of great reliability and superior performance, the products offered by the company are second to none in quality and service.

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.

Armed with some of the latest CAD tools and CNC, 5the factory has an excellent machining center. Its CED equipment provides high quality

30

Page 31: Project Report

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.

Completely built tractors are manufactured in the state-of-the-art Greater Noida plant are being exported to over 51countries in Asia, Africa and Middle East, Australia, New Zealand, Latin America and North America. The plant is spread in 60 acres in an area of 30,000sq.m with an installed capacity of 30,000 units. They are a growing family of 1200 manpower and more. They have distribution network of about 3,000 dealers to ensure the customers in 160 countries receive best purchasing advice, products and services. They have built solid reputation for quality by being the First Tractor Company in INDIA to get ISO 9001:2000 along with ISO 14001:2004 Quality Certifications. On July 21st, 2008 they rolled out their 100,000th tractor at New Holland Tractors facility, near New Delhi.

Their mission is to continuously create superior value for their customers, shareholders, employees and business partners, by together building and growing a sound business network in India, and achieving industry leadership and world class standards in both products and processes. They value innovation, dynamism and smartness. The company has focused its strength in agricultural mechanization to build a world-class tractor company in India.

31

Page 32: Project Report

Chapter Chapter

Statement of Work3.1 CBU Components

3.2 Design Process

3.3 Architectural Goals

32

Page 33: Project Report

3.1 CBU Components

CBU systems can vary significantly in their user configuration depending on a type of users. Administrator provides the access permissions to the users according to their standing levels. The user configuration includes the type of users as follows:

Administrator CBU Manager Finance Dealer

CBU systems rely on a number of common components or processes. The following list includes many of the potential components and processes seen typically:

Website design and hosting Firewall configuration and management Network administration Security management CBU server E-commerce applications (e.g., AOP, MOP, Sales Order) Internal network servers Core processing system Automated decision support systems

33

Page 34: Project Report

These components work together to deliver CBU services. Each component represents a control point to consider. Through a combination of internal and outsourced solutions, management has many alternatives when determining the overall system configuration for the various components of an CBU system. While the company does not have to manage the daily administration of these component systems, its management and board remain responsible for the content, performance, and security of the CBU system.

3.2 Design Process

The main purpose of this application is to do the data analysis and

reporting 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.

As a part of the design methodology used for developing the application,

following steps were carried out.

Identification of Database level parameters

This involves identification of the following items:

Servers - single server application

Server IP Address or DNS name for mails with URLs

Path – Dependencies on File Path

Title – A meaningful title for the database for easy identification

and categorization in database catalog

Identification of User Screens

34

Page 35: Project Report

This involves identification of the following items:

Actions for users depending on role for each form

Validation logic

Form Aliases

Form Level Security

Process for the file de-attachment

3.3 Architectural Goals

The architecture goals for the application could be outlined as follows:

Enforce Reusability to develop reusable, reliable and tested

components, which can be improved incrementally.

Decompose functionality to facilitate modularity and better

maintainability.

To ensure that all dependencies on external system can either be

configured without changes to code base or little bit changes to

code base. Also to ensure that all URLs are relative and not

include either the server or the file path of the database.

Ensure extensibility to support addition of new functionality to

keep up with business growth. Provide for Concurrent access by

multiple users to different parts of the application.

Enforce security to protect sensitive data.

35

Page 36: Project Report

Chapter Chapter

Project Plan4.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

36

Page 37: Project Report

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

The figure below shows the modular structure of CBU System:

4.2 Processor Logic for Modules

37

MastersTransactions

Reports BI Reports

CBU

System

Page 38: Project Report

Master Module (MM) Transactions (TM) Reports (RM) BI Reports (BIRM)

1. Master Module (MM)

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:

Zone Master: -

Reporting view of all the zones in to which company deals. Insert additional zone if required.

CBU Master: -

38

Page 39: Project Report

Detailed view of all CBUs. Insert additional CBU in particular zone as per requirement.

Dealer Master: -

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.

2. Transaction Module (TM)The Transaction Module lists all the annually and monthly plan of the organization. This module places the payment, sales, customer feedback, service, dealer incentive plan sub-modules. This module enlisted with all the transaction record of the products of the organization.

Transaction Services

Following Transaction services will be provided through CBU System: -

Annual Operating Plan (AOP) Locking Status Dealer Payment Event Planning Field Activity Dealer Payment Details Customer Feedback

39

Page 40: Project Report

Sales Order Approval

3. Report Module (RM)

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

40

Page 41: Project Report

Field Services Model Feedback Dealer Details Market Share etc.

4.3 Technical Facts

Microsoft .NET Compact Framework

.NET compact framework is a sub set of entire .NET framework and is targeted at mobile devices having some client side resources. It provides support for managed code and XML Web services. Currently, .NET Compact Framework is in Beta 1 and is available on devices running the Windows CE or Windows CE .NET operating systems. However, Microsoft has promised support for other platforms in the future. As of now the framework supports Visual Basic.NET and C# as development languages out of the box. Support

41

Page 42: Project Report

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 wonderfulplatform for developing modern applications.

• Rich Functionality out of the box.NET framework provides a rich set of functionality out of the box. It contains hundreds of classes that provide variety of functionality ready to use in your applications. This means that as a developer you need not go into low level details of many operations such as file IO, network communication and so on.

• Easy development of web applicationsASP.NET is a technology available on .NET platform for developing dynamic and data driven web applications. ASP.NET provides an event driven programming model (similar to Visual Basic 6 that simplify development of web pages (now called as web forms) with complex user interface. ASP.NET server controls provide advanced user interface elements (like calendar and grids) that save lot of coding from programmer’s side.

• OOPs SupportThe 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++.

• Multi-Language SupportGenerally 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

42

Page 43: Project Report

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 SupportModern 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.

• Automatic memory managementWhile developing applications developers had to develop an eye on system resources like memory. Memory leaks were major reason in failure of applications. .NET takes this worry away from developer by handling memory on its own. The garbage collector takes care of freeing unused objects at appropriate intervals.

• Compatibility with COM and COM+Before the introduction of .NET, COM was the de-facto standard for componentized software development. Companies have invested lot of money and efforts in developing COM components and controls. The good news is – you can still use COM components and ActiveX controls under .NET. This allows you to use your existing investment in .NET applications. .NET still relies on COM+ for features like transaction management and object pooling. In fact it provides enhanced declarative support for configuring COM+ application right from your source code. Your COM+ knowledge still remains as a valuable asset.

• No more DLL HellIf you have worked with COM components, you probably are aware of “DLL hell”. DLL conflicts are a common fact in COM world. The main reason behind this was the philosophy of COM – “one version of component across machine”. Also, COM components require registration in the system registry. .NET ends this DLL hell by allowing applications to use their own copy of dependent DLLs. Also, .NET components do not require any kind of registration in system registry.

• Strong XML support

43

Page 44: Project Report

Now days it is hard to find a programmer who is unaware of XML. XML has gained such a strong industry support that almost all the vendors have released some kind of upgrades or patches to their existing software to make it “XML compatible”. Currently, .NET is the only platform that has built with XML right into the core framework. .NET tries to harness power of XML in every possible way. In addition to providing support for manipulating and transforming XML documents, .NET provides XML web services that are based on standards like HTTP, XML and SOAP.

• Ease of deployment and configurationDeploying windows applications especially that used COM components were always been a tedious task. Since .NET does not require any registration as such, much of the deployment is simplified. This makes XCOPY deployment viable. Configuration is another area where .NET – especially ASP.NET – shines over traditional languages. The configuration is done via special files having special XML vocabulary. Since, most of the configuration is done via configuration files, there is no need to sit in front of actual machine and configure the application manually. This is more important for web applications; simply FTPing new configuration file makes necessary changes.

• SecurityWindows 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.

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.

Constituents of .NET PlatformThe .NET consists of the following three main parts

44

Page 45: Project Report

• .NET Framework – a completely re-engineered development environment.• .NET Products – applications from MS based on the .NET platform, including Office and Visual Studio.• .NET Services – facilitates 3rd party developers to create services on the .NET Platform.

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)

My work comprises of understanding the requirements of the user (through URS), and developing application code for the same using Microsoft Visual Studio with backend as SQL Server 2008. I am also handling the work of developing Front Page Menus & Buttons.

45

Page 46: Project Report

Development of HLD & LLD for enhancements

Requirement Analysis &

Specification

Design(HLD & LLD)

Construction

Integration Testing

System Testing

User Acceptance

Capturing & specifying Project Requirements

Developing application code & Unit Testing

eveloping application code & Unit Testing

4.5 Development Methodology

This project has been based on the Iterative Water Fall model.

1) Requirement Analysis and Specification:It involves the taking requirements from the Client as well as specifying requirements formally in documents for each module.

2) Design (High-level design & Low-level design):It involves the designing the High-level documents for the module and in-depth Structure of all the components of the module. This includes the diagram of the components. Field Mapping with the Database and I/O specifications.

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.

46

Page 47: Project Report

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.

7) User Acceptance:Finally user acceptance testing takes place to make sure that user is ready to accept the application.

4.6 Project Mentors

Project Manager:Mr. Deepak Kumar

Team Leader: Ms Neha Mishra

Team Size: 6 members

Chapter Chapter

Soft. Requirements and Specifications5.1 Introduction

5.2 General Description

5.3 Specific Requirements

47

Page 48: Project Report

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

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

48

Page 49: Project Report

process. The developer is responsible for asking for clarifications wherever necessary.

5.1.3 Developer’s Responsibilities Overview

The developer is responsible for

Developing the system Installing the software on the client’s hardware Conducting any user training if needed for the proper operation of the system

5.2 General Description

5.2.1 Product Perspective

CBU System product is the subsidiary of the NHT Applications launched by NHT Greater Noida. This product when merged with New Holland Tractor (NHT) and other related products will constitute the overall NHT solution which will fully automate all the operations of the NHT.

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.

5.2.3 User Characteristics

49

Page 50: Project Report

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.2.4 General Constraints

The system should run on windows based environment.

5.3 Specific Requirements

5.3.1 Functional Requirements

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.

50

Page 51: Project Report

Fig: Desired output as per requirement

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.

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.

51

Page 52: Project Report

Fig: Desired output as per requirement

5. The users should be able to view the MOP daywise plan for their term Plan Reports.

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.

52

Page 53: Project Report

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.

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.

53

Page 54: Project Report

Fig: Desired output as per requirement

12. The user should be able to add his MOP-Daywise Plan according to his cbu zone

Fig: Desired output as per requirement

13. 1 The user should be able to view MOP according to dealer and model wise.

54

Page 55: Project Report

Fig: Desired output as per requirement

13.2 And he should be able to edit the details and can add new variant by clicking on the dealer code link.

Fig: Desired output as per requirement

55

Page 56: Project Report

14. The customer should be able to give his feedback about the product he purchased.

Fig: Desired output as per requirement

15. The user should be able to update his monthly plan collection.

Fig: Desired output as per requirement

56

Page 57: Project Report

16. The user should be able to view his YTD and MTD collection.

Fig: Desired output as per requirement

Fig: Desired output as per requirement

17. The user should be able to view monthly dashboard of payment collection, dispatched stock and outstanding.

57

Page 58: Project Report

Fig: Desired output as per requirement

18. The user should be able to view report about sales order status wise.

Fig: Desired output as per requirement

19. The user should be able to the stock aging of depots and plant.

58

Page 59: Project Report

Fig: Desired output as per requirement

20.The user should be able to view his market-share of all months in the current and previous year.

5.3.2 User interface

CBU System would provide windows based graphical user interface to be designed using Excellent debugging tools, Integration with version control software such as Visual Source Safe (VSS) and Drag and Drop design.

Users will be provided with reports during their session. Users can

download their report statements. User interface will comply with

functional coverage, design standards and conventions, etc.

Benefits of CBU user interface are:

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:

59

Page 60: Project Report

Pentium IV 1.2 GHz 512 KB Cache 512 MB RAM VGA card with 512 MB built-in RAM 40 GB Hard Disk 101 Keyboard 15” SVGA Color Monitor 1 Parallel and 2 Serial Ports Ethernet card (10/100 Mbps)

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.

ChapterChapter

System Analysis and Design6.1 Proposed System

6.2 System Architecture

6.3 Context Flow Diagram

6.4 Database Design

60

Page 61: Project Report

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

6.2 System Architecture

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

61

Page 62: Project Report

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) 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

62

Page 63: Project Report

This layer represents the data storage and data access features, and will

host SQL Server 2008 consisting of physical database and logical objects

like tables, views, indices, procedures, etc.

The Data Source layer will be responsible for:

Storage of data

Retrieval of data

Maintenance of data

Integrity of data

Layers are independent of each other.

63

Page 64: Project Report

This three-tier architecture offers several advantages:

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.

64

Page 65: Project Report

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.

6.3 Context Diagram

65

Page 66: Project Report

66

Page 67: Project Report

6.4Database Design

6.4.1Table Structure

Table Name: NHI_LOGIN_COPY

Column Name Data Type Allow Null PK FK

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

Table Name: TM_CBU

Column Name Data Type Allow Null PK FK

MCBU_CBUCode varchar(50) N Y N

67

Page 68: Project Report

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 YN 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

MCBU_ModifiedOn datetime Y N N

68

Page 69: Project Report

Table Name: TM_DEALER

Column Name Data Type Allow Null PK FK

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

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

69

Page 70: Project Report

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

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

70

Page 71: Project Report

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

Table Name: TM_LOCATION

Column Name Data Type Allow Null PK FK

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

71

Page 72: Project Report

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

Table Name: TM_MODEL

Column Name Data Type Allow Null PK FK

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

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

72

Page 73: Project Report

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

MMOD_Category varchar(50) Y N N

Table Name: TM_ZONE

Column Name Data Type Allow Null PK FK

ZoneCode varchar(20) N Y N

ZoneName varchar(20) N N N

Description varchar(50) Y N N

CreatedBy varchar(20) Y N N

73

Page 74: Project Report

CreatedOn datetime Y N N

Active char(10) Y N N

Table Name: DEALER_PAY_DETAILS

Column Name Data Type Allow Null PK FK

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

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

74

Page 75: Project Report

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

Table Name: DISPTCH_DETAILS_SALES

Column Name Data Type Allow Null PK FK

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

75

Page 76: Project Report

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

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

76

Page 77: Project Report

ModeOfTransport varchar(30) Y N N

CancellationRef nvarchar(50) Y N N

ModifiedBy varchar(30) Y N N

ModifiedOn datetime Y N N

Table Name: CB_COLLECTION_PLAN

Column Name Data Type Allow Null PK FK

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

Table Name: CB_DISPATCH_PLAN

Column Name Data Type Allow Null PK FK

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

77

Page 78: Project Report

Chapter Chapter

Testing7.1 Objective And Scope

7.2 Testing Methodology

7.1 Objective And Scope

78

Page 79: Project Report

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.

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

o This would include selected Business Functionality to be tested for the Client.

79

Page 80: Project Report

Figure: Levels of Testing

7.2 Testing Methodology (ATLM)

80

Page 81: Project Report

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.

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.

81

Page 82: Project Report

Phase 2: Test Tool Acquisition

Test tool acquisition represents the second phase of the ATLM. This phase guides the test engineer through the entire test tool evaluation and selection process, starting with confirmation of management support. Since a tool should support most of the organizations' testing requirements, whenever feasible the test engineer will need to review the system's engineering environment and other organizational needs and come up with a list of tool evaluation criteria. A review of the different types of tools available to support aspects of the entire testing lifecycle is provided in Automated Software Testing. The test engineer then needs to define an evaluation domain to pilot the test tool. Finally, after all those steps have been completed, the test engineer can make vendor contact to bring in the selected tool(s). Test personnel then evaluate the tool, based on sample criteria provided.

Phase 3: Automated Testing Introduction Process

The process of introducing automated testing to a new project team constitutes the third phase of the ATLM. This phase outlines the steps necessary to successfully introduce automated testing to a new project, which are summarized in the following sections.

a) Test Process Analysis

During the test process analysis, techniques are defined. Best practices are laid out, such as conducting performance testing during the unit-testing phase.

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

82

Page 83: Project Report

workaround solutions are investigated for incompatibility problems that surfaced during compatibility tests.

Phase 4: Test Planning, Design, and Development

Test planning, design, and development is the fourth phase of the ATLM. These subjects are summarized in the following sections.

a) Test Planning

The test planning stage represents the need to review long–lead-time test planning activities. During this phase, the test team identifies test procedure creation standards and guidelines; hardware, software, and network required to support test environment; test data requirements; a preliminary test schedule; performance measure requirements; a procedure to control test configuration and environment; as well as defect-tracking procedure(s) and associated tracking tool(s).

The test plan contains the results of each preliminary phase of the structured test methodology (ATLM). The test plan will define roles and responsibilities, project test schedule, test planning and design activities, test environment preparation, test risks and contingencies, and acceptable level of thoroughness (test acceptance criteria).

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.

Table: Test Procedure Design Process

Step Description

1 Test Architecture Review. The test team reviews the test architecture in order to identify the test techniques that apply.

2 Test Procedure Definition (Development Level). A test procedure definition is constructed at the development test level, identifying the test procedure series that applies for the various design components and test techniques.

83

Page 84: Project Report

3 Test Procedure Definition (System Level). A test procedure definition is constructed at the system test level, identifying the test procedure series that applies for the various test techniques.

4 Test Procedure Design Standards. Design standards are adopted and a unique naming convention is adopted that distinguishes the test procedures on the project from test procedures developed in the past or on other projects.

5 Manual Versus Automated Tests. Test procedures will be depicted as being either performed manually or as part of an automated test.

6 Test Procedures Flagged for Detailed Design. Test procedures that stand out as more sophisticated are flagged. These test procedures are further defined as part of detailed test design.

7 Detailed Design. Those test procedures flagged as part of step 7 are 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.

8 Test Data Mapping. Test procedure matrix is modified to reflect test data requirements for each test procedure.

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.

Table: Development/Test Relationship

Phase Development Process

Test Process

Module (Unit) Design module Perform test planning and test environment

84

Page 85: Project Report

Development from requirements.

setup.

Code module. Create test design and develop test data.

Debug module. Write test scripts or record test scenario using module.

Unit test module.

Debug automated test script by running against module. Use tools that support unit testing.

Correct defects. Rerun automated test script to regression test as defects are corrected.

Conduct performance testing.

Verify that system is scalable and will meet performance requirements.

Integration Build system by connecting modules.

Integration-test connected modules.

Review trouble reports.

Combine unit test scripts and add new scripts that demonstrate module interconnectivity. Use test tool to support automated integration testing.

Correct defects and update defect status.

Rerun automated test script as part of regression test, as defects are corrected.

Continued performance testing activities.

Verify that system is scalable and will meet performance requirements.

System Test Review trouble reports.

Integrate automated test scripts into system-level test procedures where possible, and develop additional system-level test procedures. Execute system test and record test results.

Correct defects and update defect status.

Rerun automated test script as part of regression test as defects are corrected.

85

Page 86: Project Report

Acceptance Test

Review incident reports.

Perform subset of system test as part of demonstration of user acceptance test.

Correct defects. Rerun automated test script as part of regression test as defects are corrected.

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.

Phase 5: Execution and Management of Tests

The various steps involved during execution and management of tests are outlined below.

When executing test procedures, the test team needs to comply with a test procedure execution schedule. Following test execution, test outcome evaluations are performed and test result documentation is prepared.

Plans for unit, integration, system, and user acceptance testing are executed, which together make up the steps that are required to test the system as a whole.

Integration testing is performed, which focuses on the application internals.

During system test, the test engineer tests the integration of parts that comprise the entire system. A separate test team usually performs system-level tests.

The test team also performs analysis to identify particular components or functionality that are experiencing a greater relative number of problem reports. Test results analysis can also confirm whether executed test procedures are proving to be worthwhile in terms of identifying errors.

Each test team needs to perform problem-reporting operations in compliance with a defined process. The documentation and tracking of software problem reports is greatly facilitated by an automated defect-tracking tool.

The test team manager is responsible for ensuring that tests are executed according to schedule, and test personnel are allocated and redirected when necessary to handle problems that arise during the test effort.

86

Page 87: Project Report

Phase 6: Test Program Review and Assessment

Test program review and assessment activities are conducted throughout the testing lifecycle, to allow for continuous improvement activities. The 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 Chapter

87

Page 88: Project Report

Conclusion

88

Page 89: Project Report

CONCLUSION DRAWN

The industrial training that I underwent was truly a rewarding experience for me in more than one way. It not only gave a big thrust to my technical knowledge as prospective software professional but also helped me to enhance my skills on the personal front.

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.

I truly gained an insight into the working of the real web-based systems. This was even more rewarding as it was a typical real world situation. This project has strengthened my knowledge of Java Technology and other web-based tools.

EBS is an innovative Banking initiative that aims at continuously repositioning banking as an organization capable of fulfilling the aspirations of its customers in the present scenario. EBS will automate the various functions and activities of the bank through Internet. The solution will facilitate to the bank employees and the account holders with the different modules.

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.

89

Page 90: Project Report

REPORTING SERVICES

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

90

Page 91: Project Report

reporting platform with a comprehensive environment for authoring, managing, and delivering reports to the entire organization.

GET STARTED WITH SQL SERVER REPORT GENERATING SYSTEM

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;

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;

91

Page 92: Project Report

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 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;

92

Page 93: Project Report

2. Next we select the <New Dataset> option in the dataset bar and the window looks like as follows;

3. Name the dataset, and click on the edit button near connection string. On doing so, a new window pops up;

93

Page 94: Project Report

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;

94

Page 95: Project Report

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.

9. Now, if we click the Run button, the specified query is executed. For example,

95

Page 96: Project Report

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.

96

Page 97: Project Report

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

12. Now, we fill the required information from the database option given below the toolbar option. Our layout is ready.

13. Finally, we click on the preview option and the report is generated.

97

Page 98: Project Report

14. On making changes in the properties of the table in the layout section, we can give our report a better look.

LINKED REPORTS

98

Page 99: Project Report

A linked report is a report server item that provides an access point to an existing report. Conceptually, it is similar to a program shortcut that you use to run a program or open a file. A linked report is derived from an existing report and retains the original's report definition. A linked report always inherits report layout and data source properties of the original report. All other properties and settings can be different from those of the original report, including security, parameters, location, subscriptions, and schedules. You can create a linked report when you want to create additional versions of an existing report. For example, you could use a single regional sales report to create region-specific reports for all of your sales territories. Although linked reports are typically based on parameterized reports, a parameterized report is not required. You can create linked reports whenever you want to deploy an existing report with different settings. It must be noted that the initial steps to create a linked report is exactly similar to a parameterized report. It must also be noted that a linked report can be made only after the deployment or publishing of the report. Given below are the steps one should use to deploy a report and then create a linked report.

1. Once the report is viewed in the preview section, go to the solution explorer tab and right click on the project name and select properties. The property page of the project will be seen, as shown.

2. In the TargetServerURL column, write the URL address, and select OK.

99

Page 100: Project Report

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.

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.

100

Page 101: Project Report

6. Fill in the required information and click Create Linked Report. The linked report is created.

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

101

Page 102: Project 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.

2. In the layout section, design the reports.

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.

102

Page 103: Project Report

5. In the preview section, right click on the first report and select build. Do the same with the second report.

6. Deploy the two in the same way (as discussed before).

7. In the preview section, when you click on the column that is drilled down, the next hidden report is shown.

103

Page 104: Project Report

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.

104

Page 105: Project Report

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.

105

Page 106: Project Report

2. A window opens up, select ASP.NET Web Site.

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.

106

Page 107: Project Report

4. In the tool box, select the report viewer, and click on the report viewer that appears on the design window.

5. The code window opens up, where we can add more specifications, like parameters, default values, buttons etc.

107

Page 108: Project Report

6. Finally, on executing this, one can see the integrated report on the server.

CONCLUSION

108

Page 109: Project Report

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 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.

109