the trouble with enterprise software

8/8/2019 The Trouble With Enterprise Software

http://slidepdf.com/reader/full/the-trouble-with-enterprise-software 1/16



Introduction

y Enterprise Software Definition and need of the hour

y Enterprise Level Applicationy Different types on Enterprise Software

y Growth Of an enterprise software



y IT Department in a enterprise

y Complexity of IT department

y The Legacy System



Enterprise resource planningy Definition

It is a Set of interconnected modules to run theFinancials, product lifecycle management, Supply chain management (e.g. Purchasing, Manufacturingand Distribution), Warehouse Management, Customer

Relationship Management (CRM), Sales OrderProcessing, Online Sales, Human Resources and othermajor functions of a typical MNC.



What ERP holds.y ERP delivers a single database that contains all data for the

various software modules that typically address most of thebusiness areas

y Order tracking, from acceptance through fulfilmenty Managing inter-dependencies of complex processes bill of

materials

y The accounting for all of these tasks: tracking the revenue,

cost and profit at a granular levely Security-Reduces the risk of loss of sensitive data by

consolidating multiple permissions and security modelsinto a single structures



Problem Areasy ERP systems are very expensive- $15 million on an

average ,and many large companies have spent tens andeven hundreds of times that !!!

y

Concept of single monolith system is not valid in theera of mergers and acquisitions.

y Contrary to belief, its more like a calculator than athinking machine.

y

ERPs are often seen as too rigid and too difficult toadapt to the specific workflow and business process of some companies..



y

Re-engineering of business processes to fit the"industry standard" prescribed by the ERP system may lead to a loss of competitive advantage

y The risks and costs involved in changing it



The Vagaries of Datay Problems with growing data-errors

y Problems in integration of multiple data sources

y Unexpected bugs creeping in with increase in

complexity



SERVICE ORIENTED ARCHITECTUREy A service-oriented architecture is essentially a

collection of services. These services communicate with each other. The communication can involveeither simple data passing or it could involve two ormore services coordinating some activity.

y The .Net technology introduces the SOA by mean of web services.



SERVICE ORIENTED ARCHITECTUREy A SOA Proposes to overcome the problems involved

with updating and changing legacy systems by building modular cross-system business processes

y Service Orientation leads to separation of concerns

y

Modularity of programmingy Loose coupling of service with OS & Other

technologies that underlie application



y SOA separates functions into distinct units allowsusers to reuse them in the production of applications.

y SOA implementation rely on a mesh of softwareservices. Services comprise unassociated, loosely coupled units of functionality that have no calls toeach other embedded in them.

y The great promise of SOA suggests that the marginalcost of creating the Nth application is low.



y SOA helps business respond more quickly and cost

effectively

y It is regarded as an architectural evolution ratherthan revolution



Problems associated wit

h S

OAy Most Companies are in early Stages of a Four parttransformation to SOA that may take many years torealize

y

Complexity a deadly software killer

the trouble with enterprise software

Documents