Topic Overview: Service-Oriented Architecture For Apps Dev And Program Management Pros

For a single, isolated solution delivery project, it's OK to think of service-oriented architecture (SOA) as just Web services (WS) standards for better application integration: Your application needs something from another one, and WS technology bridges the boundaries. However, across a portfolio of solutions, this view of SOA breaks down and can easily result in siloed, point-to-point Web services that solve only short-term, project-level problems. Longer-term application delivery benefits from SOA — for example, reduced time-to-market and lower development costs — require cross-project, portfolio-level strategy and planning. SOA is proven in the market — for the past three years, 70% of current SOA users have said they will do more SOA — but getting it right requires developers to step back and ensure that they truly understand how to think correctly about what SOA is and how it will add value.

For the Research Report:

Service-Oriented Architecture For Apps Dev And Program Management Pros


SOURCE: Forrester Research
_______________________________________________________________________________

For more resources on Service-Oriented Architecture see: THE SOA NETWORK

 
_______________________________________________________________________________

Back to Main Page

Project-Oriented SOA

Abstract: "Projects are the lifeblood of an IT department. Almost everything in IT is measured through a project lens. SOA, due to its global-centric nature, is often viewed as incompatible with project-based software delivery lifecycles. Thus, most companies find themselves with the dilemma of how to effectively advance an SOA initiatives and continue to deliver projects at the same time.

The solution is to combine service lifecycle management, architecture, SOA governance, funding, and SOA metrics into a single comprehensive program. The ultimate goal is to ensure that through addressing project needs services are being effectively designed and implemented and that leverage takes place and is verifiable and that the overall SOA program objectives are being achieved. This article introduces an effective technique for moving your SOA program forward through an incremental, project-based approach."


For the complete article:

http://www.soamag.com/I21/0808-2.asp


SOURCE: SOA Magazine
_______________________________________________________________________________

For more resources on Service-Oriented Architecture see: THE SOA NETWORK

 
_______________________________________________________________________________

Back to Main Page

Only 1 in 5 SOA Projects Actually Succeed

...in-depth studies of 20 companies found a 50% complete failure rate, while another 30% were considered neither successful nor wholly failed... Many of them had deployed multiple successful projects, but most of those projects were focused on just one integration problem. It was just a bunch of Web services... The service is only built for one application and it’s never going to be used again

For the complete article:

 http://www.infoq.com/news/2008/07/Only1


SOURCE: InfoQ

_______________________________________________________________________________

For more resources on Service-Oriented Architecture see: THE SOA NETWORK

 
_______________________________________________________________________________

Back to Main Page

IT RESOURCE NETWORK 

THE BPM NETWORK | THE SAAS NETWORK | THE SOA NETWORK | THE WEB 2.0 NETWORK

THE SOA NETWORK
SOA Governance | SOA Management | SOA Networking | SOA Security | SOA Identity | SOA Test

SOA Verticals
SOA Finance | SOA Government | SOA Healthcare | SOA Insurance 
 SOA Manufacturing | SOA Retail | SOA Telecom | SOA Utilities

A Program Management Methodology for SOA

Abstract: 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.)


For the complete article:

http://www.soamag.com/I17/0408-3.asp

SOURCE: SOA Magazine

______________________________________________________________________

For more resources on Service-Oriented Architecture see: THE SOA NETWORK

 
_______________________________________________________________________________

Back to Main Page

IT RESOURCE NETWORK 

THE BPM NETWORK | THE SAAS NETWORK | THE SOA NETWORK | THE WEB 2.0 NETWORK

THE SOA NETWORK
SOA Governance | SOA Management | SOA Networking | SOA Security | SOA Identity | SOA Test

SOA Verticals
SOA Finance | SOA Government | SOA Healthcare | SOA Insurance 
 SOA Manufacturing | SOA Retail | SOA Telecom | SOA Utilities

A New Foundation: SOA Implementation for Business Transformation

