Copyright 1995 - 2006, Binary Star Development Corporation

1. SystemBuilder™ End-of-Life by IBM?Or just want a better product? There is a practical Alternative Nucleus Technology™from Binary Star Development Copyright 1995 - 2006, Binary Star Development Corporation

2. Historical Perspective System Builder technology has evolved from it’s beginnings in the early 1980’s. SB and SB+ provide a base for the development and support of thousands of different applications at tens of thousands of sites throughout the world. System Builder has historically relied on proprietary syntax and conventions to maintain a captive market, preventing organizations from migrating to newer and more flexible technologies. Copyright 1995 - 2006, Binary Star Development Corporation, All rights reserved worldwide.

3. Current Perspective - SB+ System Builder retains its proprietary syntax and convention. Training new SB+ developers remains a time consuming and expensive proposition. Deploying a SB+ Graphic User Interface (GUI) requires maintenance and support of two sets of divergent and possibly conflicting code. User interface options in the SB world remain limited. SB+ is no longer supported for many platforms. IBM does NOT support jBASE. IBM may withdraw support for SB+ on D3 and other Raining Data platforms, forcing migration to IBM Universe or Unidata environments. Copyright 1995 - 2006, Binary Star Development Corporation, All rights reserved worldwide.

4. Current Perspective - Nucleus Technology Nucleus relies on the use of syntax and convention familiar to most “Pick” programmers working in Multi-Value arenas. Developers using Nucleus become productive within twenty-four (24) hours and often achieve expert status within a few months. The learning curve is short. Nucleus is a true “event-driven” environment, providing an interface to most current “client-side” objects and utilities. Visual interface options with Nucleus abound. Nucleus provides true cross-platform compatibility and support for all current multi-dimensional environments. Source code control and configuration management is “built-in” Copyright 1995 - 2006, Binary Star Development Corporation, All rights reserved worldwide.

5. Changing the underlying process Migration to Nucleus provides a re-engineering and modification of applications that were initially designed and developed using SystemBuilder tools and syntax. Migration changes both the underlying process engine from SystemBuilder to Nucleus, as well as the way in which commands and procedures are processed and interpreted. Migration to Nucleus is NOT reverse-engineering. After migration, proprietary SystemBuilder accounts can be safely removed. Copyright 1995 - 2006, Binary Star Development Corporation, All rights reserved worldwide.

6. Reasons for Migration to Nucleus Freedom of choice - Platform, Visual and O/S Path to the future - supporting new technologies including ActiveX, JAVA, C#, .NET and Delphi Objects. Simplified support and development effort Security - all the way down to the field level Protecting your software investment - Source code control is “built-in” Rapid development, rapid deployment, rapid solution Flexibility, Reliability, Scalability Copyright 1995 - 2006, Binary Star Development Corporation, All rights reserved worldwide.

7. What Occurs in the migration to Nucleus The migration to Nucleus converts definitions initially made in the SystemBuilder environment and re-defines a new command set using industry standard syntax, understood by the Nucleus environment. After migration, your application can be managed as a Nucleus application, using the easy-to-use Nucleus Programmers Work-bench, tools and utilities. After conversion, your application will gain the benefits of enhanced security, cross-platform compatibility, built-in data warehousing support and the safety and security of fully-integrated source code management. Copyright 1995 - 2006, Binary Star Development Corporation, All rights reserved worldwide.

8. Environmental Differences In the Nucleus environment, there is NO code divergence between character based and GUI screens, reducing maintenance effort and cost. Nucleus supports a mixed display environment including GUI, Graphic Character mode, dumb terminals and web browsers. Most terminal emulators including Accuterm, Wintegrate, ViaDuct, Procomm, MacToPic, Winnix and others are supported. Visual interface options including JAVA, VBA’s, ActiveX, Delphi, .NET, C# and Web Browser models are now in the pipeline. Remote Procedure Calls (RPC’s), ODBC, Socket Events (jObjex, UniObjects, C++ calls, MvDesigner, etc.) and web events can be accommodated. A path to the future is assured with Nucleus technology. Copyright 1995 - 2006, Binary Star Development Corporation, All rights reserved worldwide.

