> Archive > Issue XVII: April 2008

Issue XVII April 2008

Relating Master Data Management to SOA

Chris Madrid

Chris Madrid

Distributed application development has proliferated business data throughout the enterprise. Customer information is frequently spread across financial information systems (FIS), enterprise resource planning (ERP) systems, customer relationship management (CRM) systems, sales automation systems, Web applications, and interactive voice response (IVR) systems. Complex enterprise application integration (EAI) solutions have been erected to keep these data silos synchronized. The resulting web of dependencies has adversely affected enterprise agility. Many enterprise architects assumed that by merely adopting SOA these complexities would be magically abstracted and a method for seamlessly aggregating this data for consumption would manifest itself by an actionable interface like a call center application or a customer self-service portal. However, it turns out that for many large IT operations challenges such as variations in data quality, differing primary keys, and multiple systems of record have created a situation where real-time aggregation of data is impractical. Master Data Management (MDM) has emerged in the last few years as...

SOA in Healthcare - Part I

Girish Juneja, Blake Dournaee, Joe Natoli, Steve Birkel

Girish Juneja
Blake Dournaee
Joe Natoli
Steve Birkel

Healthcare organizations today are challenged to manage growing portfolios of systems and applications. The cost of acquiring, integrating, and maintaining these systems is rising, while end-user demands are increasing. Furthermore, evolving clinical requirements need to be continually accommodated along with the required support for revenue cycle and administration business functions. In addition to all these factors, there are increased demands for enabling interoperability between other healthcare organizations to regionally support care delivery. SOA offers system design and management principles in support of the reuse and sharing of system resources across that are potentially very valuable to a typical healthcare organization, especially considering that SOA often does not require the reengineering of existing systems. For example, the application of service-orientation allows existing processing logic to be combined with new capabilities in order to build a library of services that can then be used as the basis for many different solutions. This two part article based on excerpts from the book "SOA Demystified" explores how healthcare organizations can leverage shared services to automate multiple business processes and strengthen overall interoperability while reducing the need to synchronize data between isolated systems. Services may be made available, no matter their location, to create solutions that reach beyond the desktop, the department, and the healthcare organization as a whole. A healthcare organization that depends upon a single system across the entire enterprise to support various departmental and care delivery needs, often already has a solution that shares and reuses system resources. Here are some typical characteristics of such an organization:...

A Program Management Methodology for SOA

James P. Lawler

James P. Lawler

Program management is a key part of any successful IT project. With SOA, the management of a "program of related projects" is often required when carrying out larger adoption initiatives. But even when your SOA project revolves around just a single solution, the management of the delivery of that solution should be part of a formal program. In this article we describe a disciplined program management methodology [REF-1] for organizations attempting SOA projects. The approaches discussed are complementary to and build upon many established project management methodologies. As part of the research carried out for this article, we analyzed 15 Fortune 10-1000 firms, with a focus on service deployment, integration of process and services architecture, and required organizational restructuring. Our findings confirm that organizations leading SOA projects with procedural and business requirements have more success than those leading their projects with technical functionality. (The results of this study are provided at the end of this article.) The need for an SOA-specific program management methodology emerged from the challenges and...

2017 2016 2015 2014 2013 2012 2011 2010 2009 2008 2007 2006