Business Programming Problems and their Solutions
Business Programming Problems and their Solutions by Mykosmos/BOS
Please check the following list of facts:
|
Business Programming Problems... |
...and... |
...Solutions by Mykosmos/BOS |
||
|
Program business procedures |
||||
|
The programming languages of usual RAD tools can not express business processes. So there is a need for a different tool to express business processes in addition to the classical database programming... |
|
...AutoScript, the scripting language of Mykosmos/BOS has the power to express directly business processes by assigning jobs to users, wait for their finish, split process path and more. Classical database and process programming can be mixed. |
||
|
Support for company Organogram |
||||
|
The usual RAD tools, used for business programming, cannot support out of the box the concept of company organogram... |
|
...Mykosmos/BOS has in advance took care of company organogram by supporting it in "system tables". The programmed business processes use extensively those tables, by assigning jobs to employees according to their roles. |
||
|
Procedure progress visualization |
||||
|
Any of the RAD tools cannot show a business process progress in any way. Simply they can not code it... |
|
...Mykosmos/BOS can show the progress of any programmed business process graphically. |
||
|
Fast development cycle |
||||
|
The RAD tools separate completely the design running mode and the application running mode. So the development cycle is longer and slower... |
|
...Mykosmos/BOS has a shorter development cycle because the developed application is always in running mode. So while running the application the developer can "right click" and design-create every resource (forms, menus, reports,...) |
||
|
Easy of support and maintenance |
||||
|
The delivered applications of usual RAD tools are poorly maintained. The whole application has to be reinstalled in every, even minor, change... |
|
...Mykosmos/BOS delivers applications that keep resources outside the delivered executable. So every form, report or menu can be simply e-mailed to the customer's site. |
||
|
Test-Debug at customer's site |
||||
|
The delivered applications of usual RAD tools are poorly supported. Debugging at the customer's site using "live data" is out of the question... |
|
...Mykosmos/BOS delivers applications that can be redesigned-debugged at the customer's site by simply "right clicking". So testing using "live data" and support on site is a usual practice. |
||
|
Run in 3 tier architecture |
||||
|
The delivered applications of usual RAD tools cannot run in 3 tier architecture. Extensive programming required in order to achieve this... |
|
...every delivered Mykosmos/BOS application runs in 3 tier architecture, over TCP/IP, by default. |
||
|
Support of Software Agents |
||||
|
The usual RAD tools can not program (in business programming level) software agents. It is considered as a very advanced feature... |
|
...Mykosmos/BOS can support "coordinators", "planners" and "experts" as software agents in order to support business logic and processes. Those agents are programmed using AutoScript. The normal scripting language of this RAD tool. |
||
|
Test-Debug Software Agents |
||||
|
The debugging of software agents, if they supported, is tedious in any programming environment... |
|
...Mykosmos/BOS has a unique debugger even when "agent code" is tested. In the same machine, the developer can write-test a "coordinating agent" that its activity normally is spreaded to different machines. |
||
|
Automatic Document Management |
||||
|
The usual RAD tools cannot support document management. This is considered as a different tool's capability... |
|
...Mykosmos/BOS can support document management at an adequate level, by allowing any database record (form) to be related to any number of (saved and compressed) files. |
||