 |
|
| Recent
Articles |
Ethical
Hacking (Finding the right people)
The concept is not an oxymoron, it is better that
you
find your issues than someone else does and takes
your
site. Most of us are familiar with zone-h the
defacement
web site...
Information Security As An Open & Closed System
The world of information security is both an open
and a closed system in light of the way that we share data. There are few
that understand that the sharing of data is a vital component of information
security, and there...
Purchasing Refurbished IT Equipment
Businesses spend
a lot of money designing, creating and maintaining their information
technology infrastructure. When the time comes to purchase
additional...
The Risks Of Reuse And Business Rules
Dian over at
BPM Enterprise
had this post that led me to this piece on The RIsks and Rewards of Reuse by Marcia
Kaufman of Hurwitz & Associates. Dian highlighted the problem of "Poor
Process" as an issue from a BPM...
2
Faces Of Demand Management
As I continue my journey through the
terminology difficulties of modern IT management, one issue that keeps
coming up (as recently as this week's...
An Appropriate S, G & A For "IT As A Business"?
Your CMDB budget depends on it...Last of tonight's triple play (I
must be feeling inspired). Let's consider the "Run IT as a Business"
concept. Let's say your IT budget is $250 million for a $25 billion
corporation.
Specializations For Outsourcing
Google's in the press
again, and this time about information security, and a host of other
"specializations" that can be, and maybe should be outsourced.
Understanding The Basics Of ITIL
In the world of IT
management, ITIL is the buzzword being heard around the globe. So what is
ITIL and how does it affect your organization? Let's take a
closer...
|
|
04.26.07
Model-Driven
Development
By James Taylor
Expert Author
Article Date: 2007-04-26
Diego Lo Giudice of Forrester published The
State of Model-Driven Development recently.
This is a well-written paper and does a nice job covering
Model
Driven Development of which it says "Forrester expects
model-driven
development (MDD) to play a key role in the future of
software
development; it is a promising technique for helping
application
development managers address growing business complexity
and
demand.".
Reading it i was struck, though, with the lack of
attention
paid to business rules in this context.
If one of the key drivers for MDD is the need to build
systems
that can cope with faster business change and to do so by
improving
business/IT alignment then business rules would seem to be
ideal.
Not only are they a great way to approach "change-time"
they can also really help with the kind of alignment
described
in Forrester's Concurrent
Business Engineering.
This made me wonder what is a model, exactly? Should it
include
non-graphical elements? Certainly Diego felt it could
include
"a declarative language for assertions".
I would go further and say it could include a declarative
language
for rules in general for, while improved business/IT
cooperation
requires a shared language, I don't believe that UML is
it.
Business rules allow for IT departments and business users
to
truly work together.
The paper also talked about the reuse of models in MDD,
which
seems like a real advantage, and about tracability
improvement
- better linkage of requirements to code.
While this sounds great, I fear that we are often talking
about
requirements that are really rules - rules
are not requirements and better traceability or better
requirements
documentation will not help.
Lastly there was some talk of Domain Specific Languages.
Instead
of using Domain Specific Languages as part of MDD, why not
use
business rules?
There's been some good discussion about this (particular
this
post) so I won't add anything.
I believe that business rules are a valid component of MDD
and
that MDD without business rules is flawed. You can check
out
a previous post with some of my thoughts on MDD
and business rules.
Comments
About the Author:
VP of Product Marketing with a passion for the
technologies of decision automation. 15 years designing, developing,
releasing and marketing advanced enterprise software platforms and
development tools. Across the board experience in software development,
engineering and product management and product marketing.
http://www.edmblog.com
|
|
