DOCSLIB.ORG

General Object-Oriented Database for Software

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
General Object-Oriented Database for Software The GOODSTEP Pro ject: General Ob ject-Oriented Database for Software Engineering Pro cesses The GOODSTEP Team Abstract 1 Ob jective of GOODSTEP The goal of the GOODSTEP project is The goal of the GOODSTEP pro ject is to enhance and improve the functionality of to develop a sophisticated database system a ful ly object-oriented database management dedicated to the supp ort of software develop- system to yield a platform suited for appli- mentenvironments SDEs and make the ba- cations such as Software Development En- sis for a platform for SDE construction with a software pro cess to olset and generators for vironments SDEs. The baseline of the graphical and textual integrated to ols imple- project is the O database management sys- 2 mented on top of it. tem DBMS. The O DBMS already in- 2 The GOODSTEP pro ject started Septem- cludes many of the features required by SDEs. b er 1992 and will last for three years. This The project has identifed enhancements to pap er mainly rep orts on the rst year of work O in order to make it a real software en- 2 within the pro ject. gineering database management system. The baseline of the pro ject is an exist- These enhancements are essential ly upgrades ing Europ ean commercially available ob ject- of the existing O functionality, and hence 2 oriented database pro duct: O [4]. Rather requirerelatively easy extensions to the O 2 2 than developing a new database manage- system. They have been developedinthe ment system from scratch, GOODSTEP will early stages of the project and are now ex- enhance and improve this pro duct. ploited and validated by a number of software Besides the enhancements and improve- engineering tools built on top of the enhanced ments of O which make it an admirably O database system. Toease tool construc- 2 2 suited system for SDEs, the pro ject pro- tion, the GOODSTEP platform encompasses vides a numb er of test cases and p erforms tool generation capabilities which al low for case studies to evaluate and justify the ap- generation of integratedgraphical and textual proach. This includes p orting and devel- tools from high-level speci cations. In addi- oping a numb er of existing software engi- tion, the GOODSTEP platform provides a neering to ols on top of the new platform, softwareprocess toolset which enables mod- the development of to ol generation capabili- eling, analysis and enaction of softwarepro- ties to exploit the features of a fully ob ject- cesses and is also built on top of the extended oriented system, and the developmentofad- O database. The GOODSTEP platform wil l 2 vanced software pro cess mo deling capabili- be validated using two CASE studies carried ties which, once again, exploit the provided out to develop an airline application and a features of O . business application. 2 The choice of an ob ject-oriented database This work has b een funded by the EU under con- management system as baseline of the tract No. 6115 ESPRIT-I I I pro ject GOODSTEP pro ject derives from the inadequacy of re- lational database systems for software engi- neering applications, which has b een recog- nized for quite some time [22,25]. This has resulted in a great e ort in b oth the indus- trial and research communities to extend the t database technology towards more curren Software Process Tool Construction werful and exible database management po toolset toolset systems. In particular, in this context we are interested in the work done on the develop- uses uses ment of ob ject-oriented database systems. The class of ob ject-oriented database sys- wo cat- tems can b e roughly classi ed in t O2 Additional functionalities egories: those o ering the full functionali- ted data mo del, which ties of the ob ject-orien O2 Kernel O2 database e will refer to from nowonas object w enhancement management system database systems ODBSs [10], and those o ering only a subset of the ob ject-oriented mo del, whichwe will call structural ly ob ject- oriented database systems. The main dis- Figure 1: The GOODSTEP SDE platform tinction b etween structurally ob ject-oriented databases and ob ject database systems, which is also the main drawback of the hances the functionalities o ered by O ,by 2 rst class, is that most of the structurally adding new functionalities to its kernel or on ob ject-oriented database systems, suchas top of it. Moreover, two to ol sets have b een PCTE/OMS [17], Damokles [12], assume a develop ed together with the enhanced O 2 certain level of granularity of the ob jects to system to constitute the GOODSTEP plat- b e stored and retrieved and that they further form. The rst to olset TCT supp orts the cannot de ne encapsulation of data struc- generation of new to ols. The other set of tures by op erations. These systems either to ols supp ort development, simulation and supp ort relations b etween coarse-grained ob- execution of software pro cesses SPT. In jects such as pro ducts of the SE life cycle particular it integrates the to ols generated e.g. A is the sp eci cation of B, A is owned by the rst to ol set. Both SPT and TCT sup- by develop er Q, etc., or else supp ort a rather p ort the development of a customized SDE. ne-grained level of ob jects suchassyntac- The rest of the pap er is structured as fol- tic units of programs or sp eci cations i.e. lows: In Section 2, we rst describ e the statements, variables, pro cedures, etc.. GOODSTEP platform in some detail. In In practice, many software engineering Section 3, we describ e the fundamental re- to ols require supp ort for b oth levels of granu- quirements for the underlying database sys- larity. By contrast, ob ject database systems tem as required by the GOODSTEP plat- are the b est approach to supp ort sophisti- form. In Section 4, we showhow these re- cated ecient storage and retrieval of ob jects quirements are addressed by O and we de- 2 at arbitrary levels of granularity [13]. scrib e the planned O extensions. Finally, 2 The pro ject amply demonstrates two im- Section 5 concludes the pap er while drawing p ortant features of an ob ject database sys- attention on ongoing and further work. tem. In the rst place, it enables much eas- ier implementations of SE-tools than when using conventional DBMSs. This is b ecause 2 Building the GOODSTEP Plat- the richer semantics of the ob ject oriented form for Software Develop- mo del is most suited to the complex data mentEnvironments handled in software engineering applications, and also b ecause there is no problem of xed The metho ds and languages to b e used for granularity of ob jects. In the second place, the development of a software application { it signi cantly improves the functionality of b e they graphical or textual languages { de- softwaretools which can bebasedupon it. p end on the application domain. For exam- The software architecture of GOODSTEP ple, real-time applications require di erent is illustrated in Figure 1. GOODSTEP en- sp eci cation and implementation languages than nancial or medical applications. More- it is p ossible to assign values to tokens and over, the pro cess mo dels that supp ort an ap- predicates to transitions, describing the con- plication development b est can not b e pre- straints on tokens consumed and pro duced de ned. They dep end not only on the appli- by transition rings. cation domain, but also on the organization and on the p eople who are running the pro- 2.1.1 SLANG cesses. Current SDEs su er from their se- We describ e SLANG by means of a simple lection of sp eci c combinations of languages example. A SLANG sp eci cation of a pro- and often assume a particular pro cess. Both cess fragment is presented in Figure 2. For usually do not completely cover the needs an elab orated discussion of SLANG, we refer of any software development and imp ose a to [7]. pre-sp eci ed development mo de. Instead, the software industry demands customiz- Executable Test Cases hmay b e easily adapted to able SDEs, whic Module * the evolving needs of software development. GOODSTEP addresses this need by provid- Start Test ing means to * de ne the pro cess used for developing Data for Test Cumulative Test ware system within the software a soft Execution Results (CTR) (DFTE) pro cess to ol-set and generate the to ols needed during the Test Cases Prepare Test Used Up course of a software pro cess using the to ol construction to ol-set. Executable Test (RET) Using the pro cess to ol-set a mo del tailored to the needs of a particular institution or Test Results Being Computed en pro ject can b e mo deled, analyzed and ev (TRBC) Execute Test later used for running a software pro ject. Test Results Using the to ol construction to ol-set, it will Summary (TRS) b e p ossible to de ne and generate concep- Test Results tual schemas and de ne and generate a set tegrated syntax-directed software devel- of in End Test Errors Found t to ols from appropriate sp eci cation opmen Add Test Result languages. Final Test Results 2.1 Software Pro cess Mo deling and Enactment Figure 2: A Mo del of a Pro cess Fragmentin Software pro cess mo deling and enactment SLANG is supp orted in GOODSTEP by the SPADE Software Pro cess Analysis Design and En- The example mo dels a pro cess activity to actment environment.
Load more

Recommended publications
  • Object-Oriented Databases Need for Complex Data Types
    Object-Oriented Databases! ■" Need for Complex Data Types! ■" The Object-Oriented Data Model! ■" Object-Oriented Languages! ■" Persistent Programming Languages! ■" Persistent C++ Systems! 8.1! Need for Complex Data Types! ■" Traditional database applications in data processing had conceptually simple data types! é" Relatively few data types, first normal form holds! ■" Complex data types have grown more important in recent years! é" E.g. Addresses can be viewed as a ! Ø" Single string, or! Ø" Separate attributes for each part, or! Ø" Composite attributes (which are not in first normal form)! é" E.g. it is often convenient to store multivalued attributes as-is, without creating a separate relation to store the values in first normal form! ■" Applications! é" computer-aided design, computer-aided software engineering! é" multimedia and image databases, and document/hypertext databases.! 8.2! 1! Object-Oriented Data Model! ■" Loosely speaking, an object corresponds to an entity in the E- R model.! ■" The object-oriented paradigm is based on encapsulating code and data related to an object into single unit.! ■" The object-oriented data model is a logical data model (like the E-R model).! ■" Adaptation of the object-oriented programming paradigm (e.g., Smalltalk, C++) to database systems.! 8.3! Object Structure! ■" An object has associated with it:! é" A set of variables that contain the data for the object. The value of each variable is itself an object.! é" A set of messages to which the object responds; each message may have zero, one, or more parameters.! é" A set of methods, each of which is a body of code to implement a message; a method returns a value as the response to the message! ■" The physical representation of data is visible only to the implementor of the object! ■" Messages and responses provide the only external interface to an object.! ■" The term message does not necessarily imply physical message passing.
    [Show full text]
  • Object Oriented Database Management Systems-Concepts
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Global Journal of Computer Science and Technology (GJCST) Global Journal of Computer Science and Technology: C Software & Data Engineering Volume 15 Issue 3 Version 1.0 Year 2015 Type: Double Blind Peer Reviewed International Research Journal Publisher: Global Journals Inc. (USA) Online ISSN: 0975-4172 & Print ISSN: 0975-4350 Object Oriented Database Management Systems-Concepts, Advantages, Limitations and Comparative Study with Relational Database Management Systems By Hardeep Singh Damesha Lovely Professional University, India Abstract- Object Oriented Databases stores data in the form of objects. An Object is something uniquely identifiable which models a real world entity and has got state and behaviour. In Object Oriented based Databases capabilities of Object based paradigm for Programming and databases are combined due remove the limitations of Relational databases and on the demand of some advanced applications. In this paper, need of Object database, approaches for Object database implementation, requirements for database to an Object database, Perspectives of Object database, architecture approaches for Object databases, the achievements and weakness of Object Databases and comparison with relational database are discussed. Keywords: relational databases, object based databases, object and object data model. GJCST-C Classification : F.3.3 ObjectOrientedDatabaseManagementSystemsConceptsAdvantagesLimitationsandComparativeStudywithRelationalDatabaseManagementSystems Strictly as per the compliance and regulations of: © 2015. Hardeep Singh Damesha. This is a research/review paper, distributed under the terms of the Creative Commons Attribution- Noncommercial 3.0 Unported License http://creativecommons.org/licenses/by-nc/3.0/), permitting all non-commercial use, distribution, and reproduction inany medium, provided the original work is properly cited.
    [Show full text]
  • Object-Relational DBMS
    Session-7: Object-Relational DBMS Cyrus Shahabi 1 Motivation Relational databases (2 nd generation) were designed for traditional banking-type applications with well-structured, homogenous data elements (vertical & horizontal homogeneity) and a minimal fixed set of limited operations (e.g., set & tuple- oriented operations). New applications (e.g., CAD, CAM, CASE, OA, and CAP), however, require concurrent modeling of both data and processes acting upon the data. Hence, a combination of database and software-engineering disciplines lead to the 3 rd generation of database management systems: Object Database Management Systems, ODBMS. Note that a classic debate in database community is that do we need a new model or relational model is sufficient and can be extended to support new applications. 2 Motivation … People in favor of relational model argue that: New versions of SQL (e.g., SQL-92 and SQL3) are designed to incorporate functionality required by new applications (UDT, UDF, …). Embedded SQL can address almost all the requirements of the new applications. “Object people”, however, counter-argue that in the above- mentioned solutions, it is the application rather than the inherent capabilities of the model that provides the required functionality. Object people say there is an impedance mismatch between programming languages (handling one row of data at a time) and SQL (multiple row handling) which makes conversions inefficient. Relational people say, instead of defining new models, let’s introduce set-level functionality into
    [Show full text]
  • Relational and Object-Oriented Databases
    Relational and Object-Oriented Databases by Willi-Hans Steeb International School for Scientific Computing Contents 1 What is a table? 1 1.1 Introduction . 1 1.2 Examples . 5 1.3 Tables in Programs . 8 1.4 Table and Relation . 33 2 Structured Query Language 35 2.1 Introduction . 35 2.2 Integrity Rules . 38 2.3 SQL Commands . 39 2.3.1 Introduction . 39 2.3.2 Aggregate Function . 40 2.3.3 Arithmetic Operators . 40 2.3.4 Logical Operators . 40 2.3.5 SELECT Statement . 41 2.3.6 INSERT Command . 45 2.3.7 DELETE Command . 46 2.3.8 UPDATE Command . 47 2.3.9 CREATE TABLE Command . 48 2.3.10 DROP TABLE Command . 51 2.3.11 ALTER TABLE Command . 52 2.4 Set Operators . 53 2.5 Views . 60 2.6 Primary and Foreign Keys . 62 2.7 Datatypes in SQL . 63 2.8 Joins . 66 2.9 Stored Procedure . 71 2.10 MySQL Commands . 72 2.11 Cursors . 73 2.12 PL and SQL . 75 2.13 ABAP/4 and SQL . 76 2.14 Query Processing and Optimization . 77 i 3 Normal Forms 83 3.1 Introduction . 83 3.2 Anomalies . 87 3.3 Example . 89 3.4 Fourth and Fifth Normal Forms . 93 4 Transaction 101 4.1 Introduction . 101 4.2 Data Replication . 107 4.3 Locks . 108 4.4 Deadlocking . 111 4.5 Threads . 117 4.5.1 Introduction . 117 4.5.2 Thread Class . 119 4.5.3 Example . 121 4.5.4 Priorities . 123 4.5.5 Synchronization and Locks .
    [Show full text]
  • Object Database Benchmarks
    Object Database Benchmarks Jérôme Darmont ERIC, Université Lumière Lyon 2, France INTRODUCTION The need for performance measurement tools appeared soon after the emergence of the first Object-Oriented Database Management Systems (OODBMSs), and proved important for both designers and users (Atkinson & Maier, 1990). Performance evaluation is useful to designers to determine elements of architecture and more generally to validate or refute hypotheses regar ding the actual behavior of an OODBMS. Thus, performance evaluation is an essential component in the development process of well-designed and efficient systems. Users may also employ performance evaluation, either to compare the efficiency of different technologies before selecting an OODBMS or to tune a system. Performance evaluation by experimentation on a real system is generally referred to as benchmarking. It consists in performing a series of tests on a given OODBMS to estimate its performance in a given setting. Benchmarks are generally used to compare the global performance of OODBMSs, but they can also be exploited to illustrate the advantages of one system or another in a given situation, or to determine an optimal hardware configuration. Typically, a benchmark is constituted of two main elements: a workload model constituted of a database and a set of read and write operations to apply on this database, and a set of performance metrics. BACKGROUND OBJECT DATABASE BENCHMARKS EVOLUTION In the sphere of relational DBMSs, the Transaction Performance Processing Council (TPC) issues standard benchmarks, verifies their correct application and regularly publishes performance tests results. In contrast, there is no standard benchmark for OODBMSs, even if the more popular of them: OO1, HyperModel, and OO7, can be considered as de facto standards.
    [Show full text]
  • Multi-Model Databases: a New Journey to Handle the Variety of Data
    0 Multi-model Databases: A New Journey to Handle the Variety of Data JIAHENG LU, Department of Computer Science, University of Helsinki IRENA HOLUBOVA´ , Department of Software Engineering, Charles University, Prague The variety of data is one of the most challenging issues for the research and practice in data management systems. The data are naturally organized in different formats and models, including structured data, semi- structured data and unstructured data. In this survey, we introduce the area of multi-model DBMSs which build a single database platform to manage multi-model data. Even though multi-model databases are a newly emerging area, in recent years we have witnessed many database systems to embrace this category. We provide a general classification and multi-dimensional comparisons for the most popular multi-model databases. This comprehensive introduction on existing approaches and open problems, from the technique and application perspective, make this survey useful for motivating new multi-model database approaches, as well as serving as a technical reference for developing multi-model database applications. CCS Concepts: Information systems ! Database design and models; Data model extensions; Semi- structured data;r Database query processing; Query languages for non-relational engines; Extraction, trans- formation and loading; Object-relational mapping facilities; Additional Key Words and Phrases: Big Data management, multi-model databases, NoSQL database man- agement systems. ACM Reference Format: Jiaheng Lu and Irena Holubova,´ 2019. Multi-model Databases: A New Journey to Handle the Variety of Data. ACM CSUR 0, 0, Article 0 ( 2019), 38 pages. DOI: http://dx.doi.org/10.1145/0000000.0000000 1.
    [Show full text]
  • Sesame: an Architecture for Storing and Querying RDF Data and Schema Information
    Sesame: An Architecture for Storing and Querying RDF Data and Schema Information Jeen Broekstra Arjohn Kampman Aidministrator Nederland b.v. Aidministrator Nederland b.v. [email protected] [email protected] Frank van Harmelen Faculty of Sciences, Vrije Universiteit Amsterdam [email protected] Abstract RDF and RDF Schema provide the first W3C standard to enrich the Web with machine-processable semantic data. However, to be able to use this semantic data, a scalable, persistent RDF store and a powerful query engine using an expressive query language are needed. Sesame is an extensible architecture implementing both of these. Sesame can be based on arbitrary repositories, ranging from traditional Data Base Management Systems, to dedicated RDF triple stores. Sesame also implements a query engine for RQL, the most powerful RDF/RDF Schema query lan- guage to date. 1 Introduction The Resource Description Framework (RDF) [Lassila and Swick, 1999] is a W3C Recommendation for the notation of meta-data on the World Wide Web. RDF Schema [Brickley and Guha, 2000] extends this standard by providing developers with the means to specify vocabulary and to model object structures. These techniques will enable the enrichment of the Web with machine-processable semantics, thus giving rise to what has been dubbed the Semantic Web. However, simply having this data available is not enough. Tooling is needed to process the information, to transform it, to reason with it. As a basis for this, we have developed Sesame, an architecture for efficient storage and expressive querying of large quantities of RDF meta-data. Sesame is being developed by Aid- ministrator Nederland b.v.1 as part of the European IST project On-To-Knowledge2 [Fensel et al., 2000].
    [Show full text]
  • Examples of Object Oriented Database in Healthcare
    Examples Of Object Oriented Database In Healthcare daguerreotypedGuessable and unstimulatedadventurously. Burgess Eucaryotic misdrawings Weston sometimessome idolism animalises so theatrically! any breakpoint Lubric Tommy result alwaysabed. represses his berberine if Zorro is ring-necked or In Object-oriented Model data stored in archive form of objects The structure which is called classes which display board within company It defines a database. Clustering is the walking of grouping a scent of objects in such church way that objects in the. Title CMConnect. And functional requirements leading data-modeling the process-mapping. Is MongoDB faster than MySQL? What decade the 4 basics of OOP? Object-oriented databases make the ghost of reduced maintenance code reusability real world modeling and. Health Data Management Splunk Architecture Ransomware Data Recovery. How AI Can Revolutionize the fireplace Industry Built In. Advice based on other factors such as memoirs and additional symptoms. Eso vlt standard. For shed some EHR collect her in structured formats and International. Types of Databases Database Models Learntekorg. PDF Intentionally-Linked Entities a database tidy for. Big Data in lens Care Applications and Challenges in Data. Object-oriented systems analysis and design fundamental data structures and. Can be enough resources become more efficiently respond thursday that of database leads to providers and mathematical certainty that decision support is a rather complicated to. Object Oriented Programming and NoSQL are vitally important. For example converting the XML xsd files that describe our base of FpML version 5. 10 Hottest Healthcare IT Developer and Programming Skills. Example Readers can develop propose implement use maintain a Webstore. Below are examples of related occupations with associated Arizona-based.
    [Show full text]
  • Mobilitydb: a Mainstream Moving Object Database System
    MobilityDB: A Mainstream Moving Object Database System Esteban Zimányi Mahmoud Sakr [email protected] [email protected] CoDE. Université Libre de Bruxelles CoDE. Université Libre de Bruxelles, Belgium Belgium FCIS. Ain Shams University, Egypt Arthur Lesuisse Mohamed Bakli [email protected] [email protected] CoDE. Université Libre de Bruxelles CoDE. Université Libre de Bruxelles Belgium Belgium ABSTRACT a moving object database system (MOD). A MOD is a database This paper demonstrates the MobilityDB moving object database system that provides the functionality of storing and querying system. It is an extensive implementation on top of PostgreSQL and moving object data via a query interface. Building a MOD requires PostGIS with multiple novel aspects. MobilityDB defines multiple extending a database system vertically at all its levels: storage, spatiotemporal types for moving geometry and geography points, access methods, operations, SQL interface, and query optimization. as well as for temporal integers, reals, Booleans, and strings. It The long established research in moving object databases has also defines a rich set of operations on these types. The typesare so far resulted in few research prototypes, e.g., SECONDO [3] and supported with spatiotemporal index access methods by extending HERMES [5]. However, an industry-scale implementation that can GiST (Generalized Search Tree) and SP-GiST (Space Partitioning be used in real-world applications is not yet available. MobilityDB GiST). The query interface is SQL. MobilityDB thus extends the is envisioned to fill in this gap. It is built on top of PostgreSQL PostgreSQL optimizer with statistics collectors and selectivity esti- and PostGIS, which are, respectively, a widely used open source mation functions.
    [Show full text]
  • Object Persistence
    Object Persistence Object Oriented Programming Introduction • One of the most critical tasks that applications have to perform is to save and restore data • Persistence is the storage of data from working memory so that it can be restored when the application is run again • In object-oriented systems, there are several ways in which objects can be made persistent • The choice of persistence method is an important part of the design of an application Object Oriented Programming Object Serialization Object Oriented Programming Object Serialization • Simple persistence method which provides a program the ability to read or write a whole object to and from a stream of bytes • Allows Java objects to be encoded into a byte stream suitable for streaming to a file on disk or over a network • The class must implement the Serializable interface (java.io.Serializable), which does not declare any methods, and have accessors and mutators for its attributes Object Oriented Programming Object Serialization // create output stream File file = new File("teams_serialize.ser"); String fullPath = file.getAbsolutePath(); fos = new FileOutputStream(fullPath); // open output stream and store team t1 out = new ObjectOutputStream(fos); out.writeObject(t1); Object Oriented Programming Using Databases • Most Client-Server applications use a RDBMS as their data store while using an object-oriented programming language for development • Objects must be mapped to tables in the database and vice versa • Applications generally require the use of SQL statements embedded
    [Show full text]
  • 1 Survey of Graph Database Models
    1 Survey of Graph Database Models RENZO ANGLES and CLAUDIO GUTIERREZ Universidad de Chile Graph database models can be defined as those in which data structures for the schema and instances are modeled as graphs or generalizations of them, and data manipulation is expressed by graph-oriented operations and type constructors. These models took off in the eighties and early nineties alongside object- oriented models. Their influence gradually died out with the emergence of other database models, in particular geographical, spatial, semistructured, and XML. Recently, the need to manage information with graph-like nature has reestablished the relevance of this area. The main objective of this survey is to present the work that has been conducted in the area of graph database modeling, concentrating on data structures, query languages, and integrity constraints. Categories and Subject Descriptors: G.2.2 [Discrete Mathematics]: Graph Theory—Graph labeling; Hyper- graphs; Network problems; Path and circuit problems; H.2.1 [Database Management]: Logical Design— Data models; schema and Subschema; H.2.3 [Database Management]: Languages—Query languages; Data description languages (DDL); Data manipulation languages (DML); Query languages; H.2.5 [Database Man- agement]: Heterogeneous Databases; H.2.8 [Database Management]: Database Applications General Terms: Design, Languages, Management Additional Key Words and Phrases: Database systems, graph databases, database models, graph database models, graph query languages, graph integrity constraints ACM Reference Format: Angles, R. and Gutierrez, C. 2008. Survey of graph database models. ACM Comput. Surv. 40, 1, Article 1, (February 2008), 39 pages. DOI = 10.1145/1322432.1322433 http://doi.acm.org/10.1145/1322432.1322433 1.
    [Show full text]
  • Object Database Management Systems: Concepts and Features
    nIST Special Publication 500-179 Computer Systems Object Database Technology Management Systems: U.S. DEPARTMENT OF COMMERCE National Institute of Concepts and Features Standards and Technology Christopher E. Dabrowski Nisr Elizabeth N. Fong Deyuan Yang NAT L INST. OF STAND & TECH R.I.C, A111D3 3aTS7t, REFERENCE NIST PUBLICATIONS -QC" 100 U57 500-179 1990 NATIONAL MSTrrUTE OF STANDARDS & TECHNOLOGY Research Informatm Center Gaithersburg, MD 20899 NIST Special Publication 500-179 t Object Database Management Systems: Concepts and Features Christopher E. Dabrowski Elizabeth N. Fong Deyuan Yang National Computer Systems Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899 April 1990 U.S. DEPARTMENT OF COMMERCE Robert A. Mosbacher, Secretary NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY John W. Lyons, Director Reports on Computer Systems Technology The National Institute of Standards and Technology (NIST) (formerly the National Bureau of Standards) has a unique responsibility for computer systems technology within the Federal government. NIST's National Computer Systems Laboratory (NCSL) develops standards and guidelines, provides technical assistance, and conducts research for computers and related telecommunications systems to achieve more effective utilization of Federal information technology resources. NCSL's responsibilities include development of technical, management, physical, and administrative standards and guidelines for the cost-effective security and privacy of sensitive unclassified information processed in Federal computers. NCSL assists agencies in developing security plans and in improving computer security awareness train- ing. This Special Publication 500 series reports NCSL research and guidelines to Federal agencies as well as to organizations in industry, government, and academia. National Institute of Standards and Technology Special Publication 500-179 Natl.
    [Show full text]