DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone >

Model Driven Development with "Oslo"

Gunther Lenz user avatar by
Gunther Lenz
·
Dec. 16, 08 · · Interview
Like (0)
Save
Tweet
4.80K Views

Join the DZone community and get the full member experience.

Join For Free

The last 3 years I was working a lot on evolving the Software Factories Paradigm and applying it to industry problems. Part of this effort I spent researching Domain Specific Modeling Languages with the Microsoft DSL Toolkit which is part of the Visual Studio SDK. Therefore I was also very curious to see what the “Oslo” project is all about so I downloaded the CTP from http://code.msdn.microsoft.com/oslo.

What is “Oslo”?

In short “Oslo” is a platform for Model Driven Applications. If we are talking about model driven applications then we can split a model driven approach into three major categories:

1.       Drawings: These are for example the white board drawings we all use to communicate architecture and design in a more informal way. Very often we use a tool such as Visio to capture those thoughts to document them.

2.       Model Assisted: In this category we capture applications that use models of some form to declaratively describe parts of it. This could be a XML based textual or graphical DSL that is used to define parts of the software.

3.       Model Driven: Applications such as Microsoft SharePoint Server that uses CAML as descriptive modeling language to drive the application.

 The overall goals of the Model based applications paradigm is to allow for high flexibility to enable agile application development, increase productivity by focusing of the essence rather than the ceremony of context tasks, and last but not least to provide higher transparency for software systems.

What are the parts that make up “Oslo”?

·         “M” : Textual language to author models.

·         Quadrant: Tools for graphical interaction with models and DSLs.

·         Repository: SQL based database to store and share models.

The key concepts of “Oslo” are shown below:

http://architects.dzone.com/sites/all/files/OsloConcepts.jpg

What is the architecture of “Oslo”?

On a very high level the “Oslo” architecture is shown below:

http://architects.dzone.com/sites/all/files/OsloArchitecture.jpg

In my next post I will drill more into the details of using “Oslo” to write your own languages, so stay tuned…..

application

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Challenges to Designing Data Pipelines at Scale
  • Your Old Laptop Is Your New Database Server
  • Stupid Things Orgs Do That Kill Productivity w/ Netflix, FloSports & Refactoring.club
  • Why Performance Projects Fail

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo