Sphere CASE: operation technology

This chapter describes common operation logic of a generic Sphere CASE application.
A Sphere CASE application consists of the following components:

1. The Sphere Portal universal client - implements basic functionality.
2. Metalogic unit (can be more than one) - implement(s) application-specific functionality.
3. Database script - implements logical database scheme structure.

Metalogic unit and database script are output produced by the Sphere Modeler. Processing database script with DBMS tools results in creation of application database scheme in which the above mentioned metalogic unit(s) also reside. Sphere Portal executable (less than 1Mb in size) has to be installed on the customer's machine to access application database. Launched it will query customer of the workplace he(she) wishes to work with. After that the appropriate metalogic unit (normally about 20Kb in size) is loaded from application database resulting in full-blown application-specific window GUI (Fig.5). Upon next start-up the Sphere Portal will check for conformity of metalogic units for the workplace stored in application database and units loaded previously. If updated the new metalogic units are reloaded from database otherwise cached metalogic is used. This approach enables for almost instant loading of application functionality optimising overall system performance.
The loaded metalogic units are executed (interpreted) by the Sphere Portal on the fly providing for combined basic and application workplace-specific functionality. The Sphere Portal interacts with DBMS through SQL queries optimized for Oracle Database platform and operation specific parameters of an application database (logic scheme, population parameters, estimated transaction traffic, etc.). Net/8 (Oracle Database 7.0-8.x) protocol is used for data exchange over network. Oracle Database security options can be used to ensure appropriate application data protection if necessary.

Fig.5. Sphere CASE operation logic

The Sphere Portal universal client (Fig.6) is the Metalogic Interpreter built on top of the system of program parameterized solutions (PPSS). Operating it combines own internally realized basic data manipulation functionality with externally realized application-specific business logic functionality stored in metalogic unit(s) interpreted. The ultimate effect of a metalogic unit(s) interpreted with the Sphere Portal is full-blown application workplace-specific window GUI. The Sphere Portal's universal nature enables customer to use it for work with any application workplace-specific functionality available as it only goes to loading another metalogic unit(s) into it. Another advantageous issue is possibility of simultaneous design of metalogic units (implementing new application-specific functionalities) and improvement of Sphere Portal engine (implementing new basic data manipulation capabilities).

Fig.6. Sphere Portal logic structure

Document
Data available for browsing and editing are displayed as basic documents (complex / compound application forms), which in general correspond to customer's hardcopy documents. Document sets are defined by application workplace-specific functionality. A document (Fig.7) can consist of one header/master (dialog) form and several detail (grid) forms (these can be lists with complex hierarchical structure). Besides that, there is a business logic unit (in VB Script) correlated with the document. Simple or hierarchically structured lists opened in a separate widow upon activation can reside in master and / or detail forms.

Fig.7. Document structure

Business logic unit (in VB Script) is available for editing within the Sphere Portal object model framework. It can be used to write code making calls to stored procedures, handling data displayed in a document (i.e. implementing business logic which is more suitable to be placed on client), displaying custom messages in information panel, etc. Standard tools like Microsoft Script Debugger can be used for debugging business logic units.

Document browser
Document browser is used for navigating different documents grouped by types or, in other words, different document registers (sets of the same type documents correlated with same form). It involves complex filtering mechanism displaying data in a Tree View structure and providing for quick navigation through locally cached recordsets.

Lists
All reference data are gathered in correlated lists. The advantage of using lists is reduction of mistyping errors through providing sets of predefined values to input reused data into documents. If updated in list the reference value is tracked and all necessary updates are applied automatically across all correlated documents. Lists can have simple or hierarchical design. Hierarchical lists with given nesting depth can be of complex tree-like structure with any branch presenting another simple or hierarchical list.

Analytical report
Analytical report provides for browsing and printing of access-granted data enabling analytical / display view customization. The starting set of analytical reports depends on the application-specific functionality of the system. Custom new analytical reports can be created with embedded editor.

Print report
Each basic document can have one or more print forms to produce hardcopies of its contents. The starting set of analytical reports depends on the application-specific functionality of the system. Custom new print reports can be created with embedded editor.

Context-sensitive help
Realized in standard format of context-sensitive help for Microsoft Windows the Sphere Portal help system presents a comprehensive reference on basic Sphere Portal data manipulation functionality and application workplace-specific functionality contained in the metalogic unit currently interpreted. Furthermore, the workplace-specific functionality reference is displayed in structure grouped regarding document types involved (basic documents, document registers, forms, lists, analytical and print reports, etc).
Operations available with Sphere Portal controls:

1. Edit:	Analytical / print report data / structure can be edited.
2. Browse:	Hierarchical list level navigation is performed.
3. Create new:	New analytical / print report can be created basing on existing template.
4. Print:	Print options can be set through an Options dialog.
5. Copy:	Document data can be copied to another document provided both of the documents have the same structure.
6. Extract:	Document data can be copied to another document with different structure.
7. Auto number:	Customized auto numbering mode can be set for each document type.
8. Initialize:	Master / detail form controls can take values by default. These can also be set dynamically with VB Script code in business logic units.
9. Value control:	Input data is controlled for compliance with integrity constraints.
10. Comment:	Custom messages can be displayed in information panel (done through business logic units in VB Script).

Basic features

1. Browsing and editing of data stored in DBMS.
   
2. Interaction with other third-party software through OLE interface.
   
3. Analytical report creation and editing.
   
4. Print report creation and editing.
   
5. Configuring GUI settings and DBMS connection settings.
   
6. Sorting, search, filtering by complex customized pattern.
   
7. Context-sensitive help.
   
8. Form editing.
   
9. Business logic editing (VB Script).
   
10. Document copying and specific data extraction.
    
11. Document grouping into document registers.
    
12. Analytical and print report printing.
    
13. Embedded network connection diagnostics tools.
    
14. User profiles stored in Registry.
    
15. Embedded audit tools.
    
16. Access control tools (for administrator only).
    
17. Normal operation at connection speeds of 9600 bps and higher.
    
18. Metalogic unit stored at server (all advantages of browser approach).
    
19. Easy implementation of new application-specific functionality.
    
20. System can be tuned and administered remotely.
    
21. Security issues addressed at database platform level (Oracle Database / Microsoft SQL Server).