Document modeling with ITP

In this stage Models are created. The first step is to create a DID: a database description. This DID is then used, with the ITP Model Language, to develop Model Documents. These model documents are, in the last stage, compiled into Models.

Database description, the create DID stage

In ITP Models data descriptions are used that describe data or sets of data from a database or databases. These descriptions are what model developers 'see' of the database(s). This means that the model developer can work with easy to understand, legible names and doesn't need to understand setup and design of the database or databases. This separation also means that people who have specific knowledge of the database or databases can develop the Data Interface Description (DID) used by the model developers. DIDs are made using one of the two ITP/Software Development Kits (ITP/SDK): ITP/SDK MultiPlatform or ITP/SDK AS/400.

ITP/SDK MultiPlatform

The ITP/SDK MultiPlatform is Windows software for the development of ITP Database Interface Descriptions. As has been said, the definitions in these descriptions link the data fields in your model documents to the actual data retrieval implementations. An implementation can be in the form of:

Even if several types of database access are combined and used from one ITP model, the document developer will still see one coherent database view.

ITP/SDK AS/400

The ITP/SDK AS/400 is native OS/400 software for the development of ITP Database Interface Descriptions (DIDs), which describe DB2/400 database files. The ITP/SDK AS/400 has, by nature of the AS/400 system, a built-in wizard to automatically generate database definitions based on any existing database file. The ITP/SDK AS/400 also includes wizards to generate RPG or COBOL program sources to handle the actual database access. To allow an unlimited freedom in retrieving information from the database, developers can modify these program sources.

Create Model Document stage

Once the DID is created the data descriptions can be used in a Model Document. A Model Document is a normal word processor document containing ITP Instructions written in the ITP Model Language. Word processor instructions are used to describe the lay out of the document and ITP Instructions are used to provide the content. The ITP Model Language is a very versatile language allowing you for example to:

And because all word-processor instructions can be used you can also:

Create Model stage

An ITP Model Document must be compiled -'translated'- into an ITP Model. Several ITP programs can create Models from Model Documents. Depending on your setup one of the following is used.

ITP/Model Development Kit, Microsoft Word extension

During development a model can be created from within Microsoft Word using the Create Model ITP/MDK menu item.

ITP/MDK Repository

In the ITP/MDK Repository, Create Model is also available as a menu item.

MakeITP and Model Creation

Two programs, available in ITP/MDK, can be used MakeITP or Model Creation. Both programs are part of the ITP/MDK installation.

Integrated model development environment: ITP/MDK Repository

The ITP/MDK Repository is the complete management and development environment for ITP Model Documents. The ITP/MDK Repository is the development environment for ITP models. Especially organizations with a multitude of models, Includes and clauses can take advantage from this product. The ITP/MDK Repository is a client-server application. The server provides secure multi-user access to a central database that stores documents, building blocks (ITP Include Documents) and ITP models. ITP/MDK is, of course, an integral part of the ITP/MDK Repository.