|
|
|
The Model-Driven System Builder
|
|
JeeWiz Architect's Guide
|
|
|
|
Contents >
2. Overview
|
|
|
2.1 The Architect Role
2.1.1 Definition
|
This manual is written for members of the development team acting as archtitects, which encompasses
- Setting high-level architectural strategy.
Stating which technologies will be used and in what circumstances. "we will use entity EJB's for updates, but JDBC calls for searches and summaries", for example.
- Implementing the architecture in JeeWiz.
This involves writing templates and patterns to generate code, build jobs and other build products; in other words, this is the 'meta-programming' role.
2.1.2 Related Roles and Products - Business
|
The following diagram shows the JeeWiz process, with the architect and related roles and products operating in a business application environment:
A typical JeeWiz architecture development is
- An architect creates a series of meta-models for the target domain.
These can be created by the project architect if necessary, but more likely they will be used out-of-the-box from the JeeWiz set.
- The 'modeler' (business or technical analyst) creates a model, in UML or XML, to specify the system.
- The architect creates, or builds upon the JeeWiz set of, a set of architecture renderings to
- convert the model into the application framework
- build the framework plus business logic into a deployable application.
- The application programmer writes the 'business logic' - the detailed programs that cannot be automatically generated.
- The build script created as a spin-off of generating the application framework is used to create the deployed application, ready for a J2EE or .NET application server
This means that
- The architect's first output is the series of meta-models, for use by the modeler
- The architect's second output is the application framework, for use by the application programmer.
2.1.3 Related Roles and Products - Technical
|
The engine of JeeWiz is a powerful meta-modeler. This can be used on its own when the issue of business logic doesn't arise.
For the JeeWiz documentation and web-site for example are produced using JeeWiz in exactly this approach.
In this case, the application framework containing business logic doesn't arise.
The process therefore simplifies to the following:
- The architect, via the meta-model, defines what the model (or specification) 'writer' can write.
- The writer - such as a technical author for documentation - creates the 'model', which in this case is a specification of what must be written.
In the case of the JeeWiz documentation model, the writer creates a manual/chapter/section structure with embedded HTML constructs.
Other target environments will have different views of what the writer must create.
- The architect defines how the model should be transformed into a build product, such as this HTML manual.
The architect only has one 'customer' in this scenario - the writer. The rest of the process is the responsibility of the architect.
Copyright (c) 2001-2008 New Technology/enterprise Ltd.
| |
