The content has been bookmarked!
There was an error bookmarking this content! Please retry.
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.
Getting Started with Stratos - an Open Source Cloud Platform
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
A practical guide to choosing the right agile tools
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
No comments
Watch Thread Reply