dialogue monitor. A structured "Menu Selection"
dialogue governs user-system interactions. A tailored
non-procedural language facilitates problem
articulation, with syntax designed to match the
control subject area. Predicates, expressed through
Russian inductive sentences, form co-occurring
formulations, with action preceding a list of goals
representing unknowns. Syntactic rules' keywords are
specified by users within the subject area, ensuring
task formulations adhere to Russian grammar and
meet syntactic requirements.
3.2 Software Suite: A Comprehensive
Selection for All Banking Needs
Models of tasks and technological processes are
stored in the module bank as operation tables. The
control system of this module bank analyses
interactions with operating personnel, creating a
general control system model. Tasks are categorised
into operational planning, control, and analysis
groups. Planning models and optimisation criteria are
defined for each task type, tailoring input and output
forms for operational and management levels. These
forms enable efficient database utilisation by
displaying non-overlapping details.
Depending on production nature and planning
methods, a production situation analysis model is
selected. The resulting control system's conceptual
model undergoes analysis to establish computational
schemes and data access methods. Algorithms are
chosen based on efficiency criteria, transforming the
conceptual model into a computational scheme, with
defined data access schemes, facilitating dialogue-
mode information exchange.
The conceptual model is stored in the application
software package bank's information section,
generating software based on computational schemes
and data access plans. The generated software is
transferred for operation. The application package
bank's information section includes library sets
containing source and object images, program data
sheets, and sets for visual and tabular output forms.
This systematic approach ensures efficient software
generation tailored to specific user needs, enhancing
operational effectiveness and facilitating information
exchange in dialogue mode.
3.3 Decoding the Data Bank: Insights
and Discoveries
The databank comprises organisational list data
structures, detailed in the system feature bank. Its
initial data volume varies depending on task scope.
Primarily, the databank buffers data, bridging time
gaps between solved tasks, and serves as central
storage, ensuring information reliability and validity.
A Database Management System (DBMS) is utilised
as a software tool. Implementing a DBMS
standardises data input-output and facilitates
presentation via program modules, ensuring
information consistency and reliability.
Figure 3: Inside Compass: Understanding Its Database
Management Structure.
The Algorithmic Process Information System
utilises the Compass Database Management System,
comprising schema, fragment, and related schema
translators, alongside a data manipulation language
pre-processor, autonomous access module, utility
group, and resident executive system. At its core, the
resident executive system incorporates the Compass
archive system, resident database management
system, and CMPSA administrative process monitor.
The system's information segment consists of data
structured and utilised within the information
system's functional framework, where stored fields
represent the smallest data units, stored records
comprise related fields, and stored files consist of
records of the same type. Adopting a full network
structure approach in its conceptual model, Compass
also incorporates service tools for system
administration, initiated through dialogue-based
commands at the terminal.
Service tools within the Compass Database
Management System are activated via specific
commands issued in dialogue mode from the
terminal. These tools are categorised into groups