Tracking change and innovation in the enterprise software development community
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Free Book Offer
SOA Demystified
$40 Value
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Recorded at:
Presented by Jay Fields on May 08, 2008
Learning to be a Good Product Owner: Foundation Skills
Understand and Align BPM, SOA, and Lean Six Sigma: 43 page IBM Redguide
Technical Debt and Design Death
Consolidation and Virtualization Are NOT Enough: The Case for Non-x86
I enjoyed the presentation. Thanks!
Two related questions:
1. If I understand correctly, the system is not forcing the user to type syntactically-well formed string in some controlled grammar. Instead, the regexes do the magic under the hood. If so, does/could it happen that the business user naively uses a novel language construct (and instead of or, or a meaningful "not" or "could" instead of "does") which the BNL designer did not anticipate, but which get swept up in general regexes, and the meaning is harmed in some subtle way that may be hard for a business user to defend against using the testing tools available?
2. Given the narrowly targeted domain specificity of the language, a similarly targeted UI might work as well. for example:
compensate $ [number] per [enum: $1M-profit, deal] if
[enum: gross, recent_deals, all_deals] exceeds [number]
(where the stuff in square brackets is shorthand for the appropriate HTML form-tags)
Do you have insights as to which circumstances favor a UI vs BNL?
Thanks again!
Michael Niv.
Hi Michael,
Like almost everything in software: it depends. There are so many ways to translate external DSLs to executable code that it will depend on which solution you go with. If you have a strong security (or just general) concern you can use something such as TreeTop to create an entirely external DSL and pretty much entirely mitigate the risk. On the other hand, if you do something as simple as replace spaces with dots, then you are allowing for potential issues. Of course, those issues might be acceptable given timelines, trust, etc.
Using form elements instead of a DSL is a commonly discussed option. I think it generally depends on how dynamic the language is. For example, I always thought trying to create SQL statements with forms was dreadfully painful. I would go with forms when possible, but if things are dynamic, I would quickly start considering a language.
For example, my current project allows you to specify the following conditions:
Date Range is 5/10/99
Date Range is from 4/10/99 to 5/10/99
Profit is greater than X
Profit is less than X
Profit is X
Cost is greater than X
Cost is less than X
Cost is X
And, so on, for many different conditions. This is something dynamic enough that it's painful to do in forms.
I hope that's helpful, please shoot me another question if you want more info.
Cheers, Jay
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.
2 comments
Watch Thread Reply