In the News
Newsletter - 02/28/08
Newsletter - 04/14/08
Newsletter - 04/21/08
Designer Studio Gallery

Customer Spotlight
Technical Scope
 Other Links

Software as a Service
Technology Landscape
Technical Scope
Overcoming barriers to IT success

  1. Connect to data from other systems. Aggregating data from disparate data sources - requires ability to connect in or represent data from dissimilar applications. Open connectivity between disconnected systems through mapping tools that expose hierarchical data models between two disparate systems.
  2. Share data with other systems.
  3. Overcome the gap that exists between defining business requirements and programming the code units to deliver required functionality.
  4. Standardize the methods used to deliver required functionality across a multi-programmer team. Teams assemble software workflows from functional modules that define application logic and data flows.
  5. Deliver a user interface for non-programmers that allows them to incorporate complex programming concepts - threading or asynchronous processing - into the applications they assemble.
  6. Expose data and logic layers of an application to developers, support personnel and external systems so that at runtime execution the system can audit and trace workflow and data paths.
Areas of technical challenge

  1. Current programming technologies and development environments (IDE) provide visual development for user-interface designs only; application logic requires specific language syntax and programming constructs as well as programmed connectivity to data stores.
    1. Toreion designer studio represents programming logic, data elements and data flow using a visual environment to represent the programming concepts such as client-side tasks, conditional logic, logic routing, rules based routing, asynchronous threading/processing
    2. Toreion designer studio uses workflow programming to visually assemble code modules into programs. Represent a workflow within the real estate of a web browser.
    3. Toreion designer studio build UI views in a WYIWYG design environment.
  2. Current programming technologies each deal with software design concepts in their own unique way making it difficult to implement common programming standards across a team of developers. Typically business logic is programmed into the compiled code - business logic and code syntax are tightly bound together. Toreion Designer Studio decouples the programming concepts from the business logic using modules that generate the overall instruction set. This enforces a standardized approach to building workflow applications.
    1. Toreion workflow engine interprets instruction sets at runtime execution. Workflows are parsed at the start of a program event; the instruction set is converted to an object in memory - all subsequent calls in that workflow instance reference the object.
    2. Toreion caching model for the management of multiple, concurrent workflow instances. Caching the objects allowed them to be shared across multiple sessions of a workflow expanding the number of simultaneous calls allowed on that workflow.
  3. Persist representation of application workflows as XML instruction sets.
    1. Toreion uses XML to represent hierarchical structures within workflow instruction sets. XML is typically used as a data definition protocol - Toreion uses it as a declarative language as well as for data definition. This includes user interface view definitions, data designs, data transformations [regular expressions], protocol schemas [cXML, EDI] in assembled logic.
    2. Toreion managed software change control through versioning of workflow application designs that allows side by side execution of workflows for simultaneous testing across multiple versions.
  4. Provide an asynchronous feedback mechanism (event system) to maintain the state between the web-browser client and the data/logic server for the complex transactions found within enterprise applications. Toreion had to replicate a client server environment in a stateless environment [web browser].
    1. Toreion event system that followed traditional publish + subscribe methodology leveraging XML to assemble event messages/payloads.
      1. Exception handling - system, workflow, user inputs. Used exceptions to trigger notification to system auditor providing improved error resolution.
      2. Robust auditing, messaging and tracking to improve the performance and trace-ability on execution. Provided real-time feedback on execution of workflows during design phases as well as for optimizing enterprise application performance.
      3. Multiple listeners could subscribe to an event queue - many to one relationship.
    2. Toreion developed an abstract publish-subscribe messaging system that could manage dynamic events generated at run-time.
    3. Event filtering [client/server]. Clients or server can subscribe to a queue where events are being published to. Clients and servers receive events in the queues they have subscribed to based on data in the event.
    4. Event multicast distribution system: as opposed to a peer-to-peer distributed model [inefficient bandwidth consumption]. By chaining proxy listeners within event queues large volumes of events can be distributed simultaneously while minimizing the load/bandwidth consumption on the event system network.

  Contact Us | Terms of Use | Privacy Policy
© 2004-2008 Toreion Corporation. All Rights Reserved.