================================ þ THE GUIDELINES DEVELOPMENT MODEL ================================ Constructed along a six-part development model, which is ideally suited to both old and new operating environments, Guidelines has been built to answer the needs of developers wishing to produce software that is capable of addressing heterogeneous computer networks from one single development point. The development model makes it possible, for example, to create a GUI that can be re-compiled to run under both the OS/2 and Windows operating systems, maintaining the same look and feel, as well as a single set of source code for the interface. Developers can then create a Logic module (program) to run on a client workstation today, one which is capable of being re-compiled (in a different language if necessary) and placed on the server without destroying the integrity of the application using that program. By making the programs 'network intelligent , they can then be deployed into both a desktop and a corporate server for large numbers of clients in multiple sites and environments. This allows them to control their performance and workstation access to information from a central point of the application servers. The next level, the repository, can control the same source code and databases of a corporate teamworking development environment dealing with large groups of developers, all working on versions of the same application(s). The repository will also assist in ensuring that all delivered programs are working and tested. Finally, applications can be developed which, instead of 'hard coding database and program-to-program access, can be 'soft coded to ensure re-usability of code, and the ability to change hardware and networks without major upheaval. The move from todays' Tables and Views database technology, which applications currently being developed will comply with, to the future's OOT will be a major step for most companies. Many will want to test the water by running applications systems with a partial database and a partial Object store structure. Guidelines is unique in allowing you to do this, thus providing a gradual evolutionary move into the new OO environments, rather than a single expensive revolutionary leap. ================================ þ THE GUI ================================ The GUI segment of JBA Guidelines delivers a highly productive environment which enables both business and technical users to contribute to the application development cycle. Its intuitive and natural interface has been developed to combine direct manipulation of on-screen design with a range of powerful controls for the professional developer, who can also create professional and consistent applications without needing to know about low level operating system screen interfaces. Now, system architects can deliver enterprise business data in an accessible manner appropriate to the level and needs of the users, even if a number of GUIs of varying complexity and design will be required within a single application model. As a result, system designers can concentrate on delivering benefits in the development processes, allowing intended users to become ever more involved in the design phase. The result of this co-operation is that the GUI software development tool must be flexible enough to allow end-users to interpret and model their ideas while having a sufficiently rich feature set to allow developers the freedom to re-interpret these ideas in a practical and deliverable form. As any system should be live and dynamic, the Guidelines GUI tool will also allow future changes in business practice to be reflected in the delivered application without compromising system integrity. And to ensure that they will run faster than equivalent-function interpreted GUIs, graphical applications generated by Guidelines are native-compiled C++ programs. They can be either self contained .EXE files, or .DLL files - in fact, a completed business application will be a combination of both. The advantage of this approach is the re-usability of program and interface code across the enterprise. There is also an event driven programming environment which automatically creates event driven programs. Any number of program modules can be created to perform either multiple or single application-related events, and support for programming direct control related events such as clicking a button, or selecting a menu item is included. ================================ þ LOGIC, LANGUAGES AND COMPILER ================================ Following the acceptance of workable client-server environments and the emerging importance of object enabled applications, the location of business logic underpinning enterprise IT systems will do much to determine the scalability, transportability and reliability of the application. To meet these, system developers require the ability to partition application logic into discrete components physically resident on the most appropriate host platform. This not only ensures effective use of resources but enables working legacy code to be incorporated into the re-engineered solution. With Guidelines, developers are free to choose the most appropriate platform for the business logic without requiring a change in toolset. This choice can be made on the basis of client rather than vendor need, to ensure the best business fit. Furthermore, existing logic can be substituted for object based business code at any time, future proofing critical applications and reducing maintenance. A critical decision for any application developer is the choice of language. This will underpin the ability to deliver a workable business solution within the time frame required and to the desired specification. To be most effective, the language must be flexible, rapid, rich in function and high in performance and scalability. It must also be capable of extending to meet the changes inevitable with Object Oriented application design and implementation. JBA Guidelines meets the challenge by combining the rapid application development features of 4GLs with the generation of native code for the client or server. It does this by providing JOT, a platform independent High Level language. JOT combines the look and feel of languages such as RPG, C, COBOL and BASIC, with the ability to generate C++ code for the target platform. The JOT language has been designed for rapid learning by both experienced and novice programmers while offering the range and breadth of function required for serious client server developments. Guidelines enables developers to select a target compiler for the platform of choice and generate native C++ or RPG code, for platforms which include OS/2, MS Windows, AS/400 RPG and AS/400 C++. The modular design ensures future platforms may be incorporated when required. Guidelines offers the C++ developer the ability to either program in JOT, or C++, or to combine both languages within an application to provide the required end functionality. Again whatever language the developer works in, the resulting applications are generated in native C++. ================================ þ NETWORK MANAGEMENT AND CONNECTIVITY ================================ Network management is an extremely important and usually neglected part of overall enterprise-wide systems control. Applications created by localised development tools run autonomously, with little or no control over the location of the servers that support the applications users. Guidelines, in an upcoming release, will be able to design and build large-scale solutions which can incorporate application partitioning principles, with the ability to move both data and logic around the enterprise computing model in segments controlled from a central location. A central administrator may maintain any or all of the desktop Guidelines application environments, so if a server fails, a central administrator can "switch in" an alternative server by updating all users Guidelines environments to reflect the changed location of the databases. By doing this, failure of key sites or even total disaster situations can be handled from an Enterprise's central facility, minimising any impact on the ability of the enterprise to continue working. The Guidelines network management facility also means that changes in hardware platform strategy can be easily accommodated. So if strategy changes from PC-LAN to central minicomputer then once the data and logic have been transferred to the new platforms, the users can be software "switched" from the old platform to the new. Guidelines generated Applications are today capable of concurrently accessing multiple databases on multiple platforms, enabling the applications developer to create a client application which uses data from say an Oracle database on an RS/6000, and DB2/400 on the AS/400, to deliver business functions such as Order Processing. The network management and connectivity segment also offers efficient networking capabilities, as well as a mix of hardware and software networking strategies, with differing client and server requirements for database access. And the DCE three tier model (Distributed Computing Environment) builds workgroup client-server solutions that integrate to a mainframe for a true enterprise-wide IS strategy. Whatever strategy is adopted, it will be flexible enough to cater for all foreseeable current and future requirements in order to facilitate the emerging OOT without invalidating current conventional requirements. Guidelines offers standard interconnection methodologies such as TCP/IP, SNA and named pipes, so that heterogeneous computing environments can be built to take advantage of the strengths of the components. By mixing the network connectivity components as required, applications can be built to conventional thin client-server standards, thick client-server with application partitioning and also to fully distributed Object Oriented application standard. Or any mix of these topologies, ensuring an easy transition from conventional procedural to full Object Oriented solutions. ================================ þ THE REPOSITORY ================================ Guidelines Repository supports and surrounds the entire application programming environment with the facilities required for successful teamwork based development. Code can be shared between programmers, who also have the ability to control versions of program code and book them 'in and out for maintenance and enhancements. Databases can be created on multiple hosts from a single definition, and then data definitions can be directly imported into a GUI program, thus ensuring the integrity of the underlying data files. Access is provided to multiple databases for both creation of new tables and views and the access during a running application program. The ability to run a teamwork programming environment and split programming teams into functional units according to the application design and version control at the program (Class) level is also provided. This enables large projects to be broken down into more manageable parts, each with a specific delivery target. Guidelines Workframe provides a single developer or a development team with a single point of entry for all the tasks involved in successful application development, and any subsequent maintenance or enhancements of any part of the application. It includes a standard method of creating and accessing all of the functions required by a teamworking programming environment including Version control. And the Workframe also provides access to a Class Browser which is capable of both displaying and creating CORBA standard Object Classes and method definitions. There is also a single method of access to the database (tables and views) structures, regardless of their physical implementation. It is even possible to create a database on one platform and then transpose it to the other for implementation. Guidelines enables the development of corporate applications away from the target server platform, allowing you to run multiple developer teams which may not be physically attached to the same repository management server. This provides the application development management to run a greater number of developers than would normally be supported should they all need to be attached concurrently to a central server. ================================ þ MESSAGING ================================ The challenge facing application developers today is to create applications which not only address current problems and use whatever available technology is best suited to the business user today, but which are still capable of adapting to and coping with the problems of tomorrow. For example, applications written today use Tables and Views, whereas those designed for the future will use Distributed Objects. Therefore, as technology which can provide business related advantages gradually changes and becomes available, so the applications must be capable of changing to match it. The answer is the unique Guidelines Messaging component. It provides the developer with an Object programming environment, while providing the ability to access both current technology and the OO environment of tomorrow. To ensure that there is the ability to re-use programming code modules in a structured manner, the Message layer has been designed and constructed to fully comply with the CORBA standards. With its native JOT verb support, the Guidelines message layer has a single programming interface which is consistent with the entire application development environment. And to support heterogeneous implementations Guidelines provides CORBA IDL support. The problems with standards, however, is that they evolve almost as fast as the technology itself. With JBA's experience and expertise, which have placed us at the leading edge of object development strategies and earned our place as a Corporate member of the Object Management Group (OMG), Guidelines will continue to provide full compliance with the emerging industry standards for Object Oriented development. ================================ þ DATABASE CONNECTIVITY ================================ Guidelines provides the developer with a consistent programmable interface - JOT - through which access to multiple databases is supported transparently. The developer has the ability to dynamically change the server database for each client, and the client's ability to access multiple databases concurrently, so that the application runs with the correct data. And the business application has the ability to access multiple databases from multiple vendors concurrently. Guidelines also provides a local indexed file support, designed to provide speed of access for the client application, for occasions where local work data is required and the application does not warrant the purchase of a third party relational database package. Through JOT, Guidelines provides support for ODBC third party products such as Q+ELib (DataDirect), which in turn provide a single and consistent method of access to numerous vendors databases, such as Oracle, Sybase, Informix, Paradox and dBase to name just a few. In providing this support Guidelines naturally positions itself in the corporate sphere, and distances itself from the choice of database engine. Should an organisation change its database in the future, or need to integrate with multiple databases, Guidelines ensures that the business applications keep running and all that is required for the new database are the relevant ODBC database drivers. This leads on to a key part of Guidelines ability to support Information System design. While an organisation may start with a single database from one vendor, business acquisitions, mergers and technology changes will bring a variety of databases across the enterprise. The ability to create applications which are able to use such a variety, regardless of vendor, will be key to the enterprise strategy.