"It wasn't just small changes that Wachovia's Corporate and Investment Banking (CIB) division was eyeing when it first looked to deploy a service-oriented architecture (SOA). Rather, it was a total transformation resulting from a mandate from the division's head to create a business-aligned IT group, according to Tony Bishop, SVP and director of product management for the CIB technology group."

A New Foundation: SOA Implementation for Business Transformation


SOURCE: Wall Street Technology

______________________________________________________________________

For more resources on Service-Oriented Architecture see: THE SOA NETWORK

 
_______________________________________________________________________________

Back to Main Page

IT RESOURCE NETWORK 

THE BPM NETWORK | THE SAAS NETWORK | THE SOA NETWORK | THE WEB 2.0 NETWORK

THE SOA NETWORK
SOA Governance | SOA Management | SOA Networking | SOA Security | SOA Identity | SOA Test

SOA Verticals
SOA Finance | SOA Government | SOA Healthcare | SOA Insurance 
 SOA Manufacturing | SOA Retail | SOA Telecom | SOA Utilities

Rule #1: The requirements for SOA-based development projects should focus first and foremost on the delivered applications, not the services.

Rule #2: Services should be re-used, re-factored, used from a third party where appropriate and built new only as a last resort.

Rule #3: Services need to be delivered with a comprehensive set of unit tests.

Rule #4: Always perform consumption-side tests before deploying a service into production.

Rule #5: Separate your production deployments from your consumption deployments.


For the complete article:

Five Rules for Development-time SOA Governance


SOURCE: Enterprise Systems

________________________________________________

>> Back to Main Page

Gary E. Smith
SOA Project Manager

Roles for Maintenance and Evolution of SOA-Based Systems

Development, evolution and maintenance of SOA-based systems demands rethinking of the traditional system evolution and maintenance roles. The key objective of this paper is to present preliminary ideas on the roles required for maintenance and evolution of SOA-based systems and to suggest areas of needed research.

Roles for Maintenance and Evolution of SOA-Based Systems

________________________________________________

>> Back to Main Page

Gary E. Smith
SOA Project Manager

"The ability of service-oriented architecture to rapidly assemble new applications and orchestrate multiple solutions comes from a commitment to reuse. But for that to work, it must be implemented enterprisewide, say the three internationally known, former META Group analysts.

The common approach of implementing SOA on a project-by-project basis fails to mandate the basic changes in development procedure that SOA requires. Developers may implement the standards that SOA has largely co-opted from the Internet, but they are free to reinvent existing services rather than reusing what already exists."

Gary E. Smith
SOA Project Manager

"For example, in your SDLC process your goal is to have an automated mechanism by which people check things in and automatically do builds, and automatically do tests," she answered. "If you actually implement governance and compliance testing as part of those processes, then the development team doesn't have to do anything extra. They are simply following their standard process. Yet at the same time you're doing compliance testing. And you can feed information directly back to the developers saying 'You might have violated a couple policies here. Here's the recommended approach to resolve that.' "

SOURCE: SearchWebServices

Best practices of the SOA development lifecycle


________________________________________________

>> Back to Main Page

Gary E. Smith
SOA Project Manager

'First, do no harm,' guides Marriott SOA plans

T"he MBO approach to the business side starts with the COO and CIO and includes all levels of management. While IT notoriously faces difficulty communicating the value of SOA to business people, Whitridge offered a list of tips for bridging the chasm. To get the point across in meetings, he said he found it is important to make sure the list of objectives IT offers to the business side:

• Is simple to understand and communicate
• Ensures ability to set goals and measure them
• Articulates what we have accomplished, what we are working on and what we have deferred
• Includes organization and process – not just technology
• Provides the business with realistic and affordable options
• Avoids "over commit and under deliver"
• Eliminates "boil the ocean" or "big bang" efforts "

SOURCE: SearchWebServices

'First, do no harm,' guides Marriott SOA plans

________________________________________________

>> Back to Main Page

Gary E. Smith
SOA Project Manager

The solution is Incremental SOA
What is Incremental SOA? It is a sensible, phased, low-risk approach for creating an SOA for your organization. Download the white paper today and you’ll learn about the 4 critical steps for success with SOA.

