Presentation is here
Composition is a collaborative effort -- has more roles - Development is a programmer driven effort - need for modelers, analysts
Services should be constantly evolving - else it is dying. I disagree - some services are static due to the nature of what it does -
Model Driven development view - looks like where we are trying to go with things like MCS and One App - This approach for model-driven is where we are going - need a more holistic view - and how this ties into our legacy modernization view.
Having a Process person who knows with the business - looks like the Lesa role
Multiple Lifecycles to manage - each circle is a lifecycle - Data changes the least (outer circle) - to compositions - One big aha here is that putting services on the same lifecycle as apps is a problem - seems to suggest that one SDLC for services and apps is not a good thing - the velocity of change is very different - Processes change slower then service but faster than apps
Must track the users of the service - Composite apps are making this much worse - When Daryl asked who was using a registry/repository to track users - I was the only one in a room of 60+ to raise my hand.
Composition is the big theme to date in the conference
No comments:
Post a Comment