10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
How would you like to view the presentation?
Getting Started with Stratos - an Open Source Cloud Platform
Agile Development: A Manager's Roadmap for Success
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Monitor your Production Java App - includes JMX! Low Overhead - Free download
#, I would love to have more insight in actual apps using OSGi apart from the app servers and embedded things. What Neil mentioned, where are the banking apps, and some of the like?
Now, just to clarify, SOA is more the architecture using the service metaphor. SOA is not a pattern, nor is it the web service triangle displayed. The service is modeled used the triangle, not SOA.
Fascinating the concept of components as living things. In one of my university works I presented the notion of passive objects against dynamic or active objects. These second ones would have the same properties Neil adds to components, like awareness of environment and responsiveness to it. Still, components do not require that as minimum. A component can be a dumb thing, passive.
And of course, components using services to offer functionality is one of the ideas under SCA.
At the end of the day, this proposal is about an SOA infraestructure (OSGi) used to create an COA application. Interesting.
William Martinez Pomares.
Architect's Thoughts
Funny. His definition of Components is precisely the same definition DAI people use for Agents.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
2 comments
Watch Thread Reply