Information systems

The Practical Handbook of Internet Computing

Volumn , Issue , 2004, Pages 33-1-33-19

  Yu, Eric ^a  

^a UNIVERSITY OF TORONTO   (Canada)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 85056047482     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1201/9780203507223     Document Type: Chapter

References (91)

1. Banville, Claude and Maurice Landry (1992). Can the Field of MIS be Disciplined? In: Galliers, R., Ed., Information Systems Research: Issues Methods and Practical Guidelines. London et al.: Blackwell, 61-88.
2. Basili, Victor R. and G. Caldiera (1995). Improve software quality by reusing knowledge and experience. Sloan Management Review, 37(1): 55-64, Fall.
3. Berners-Lee, Tim, Jim Hendler, and Ora Lassila (2001). The semantic web. Scientific American, May, 2001.
4. Bernstein, Philip A. (2001). Generic model management — a database infrastructure for schema management. Proceedings of the 9th International Conference on Cooperative Information Systems (CoopIS 01), Trento, Italy, LNCS 2172, Springer, New York, 1-6.
5. Bernstein, Philip A., Bergstraesser, T., Carlson, J., Pal, S., Sanders, P., Shutt, D. (1999). Microsoft repository version 2 and the open information model. Information Systems, 24(2): 71-98.
6. Boehm, Barry (1981). Software Engineering Economics. Prentice Hall, Englewood Cliffs, NJ.
7. Boehm, Barry and Hoh In (1996). Identifying Quality-Requirement Conflicts. IEEE Software, March, 25-35.
8. Boman, Magnus, Janis Bubenko, Paul Johannesson, and Benkt Wangler (1997). Conceptual Modeling. Prentice Hall, Englewood Cliffs, NJ.
9. BPMI. The Business Process Management Initiative. www.bpmi.org
10. Brinkkemper, Sjaak and S. Joosten (1996). Method engineering and meta-modelling: editorial. Information and Software Technology, 38(4): 259.
11. Bussler, Christoph (2002). P2P in B2BI. Proceedings of the 35th Hawaii International Conference on System Sciences. IEEE Computer Society. Vol. 9: 302-311.
12. Checkland, Peter B. (1981). Systems Thinking, Systems Practice. John Wiley and Sons, Chichester, U.K.
13. Chen, Peter (1976). The Entity-Relationship Model: towards a unified view of data. ACM Transactions on Database Systems 1(1): 9-36.
14. Chrissis, Marybeth, Mike Konrad, and Sandy Shrum (2003). CMMI : Guidelines for Process Integration and Product Improvement. Addison-Wesley, Reading, MA.
15. Chung, Lawrence, Brian Nixon, Eric Yu, and John Mylopoulos (2000). Non-Functional Requirements in Software Engineering. Kluwer Academic, Dordrecht, The Netherlands.
16. Cockburn, Alistair (2001). Agile Software Development. Addison-Wesley, Reading, MA.
17. Curran, Thomas and Gerhard Keller (1997). SAP R/3 Business Blueprint: Understanding the Business Process Reference Model. Pearson Education, Upper Saddle River, NJ.
18. Curtis, Bill, Mark Kellner, and James Over (1992). Process modelling. Communications of the ACM, 35(9): 75-90, September.
19. Davenport, Thomas H. and J.E. Short (1990). The new industrial engineering: information technology and business process redesign. Sloan Management Review, 1990, 31 (4): 11-27.
20. DeMarco, Thomas (1979). Structured Analysis and System Specification. Prentice Hall, Englewood Cliffs, NJ.
21. DeMarco, Thomas and T. Lister (1999). Peopleware, 2nd ed. Dorset House, New York.
22. deMichelis, Giorgio, Eric Dubois, Matthias Jarke, Florian Matthes, John Mylopoulos, Michael Papazoglou, Joachim W. Schmidt, Carson Woo, and Eric Yu (1998). A three-faceted view of information systems: the challenge of change. Communications of the ACM, 41(12): 64-70
23. ebXML. www.ebxml.org.
24. Ehn, Pelle (1988). Work-Oriented Development of Software Artifacts. Arbetslivscentrum, Stockholm.
25. Falcone, Rino, Munindar P. Singh, and Yao-Hua Tan (2001). Trust in Cyber-Societies: Integrating the Human and Artificial Perspectives. Lecture Notes in Artificial Intelligence 2246. Springer, New York.
26. General Accounting Office (GAO) (2002). Information Management: Challenges in Managing and Preserving Electronic Records. Report number GAO-02-586. GAO, Washington, D.C.
27. Gibbs, W. Wayt (1994). Software’s chronic crisis. Scientific American (International edition) September 1994. 72-81.
28. Gilder, George (1993). Metcalfe’s Law and Legacy. Forbes ASAP, September 13, 1993. http://www.gildertech. com/public/telecosm_series/metcalf.html
29. Giunchiglia, Fausto, James Odell, and Gerhard Weib, Eds. (2003). Agent-Oriented Software Engineering III, Third International Workshop, Bologna, Italy, July 15, 2002. Lecture Notes in Computer Science, 2585. Springer, New York.
30. Goguen, Joseph and Marina Jirotka, Eds. (1994). Requirements Engineering: Social and Technical Issues. Academic Press, London.
31. Gomez-Peres, A. and O. Corcho (2002). Ontology languages for the semantic web. IEEE Intelligent Systems 17(1): 54-60.
32. Gorgone, John T. et al. (2002). IS 2002 — Model Curriculum and Guidelines for Undergraduate Degree Programs in Information Systems. Association for Computing Machinery (ACM), Association for Information Systems (AIS), Association of Information Technology Professionals (AITP). http://www.acm.org/education/is2002.pdf.
33. Greenspan, Sol J., John Mylopoulos, and Alexander Borgida (1994). On Formal Requirements Modeling Languages: RML Revisited. International Conference on Software Engineering. ACM Press, New York. pp. 135-147.
34. Guarino, Nicola and Christopher A. Welty (2002) Evaluating ontological decisions with OntoClean. Communications of the ACM, 45(2): 61-65.
35. Hammer, Michael (1990) .Reengineering work: don’t automate, obliterate. Harvard Business Review, July. 104-112.
36. Hauser, J.R. and D. Clausing (1988). The house of quality. Harvard Business Review, (3), May, 63-73.
37. HL7. www.hl7.org.
38. Holtzblatt, Karen and H.R. Beyer (1995). Requirements gathering: the human factor. Communications of the ACM, 38(5): 30-32.
39. Huhns, Michael and Munindar P. Singh (1998). Readings in Agents. Morgan Kaufmann, San Francisco, CA.
40. Humphrey, Watts (1995). A Discipline for Software Engineering. Addison-Wesley, Reading, MA.
41. IETF. The Internet Engineering Task Force. http://www.ietf.org/.
42. Isakowitz, Tomas, Michael Bieber, and Fabio Vitali (1998). Web information systems. Communications of the ACM, 41(7): 78-80.
43. ISO (1992) ISO9000 International Standards for Quality Management. Geneva, International Organization for Standardization.
44. Jarke, Matthias, John Mylopoulos, Joachim Schmidt, and Yannis Vassiliou (1992). DAIDA: an environment for evolving information systems. ACM Transactions on Information Systems, 10(1): 1-50, 1992.
45. Jarke, Matthias, K. Pohl, K. Weidenhaupt, K. Lyytinen, P. Martiin, J.-P. Tolvanen, and M. Papazoglou (1998) Meta modeling: a formal basis for interoperability and adaptability. In B. Krämer, M. Papazoglou, H.-W. Schmidt, Eds., Information Systems Interoperability. John Wiley and Sons, New York, pp. 229-263.
46. Kling, Rob (1996). Computerization and Controversy: Value Conflicts and Social Choices, 2nd ed. Academic Press, San Diego, CA.
47. Kruchten, Philippe (2000). The Rational Unified Process: An Introduction, 2nd ed. Addison-Wesley, Reading, MA.
48. Lamsweerde, Axel van (2000). Requirements Engineering in the Year 00: A Research Perspective. 22nd International Conference on Software Engineering, Limerick, Ireland, ACM Press, New York.
49. Lee, Jintae (1997). Design rationale systems: understanding the issues. IEEE Exper., 12(3): 78-85.
50. Lyytinen, Kalle (1987). Different perspectives on information systems: problems and their solutions. ACM Computing Surveys, 19(1): 5-44.
51. Loucopoulos, Pericles and R. Zicari, Eds. (1992). Conceptual Modeling, Databases and CASE: An Integrated View of Information System Development. John Wiley and Sons, New York.
52. McConnell, Steve (1996). Rapid Development: Taming Wild Software Schedules. Microsoft Press.
53. Mowshowitz, Abbe (1997). Virtual Organization — introduction to the special section. Communications of the ACM, 40(9): 30-37
54. Muller, Michael J. and Sarah Kuhn (1993). Participatory design. Communications of the ACM, 36(6): 24-28, June.
55. Mulligan, Deirdre K. (2003). Digital rights management and fair use by design. Special issue. Communications of the ACM, 46(4): 30-33.
56. Mylopoulos, John (1998). Information modeling in the time of the revolution. Invited review. Information Systems, 23(3, 4): 127-155.
57. Mylopoulos, John, Alex Borgida, Matthias Jarke, and Manolis Koubarakis (1990). Telos: representing knowledge about information systems. ACM Transactions on Information Systems, 8(4): 325-362.
58. Mylopoulos, John, K. Lawrence Chung, and Eric Yu (1999). From object-oriented to goal-oriented analysis. Communications of the ACM, 42(1): 31-37, January 1999.
59. Nissen, Hans W. and Matthias Jarke (1999). Repository support for multi-perspective requirements engineering. Information Systems, 24(2): 131-158.
60. NIST (1993). Integrated Definition for Function Modeling (IDEF0). 1993, National Institute of Standards and Technology.
61. Nonaka, Ikujiro and Hirotaka Takeuchi (1995) The Knowledge-Creating Company. Oxford University Press, Oxford, U.K.
62. OASIS. Organization for the Advancement of Structured Information Standards. http://www.oasisopen.org/.
63. OpenGroup. The Open Group. http://www.opengroup.org/.
64. Papazoglou, Michael (2001). Agent-oriented technology in support of e-business. Communications of the ACM 44(4): 71-77.
65. Potts, Colin and Wendy Newstetter (1997). Naturalistic Inquiry and Requirements Engineering: Reconciling Their Theoretical Foundations. Proceedings of the 3rd IEEE International Symposium on Requirements Engineering, Annapolis, MD, January 1997. 118-127.
66. Ramesh, Bala and Matthias Jarke (2001). Towards reference models for requirements traceability. IEEE Transactions on Software Engineering, 27(1): 58-93.
67. Rosenbloom, Andrew (2000). Trusting technology: introduction to special issue. Communications of the ACM, 43(12), December.
68. Ross, Douglas T. and D. Schoman (1977). Structured analysis for requirements definition. IEEE Transactions on Software Engineering 3(1): 6-15. Special Issue on Requirements Analysis, January.
69. Royce, W.W. (1970). Managing the Development of Large Software Systems: Concepts and Techniques. Proceedings of WESCON, IEEE Computer Society Press, Los Alamitos, CA.
70. Rumbaugh, James, Ivar Jacobson, and Grady Booch (1999). The Unified Modeling Language Reference Manual. Addison-Wesley, Reading, MA.
71. SACMAT (2003). 8th ACM Symposium on Access Control Models and Technologies, June 2-3, 2003, Villa Gallia, Como, Italy, Proceedings.
72. SemanticWeb. The Semantic Web community portal. http://semanticweb.org/.
73. Smith, Howard and Peter Fingar (2002). Business Process Management: The Third Wave. Meghan-Kiffer Press, Tampa, FL.
74. Standish Group (1995). Software Chaos. http://www.standishgroup.com/chaos.html.
75. Timmers, Paul (2000). Electronic Commerce: Strategies and Models for Business-to-Business Trading. John Wiley and Sons, New York.
76. UDDI. www.uddi.org.
77. UN/CEFACT. United Nations Centre for Trade Facilitation and Electronic Business. http://www.unece.org/cefact/.
78. Vassiliadis, Panos, Christoph Quix, Yannis Vassiliou, and Matthias Jarke (2001). Data warehouse process management. Information Systems, 26(3): 205-236.
79. W3C. The World Wide Web Consortium. http://www.w3.org/.
80. WebServices. WebServices.org portal. http://www.webservices.org/.
81. Webster, Dallas E. (1988). Mapping the Design Information Representation Terrain. IEEE Computer, 21(12): 8-23.
82. Weinberg, Jerry (1998). The Psychology of Computer Programming, Silver Anniversary Edition. Dorset House, New York.
83. Wiederhold, Gio and Michael R. Genesereth (1997). The conceptual basis for mediation services. IEEE Expert, 12(5): 38-47.
84. Wood, Jane and Denise Silver (1995). Joint Application Development, 2nd ed. John Wiley and Sons, New York.
85. Yang, Jian and Mike P. Papazoglou (2000) Interoperation support for electronic business. Communications of the ACM, 43(6): 39-47.
86. Yu, Eric (January 1997). Towards Modeling and Reasoning Support for Early-Phase Requirements Engineering. Proceedings IEEE International Symposium on Requirements Engineering, Annapolis, MD, 226-235.
87. Yu, Eric and John Mylopoulos (1994).Understanding “Why” in Software Process Modeling, Analysis and Design. Proceedings 16th International Conference on Software Engineering, Sorrento, Italy.
88. Yu, Eric and John Mylopoulos (1994). From E-R to A-R — Modeling Strategic Actor Relationships for Business Process Reengineering. Proceedings 13th International Conference on the Entity-Relationship Approach, Manchester, U.K., December 1994
89. P. Loucopoulos, Ed., Lecture Notes in Computer Science 881, Springer-Verlag, New York, 548-565.
90. Yu, Eric, John Mylopoulos, and Yves Lespérance (1996). AI models for business process reengineering. IEEE Expert, 11(4).
91. Yu, Eric S. K. (2002). Agent-oriented modelling: software versus the world. In Michael Wooldridge, Gerhard Weib, and Paolo Ciancarini, Eds. Agent-Oriented Software Engineering II, Lecture Notes in Computer Science 2222 Springer, New York, 206-225.