9. Conversion Tools The conversion tools include:  Definition Layer Translation  Rules Layer translation  Menu Layer translation  Paragraphs Layer translation  Parser  Algebraic converter  BASIC logic converter Copyright 1995 - 2006, Binary Star Development Corporation, All rights reserved worldwide.

10. Processing the conversion Conversions can be addressed as individual System Builder “projects”. Conversions can be done by:  ‘Drilling’ through individual menu items  ‘Drilling’ through a screen and it’s components  Processing a list of screens to convert during a “pass” Copyright 1995 - 2006, Binary Star Development Corporation, All rights reserved worldwide.

11. Conversion options Syntax: SB1 SBSystemCode ProcessName (optionsSBSystemcode is the SYSID used in SB (as CH in sbdemo)ProcessName can be any ID in the xxPROCESS, xxDEFN, xxPROGS or any referenced Include. More than 15 options can be specified Overwrite, Header Suppress, Footer Suppress, Dialog, Compile Secondary Screen, Compile Paragraphs, Recursive, Global Equates, Verbose output, Build CONTENTS, Initialize work items, force cross-compile xxPROGS, force cross-compile INCLUDE segment, etc. Copyright 1995 - 2006, Binary Star Development Corporation, All rights reserved worldwide.

12. Conversion Processing The system ID determines which SB system group of control files to interrogate The search begins in the associated PROCESS file and drills into the related components. The result is a self-contained set of executable and linked objects used by Nucleus. SB1creates a Nucleus project (synonymous to SB SystemID) Copyright 1995 - 2006, Binary Star Development Corporation, All rights reserved worldwide.

13. Files are created Creation of a Nucleus project entails the (automatic) creation of the Nucleus development files, including:  Project.WINSCREENS  Project.ISUB  Project.ISUB,S  Project.ISUB,INCLUDES  Project.ISUB,FUNCTIONS  and optionally, PARAGRAPHS & INPUTHELP.FILE Copyright 1995 - 2006, Binary Star Development Corporation, All rights reserved worldwide.

14. Compilation of a screen Compiling Screen ORDER.ENTRY ORDER.HEAD USING NUCH.SCRDICTS,ORDER.ENTRY ORDER.NUMBER WINDOW(74,15,1,2) HEADING "Order Entry" @(21,0) ORDER.NUMBER @(21,1) ORDER.D ATE @(21,2) CUST.CODE @(59,2) DISPLAY FAKE ORDTYPE @(21,3) CUSTREF @(21,5) DELIVERY @(21,6) TERMS @(1,9,4) PARTNO @(11,9) DISPLAY FA KE STDESC @(41,9) QTY @(50,9) PRICE @(65,9) LINE.TOT @(64,14) DISPLAY FAKE ORDTOT @(1,0) "Order Number" @(1,1) "Order Date" @(1,2) " Cust Code" @(1,3) "Customer Ref" @(1,5) "Delivery Code" @(1,6) "Terms" @(1,8) "Partno" @(11,8) "Description" @(41,8) "Qty" @(50,8) " Price" @(65,8) "Line Tot" @(1,7) LINE(72) @(1,13) LINE(72) @(57,1) BOX(15,1) FOOTING "SB+ to Nucleus" ID-INSCREEN COMPILE SCR.ORDER. ENTRY Parsing arguments... Binding Data File for User-defined Subroutines Building Init Subroutine SCR.ORDER.ENTRY Page limits & tabs -+++--+ Window limits -+ Multivalued windows -+ Id definition ----------------------+ Cross reference + Active fields ---------------------------////////////////////////// Remote Files ---------------------------------o+ Field Colors + Compiling Init Subroutine SCR.ORDER.ENTRY Precompile: SCR.ORDER.ENTRY Compile: SCR.ORDER.ENTRY Compiling: Source = 'NUCH.ISUB/NUCH.ISUB/SCR.ORDER.ENTRY', Object = 'NUCH.ISUB.O/SCR.ORDER.ENTRY' ************************************************************************************************************************************ *********** Compilation Complete Copyright 1995 - 2006, Binary Star Development Corporation, All rights reserved worldwide.

15. Compilation of a screen "SCR.ORDER.ENTRY" cataloged. Parsing Algabraic Functions.. Compiling User Subroutine SUBS.ORDER.ENTRY Precompile: SUBS.ORDER.ENTRY #................. Compile: SUBS.ORDER.ENTRY Compiling: Source = 'NUCH.ISUB/NUCH.ISUB/SUBS.ORDER.ENTRY', Object = 'NUCH.ISUB.O/SUBS.ORDER.ENTRY' ******************************************************************************************************************************* Compilation Complete. "SUBS.ORDER.ENTRY" cataloged. Reading item 'SUBS.ORDER.ENTRY' Checking Out SUBS.ORDER.ENTRY, Version 1.0p0e11 Reading item 'SUBS.ORDER.ENTRY' Source Code ControlCheckout Copyright 1995 - 2006, Binary Star Development Corporation, All rights reserved worldwide.

16. The conversion includes Re-engineering of BASIC subroutines, removing SB artifacts. Re-engineering of BASIC code and subroutines replacing SB specific code segments with appropriate Nucleus routines. Converting Paragraphs (P) references to BASIC subroutines directly callable from Nucleus, following standard NNF2 syntax. Menu’s are converted and managed as either Nucleus process control menus, or “drilled-to” from a parent “I” or “O” process . Converting application screens and reports while maintaining the “look and feel” of the original. Copyright 1995 - 2006, Binary Star Development Corporation, All rights reserved worldwide.

17. Screens - Payroll/HR • Payroll Voucher register • Voucher Detail • Earnings Detail <F5> • Deductions Detail <F6> • Employee Tax Detail <F7> • Voucher Register - GUI • Employee Voucher Detail (GUI)<F5> • Voucher Earnings Detail (GUI) <f7> Examples shown are from a SB+ application by TheBowman Group, converted to Nucleus Technology Copyright 1995 - 2006, Binary Star Development Corporation

24. Pulldown

27. Migration - notes Developers supporting applications converted from SB+ to Nucleus are required to have a functional understanding of Nucleus application development. A short training session should be scheduled to orient programmers and support personnel. The Nucleus Software Development Kit (SDK) must be registered and licensed at all sites where development or application modification occurs.  A run-time environment is available for distributed sites where no development occurs.  Licensing of individual Nucleus users is mandatory. Copyright 1995 - 2006, Binary Star Development Corporation, All rights reserved worldwide.

28. Nucleus Technology - a practical alternative After conversion to Nucleus, all proprietary SystemBuilder accounts may be safely removed. After conversion, no vestiges of SystemBuilder need remain, and support for System Builder can be discontinued. As long as licensing for Nucleus and the Nucleus SDK remains in place, your applications initially developed using SystemBuilder can be safely run, modified and maintained within the Nucleus environment, using Nucleus tools. Binary Star Development Corporation aggressively protects Intellectual property provided to us by our distributors, dealers and prospective customers. The screens shown in this presentation were provided to illustrate that there is an alternative to SystemBuilder, and that Nucleus Technology from Binary Star provides this path. Copyright 1995 - 2006, Binary Star Development Corporation, All rights reserved worldwide.

29. Is Migration to Nucleus appropriate? Is your current platform no longer supported by IBM ? Do you want to add a Graphic User Interface (GUI) without having to maintain multiple sets of code? Would you like a vendor that is more responsive to your needs? Are you are finding that the effort to hire and train SB+ developers is becoming more difficult, time consuming and expensive? Do you want to simplify application maintenance and support? Do you want to extend the life of your existing Pick applications and integrate .NET, Visual Basic, ActiveX controls, C# or Java objects without investing in a major re-write? Do you need to comply with new regulatory requirements and forsee difficulty in achieving this goal? A single Yes, can justify your migration.

30. Nucleus Technology™ Accelerating Development, Empowering Change To see if migration from SB/SB+ to Nucleus - would be appropriate - or how long would it take - or how much it could save - please call... Nucleus Technology is a product of Binary Star Development Corporation1640 Riverland Road, Ft Lauderdale, Florida 33312 USAToll free +1 (866) 882-1888 or (954) 791-8575http://www.binarystar.com email info@binarystar.com Trademarks mentioned within are the property of their respective owners. Copyright 1995 - 2006, Binary Star Development Corporation All Rights reserved worldwide.