Download the white paper


________________________________________________

>> Back to Main Page

Gary E. Smith
SOA Project Manager

THE SOA NETWORK
The SOA Network	www.soanetwork.net
The SOA Blog Network	www.soablognetwork.com
SOA Book Network	www.soabooks.net
SOA Developer Network	www.soadeveloper.net
SOA Training Network	www.soatraining.org
SOA Career Network	www.soahotjobs.com
SOA Architect	www.soaarchitect.org
SOA Enterprise Architect	www.soaenterprisearchitect.org
SOA Network Architect	www.soanetworkarchitect.com
SOA Security Architect	www.soasecurityarchitect.com
SOA Identity Architect	www.soaidentityarchitect.com
SOA Governance Architect	www.soagovernancearchitect.com
SOA Test Architect	www.soatestarchitect.com
SOA Telecom Architect	www.soatelecomarchitect.com
SOA Project Manager	www.soaprojectmanager.com
SOA Business Analyst	www.soabusinessanalyst.com
AON Network Architect	www.aonnetworkarchitect.com
SONA Network Architect	www.sonanetworkarchitect.com
GRID Network Architect	www.gridnetworkarchitect.com
THE BPM NETWORK
BPM Blog Network	www.bpmblognetwork.com
BPM Architect	www.bpmarchitect.com
Business Process Architect	www.businessprocessarchitect.com

Gary E. Smith
SOA Project Manager

A recent McKinsey & Company survey of 72 CIOs and other senior IT executives from North American companies with annual revenues of at least $500 million confirmed two trends we have seen in our consulting work. First, nearly two-thirds of respondents plan to migrate to SOA in 2007. SOA is already bringing organizations major benefits: large reductions in development time, lower maintenance and other operating costs, and greater flexibility to change business processes. For example, one global financial services firm has saved about 12,000 person-days in system-development time after adopting SOA and providing developers with a set of services from which they can write applications.

SOURCE: CIO Magazine

CIO Magazine

________________________________________________

>> Back to Main Page

Gary E. Smith
SOA Project Manager

"What is a project manager’s primary concern? Well, it could be one of three things: delivering the solution as defined (scope), delivering the solution on time (schedule), or delivering the solution on budget (resources). Based on my own experience, the one thing that will drive a project manager nuts is when you add scope. Adding scope either lengthens the schedule or adds cost, both of which are probably the thing that the PM’s performance is being judged against. Most PMs I know aren’t evaluated on their ability to deliver what was promised, they are evaluated on whether dates were met and costs were controlled."

Managing Service Development


________________________________________________

>> Back to Main Page

Gary E. Smith
SOA Project Manager

"One of the first and most challenging steps in your SOA Project is to build the project team with required resources and skill; you need to identify who is involved in the SOA project. SAP can provide you will Platform, applications on top of this platform; various development tools required for building Composite Applications but we still need people intervention in order to make the process working. Less and Less people intervention required in order to make it working but let's leave it to the separate discussion.

More and more organisations are interesting in building their SOA roadmap and moving forward into the implementation phase. At the end of the day, this is what makes their business more competitive and agile. Unfortunately, most companies do not have enough skills yet in order to move forward with their SOA vision and most of them think that a lot time requiredto up-skill and train the people. To appropriately structure an SOA project, you need to consider that these roles might need to evolve to match the SOA concept or even create some new roles that did not exist before. I personally believe that this process can be done quite easily if you select the right approach and strategy."

SOURCE: SAP Developer Network

SOA Project Overview – Building Composites – Roles and Skills


________________________________________________

>> Back to Main Page

Gary E. Smith
SOA Project Manager

What Everyone Needs to Know About SOA - ECommerce Times

From a project management perspective, SOA presents additional risks to project success. Legacy applications mean legacy application owners and an increase in political risk. How are you going to get all these departments to work together effectively? IBM predicts that the services related to SOA over the coming years will dwarf the software and hardware purchases.

What Everyone Needs to Know About SOA


________________________________________________

>> Back to Main Page

Gary E. Smith
SOA Project Manager