|
What does model-driven
development involve? CASE tools can help you transform
models into code and vice-versa. But model-driven development requires methodology
before technology |
|
||
|
Conditions of use….FAQS….Feedback….Community….Value proposition….Training
for Architects….Certificates
for Architects….News…. |
|||
|
|
|||
|
Capable architects focus modelling effort and ensure
consistency between models |
|||
|
Development usually requires you to document: ·
The
business case ·
Business
process and or use case models ·
Business
rules ·
User
interfaces (the users workspace) ·
Business
service interfaces ·
The
business data model. |
Model-driven development requires you to address: ·
Is
the system business process driven or workspace/event driven? ·
How
many levels of goal, process and component decomposition? ·
How
do you match top-down requirements to bottom-up designs? ·
Business
rules: when/where are validations & calculations done? |
·
How
do you ensure models are consistent with each other? ·
How
far do your models abstract from code? ·
How
do you transform a model into code? ·
Will
you maintain models in the long term? and how? |
|
|
Are your architects
capable? Do they follow best practices? Are they certificated to an industry
standard? Do you want to grow your
software architects into solution and enterprise architects? Click on Training
for Architects above. |
|||
