SmartGuide™ components

Time and cost savings of 50 to 66% are possible thanks to the SmartGuide tools that drastically reduce coding needs and that allow reusing existing services.

SmartGuide Designer

SmartGuide Designer allows non-technical personnel to convert their knowledge and know-how into Smartlets™, which are applications that facilitate searching for, exchanging and processing information that is 100% relevant to a user. This absolute relevance is assured by orchestrating the user experience in a series of logical steps that adapt according to their needs.

SmartGuide Designer contains a slew of features that greatly speed up deployment times.

SmartGuide API

The SmartGuide API allows Java and .NET developers to add custom functionalities such as initializing Smartlets with data from external systems, communicating with the J2EE or .NET context, or sending collected data to back-end systems.

These new functionalities can then be made available to non-technical personnel who can incorporate them in one or more Smartlets.

JSP, ASP and XSLT tags

With SmartGuide, you can completely separate an application's logic and presentation layers. This allows a domain expert to concentrate on a application's business logic and content without worrying about its' appearance. Conversely, a graphic or web designer can focus on creating user-friendly interfaces that are standards-based and accessible while working with a familiar technology, be it JSP, ASP or XSLT.

The SmartGuide tags allow creating presentation templates that can be reused across multiple applications. This mechanism greatly reduces time-to-deployment and helps standardize the appearance of content and fields (size of text boxes, location of labels, etc.). Once templates are built, changing the look and feel of an application is as simple as clicking a button.

SmartGuide Server

SmartGuide Server is a platform-agnostic engine that runs and displays Smartlets to end users. Built to support a large number of concurrent users, SmartGuide Server can be deployed in a J2EE or .NET environment. For more details, consult the system requirements section.