5,6c5,7
< \author{August G. Reinig\\ supported by \\Vandana Gandhi \\ Dolly Sinha}
< \date {\today}
---
> \author{August G. Reinig\\ supported by \\Vandana Gandhi \\ Dolly Sinha;
> \\(Intro and Requirement sections \\revised by R Lechner on Oct 2 1996)
> \\Path: \$CASE/93su523/olc/base/doc/jparchitecture/newarchitecture.tex}
24,25c25,26
< The   large  software  system  are  typically  divided  into
< {\em domains}.   Where a domain is a separate real,  hypothetical,
---
> Large  software  systems  are  typically  divided  into
> {\em domains}.   A domain is a separate real,  hypothetical,
42a44
>               (The Timer class itself is in the service domain.)
49c51
< The {\em implementation domain} is final step in the building  of
---
> The {\em implementation domain} is the final step in the building  of
55,61c57,103
< This OLC Architecture Project comes under above last two domains. There are nine
<  classes in Architecture Project, namely,State Model, Active Class, State,
<  Active Instance,  Transition, 
<  Event Type, Enable , Event Instance and  Timer class. The Timer class is not 
<  incorporated in the {\em olc93su523.sch } schema  though.The methods are
<  written for each class separately in thier respective files , the
<   description of relevent methods is given in {\tt *.h } files.
---
> This OLC Architecture Project comes under above last two domains, Architecture
> and Implementation. There were initially eight classes in Architecture Project, 
> namely, State Model (SM), Active Class(AC), State(ST), Active Instance(AI),  
> Transition(TR), Event Type(ET), Enable(EN), and Event Instance(EI). 
> \footnote{ {\em Ref:} Data model for the  olc93su523 schema in \\
> \$CASE/95f522/95folc/base/doc/lcp\_architecture.idraw}\\
> 
> The Timer Service Class is also documented in this report. Later, a second
> Service Class Operator(OP) was added, with separate documentation
> \footnote{{\em Ref:} User Guide on How the Operator Class Works in the 
> Juice Plant Environment, by C Traynor.}
> 
> The event types are associated with the state transitions which they 
> enable by the associative entity or Enable (EN) table.
> During state model interpretation,
> one or more action routines are executed at each transition-dependent 
> change of state (including re-entry to the same state).
> 
> The functions to be executed at the time of entry to a new state
> are defined as methods in the source code of the class definition 
> {\tt (*.c) } file, and the 
> interface  signatures of these methods are given in the corresponding
> class declaration {\tt (*.h) } files.  
> 
> In this report and in the initial implementation, 
> each state (ST) instance contains the name and address
> of the function to be executed on entry into this state.
> 
> A subsequent revision of the {\em olc93su523.sch } schema incorporated
> a new Function Table (FT) passive class or table
> \footnote{{\em Ref:} see \$CASE/95s522/95solc/aareadme; 
> also revised data models for the Juice Plant in \\
> \$CASE/95f522/95folc/base/doc/lcp\_architecture.idraw\\
> and in \\
> \$CASE/95f522/95folc/base/doc/idrawMainItimer/opfig3.idraw\\
> by bmehta  who updated the main loop timing with setitimer.}
> 
> In a corresponding revision of the olc Architecture, the Event Dispatcher of 
> the state model interpreter was modified to associate the newly entered  state 
> with a sequence of (zero or more) action routines by a new State\-Function map 
> (a binary relation that is defined by the associative entity table SF). 
> 
> \footnote{{\em Ref:} \$CASE/95f522/95folc/base/doc/95folcMainItimer\_md\_dr.tex}
> 
> \footnote{{\em Note:}  Table SF implements a  symmetric 
> M:N relation between ST and FT via associative entity SF; this relation is 
> traversed in the ST to FT direction during state model interpretation.}\\
67,68c109,111
< \item The architecture was to follow the data model presented to us in class.
< This model is show in the appendix.
---
> \item The architecture was to follow the data model presented to us in 93su523
> class.  The original model shown in the appendix was later revised.
> \footnote{{\em Ref:} \$CASE/95f522/95folc/base/doc/lcp\_architecture.idraw}
71c114,117
< used to support the object described by the schema file.
---
> be used to support the object classes and tables described by the schema file. 
> \footnote{JPsim and olcArchitecture were upgraded to chgen v8 by glazar and 
> msrdanov in\\ 
> \$CASE/95s522/95solc/base/Master/JPsim/olc.}
77a124,125
> It covers the state model interpreter but not the application of chgen, 
> nor the service classes TImer and OPerator.
95c143
< \item VAX C V V3.2-004 on OpenVMS VAX
---
> \item VAX C V V3.2\-004 on OpenVMS VAX
119c167
< using {\tt P()} you cannot have a space before or after the comman in the
---
> using {\tt P()} you cannot have a space before or after the command in the
121c169
< comment based token pasting.
---
> comment\-based token pasting.