Documents can exist in several versions and representations. Even in the latter case, deviations have to be allowed for in a seemless way. Rigid, transaction-like workflow models where exceptions have to be catered for in advance, are to be avoided. At Argo, workflow is seen as a means to intelligently support end-users within the context of their business processes, by offering relevant options to choose from within particular contexts or at specific steps in a process. By default, the end-user can take other, appropriate actions when and if necessary.
Rigidity is to be the exception, rather than the rule.
End-users have to be able to handle incoming and outgoing task assignments, and to manage workflow processes. Configuration and administration tools allow end-users to set up the object model and the database structures, to configure applications, to set up workflow process templates, to manage users and access control, to import and export database information, to manage the database and and to manage caching and backup of documents. The latter is needed to reach users not connected to the system by electronic mail, e.g. for notifications. Electronic documents have to be stored on optical storage. This part gives an overview of the Requirements for the FrameworkForAdaptiveDesign built at Argo.