Document versioning

M.W. Williams, RICEWQ Users Manual and Program Documentation, Version 1.4, Waterborne Environment, Leesburg, VA (1998). 

Neitsch SL, Arnold JG, Kiniry JR, Williams JR (2005) Soil and water assessment tool theoretical documentation Version 2005. Grassland, Soil and Water Research Laboratory Agricultural Research Service, 808 East Blackland Road, Temple, Texas Blackland Research Center Texas Agricultural Experiment Station 720 East Blackland Road, Temple, Texas 76502, USA. Available at www.brc.tamus.edu/swat/doc.html... 

Wolery, T. J., 1992b, Eq3nr, a computer program for geochemical aqueous speciation-solubility calculations theoretical manual, user s guide, and related documentation (version 7.0). Lawrence Livermore National Laboratory Report UCRL-MA-110662 (3). 

Hamilton, Bruce. 1996. Gasoline frequently asked questions. INTERNET USENET, Archive Name autos/gasoline-faq/partl (Document Version 1.09). http //www.paranoia.com/ filipg/HTML... 

Since networks change frequently, maintaining these diagrams with documented version control is important. A good recommendation is to have procedures in place for regular review of these diagrams (e.g., quarterly). 

Operating system software—document version and data communication protocols, and establish extent of use. 

Standard firmware (non-user-programmable)—document version, document user configuration and parameters, calibrate, verify operation... 

Available Chemicals Directory (ACD) Documentation, Version 95.2, MDL Information Systems, Inc., 1995. 

UNITY Chemical Information Documentation, Version 2.3, Tripos, Inc., St Louis, MO. 

SYBYL Molecular Modeling Documentation, Version 6.1, Tripos Inc., St. Louis, MO. 

A system should be established to document and control the versions of computer system software and hardware through the development, testing, and use of the system. Configuration Management needs to link software and hardware versions to particular data sets and document versions. Changes to software, hardware, data, and documentation may be interdependent. 

Note There are no specific validation activities for Category 1 software (COTS compilers and operating systems) beyond documenting version details. 

Since the conference was planned in advance, it is represented as a task in the AHEAD system. The compounding expert, who is assigned to this task, initiates the conference via the work environment of the AHEAD system. To this end, he starts the task and opens its work context, from where external tools may be activated. When the compounding expert activates the command for initiating a conference, a dialog is displayed in which the participants of the conference are selected from a menu of available participants (Fig. 1.21). Likewise, all document versions contained in the work context are offered as subjects of the conference. Here, the compounding expert selects the animated simulation results for different screw speeds which have been prepared by the 3D simulation expert. 

In order to represent such dependencies between document versions explicitly in the model, the dynamic behavior of documents needs to be taken into account. This issue is discussed in the next subsection. 

To describe the dynamic behavior of documents, their different versions and configurations evolving over time need to be captured. In the following, we will introduce a model that combines such a description with the static description of document types and their dependencies introduced in the preceding Subsect. 2.3.2. In addition, the model reflects the structural composition of documents and document versions. Figure 2.7 shows the top-level concepts of this Document Model, which is represented both in UML and in OWL. It is consistent with the Product Area of the PDW Core Ontology, which is presented in Subsect. 4.1.5. 

The relation hasContent is inherited by the classes Product and Version-Set and their respective subclasses DocumentVersion and Document. Thus, it can be employed to describe the content of both documents and document versions. If the content of a document remains the same for all its versions, a ContentDescription can be associated with a Document directly if, on the other hand, the content may change from one version to another, the different ContentDescriptions should be linked with their corresponding Document-Versions. 

Activities. The overall design process is decomposed into tasks (rectangular boxes) which have inputs and outputs (white and black circles, respectively). The order of tasks is defined by control flows (thick arrows) e.g., reaction alternatives must have been inserted into the flowsheet before they can be simulated. Finally, data flows (arrows connecting circles) are used to transmit document versions from one task to the next. 

Integration. There are several relationships between products, activities, and resources. In particular, tasks are assigned to positions (and thus indirectly to employees). Furthermore, document versions are created as outputs and used as inputs of tasks. 

Management of activities, products, and resources is fully integrated Tasks are assigned to positions, inputs and outputs of tasks refer to document versions. Moreover, AHEAD manages task-specific workspaces of documents and supports invocation of design tools (see below). 

The product area (top) contains basic models for the artifacts created or modified during the design processes - documents, document versions and their structural composition. 

The extruders and their structural composition, as created by the MOREX tool (see Subsect. 5.4.2), are extensions of the Product and Document concepts. Each Document has a set of Document Versions that in turn contain the Extruder realizations, and other Plastics Engineering (PE) Devices. 

The metadata of the new document version is read by the PDW document name, version and ID, user and session information, etc. 

A new Document Version instance is created in the repository and related to the Document instance as its new and current version. 

Where Tamino differs from Oracle is that Tamino allows the stored data to determine reverse compatibility rather than the schema document versions themselves. One can pass a parameter to the. define command to attempt to do some static validation first - determining just from the documents themselves whether it is possible for reverse compatibility to be guaranteed - but eventually all documents are... 

Temporal XML Schema (Currim et al. 2009) - also referred to as xXSchema -is a way to formalize the temporal nature of schema and document versioning. The framework is assembled by the same research group that helped develop the temporal extensions to SQL. In all other frameworks discussed to date, the relationship between versions of schemas and documents are informal if they exist at all two versions of the same schema version are considered to be two separate schemas, related to each other only by whatever point-in-time script was used to perform the migration. xXSchcma makes evolution over time a first-class concept, modeling different versions of the same conventional XML schema in the same document. 

Miller, 1., Lee, G. and Dershowitz, W. 1999. MAFIC Matrix/Fracture Interaction Code With Heat and Solute Transport User Documentation, Version 1.6, Golder Associates Inc., Redmond, Washington, November 30. 

Wolery T. J., Daveler S.A. (1992) EQ6, a Computer Program for Reaction Path Modeling of Aqueous Geochemical Systems Theoretical Manual, Users Guide, and Related Documentation (Version 7.0). UCRL-MA-110662 Pt IV Livermore Lawrence Livermore National Laboratory, 338 p. 

Configuration of documentation (versioning, archiving, change control)... 

Are the deliverables of a good quality, are the documents version controlled, stored in the correct place and approved ... 

Many of the EPA s guidance documents are undated. Absent version numbers or dates, the best way to track document versions is by reviewing the metadata attached to the documents. 

ABAQUS, Abaqus documentation . Version 6.9, 2009, http //www.simulia.com... 

CSIC, GLONASS Interface Control Document, Version 4.0, The Ministry of Defence of the Russian Federation Coordination Scientific Information Center, 1998. Available in electronic form at http //www.rssi.ru/SFCSIC/SFCSIC main.html... 

AUTOSAR, Technical Safety Concept Status Report, vol. Document Version 1.2.0, no. Part of Release 4.1 Rev 1 (October 2013)... 

So the validation work is really a carefully documented version of the PSAT. It is work that should be done by an independent auditor who can study the records impartially and be satisfied that no items remain unclear or untested. 

Corrective Action at Outdoor Shooting Ranges Guidance Document - Version 1, Colorado Department of Public Health and Environment, January 2005 (The full text is available on line at www.cdphe.state. co.us/hm/shootingrange.pdf.)... 

Hazardous Wastes. A User-Friendly Reference Document Version 1 October 2009... 

Gemini Science Requirements Document, Version 1.1, November 1992. 

---