Introduction

Enterprise Software – Definition and need of the hour

Enterprise Level Application
Different types on Enterprise Software
Growth Of an enterprise software
IT Department in a enterprise
Complexity of IT department
The Legacy System
Enterprise resource planning
Definition
It is a Set of interconnected modules to run the
Financials, product lifecycle management, Supply
chain management (e.g. Purchasing, Manufacturing
and Distribution), Warehouse Management,
Customer Relationship Management (CRM), Sales
Order Processing, Online Sales, Human Resources
and other major functions of a typical MNC.
What ERP holds….
ERP delivers a single database that contains all data for
the various software modules that typically address most
of the business areas
Order tracking, from acceptance through fulfilment
Managing inter-dependencies of complex processes bill of
materials
The accounting for all of these tasks: tracking the revenue,
cost and profit at a granular level
Security-Reduces the risk of loss of sensitive data by
consolidating multiple permissions and security models
into a single structures
Problem Area’s
ERP systems are very expensive- $15 million on an
average ,and many large companies have spent tens
and even hundreds of times that !!!
Concept of single monolith system is not valid in the
era of mergers and acquisitions….
Contrary to belief, it’s more like a calculator than a
“thinking machine”….
 ERPs are often seen as too rigid and too difficult to
adapt to the specific workflow and business process of
some companies..
Re-engineering of business processes to fit the
"industry standard" prescribed by the ERP system
may lead to a loss of competitive advantage

The risks and costs involved in changing it…

The Vagaries of Data
Problems with growing data-errors

Problems in integration of multiple data sources

Unexpected bugs creeping in with increase in

complexity
SERVICE ORIENTED ARCHITECTURE
A service-oriented architecture is essentially a
collection of services. These services communicate
with each other. The communication can involve
either simple data passing or it could involve two or
more services coordinating some activity.

The .Net technology introduces the SOA by mean of

web services.
SERVICE ORIENTED ARCHITECTURE
A SOA Proposes to overcome the problems involved
with updating and changing legacy systems by
building modular cross-system business processes
Service Orientation leads to separation of concerns
Modularity of programming
Loose coupling of service with OS & Other
technologies that underlie application
SOA separates functions into distinct units allows
users to reuse them in the production of applications.
SOA implementation rely on a mesh of software
services. Services comprise unassociated, loosely
coupled units of functionality that have no calls to
each other embedded in them.
The great promise of SOA suggests that the marginal
cost of creating the Nth application is low.
SOA helps business respond more quickly and
cost effectively

It is regarded as an architectural evolution rather

than revolution
Problems associated with SOA
Most Companies are in early Stages of a Four part
transformation to SOA that may take many years to
realize
“Complexity a deadly software killer”