Tracking change and innovation in the enterprise software development community
Free Book Offer
SOA Demystified
$40 Value
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Posted by Abel Avram on Mar 19, 2009
In this presentation recoded during QCon London 2008, Magnus Christerson discusses about the importance of using DSLs which allow business experts to freely express their knowledge about their domain using familiar tools. Henk Kolk presents a concrete example addressing pension fund issues and based on a DSL.
Watch: Domain Expert DSLs (1h)
In the first part of the session Christerson talks about Intentional Software Development emphasizing the need for domain experts to be able to freely express their knowledge of the domain and intentions for the product to be created by using the tools they are accustomed with. The domain experts are practically using a DSL to write the specifications. Since such specifications are not directly executable by a computer, the programmer’s job is to create a code generator translating the specs into code (Java, C#, Ruby, etc.). The result is a clear separation of concerns between business experts and programmers. The former are responsible for clearly and correctly expressing the business rules of the domain, while the later are concerned only with the automatic translation of the document written in the specified DSL into code. They work together on the language workbench which Martin Fowler defined as follows:
1. Users can freely define new domains, including languages, that are fully integrated with each other.
2. The primary source of information is a persistent abstract representation.
3. Domain designers define domains in three main parts: schemas, editors, and generators.
4. Domain users manipulate a domain through a projectional editor.
5. A domain workbench can work with incomplete and contradictory information.
In the second part of the session Kolk talks about a concrete Capgemini project that uses a DSL to create a solution for pension funds. Their program accepts business rules that pension domain experts are used with and converts them into Java or C# code.
The session concludes with Christerson and Kolk answering questions.
Agile Development: A Manager's Roadmap for Success
Regaining control of the data centre
The 5 Mandates of Software Development Teams - Presto Manifesto
Architectures Behind Facebook, Skype, Sky.com, Bwin, League of Legends @ QConLondon
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
No comments
Watch Thread Reply