• This is a community for Developers who use OOPS Concepts in their daily development processes.    Login to Ask Questions
• Here you will find various resources around OOPS Concepts.
• Tips from experienced Developers and Architects on OOPS! Post Your Tip
• You are welcome to share your experience with using OOPS in your development. Share Now

by Dharmesh Mistry

You’ve finally got your head around service-oriented architecture (SOA) – but now a new acronym threatens to create panic amongst the IT organisation: web-oriented architecture (WOA).

WOA encompasses some big aims and hopes to spread the good work of service-orientation to web-based applications. Are the aims realistic, or are we really looking at the next piece of vendor spin?

Scrum is an agile approach to software development. Rather than a full process or methodology, it is a framework. So instead of providing complete, detailed descriptions of how everything is to be done on the project, much is left up to the team. This is done because the team will know best how to solve its problem.

By John Clifford, CSM, CSPO, CSP

Many teams moving to Scrum have questions about the Product Owner position. Is the Product Owner a member of the Scrum team? What role does the Product Owner play in the day-to-day life of a Scrum project? How do we map current functional roles to Scrum roles, specifically with regard to the Product Owner? Who should we select as our Product Owner?

As a ScrumMaster, I was asked this question many times. Sometimes I had enough time to explain, sometimes not. But every time it was challenging to provide a clear picture of what a ScrumMaster really does.

To help myself and other ScrumMasters, I have started to write down general activities, which characterize the role of the ScrumMaster (see below).

The priority of activities varies by company.

1.Keeps Scrum process running
2.Ensures a proper power balance between PO, Team, Management
3.Protects the Team
4.Moderates in the Team
5.Helps to organize (e.g., Meetings)

Here is a collection of Audio Files for free download. Podcast by Indutry experts on SOA Design and SOA Concepts. Listen to the Experts and Authors on the Subject. Hope you find it useful.

http://soaconcepts.com/?q=node/55

Martin Fowler

Using a agile method is not for everyone. There are a number of things to bear in mind if you decide to follow this path. However I certainly believe that these methodologies are widely applicable and should be used by more people than currently consider them.

By Dave Chappell

Myth #1. ESB is just a new name for EAI.
While many IT architecture groups are focusing on building SOAs, they still inevitably beg the question of "how is ESB different from EAI?" An ESB is an infrastructure for building an enterprise SOA, and is capable of being used in a more general way than a conventional EAI broker. According to Forrester Research, an ESB helps enterprises obtain the value of SOA by increasing connectivity, adding flexibility that speeds change, and providing greater control over use of the important resources that it binds.

Web-oriented architectures are easier to implement and offer a similar flexibility to SOA.

By Roger Smith

CIOs and system architects find themselves stymied as they try to sledgehammer complex SOAs into their enterprises. Top-down, "if you build it, they will come" approaches to service-oriented architecture often wind up failing--sometimes spectacularly. Instead of better aligning business processes and IT departments, as was promised, too many employees remain oblivious to expensive SOA initiatives. And those optimistic ROI projections? Forget 'em.

SOA Repository Best Practice
By: John Moe, Head of Business Integration, TORI Global
Tuesday, December 8, 2009

For those of us who have been developing applications for many years (think COBOL & Assembler from the 70s and 80s), the idea of having a code library (programs and routines) is nothing new. However for the Web Services generation, this concept has taken a while to re-emerge, but has now been packaged in the form of a services registry and/or repository.