Thursday, January 23

In the commercial world, the deliver software solutions that work is the norm.

On initial look, the wedding of Technologies and ZapThink would possibly seem to be somewhat of a mismatch: shop Federal contractor acquires unorthodox design thought leadership firm? however look below the surface, and therefore the synergies become apparent, as Dovèl has long had AN unorthodox approach to design, since in the end, we have a tendency to concentrate on design that truly works.

In the business world, delivering software system solutions that job is that the norm (or a minimum of, comparatively common), however sadly, within the world of state acquiring, it looks that such a big amount of initiatives square measure very little over thinly veiled cash pits – a fine example of our tax greenbacks at work. Federal design initiatives square measure a case in point: such a big amount of design comes within the government yield very little over listing architectures, a haul ZapThink mentioned in irreverent detail a couple of year past.

In that article, ZapThink referred to as out the Department of Defense design Framework (DoDAF) as a blatant example of the listing design drawback. To be sure, several DoDAF efforts yield very little over multiple binders of documentation. however any design framework is nothing over a tool, and whether or not a tool helps solve a haul depends a lot of on however it’s used than on the tool itself. In fact, at Dovèl, we’ve got found DoDAF to be valuable for architecting systems that not solely work, however that meet evolving business desires. Our secret? Combining DoDAF with Model-Driven design (MDA) to implement a dynamic delivery approach that offers our consumer an answer that mechanically responds to vary.

Connecting MDA and DoDAF

MDA may be a software system style approach from the item Management cluster (OMG) that provides a group of pointers for structuring specifications expressed as models. It conjointly offers a standard approach for coming up with and building systems that stay decoupled from the ultimate languages, platforms and middleware environments that may support them. Architects use MDA to outline platform freelance models which will be translated into one or a lot of platform specific models for the particular implementation.

For many years the U.S.A. Department of Defense (DoD), and really, the complete centralized, has been troubled to attach their business initiatives to the technologies that facilitate understand these initiatives. For this reason, the executive department leveraged MDA to develop DoDAF. The intent of executive departmentAF was to produce a unique thanks to specify and build systems: a mechanism for DoD programs to style their systems once so transition them over time once new technology comes on.

Unfortunately, typical DoDAF initiatives find yourself with unimplemented architectures, or at a minimum, design artifacts that don’t seem to be reusable throughout implementation. to handle these issues, Dovèl developed AN MDA-based approach for a administrative unit that power-assisted in continuous code generation – one amongst the a lot of advanced capabilities of MDA. we have a tendency to provided AN end-to-end integrated design from needs through execution. This forward-engineering approach was unendingly repeatable, serving to to determine a living design that actively target-hunting and ruled system development through system delivery.

The figure below illustrates the deployed system. we have a tendency to used a model-driven approach that generated reusable artifacts that implementation specific tools will consume, thereby sanctioning forward compatibility, which supported tracing to needs for backward compatibility. In essence, we have a tendency to achieved continuous code generation. Basically, each whole that the MDA tool generated was expendable by the implementation tools.

Integrated MDA method

We used AN integrated Enterprise design tool to model the varied DoDAF views. It conjointly supported the flexibility to export the views for development, in XML method Definition Language (XPDL) format compatible with a selected development tool.