Report From the 1986 Workshop on Integrated Data Base Development for the Building Industry (1987) / Chapter Skim
Currently Skimming:
'INTEGRATOR DESCRIPTION AND FUNCTIONAL SPECIFICATION'
'INTEGRATOR DESCRIPTION AND FUNCTIONAL SPECIFICATION'
Pages 39-48
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 39... ...
IDB CONCEPT The IDB for a building project will exist from the very start of the programming and planning phase of the building process when the idea for the building originates. The IDB will be an active element of the process through the operational and facility management phase (when large cost advantages are expected to result)
|
From page 40... ...
, 2. A transitional data base that holds data resulting from the tasks of participants no longer active in the process; over time, this collection of data will grow as the building project proceeds, and, eventually, is expected to comprise essentially all of the data of the IDB, and 3.
|
From page 41... ...
The third group, which deals with communications among sites and DBMSs, suggests the use of standard communications protocols over conventional communications networks or facilities. However, special data base-oriented protocols may be necessary to preserve semantic integrity among some heterogeneous DBMSs.
|
From page 42... ...
Distributed Transaction Manager The distributed transaction manager (DTM) receives subqueries from the execution plan generator of the GDM and controls the execution of those queries and transactions so as to ensure the consistency of the data base by providing a hierarchy of concurrency control and recovery control by utilizing a two-phase commit protocol.
|
From page 43... ...
Resource Management Results IntegratIon ExecutIon Plan GeneratIon I Local TransactIon CoordInatIon InteractIon wIth Local DBMS Local-Resource CoordInatIon (Interface wIth Data Managers) Assembly of IndIvIdual Results L Structured Data Transfer Protocols Command Transfer Protocols Structure Transfer Protocols Type and Format TranslatIon Protocols Data CommunIcatIon Protocols ' FIle Transfer Protocol | Data PresentatIon Protocol | -- I Network Interprocess CommunIcatIon Protocol j FIGURE 4-1 Functional requirement areas.
|
From page 44... ...
5. The actual implementation of the integrator depends on the hardware, software, communication, applications and data base components available throughout the building life cycle.
|
From page 45... ...
This would be done by the application interface portion of the integrator, not the application itself. This could also be used by the IDB for global data base activity.
|
From page 46... ...
The translator converts data into or from the neutral file format from or to the specific format of the application issuing the request. PROPOSED PROTOTYPE IDB EXTENSION The 1986 prototype IDB demonstrated the capability of interaction of dissimilar systems in the architect-engineer-constructor continuum.
|
From page 47... ...
The composition of a mail item on the AT which covered a data base query, 2. Dispatching that item to the mail system, 3.
|
From page 48... ...
the response to an appropriate format for the application executing on the AT. In this simple scenario it can be assumed that the director has knowledge of all the files and fields of the ORACLE data base and can ascertain that the canonical query refers to known files and fields.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.