Logical routing specification in office information systems

A message management system is an office information system for managing structured messages, integrating the facilities of computer-based message systems and database management systems, and adding to them the capability of "intelligent" handling of messages. This allows the office information system to support messages tha t can use information about themselves (such as structure and content) or about the system to effect their own processing. Logical routing of messages in an office information system is a function that can benefit from such intelligent processing. A framework and language are introduced for the specification of logical routing for messages in an office information system. By associating routing specifications with message types, the system assumes the responsibility both for evaluating the current message instance state to yield the next destination for the instance and for forwarding the instance. The user is freed from the need to direct explicitly each instance of a message type. The routing specifications are based on a variety of criteria, including message instance state and system characteristics. A routing specification language is described, with examples, and an implementation for a distributed workstation environment is outlined.

[1]  Dennis Tsichritzis.  Message addressing schemes , 1984, TOIS.

[2]  Dennis Tsichritzis,et al.  An office form flow model , 1980, AFIPS '80.

[3]  K. Thompson,et al.  The UNIX time-sharing system , 1978 .

[4]  Oscar Nierstrasz,et al.  Message Flow Modeling , 2022 .

[5]  David Gries,et al.  The Science of Programming , 1981, Text and Monographs in Computer Science.

[6]  Vincent Y. Lum,et al.  Specification of Forms Processing and Business Procedures for Office Automation , 1982, IEEE Transactions on Software Engineering.

[7]  Bjarne Stroustrup,et al.  C++ Programming Language , 1986, IEEE Softw..

[8]  A. Retrospective,et al.  The UNIX Time-sharing System , 1977 .

[9]  Andrew Bechtolsheim.  The SUN workstation architecture , 1982 .

[10]  Clarence A. Ellis,et al.  Office Information Systems and Computer Science , 1980, CSUR.

[11]  Dennis Tsichritzis,et al.  Form management , 1982, CACM.

[12]  Oscar Nierstrasz,et al.  A System for Managing Structured Messages , 1982, IEEE Trans. Commun..

[13]  D.C. Tsichritzis,et al.  Office information systems: Challenge for the 80's , 1980, Proceedings of the IEEE.

[14]  Marcos A. Bernal,et al.  OfficeTalk-D: An experimental office information system , 1982, COCS.

[15]  Moshé M. Zloof.  QBE/OBE: A Language for Office and Business Automation , 1981, Computer.

[16]  Narain H. Gehani.  The Potential of Forms in Office Automation , 1982, IEEE Trans. Commun..

[17]  Ray A. Jarvis,et al.  A Computer Vision and Robotics Laboratory , 1982, Computer.

[18]  Frederick H. Lochovsky,et al.  A system for interactively designing message templates , 1983 .

[19]  Alison Lee,et al.  Enhancing the usability of an Office Information System through direct manipulation , 1983, CHI '83.

[20]  John Hogg,et al.  An active mail system , 1984, SIGMOD '84.

[21]  Brian W. Kernighan,et al.  The C Programming Language , 1978 .

[22]  David D. Redell,et al.  Evolution of the Ethernet Local Computer Network , 1982, Computer.

[23]  Philip A. Bernstein,et al.  Concurrency Control in Distributed Database Systems , 1986, CSUR.

[24]  Clarence A. Ellis,et al.  OfficeTalk-D: An experimental office information system , 1982 .

[25]  Murray Hill,et al.  Yacc: Yet Another Compiler-Compiler , 1978 .

[26]  Jo-Mei Chang,et al.  Database Alerting Techniques for Office Activities Management , 1982, IEEE Trans. Commun..

[27]  Thomas Patrick Martin.  A communication model for message management systems , 1984 .

[28]  Dennis Tsichritzis.  Integrating data base and message systems , 1981, VLDB 1981.

[29]  Roger M. Needham,et al.  Grapevine: an exercise in distributed computing , 1982, CACM.

[30]  Oscar Nierstrasz,et al.  Message flow analysis , 1984 .