Input specification languages

In the next step, additional aspects of the work process are added to the model or described in a more precise way (2). Both the choice of aspects and the degree of detail depend on the intended applications of the work process model. For example, if a design process model is supposed to guide an inexperienced designer, behavioral aspects of the design process (such as the sequence of activities to be performed and conditions for their execution) can be expressed in natural language. In contrast, if the work process model is intended, for example, as input specification for a workflow management system, a formal and detailed description of behavioral aspects is required. 

The basis of ALADDIN is the Daylight Chemical Information Systems software, particularly GENIE, a substructure specification language. When GENIE finds a query substructure in an input SMILES structure, it can return to the user those atoms in the structure that correspond to those hit. Since in a MENTHOR database the coordinates of the atoms are stored in the order in which they occur in the SMILES for that molecule, the coordinates of the atoms of interest are thereby identified. Thus, our geometric objects are established from this set of atoms, and geometric tests are performed on them. Steric tests are performed on molecules that meet the geometric criteria. 

We choose LNT [5] as target specification language which derives from two standards Lotos [1] and E-Lotos [2]. This choice is justified by the expressiveness and richness of LNT. It provides expressive enough operators for data and behaviour description and it has a user-friendly notations to simplify the specification writing. Indeed, LNT is a CADP [6] (Construction and Analysis of Distributed Processes) input language. It is a popular formal verification toolbox that implements many formal methods. 

If the query provides thousands of hits, the analyze features are particularly advantageous. One method is to analyze the results by any of the criteria that arc listed, c.g., by language (default), author names, journals, puhlication year, and so on. If one specification is selected and the choice is modified, the hit list will be updated. A more specific analysis is available with the Refine" option. where the user has the opportunity to choose one of eight criteria (including the search topics above) with further individual input. Several refinements of the hit list can reduce the result to a concise list of literature. To read the abstract of an article, the microscope button (to the right of the citation) has to be pressed (Figure 5-15). 

The second edition CD-ROM contains 139 validation SOPs they are made available so that customers can input them into their computers and use their Microsoft Word programs to edit and print these documents. The contents of the procedures are written in simple and precise language to be in compliance with FDA regulation GMP and GLP requirements. The book ensures minimization of the number of documents to avoid the nightmare of the head of quality assurance at the time of FDA audit. The SOPs exclusively refer to the documents specially required for compliance however, specific formats are not included to ensure that the electronic templates can be easily used by pharmaceutical, bulk pharmaceutical, medical device, and biotechnology industries. 

There are many reasons for this choice, among them the prior existence of control structures, data structures, input/output facilities, and a general von Neumann framework. Further, a preprocessor can be implemented to compile Multilin into the embedding language and a selection of subroutine calls which can be coded specifically for each architecture. 

A third technique that a developer can use to test ES code involves simulation. Simulators can test entire systems or parts of systems and are similar to drivers. A simulator approach is more functionally oriented than a driver in that a simulator usually will be utilized to test a call for a conventional language or package (e.g., LOTUS), whereas a driver is interested in values or a specific ES element. Simulators can also generate data input for real-time testing of ES code. Use of a simulator test approach, particularly just prior to integration and installation, allows for initial data and information to be generated for Method III which is the qualitative knowledge-base review approach. 

Scientific Language Interface. The SLI is a domain-specific interface designed to allow the intuitive expression of complex scientific problems in a language most natural for the investigator. The SLI is composed of an interactive display editor and an input language derived from the problem domain. In the... 

---