• Documents
  • Authors
  • Tables
  • Log in
  • Sign up
  • MetaCart
  • DMCA
  • Donate

CiteSeerX logo

Advanced Search Include Citations

Tools

Sorted by:
Try your query at:
Semantic Scholar Scholar Academic
Google Bing DBLP
Results 1 - 3 of 3

The Object-Oriented Database System Manifesto

by Malcolm Atkinson, François Bancilhon, David DeWitt, Klaus Dittrich, David Maier, Stanley Zdonik , 1989
"... This paper attempts to define an object-oriented database system. It describes the main features and characteristics that a system must have to qualify as an objectoriented database system. We have separated these characteristics into three groups: ffl Mandatory, the ones the system must satisfy in ..."
Abstract - Cited by 361 (5 self) - Add to MetaCart
This paper attempts to define an object-oriented database system. It describes the main features and characteristics that a system must have to qualify as an objectoriented database system. We have separated these characteristics into three groups: ffl Mandatory, the ones the system must satisfy

Specifying Information System Dynamics in Troll (Extended Abstract)

by Peter Hartel, Thorsten Hartmann, Jan Kusch, Gunter Saake , 1994
"... 1 1 Introduction Information Systems are becoming more and more complex. They span over many different application domains, have to integrate several heterogeneous resources, and to cooperate with existing systems [SJH93]. Therefore it is important to model such systems on an abstract level without ..."
Abstract - Add to MetaCart
the allowed evolution of the system, i.e. the permitted and maybe mandatory state transitions. ffl The...

unknown title

by J. Cazin, P. Cros, R. Jacquart, M. Lemoine, P. Michel
"... A few years ago, formal developments were still considered an academic task. The main reasons were the size of addressable problems, the heaviness of notations, the lack of support tools, and the time overhead compared with usual empiric developments. These few arguments become more and more obsolet ..."
Abstract - Add to MetaCart
methods are mandatory to be used to produce correct software. But it makes no use to define such methods without giving means to control their application. Such a control must dispose of a formal notion of development it can refer to when checking the correctness of a given development step.ffl
Results 1 - 3 of 3
Powered by: Apache Solr
  • About CiteSeerX
  • Submit and Index Documents
  • Privacy Policy
  • Help
  • Data
  • Source
  • Contact Us

Developed at and hosted by The College of Information Sciences and Technology

© 2007-2019 The Pennsylvania State University