everything a user of a support system is doing can be related to the accomplishment of a goal , for example , to create a new software product . hereinafter the term &# 34 ; process &# 34 ; is used to describe the steps needed to accomplish such goals , including the order in which such steps occur and the like . processes are a natural way to structure the work of a designer . the description of a process , therefore , must be the result of a careful analysis by experts of how a designer should proceed in an optimal way in order to achieve the intended goal . to describe a process formally in the present invention , a special language called pdl ( process description language ) is used . in order to assist a designer in the work defined by the process , the pdl description must be executable , otherwise it would only be a description comparable to a textual description . by executing the description , the user of the system receives guidance through all of the steps required to reach the desired goal . it should be understood that the present invention comprises two distinct elements . first , the process element , and second , the support system element . prior to receiving assistance the process to be supported must be described formally , using pdl as described above . this process description is then input ( in modified form ) to a process description interpreter , whereby the support system can provide assistance in the achievement of the process goals . thus , fig1 illustrates the initial steps of process definition . the process requirements are analyzed in block 300 and an informal model of the process is then created in block 302 ( as for example , a textual description ). in blocks 300 and 302 we have an informal indication of what results should be produced and which different steps need to be taken in the process . next , a pdl process specification is created in block 304 , while the information model of the process , such as data schemes , are fabricated in block 306 . the pdl specification is made by system designers responsible for the support system and who specialize in developing processes tailor - made to the needs of a specific company and / or for a specific purpose , e . g ., feature design , fault reports , etc . ( although an ordinary user could in principle also design a process description ). the pdl description , for example , contains a number of basic features . first , it describes the breakdown of a process into separate subprocesses , each subprocess describing tasks that can be performed in parallel with tasks described by other subprocesses so as to increase productivity . this closely matches the situation a designer faces using a modern workstation , where a number of computer tools can be executed in parallel . each of the tools would then be described by some process in pdl , the subprocess describing what should be achieved by using the tool and how the tool interacts with the other subprocesses or tools . second , it describes how the tasks described by different subprocesses interact by specifying events that are communicated asynchronously between the processes . third , the pdl description describes conditions for the start and finish of a specific subprocess . fourth , it describes the different steps and activities comprising a subprocess , e . g ., edit , compile , link , test , and for each of the activities the conditions that need to be fulfilled in order to start that step or activity . finally , the pdl description illustrates the interaction with the user by dictating how to present information about the state of the process and which possible steps are appropriate to be executed at the present state of the process . in order for the user to make his or her own choices and to avoid the support system being perceived as a hinderance by restricting the user to a certain sequence of activities , three properties of the pdl description are essential . first , only the state of the process determines what can be done ; this assures that the order in which activities are performed are of minimal importance . second , the pdl description assures flexibility by presenting the user with a number of suggestions relevant to the current state of the process , any of which the user is free to choose . thus , the support system does not force the user to follow a certain choice of actions . third , the user can perform activities directly , without using the choices presented by the present invention . these three properties of the pdl description will ensure that the different tasks which the designer has to do can be handled in a way that is not perceived as too rigid . referring now to fig2 there is shown the steps needed to be taken in order to execute the pdl description of the process defined in fig1 and thus give assistance for some particular process . first , in block 350 , the pdl description of the process is created . this description is then analyzed and converted in block 352 to the appropriate format for the assistant logic interpreter . once properly formatted the description is loaded into the assistant logic interpreter 44 ( see fig4 ) at block 354 so that the system can provide the necessary support for the user . these steps are taken by a system programmer in order to prepare the support system to give the assistance expressed in the pdl description . thus , this readies the second aspect of the invention , i . e . , the assistance element . when the user decides to work with tasks described by a certain process , the assistant logic interpreter 44 starts to interpret the converted format of the pdl description , thereby giving assistance to the designer trying to accomplish his task . thus , another name for a pdl description is &# 34 ; assistant logic ,&# 34 ; since pdl describes the logic of the assistant , i . e ., how it works . during execution of the assistant logic , a number of &# 34 ; shadow &# 34 ; objects are created in the assistant . these shadow objects represent the &# 34 ; real &# 34 ; objects , files , descriptions , etc . which the designer is creating and working with as a part of his task . these shadow objects are used in the assistant logic to keep track of the status of each of the real objects with respect to the process describing the work . by keeping track of the state of the objects , conditions can be checked in order to see if new actions are appropriate and in that case suggest them to the user . these shadow objects are part of the information model described in fig1 . now referring to fig3 there is shown a block diagram illustrating the primary components of an expert system , similar to the expert system 20 of the present invention . the typical expert system relies upon a corpus of knowledge that accumulates during the creation of the system itself . this corpus of knowledge resides within the knowledge base 30 of the expert system 20 . information stored within the knowledge base 30 may be broken down into categorical units and discrete sections of the knowledge base 30 . this aspect is shown through the # 1kb and the # 2kb contained in the knowledge base 30 . the knowledge required for proper operation of the support system 8 must be explicit and accessible to the expert system 20 . the general problem solving element of the expert system 20 comprises the inference engine 32 . the inference engine 32 invokes rules stored within the rule base 34 . the inference engine 32 determines how the rules contained within the rule base 34 apply to the problem at hand and the order in which these rules should be executed . many of the rules in the expert system 20 take the form of heuristics which consist of simplified approaches to the search for a solution . in operation , the inference engine 32 scans data in the data base 36 , matching data with the criteria from the rule base 34 . in turn , the heuristic approach relating to the rule base 34 generates information for the knowledge base 30 . initially , the rules employed in the process originate from an expert 38 , with no specific order being required for the rules . further , the information in the knowledge base 30 undergoes real time updating during the operation of the expert system 20 . alternatively , operation of the expert system 20 may proceed by utilizing the induction engine 40 to formulate rules for the rule base 34 . the induction engine 40 operates by deriving general principles applicable to the process from particular information found within the knowledge base 30 . the expert 38 can either provide rules directly or give examples which can be converted to rules by the induction engine 40 . referring next to fig4 there is shown a block diagram of the support system illustrating the component parts thereof in accordance with the teachings of the present invention . being a computer based system , so as to provide the advantages thereof , the preferred embodiment of the present invention resides in a computer 41 which is adapted to execute pre - established sequences of logic statements ( i . e ., programs and / or firmware ) and to read from and write to memory . central to the operation of the support system 8 is the assistant 12 . the assistant 12 comprises the assistant logic module 42 and the assistant logic interpreter 44 . the assistant logic module 42 consists of a converted pdl description as described above , which defines the process and represents the goal to be achieved . the assistant logic interpreter 44 houses the expert system 20 . in one preferred embodiment , the expert system 20 is programmed in prokappa language as designed by intellecorp , inc ., 1975 el camino real west , mountain view , calif . the present invention adds graphics to the supplied protalk language for increased operational simplicity . the assistant 12 , and specifically the assistant logic interpreter 44 , communicate through the message handler 46 with tools in the support system , including but not limited to , compilers and editors . the tool and the tool functions are the basic building blocks in terms of which the process is expressed , and the way through which the process is implemented in the support system . in this way most of the process specific knowledge can be allocated to the pdl description instead of in the tools . therefore the different tools are easier to reuse in other processes , and the tools do not have to be changed when the process is modified . also connected to the assistant 12 is the data base 36 . the data base 36 both stores information generated or processed by the support system 8 in general as well as provides access for the assistant logic interpreter 44 and the assistant logic 42 to previously stored process information . in order to increase productivity when using the support system 8 , each of the tools 22 operate in parallel with each of the other tools 22 ( in different unix processes if implemented on a unix platform ). each tool interacts with the assistant 12 by exchanging messages regarding the current status of actions being taken by that tool . thus , many concurrent activities occur within the support system 8 , and each of these concurrent activities is monitored and analyzed by the assistant 12 . still referring to fig4 there is also illustrated the user interface / activity window 48 of the assistant . the user interface 48 communicates to the user 16 the status of the process and provides the user with guidance in performing the activities defined by the process . the user interface comprises the only element of the assistant 12 apparent to the user 16 . the expert system 20 in the assistant 12 analyzes the actions of the user 16 ( through messages received from the tools or choices made in the assistant user interface ) in the context of the current process and generates the proper graphical information for the particular situation . within the user interface 48 communications of information is possible using a number of different representations . the information displayed , for example , may take the form of lists , or could take the form of graphical representations as well as flow charts . the numerous interfaces available are illustrated by means of the block 50 representing a first alternative interface and the block 52 , representing a second alternative interface . the user has the choice as to which mode of interface is most appropriate with his or her skills and the task at hand . referring now to fig5 there is shown a more detailed flow chart describing the way in which the assistant 12 works in run time , when the assistant logic interpreter 44 is loaded with the process description , as described above . from the flow chart it is apparent that the assistant 12 depends on a number of factors regarding the tools 22 that are part of the support system 8 . first , the assistant 12 must be able to start the tools 22 and to invoke tool functions . this is done through a message handler 46 that takes care of communication . also , the tools must report different events taking place , since most of the tool events have relevance to the state of the process and the achievement of the design goal , such as modifying a file , creating an interface description , or compiling a program . which events a tool should report is decided when the process description describing the task is designed . since a tool can communicate with the assistant 12 no matter where it was started ( from the assistant activity window , from a database browser , or from a unix shell ), the system 8 allows the user to start tools by other means than the activity windows 48 - 52 handled by the assistant 12 . the user can also execute different tool functions directly from the tools that are not necessarily shown as suggestions in the activity windows . therefore , the assistant 12 and the assistant logic 42 must be able to handle events originating from different tools at any time . this is possible since the pdl description , which describes what to do when an event occurs , only refers to the current state of the process , not to the order in which events have occurred ( this is possible using the triggering mechanisms of the underlying expert system ). any event , therefore , is interpreted in terms of the state of the process , regardless of if it was related to a suggestion from the assistant 12 or not . still referring to fig5 a detailed explanation of the flow shown there follows . beginning with block 60 , the user selects the task that he or she should perform . for example , the task could be the design of a new software product , or taking care of an error report . in block 61 , the assistant 12 selects the appropriate pdl description of the particular task ( this is done internally and automatically within the assistant ). this description has previously been analyzed and converted as described in fig2 . proceeding on to block 62 , the current state of the process describing the task is loaded into the assistant 12 from the database 36 . this loading is most relevant when the user has previously worked on the task and saved the status of the prior work . in block 63 the assistant 12 makes suggestions on the actions to be taken based upon the current state of the process . the manner in which the suggestions are shown depends upon the user interface employed as described above . block 65 describes the assistant 12 waiting for events occurring in the support system 8 . the branch to block 66 indicates that a tool reports the result of a function invocation as an event to the assistant 12 . in response to the event generated in block 66 , block 67 changes the state of the process , since it is derived from the events taking place in the support system 8 . if the user had made a selection of one of the assistant &# 39 ; s suggestions from within the activity window , block 68 would be active . if the branch from block 68 to block 69 is followed , and the suggestion selected from within the activity window involves executing a tool function , the tool 22 is started ( if needed ) and the proper function called via the message handler 46 . proceeding on to block 70 , the state of the process is changed , reflecting the invocation of the tool function . if , however , the suggestion selected by the user does not involve invoking a tool function , the internal state of the process is changed through the mere selection made by the user . in this case , the user usually indicates that some manual activity has been performed in the process . after the state change has been effected , in block 72 the assistant 12 deduces the effects of the change . as a result of the analysis conducted in block 72 the assistant may then automatically invoke other tools in block 73 . further , as a result of the analysis in block 72 a consistency check between different information elements may automatically be precipitated in block 74 and the errors found therein would then be reported in block 75 . additionally , the assistant 12 may , as a result of the analysis of block 72 , deem automatic tool invocation unnecessary and , instead , generate a new set of suggestions for the user . the new set of suggestions are based upon the new process state created , whereupon the cycle is repeated . if , however , the user wishes to quit that occurs in block 77 and the state of the process is saved in block 78 . referring next to fig6 there is illustrated the browser server 90 aspect of the present invention which comprises an independent element of the support system 8 . the browser server 90 allows the user 16 to look for objects in the system data base 36 and to select those objects without direction from the assistant 12 . the browser server 90 does not provide suggestions to the user . found objects such as descriptions , flow charts , programs , etc . may be examined through the browser server 90 , and tool operations on the object can be initiated . still referring to fig6 the browser server 90 begins with the start browser block 92 . upon commencement of the browser server 90 , the user , at block 93 and 94 , can search for and select an object in the system data base 36 . when the object is selected a menu can be displayed , at block 95 , of available operations for the object . the block 96 starts the tool 22 and this fact is reported to the assistant 12 in block 98 . this permits the assistant view of the system to be consistent , in terms of knowing what events are taking place . thus , the user may interact with the support system 8 in a variety of ways , one of which being through the browser server 90 , and still getting support from the assistant 12 . referring next to fig7 there is shown a flow diagram of tool function invocation . since the user can initiate the tools 22 without help from the assistant 12 , the user can also execute different tool functions that are not necessarily shown as suggestions in the activity window handled by the assistant 12 ( as described above in the browser aspect ). thus , the assistant 12 and the assistant logic 42 must be able to handle events originating from various tools at any given time . this is possible because the pdl description , which describes what to do when an event occurs , refers only to the current state of the process , not to the order in which activities have been performed as mentioned above . any event , therefore , is interpreted in terms of the state of the process regardless of whether or not the assistant forwarded it in terms of a suggestion . consequently , for a tool designer to conform to the requirements imposed by the assistant 12 , the tool must function in the following manner . first , the tool function is started at block 370 , and this fact is reported to the assistant . after the start , the tool can accept an invocation of a tool function in block 371 . the tool function is invoked either through the assistant 12 via block 372 or through the tool user interface via block 374 . next , the tool function is performed at block 376 , and , if required by the process , the results therefrom are reported to the assistant 12 at block 378 . again , the tool functions relevant to the process ( and thus required to be reported to the assistant ) are determined during design of the process . the cycle is repeated , and the tool is ready for the next tool function to be initiated from the waiting for invocation block 371 , or the tool is stopped at block 380 . referring next to fig9 there is shown a pdl diagram of an example of a typical process description specifying the assistance given in one of the prototypes of the present invention which illustratively describes the different steps a secretary needs to take when handling a meeting . since the process description is expressed through graphical symbols , the flow diagram of fig9 employs such graphical symbols in the following discussion . furthermore , the system 8 converts the graphical flow diagram to a format that can be interpreted by the assistant logic interpreter 44 as described above . the textual information shown in fig9 - 15 is a partial view of the complete content of the flow diagram . each graphical symbol can have different kinds of textual information attached to it ; an informal comment , implicitly or explicitly specified executable code , documentation , parameter specifications , etc . the view presented in fig9 - 15 only shows the parameter specifications for the icons in order to simplify the diagrams and render them easier to read . in this view both variables and constants are specified as parameters , with variables being designated by a question mark as the first character thereof . in the graphical editor supporting this language , this view can be changed to any of the other views described previously . referring next to fig8 there is shown further examples of the components of the pdl icons . a basic building block in pdl is the activity construct which describes the conditions and effects of an activity and takes the general structure illustrated in fig8 . the activity icon 386 is surrounded on one side by the precondition icons 388 . the precondition icons 388 describe the necessary conditions for the activity to be executed . for example , in fig1 , the symbols 140 , 142 , and 144 are all preconditions . the activity icon 386 acts as a reference to the complete construct , i . e ., all of the preconditions and effects . the effect icons 390 can represent an operation to be performed , either by the user or automatically through the assistant 12 . there also exists a number of different predefined icons representing specific conditions and effects , e . g ., menu icons , file icons , clock icons , etc . predefined executable code , documentation , etc . are attached to those icons , and parameters can be given to the icons . it should be noted that all variables introduced in an activity are local to the activity . as stated above , shadow objects internal to the assistant are holders of state information . in order to keep track of documents , programs , the different processes , subprocesses , etc . all of them are represented as shadow objects in the assistant 12 . these shadow objects are created when the corresponding real objects are created . there exists a specific icon in pdl , the instantiation icon ( instantiation in general means creating a particular example from a template , such as a description of a shadow object ), that represents the creation of a shadow object . in the case of the instantiation symbol 102 in fig9 a , a secretary task is instantiated . the diagram of the secretary task is in general describing a number of possible tasks and many different meetings can be arranged using this description . when executing the description in order to assist a user in arranging a particular meeting , this particular meeting arrangement task must have a representation , i . e . , a shadow object . the instantiation symbol 102 represents the creation of such an instance , which then can hold status information about this particular meeting arrangement task , and can be referred to from other parts of the diagram . referring next to the flow diagrams of fig9 a - 9c , the process described relates to the tasks required of a secretary to arrange a business meeting or the like . the diagrams show different aspects of the process . the uppermost part , fig9 a , is a descriptive illustration of the start conditions of the process while the middle part fig9 b , describes the breakdown of the process into subprocesses . the secretary process , as is possible for any other process handled by the support system 8 , can contain several subprocesses . the subprocesses illustrated in fig9 b are the material subprocess 108 , the notice subprocess 116 , the meeting subprocess 118 , the text editing subprocess 119 , and the protocol handling subprocess 122 . the material subprocess 108 describes how to collect the materials needed for the particular meeting while the notice subprocess 116 describes how to send information to the attendees of the meeting . the meeting subprocess 118 describes how to conduct the meeting and the text editing subprocess 119 describes how to enter text ( for example , what tool to use ). the protocol handling subprocess 122 describes how to handle the subtask of writing a protocol . the lower part , fig9 c , describes the stop condition of the process . it should also be understood that there exist other views of the process ( interface view , activity view , etc .) which are not shown in fig9 a - 9c . each of the subprocesses begins automatically once the criteria for instantiation have been satisfied , which for example , could be that a service which the process offers has been requested ( such as text input from some other subprocess ). a sequence of processors or subprocesses can also be described , and in this case the event important to the task of a succeeding process is the event &# 34 ; finished &# 34 ; reported by the preceding process . the transfer of information diagrammatically indicated by arrows such as the &# 34 ; edit &# 34 ; arrow 112 and the &# 34 ; material finished &# 34 ; arrow 114 within fig9 b , further illustrates the exchange of events relevant to the subprocesses describing concurrent tasks . the arrows are of no semantic importance in the diagram and are only an informal way of describing information flow . the real exchange of information is handled by the inference engine 32 of the underlying expert system 20 and is described in detail in the corresponding subprocesses . the icon 100 , represents the fact that the support system 8 begins its operation by receiving an external event that initiates the process ( corresponding , for example , to the user creating a new meeting arrangement task ); the parameters of the event is the name (&# 34 ; start &# 34 ;) and the kind of process to start (&# 34 ; secretary &# 34 ;). instantiation occurs at icon 102 . the symbol 104 represents the setting of initial values associated with the secretary process , and is described as a state change of the process ( the aspect &# 34 ; started &# 34 ; of the process is set to true ). the activity icon 101 represents the complete activity , as described above . referring next to the different arrows shown in fig9 b , the edit arrow 112 indicates the material subprocess 108 referring to a service handled by another subprocess . in this case , from within the material subprocess 108 the text editing subprocess 119 is utilized . the text editing subprocess 119 describes how to use a text editor which can be performed in parallel and concurrently with activities described by other subprocesses in the system . once the material subprocess 108 and the notice subprocess 116 have completed their respective tasks the finished events 114 and 115 occur . the &# 34 ; notes from meeting &# 34 ; event 120 from the meeting 118 indicates that data from the meeting is available . the meeting data is utilized by protocol handling subprocess 122 which represents the postmeeting work which must be done . the edit event 112 leads to further text editing by text editing subprocess 119 . thus , fig9 b illustrates event exchanges between subprocesses describing tasks that can be executed in parallel . the tasks of the material subprocess 108 and the notice subprocess 116 , for example , can occur in parallel , as is evidenced by the lack of any synchronizing events being exchanged between them . referring now to fig9 c , in icon 124 , the condition describes the state where the halted aspect in any subprocess is true . in icon 126 the condition states that such a process must be of kind &# 34 ; protocol handling &# 34 ; to be of interest for this activity . in icon 128 the secretary process ( identified by process ) is found which owns the halted subprocess . finally , in icon 130 the secretary process is halted . referring next to fig1 , there is also illustrated the method for processing data pursuant to the teachings of the present invention . this represents an instantiation of the notice subprocess 116 of fig9 . thus , the secretary task must have been started , which is represented by the symbols 130 and 132 ( the started aspect is true and the kind of process is &# 34 ; secretary &# 34 ;). when the precondition is true , the activity 135 is begun and the instantiation of the notice subprocess 116 is effected in symbol 136 ( the reference to this instance is &# 34 ; subprocess &# 34 ;). then at the symbol 138 , the initial values of the notice subprocess are recorded as state information . referring next to fig1 , there is illustrated , in further detail , the method for processing data pursuant to the teachings of the present invention and , in particular , an edit activity 145 . the mechanisms of the underlying expert system will detect when the preconditions of the activity are true . for the edit activity 145 to be possible , the symbol 140 indicates that the notice subprocess must be started . the symbol 142 indicates that data requiring temporary file storage will be generated through the present activity and , therefore , a temporary file name must be known in order to store the information ( the way in which this is done is described in the code section of the symbol which is not shown here ). next , the menu 144 functions as the description of interaction with the user . in pdl language the menu symbol abstracts the way in which the assistant 12 interacts with the user , for example , activity lists can be presented to the user . first , the symbol represents the text ( in this particular case &# 34 ; write notice &# 34 ;) that is presented to the user . the text presented describes an activity that can or should be performed by the user . the menu 144 also implies an object , e . g ., a file , code , etc ., on which the activity is performed ( in this case the temporary file represented by ? temp ). further , the menu 144 represents a condition . before the user explicitly selects the activity in the activity list , this condition is always false , and the effects , such as execution of a tool function or a state change , are not effected . when the user selects the activity in the user interface , the condition becomes true and the effects are executed . in this case , when the user selects the write notice choice in the activity list , an edit event is sent ( corresponding to arrow 112 in fig9 b ) in symbol 146 to another subprocess requesting an edit task . this request is handled by the text editing subprocess ( not shown here ), where the editor is started and the user then uses the editor to write notice of the meeting . referring next to fig1 , there is shown further details of the data processing of the present invention . the description of the notice subprocess 116 continues with an activity 151 comprising the retrieval of data pertaining to who is going to attend the meeting . the symbol 150 indicates that information must be retrieved if the state of the &# 34 ; others &# 34 ; aspect of the process is false . the symbol 152 could result in a menu window which requests entry of those expected to attend which would then be described in the code view of the icon 152 , using basic windowing primitives supported by the system . the symbol 154 represents the state of the notice subprocess 116 and symbolizes that retrieval of the names has occurred ( the state of the &# 34 ; others &# 34 ; aspect is now true ). this activity is triggered by the activity described below in connection with fig1 . referring now to fig1 , the description of the notice process continues . beginning with the symbol 160 , an event from another subprocess is detected in which a file has been saved . this information originates from the text editing subprocess 119 . at the symbol 162 , the system performs a check to verify that the file saved is the same file as referred to in the temporary filename 142 ( this is part of the state information of the process ). the system next checks whether the next condition has been satisfied , i . e ., whether all other attendees have been accounted for , which occurs at symbol 164 . if this is not true , the activity of fig1 is triggered in order to get the attendees . here the goal driven aspect of the underlying expert system is used , i . e ., if a condition is not fulfilled and there exists an activity the effects of which will satisfy the condition , this activity will be performed . at the symbol 166 , the system ascertains whether notices have previously been sent to the attendees ( this is recorded as state information on the ? file object ). this illustrates the non - sequential character of the overall support system 8 . with each of the processes and subprocess operating in parallel fashion and concurrently , the system must perform checks to assure itself that work does not get repeated , and thereby result in erroneous results , in decreased performance and slower processing capabilities of the system . thus , because only one notice of the meeting is required the symbol 166 performs the check . in satisfying the final condition , the menu 170 provides the user 16 with the choice of selecting the &# 34 ; send notice &# 34 ; activity 171 . at symbol 172 , the assistant of the present invention sends the notice and prints it . the symbol 172 symbolizes an operation which loads , mails , and prints the notice for transmittal to all necessary parties ( which could be achieved by using the unix mail and print services which are again described in the code view of the icon ). the symbol 174 records the state information that the notice has been sent on the ? file object , and thereby this activity cannot be repeated . referring now to fig1 , elements of the notice subprocess are further detailed in diagrammatic form . the symbol 180 indicates the condition that a &# 34 ; hard copy &# 34 ; of the notice must already have been created ; in other words , the notice was printed ( this occurs in activity 171 above ). the menu 182 , tells the user that the notice should be placed on the notice board in the desired location . the activity 184 in this case represents an activity which the support system 8 cannot assist in by supplying tools ; rather , the user must physically place the notice himself or herself . therefore the icon 186 indicates that only an internal state change takes place in this activity and no external tool is involved . finally , referring to fig1 , the activity 194 comprising completion of the notice subprocess is illustrated therein . the conditions 190 and 192 are true when the notice has been sent and posted . the symbol 196 stops the process , and the symbol 198 records this state change . it also operates an event for processes interested in this fact due to the triggering mechanisms of the expert system . referring back to fig9 b , it is seen that the notice subprocess 116 leads to the meeting 118 , when the finished arrow 114 is followed . thus , at the occurrence of the event 198 the meeting 118 would be instantiated and the necessary steps and tasks required to complete the meeting would then take place . a symbol identifier description is attached hereto as appendix a . the description defines the graphical symbols utilized by the support system 8 as illustrated in fig8 - 15 . also attached hereto , as appendices b and c are detailed program listings for carrying out the data processing steps for a different prototype designed according to the teachings described in this application . more particularly , appendices b and c are program listings illustrating the manner in which code is generated in prokappa language by the pdl graphical language for execution within an expert system 20 of the type used in the present invention . while the exemplary processes defined by the program listings of appendices b and c are entirely different from the example of the secretary process shown in fig8 - 15 , the listings are instructive to illustrate how the pdl definition of a process is reduced to executable code . in fig8 - 15 a number of different activities have been shown . these are internally non - sequential , since the conditions for each of them are tested for validity no matter which other activities have been performed . in this way a maximum of flexibility can be achieved for the end user . through the mechanisms described above , the support for different tasks can be created and modified without having to change the different tools being used . the formal description acts as a control program on top of a number of components , describing the logic that is needed in order to make single tools act in an integrated way . thus , there has been described and illustrated herein a method and apparatus for system development support . those skilled in the art , however , will recognize that many modifications and variations besides those specifically mentioned may be made in the techniques described herein without departing substantially from the concept of the present invention . accordingly , it should be clearly understood that the form of the invention as described herein is exemplary only and is not intended as a limitation on the scope of the invention . ## spc1 ##