Jump to content

Common Source Data Base

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Stefan Landstorfer (talk | contribs) at 20:20, 22 August 2007 (Connection between authoring and illustrating environment and data vault). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

The aim of a CSDB (Common Source Data Base, in accordance with specification S1000D) is to provide the user with automated processes to handle complete publications, to exchange data between the customer and the industry and to ensure data integrity and security during all processes, listed above.

Handle technical publication

These technical publications consisting of DataModules (DM), Illustrations (ICN) and its Info Object Instance (IO). The Info Object instance (XML file, using a special Document Type Definition) consists of DM- and ICN- references to lead the loading process into a retrieval system.

Connection between exchanging, authoring and illustrating environment and data vault

The basic mechanism is to copy 1000D objects like DMs, IPRF's or Illustrations out of the secured vault of a CSDB into a working area, to avoid that more then one user changes the object. After the changes, the object will be copied back to the CSDB vault, but issue raised.

Furthermore the CSDB is able to support technical authors or operators with a checking environment. The checks result in standardized files like CSV or plain text, to ensure an easy transfer to the originator of the checked data. The originator may be the technical author or in case of international data exchange in accordance with ASD/AIA Spec. 1000D, an industrial partner respective a international customer of the documentation. The checks enclose tests against official documents like
– business rules of the programme
– guidance document
– ASD/AIA Spec. 1000D and its versions
– or in the latest version of 1000D against the business rule exchange datamodule (BREX DM).

Nationalisation

If the customer is interested in national/translated and customized documentation out of the common documentation, a nationalization process must be supported of the CSDB.

ASD/AIA 1000D Data exchange

Data exchange routines and automatisms are the most important reason to develop a CSDB, to ensure a process reliability. The import and export routines can be fully automated or be performed via CSDB operator.

The components of a Data exchange package are for example:
– one data dispatch note (DDN)
– a certain ammount of datamodules (DMs) and
– all illustrations, referenced by the DMs above.

The identifier of a DDN is the (DDN-Id) found within the sgml/xml file and expressed in the filename plus related extension.
The identifier of the DM is the data module code (DMC) found within the sgml/xml file and expressed in the filename plus related extension.
The identifier of the Illustration is the illustration controll number (ICN) found within the cgm/tif/mil/cg4/etc. file and expressed in the filename plus related extension.

These packages contain all necessary informations to provide the reciever with the necessary informations.

The CSDB must provide or support the complete Integrated Logistics Support (ILS) process with its information. Thus detailed query and search masks have to be delivered.

A good solution may be to use commercial off-the-shelf database products to implement business logic. The CSDB must be able to handle all file formats supported via the actual version of Spec. 1000D.