On the role of conceptual schemas in information systems development

Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)

Volumn 3063, Issue , 2004, Pages 16-34

  Olivé, Antoni ^a  

^a UNIVERSITAT POLITÈCNICA DE CATALUNYA   (Spain)

Author keywords

[No Author keywords available]

Indexed keywords

SOFTWARE ARCHITECTURE; SPECIFICATIONS;

CONCEPTUAL MODELLING; CONCEPTUAL SCHEMAS; DOMAIN KNOWLEDGE; DOMAIN MODEL; FUNCTIONAL SPECIFICATION; INFORMATION SYSTEMS DEVELOPMENT; IS ARCHITECTURE; SOFTWARE COMPONENT;

INFORMATION SYSTEMS;

EID: 70349508788     PISSN: 03029743     EISSN: 16113349     Source Type: Book Series    
DOI: 10.1007/978-3-540-24841-5_2     Document Type: Conference Paper

References (40)

1. ANSI/X3/SPARC. “Interim Report from the Study Group on Database Management Systems”. FDT Bulletin of the ACM, 7(2), 1975.
2. Berners-Lee, T.; Hendler, J.; Lassila, O. “The Semantic Web”. Scientific American, May, 2001.
3. Brachman, R. J; Levesque, H.J. (Eds). Readings in Knowledge Representation. Morgan Kaufmann, 1985.
4. Bubenko, J.A.jr. “Information Modeling in the Context of System Development”. Proc. IFIP 1980, North-Holland, 1980, pp. 395-411.
5. Ceri, S.; Fraternali, P. Designing Database Applications with Objects and Rules. The IDEA Methodology. Addison-Wesley, 1997, 579.
6. Chandrasekaran, B.; Josephson, J.R.; Benjamins, V.R. “What Are Ontologies, and Why Do We Need Them?”. IEEE Intelligent Systems, January/February 99, pp. 20-26.
7. Daniels, J. “Modeling with a Sense of Purpose”. IEEE Software, January/February 2002, pp. 8-10.
8. Evans, E. Domain-Driven Design. Tackling Complexity in the Heart of Business Software. Addison-Wesley, 2003.
9. Gruber, T.R. “Toward Principles for the Design of Ontologies Used for Knowledge Sharing”. In N. Guarino and R. Poli, (Eds.), International Workshop on Formal Ontology, Padova, Italy. August 1993.
10. Gunter, C.A.; Gunter, E.L.; Jackson, M.; Zave, P. A Reference Model for Requirements and Specifications. IEEE Software, May/June 2000, pp. 37-43.
11. ISO/TC97/SC5/WG3 Concepts and Terminology for the Conceptual Schema and the Information Base, J.J. Van Griethuysen (ed.) March 1982.
12. Jackson, M. System Development. Prentice Hall, 1983, 418 p.
13. Jackson, M. The meaning of requirements. Annals of Software Engineering, 3(1997), pp. 5-21.
14. Jackson, M.; Zave, P. Deriving Specifications from Requirements: an Example. Proc. ICSE’95. IEEE Computer Soc. Press, pp. 15-24.
15. Jacobson, I.; Booch, G.; Rumbaugh, J. The Unified Software Development Process. Addison-Wesley, 1999, 463p.
16. Jardine, D.A. Concepts and Terminology for the Conceptual Schema and the Information Base. Computers & Standards 3 (1984), pp. 3-17.
17. Johnson, J.; Henderson, A. “Conceptual Models: Begin by designing what to design”. Interactions, Jan-Feb. 2002, pp. 25-32.
18. Kleppe, A.; Warmer, J.; Bast, W. MDA Explained. The Model Driven Architecture: Practice and Promise. Addison-Wesley, 2003, 170 p.
19. Kowalski, R. “Algorithm = Logic + Control”. Comm. ACM, 22(7), 1979, pp. 424-436.
20. Letbridge, T.C.; Singer, J, Forward, A. “How Software Engineers Use Documentation: The State of the Practice”. IEEE Software, Nov/Dec 2003, pp. 35-39.
21. Loucopoulos, P. Conceptual Modeling. In [22], pp. 1-26.
22. Loucopoulos, P.; Zicari, R. (Eds). Conceptual Modeling, Databases and CASE: An Integrated View of Information Systems Development. Wiley, 1992.
23. Martin, R.C. Agile Software Development. Principles, Patterns and Practices. Prentice Hall, 2003, 529 p.
24. Mylopoulos, J. “The Role of Knowledge Representation in the Development of Specifications”. Proc IFIP-86, North-Holland, 1986, pp. 317-319.
25. Mylopoulos, J. “Conceptual Modeling and Telos”. In [22], pp. 49-68.
26. Olivé, A. “An Introduction to Conceptual Modeling of Information Systems”. In Piattini, M.; Díaz, O. (Eds.) Advanced Database Technology and Design. Artech House, 2000, pp. 25-57.
27. Olivé, A. “Integrity Constraints Definition in Object-Oriented Conceptual Modeling Languages”. Proc. ER 2003, LNCS 2813, pp. 349-362, 2003.
28. OMG. “Model Driven Architecture (MDA)”. Document number ormsc/2001-07-01. 2001.
29. OMG. OCL:Object Constraint Language 2.0. OMG Document ad/2003-01-07. 2003.
30. OMG. UML 2.0 Superstructure Specification. Doc ptc/03-08-02, 2003.
31. Rugaber, S. The use of domain knowledge in program understanding. Annals of Software Engineering, 9 (2000), pp. 143-192.
32. Russell, S.; Norvig, P. Artificial Intelligence. A Modern Approach. Prentice-Hall, 1995, 932 p.
33. Selic, B. “The Pragmatics of Model-Driven Development”. IEE Software, September/ October 2003, pp. 19-25.
34. Sommerville, I.; Sawyer, P. Requirements Engineering. John Wiley & Sons, 1997, 391 p.
35. Sowa, J.F. Knowledge Representation. Logical, Philosophical and Computational Foundations. Brooks/Cole, 2000, 594p.
36. Thayer, R.H.; Thayer, M.C. “Glossary”. In Standards, Guidelines, and Examples on System and Software Requirements Engineering. IEEE Computer Society Press, 1990, pp. 501-572.
37. Tryfona, N.; Jensen, C.S. “Using Abstractions for Spatio-Temporal Conceptual Modeling”. Proceedings of the 2000 ACM Symposium on Applied Computing, pp. 313-322.
38. Vieille, L. “From Data Independence to Knowledge Independence: An on-going Story”. Proc. of the 24th VLDB Conf, New York, 1998, pp. 650-654.
39. W3C. “OWL Web Ontology Language Guide”. http://www.w3.org/TR/2003/CR-owlguide-20030818/
40. Wieringa, R.J. Design Methods for Reactive Systems. Morgan Kaufmann, 2003, 457 p