New to this site?
First TRIMM Java standalone project
Simplest TRIMM Java Maven example
Getting started with TRIMM JPA
First TRIMM Groovy project (standalone)
Writing your own TRIMM Java, TRIMM JPA or TRIMM Groovy/Grails generator extension
Worried that your software projects go over time and budget?
Model Driven Development can move your software development to the next level by giving your developers and business experts, a common foundation for dealing with specification, development, automation and testing.
Model Driven Development gives you the freedom to perform agile development using local resources that are placed close to the business, while at the same time keeping the budget on a short leash and avoiding schedule slippages.
Off-shoring is often praised as the only way to scale resources and keep costs low, but the reality is often another. Off-shoring projects typically take longer because of communication difficulties, cultural differences and the problem that decisions are made far away from those that are performing the work. The savings on labor costs are eaten up by the need for locally talented architects and developers that are specifying and describing the work others have to perform.
Our response is a higher abstraction level, high level of automation and full developer influence on the final product – Go against the flow and jump on the high speed Model train.
Contact us today for an inspirational meeting or a free lecture about the possibilities with Model Driven Development.
Get started quickly and be convinced of the potential of Model Driven Development
The flow of a typical Proof of Concept (PoC):
- Day 1 – Start-up meeting where the contractual framework for PoC is reviewed and reconciled. At this meeting participants are typically the project director, project manager, business experts as well as architects and key developers
- Day 2 and 3 – Meetings with the project group, which typically consists of business experts, architects and developers to clarify uncertainties and get everyone involved from the start
- Day 4 and 5 – Model development
- Day 6 – Presentation of the initial models and feedback from the project group
- Day 7, 8 and 9 – Modeling, integration with the technical platform and the development of code interpretation or code generation
- Day 10 – Final presentation of the PoC results and documentation of the PoC
Prior to initiating the PoC is important to define the desired goals well as define some clear success criteria. We therefore start every PoC with a series of clarification meetings to ensure that everyone agrees on the content of the PoC and the desired results.
Are you ready to solve your challenges in a new and effective way? Contact us for more information
We can not solve our problems with the same thinking that created them.