Goals (20) for the Book

  • G1 To find an atomistic, reductionist representation for source code as a basis for a higher-order model, simulation, and user interaction.(48)
  • G2. The main concepts express the metatheoretical relations of the proposed PC according to Peirce’s semiotic triad.(50)
  • G3. To emphasize the meaning of the symbolic language: both in translating source code into an internal language and further into a metalanguage for user interpretations.(51)
    G4. To establish a convention to define an element for symbolic presentation.(52)
  • G5. To implement GrammarWare using a symbolic formalism.(54)
  • G6. To create a model weaver for ModelWare in order to build a reductionist model for embedding Java semantics to it for simulation purposes.(55)
  • G7. To describe formalism for source code simulation according to the automata theory as well as to create a platform for partial simulation.(56)
  • G8. To create a bridge between the code model and the user language supporting the maintenance approach based on KnowledgeWare.(57)
  • G9. To describe transformation semantics between the technology spaces as automata.(59)
  • G10.To express the main relations of the captured knowledge as nested types as a multi-layer presentation.(59)
  • G11.To realize a knowledge access interface containing the three semiotic layers.(60)
  • G12.To create a sequential computation model for SimulationWare.(63)
  • G13.To illustrate how to implement parallel activities, e.g., threads in order to capture program flows.(64)
  • G14.To plan a hierarchical action model to support solving maintenance tasks in the known cognition layers.(65)
  • G15.To express the user’s questions and hypotheses in a formal way, referring to a singular element or a flow of the model or to a derived tree.(66)
  • G16.To show a demonstration for simulating an example and a theoretical approach as regards the captured PC flow using hypotheses.(69)
  • G17.To validate the process – including all technology spaces – by a small sample program by comparing its output tape with a manually estimated program flow.(70)
  • G18.To create a hybrid construction, combining the benefits of OOP and logic programming.(73)
  • G19.To show how a PC process works leading to low-level actions.(74)
  • G20.To formalize the main features of Pragmatics in Visual Prolog and to demonstrate the corresponding tool, JavaMaster.(75)