A speech-act-based office modeling approach
ACM Transactions on Information Systems (TOIS)
COCS '95 Proceedings of conference on Organizational computing systems
Proceedings of the 9th annual international ACM SIGIR conference on Research and development in information retrieval
Tolerating exceptions in workflows: a unified framework for data and processes
WACC '99 Proceedings of the international joint conference on Work activities coordination and collaboration
A Knowledge-based Approach to Handling Exceptions inWorkflow Systems
Computer Supported Cooperative Work
Handling of Irregularities in Human Centered Systems: A Unified Framework for Data and Processes
IEEE Transactions on Software Engineering - special section on current trends in exception handling—part II
Active Databases as a Paradigm for Enhanced Computing Environments
VLDB '83 Proceedings of the 9th International Conference on Very Large Data Bases
An office study: Its implications on the understanding of organizations
COCS '84 Proceedings of the second ACM-SIGOA conference on Office information systems
| Hi-index | 0.00 |
Conventional approaches to "office automation" focus on the lowest common denominator of office work: typing, filing, filling in forms, etc. As a consequence, the process of office systems analysis lacks tools and techniques that address the office in terms of business functions rather than as manipulation of paper artifacts. The Office Specification Language (OSL) and its associated analysis methodology have been developed as a means of implementing a functional approach to office procedure analysis and description. OSL is based on several premises derived from a study of office systems analysis at a functional level: -There exist high-level constructs common to a wide variety of disparate offices. A structured formal language built upon such standardized abstractions can be useful in helping an analyst approach, understand, and describe the operations of many offices. -Office procedures deal with (abstract) objects, not paper forms. Forms and other documents are not basic to office operations: they are mechanisms for organizing and transmitting information about some more fundamental object. Therefore office analysis should focus not on forms, but rather on the underlying business requirements that must survive any change in system implementation. -Office procedures are fundamentally simple; their apparent complexity is not inherent, but due to a myriad of special cases, historical accretions, and implementation details. Identification of a procedure''s core requirements is the framework upon which analysis should be based. Such an understanding is a prerequisite to effective reorganization of and design of support systems for office functions. OSL is postulated to be of utility for office analysis and systems design. Field tests of the language and methodology have shown that our basic approach is effective for analysis purposes, and have identified directions for further improvements.