Understanding SOAs

After the last class in which we were introduced to services and asked to create a component map for a learning department, I was feeling a little lost. That was no easy task--plus I didn't know what the he** a learning department did, so how was I supposed to put together a map based on the components of said department? Whatever, I tried. I learned that it is no easy task. That is the point, n'est pas?

I'm feeling a lot more on board following the SOA lecture. Breaking down business applications into services, using the technology that is available to make these services independent components and then rearranging them to create new capabilities. Got it. And Oscar's example really helped me to visualize it. Seems like a really great idea that requires a lot of change and adaptability on the part of people within an organization as well as time and money. I'm assuming it is the need for change that is the biggest obstacle to implementing SOA within an organization.

Kind of jonesing for a trip to a farm amusement park now. I think my kids would like it.