Project Oslo
Nothing much about what is going on other than a http://www.directionsonmicrosoft.com/samples/Olso1107.pdf during Microsoft SOA & BP Conference this Oct(site: http://www.mssoaandbpconference.com/), Microsoft announced a new software initiative for the next wave of technologies code named “Oslo”.
The trend in itself is a next logical and smart move towards a better applications that truly serve the purposes let’s look at this way, what did we used to do:
- Get requirements probably a collection of business process “models” + use cases that describes how the business flows
- Build a design that meet the requirements
- Build and test code that satisfy the requirements
During the process we get lost between what was the original process & requirements and the code that was actually developed, add to that the requirements that keep changing and we will end up with a jungle and maze of elements to correlate.
Yes we build matrices that help us track back a piece of “let us say orchestration” to the original requirements and we all know very well that does not happen (direct relation) example: user provisioning on system X is one model by the analyst but might end up developed on collection of WCF services & WF workflows and definitely BTS orchestrations
One of the other things missing currently is modeling tools, business analysts and system analysts build models using Visio & word docs which is merely guidance for developers & software designers to build the solution. So any changes on the models will require the exact same translation used in the initial design phase to maintain the code.
Oslo is addressing all of the above knowing that with ESB guidance (check this out) and BTS R2. Basically the model originally design is the thing that gets run debugged and accordingly changed when requirements changes
John Flanders also blogged about it during the actual annoucment