2. About Nad
• President and founder (in 1985) of TechWRITE, Inc., a technical
communications/e-learning company located in Woodbury,
New Jersey, USA
• PLAIN Board member and webmaster
• STC Associate Fellow
• Past President of STC Philadelphia Metro Chapter
www.techw.com
twnad@techw.com
856-848-6593
www.techw.com
5. Visuals today
• LOB-specific and process-specific document templates, workflows, and business rules for many document types. Global common
document templates, workflows, and business rules for many document types.
• (High priority) Availability of standardized API in various areas (presentation, etc.) for application integration
– Each vendor should define the APIs, platforms supported (i.e.Java and .NET), SOA solution provided, support for standards like
Java JSR.
• User interface options: The variety and options of UI available
– This is important because there are clearly requirements for Office, Outlook, File Share (File Share Services, WebDAV, ftp),
Application API and Web Based UIs
• Flexible capability to define taxonomies, workflows, presentation templates, object models, retention policies etc. at enterprise,
regional & LOB level
– From our Global Design Document, the solution should provide the interfaces and tools in order to implement the following:
• Global Taxonomy and Object Hierarchy
• Global Cabinet and Folder Hierarchy
• Document Retention
• Litigation Hold
• Reference Data Synchronization and Usage
• Open Architecture: ability to integrate with various vendor BPM and Records Management tools/applications
– The vendor must be able to demonstrate the ability to interface with external application and services including Business
Process Engines (integaret with Staffware or others), Federated Records Management (integrate with ELAR or others),
Federated Search (integrate with Endeca)
• Open Architecture: Ability to build a federated architecture, capability for interfaces/distributed architectures of several document
archives/warehouses
• Document linking: How are linked documents stored/maintained, are renditions of linked/embedded documents available
– The vendor must be able to demonstrate the ability to manage complex Office documents with embedded object and links.
They also need to demonstrate which UIs support this functionality.
• Ability to support global search options (predictive document caching), how are searches and document retrieval enabled in a
federated model. In a federated model, how are local repository documents included in global searches.
• Messaging capabilities between applications/internal parties
– What are the supported mechanisms? JMS, MQSeries, MSMQ, SMTP, SOA etc.
• Integration with JAP environment
• International language support
Line of Business support – Architecture,
Taxonomies/Object Model & Workflows/BPM
27. Bibliography
• Visual Language for Designers, Connie Malamed
• Graphics for Learning, Ruth Colvin Clark and Chopeta Lyons
• E-Learning and the Science of Instruction, Ruth Colvin Clark and
Richard E. Mayer
• The Rapid e-Learning Blog – Tom Kuhlmann
http://www.articulate.com/rapid-elearning/visual-graphic-design/
www.techw.com