Oslo will be Microsoft's new Model Driven Development platform. Oslo's success will depend on many factors, but must begin with some foundational architectural decisions. In particular, technology decisions must be made for building and storing models.
The Microsoft Professional Developer's Conference (PDC) introduced Oslo to the world. If you've seen any of the PDC Oslo sessions or read anything about Oslo, you'll quickly realize that Oslo is composed of a nontrivial number of working parts. There are parts for viewing models, new languages, and a database housing it all. This article centers on the role of the model storage database called the Repository. Using models shipping with the Oslo SDK, the article will show how models are stored in the Oslo Repository.
Oslo Explained
A complete introduction to Oslo is beyond the scope of this article. Refer to the Sources section at the end of the article. Still, some context is important to understanding the role of the Repository.
Model-driven development has existed for years in the guise of markup languages such as HTML. In Model Driven development, a tool creates the markup and a runtime executes against the generated markup. In the HTML example, an HTML editor creates the HTML code and a browser (runtime) interprets the HTML.
Oslo will carry model-driven ideas further. It will encompass not only XAML models like WCF and WF, but also model information devoted to platforms like System Center Operations Manager and roles like the Systems Analyst.
Read the Rest of this Article at Developer.com