OBJECT CODE

The object code for DDAPLUS and its dependencies is provided in the software package Athena Visual Studio, which is available at www.AthenaVisual.com. 

To complete the codes required for a given problem, the user provides a driver program (here called MAIN) and four subroutines fsub, Esub, Jac, and Bsub. Each of these subroutines must be declared EXTERNAL in the MAIN program. Table B.l summarizes the roles of these user-provided subroutines all are needed for proper linking, but a dummy form suffices for any subroutine that will not be executed. Further information on these subroutines is provided in Sections B.3 through B.6, and detailed examples are given in Section B.IO. 

All the subroutines described in this appendix can be created automatically by Athena Visual Studio in ANSI standard FORTRAN-77. Since FORTRAN-90/95 is compatible with this standard, there should be no difficulty in using the package under FORTRAN-90/95. The user needs only to supply the (1) model equations, (2) the initial conditions, and (3) any pertinent data. The user input is decribed in more detail in the Help menu of Athena Visual Studio, by clicking Book Examples and then Appendix B and finally selecting the appropriate example. 

---

Too many object code instructions - program returns to ISIM Monitor. 

One architectural view includes all third-party libraries that will be used and import relations from packages that make use of these libraries. This view also explicitly describes the packages for tools (compilers, UI builders, and so on) that are used to populate other packages (containing object code, UI screens, and so on), documenting all project and module usage dependencies. 

The ASPEN system does facilitate the inclusion of a user s own model either in FORTRAN source code or compiled into an object code. The proprietary model may rely on the entire physical property system to calculate the required properties, however, the user routines must have the correct interface calls. These are to be documented in the ASPEN user manual. 

All documents, hardware units, and software programs must be uniquely identified. It is not necessary to violate warranty seals in order to uniquely identify subcomponents. However, in situations where hardware units and software programs do not have a unique identification, physical labels and software header information can be added retrospectively. Unique identification should include the model number for hardware and the version number for software (e.g., MS Windows 2000 Professional Service Pack 2). Current approved versions of source code must correspond to current approved versions of software documents, object code, and test suites. All source code should have associated documentation. 

Object Code A computer program that is the output of trauslated [assembler or compiler] source code. [Defiued for this book.]... 

Source code is the human readable form of program code, written in its original (source) programming language. Source code must be compiled, assembled or otherwise interpreted before it can be executed by a computer. The executable code is referred to as object code because it is not readily understandable because it exists as machine hexadecimal code. [Dehned for this book.]... 

SYNCOM Stand-alone program for converting descriptions of chemical reactions written in ALCHEM into an object code usable by the SECS program. 

Because the applications of the technology are new, many issues must be resolved, such as The cost of distributing a knowledge base may require a license fee to the expert system shell developer. This is very different from FORTRAN programs which can be distributed as object code, with no fees to the FORTRAN compiler developer. 

FIGURE 5.4 PCA of the data of Table 5.3. On the left, the score plot of the objects (coded according to the category number), on the right the loading plot of the variables (coded according to the order in Table 5.3). 

ASSEMBLE NON ROUND OBJECT CODE UP TO INCL. 18 LBS. OVER 18 LBS. THRU 48 LBS. 

A-2 Executable Object Code and Parameter Data Item Files, if any, are produced and loaded in the target computer. O o o o Executable Object Code 11.12 ... 

A-6 Executable Object Code complies with high-level requirements. o o o o SAV Verification Cases and Procedures 11.13 ... 

A-6 Executable Object Code is robust with low-level requirements. O o SAV Verification Results 11.14 ... 

Executable Object Code (integrated and compatible, complies and robust) Verification (coverage of high-level requirements)... 

Independence (statement coverage, decision coverage, data and control coupling, executable object code and source code complies with low-level requirements, high- and low-level requirements comphance, accuracy and consistency)... 

Independence (modified condition decision coverage, executable object code robustness with low-level requirements, source code complied, with SAV architecture, accuracy and consistency, partitioning integrity, SAV architecture is compatible with high-level requirements and consistent)... 

Fig. 9B.2 shows the role of testing in the SAV lifecycle. It is an empirical evaluation of the executable object code against each of the other lifecycle products. 

Requirements coverage analysis - to determine requirements-based testing shortfalls. Source code structural coverage analysis - to determine requirements-based testing shortfalls. Source to Object Code Traceability and Analysis. 

B8.6 Test Coverage Analysis Requirements The intent of specifying coverage objectives in SAV assnrance standards is to ensure evidence is provided that all relevant behaviours of the SAV (executable object code) have been explored. The overall intent is to provide an nnambignons end point for testing. 

---