Specifying Collaborative System Requirements in Terms of Platforms and Services



Increasing collaboration in business processes has resulted in increased demand for information systems that support collaboration in business processes. Many system development methodologies, however, are oriented towards defining processes that are fixed both in their process steps and process functions. Collaborative systems, however, are more uncertain in nature and collaborative processes usually evolve to accomplish the goal. Hence requirements cannot be specified to the same level of detail. Collaborative processes are often user driven and requirements must accommodate such users by providing a flexible platform of services that can be configured by users to fit their work practices. This paper introduces the concept of collaboration level as a way to specify collaborative platforms of services and ways to implement such platforms.


Requirement Analysis Collaborative Process Joint Planning Collaborative System Technical Strategy 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. Hawryszkiewycz, I.T. (2006a): “Engagements as a Unifying Concept for Process Integration,” Proceedings of the 14th International Conference on Information Systems.Google Scholar
  2. Hawryszkiewycz, I.T. (2006b): “A Framework for Raising Collaboration Levels on the Internet,” 7th International Conference on Electronic Commerce and Web Technologies, Krakow, Poland, pp. 82–91.Google Scholar
  3. Hawryszkiewycz, I.T. (June, 1996): “Providing Computer Services for Business Networks,” Proceedings of the 9th International Conference on EDI-IOS, ISBN-961-232-000-4, Bled, pp. 398–411.Google Scholar
  4. Hawryszkiewycz, I.T. (October, 1997): “A Framework for Strategic Planning for Communications Support,” Proceedings of the Inaugural Conference of Informatics in Multinational Enterprises, Washington, pp. 141–151.Google Scholar
  5. Hofstede, G. (1980): Culture's Consequences: International Differences in Work-Related Values, Sage, Beverly Hills, CA.Google Scholar
  6. Jacobs, J.L., Dorneich, C.P., and Jones, P.M. (October, 1998): “Activity Representation and Management for Crisis Action Planning,” IEEE International Conference on Systems, Management and Cybernatics, pp. 961–966.Google Scholar
  7. Jiang, L., Eberlein, A., and Far, B.H. (2005): “Combining Requirements Engineering Techniques—Theory and Case Study,” Proceedings of the 12th IEEE International Conference on the Engineering of Computer-Based Systems (ECBS 05).Google Scholar
  8. Ott, M. and Nastalsky, L.: “Modeling Organizational Forms of Virtual Enterprises,”http://fb5www.uni-peterbon.de/winfo2
  9. Padula, A. (2004): “Requirements Engineering Process Selection at Hewlett-Packard,” Proceedings of the 12th International Requirements Engineering Conference.Google Scholar
  10. Shanks, G., Lansley, S., and Weber, R. 2004: “Representing Composites in Conceptual Modeling,” Communications of the ACM, 43(7), 77–80.CrossRefGoogle Scholar
  11. Tan, J., Wen, J., and Awad, N. (2006): Health Care and Services Delivery Systems as Complex Adaptive Systems,” Communications of the ACM, 48(5), 37–44.Google Scholar
  12. Whittaker, S., Swanson, J., Kucan, J., and Sidner, C. (1999): “Telenotes: Managing Lightweight Interactions in the Desktop .”Google Scholar
  13. Zhang, J., Patel, V., Johnson, K., and Smith, J. (2002): “Designing Human Centered Distributed Information Systems,” IEEE Intelligent Systems, September/October, 42–47.Google Scholar
  14. Zimmerman, A., and Nardi, B.A. (April 2006): Whither of Whether HICI: Requirements Analysis for Multi-Sited, Multi-User Cyberinfrastructures,” CHI 2006, Montreal, Canada.Google Scholar

Copyright information

© Springer Science+Business Media, LLC 2009

Authors and Affiliations

  1. 1.Faculty of Information TechnologyUniversity of TechnologySydney

Personalised recommendations