Choosing an environment data model
The semantic data model provides most of the capabilities needed to support software engineering projects. There are some aspects of supporting projects that are not adequately addressed by this model. This paper recommends several extensions to address these inadequacies. First, extensions are described to support the specification and enforcement of project data integrity. Second, extensions are described that support some of the behaviorial aspects of projects, such as methods. Third, extensions are described to control the scope of names and to control the visibility of operations and objects in a project. Software project examples are used to illustrate these extensions.
KeywordsObject Type Dynamic Constraint Cardinality Constraint Object Instance Type Package
Unable to display preview. Download preview PDF.
- [EC]Ecklund D. J., "Robustness in Distributed Hypothetical Databases," Nineteenth Hawaii International Conference on System Sciences, 1986.Google Scholar
- [HM]Hammer M. & McLeod D., "The Semantic Data Model: A Modeling Mechanism for Database Applications," International Conference on the Management of Data, 1978.Google Scholar
- [KK]KIT/KITIA, "DoD Requirements and Design Criteria for the Common APSE Interface Set (CAIS), "October, 1984.Google Scholar
- [MK]Moore, B. & Kou J. "Requirements for a Software Information Database," GTE Labs, TN No. 85-1552.01, 1985Google Scholar
- [RL]Rudmik A., & Lubeck D., "Integrated Project Support in Third Generation Environments," Nineteenth Hawaii International Conference on System Sciences, January 1986.Google Scholar
- [ST]Stars Joint Program Office, "Joint Services Software Engineering Environment (JSSEE) Operational Concept Document," November 1984.Google Scholar
- [ZW]Zdonik, S., & Wegner, P., "Language and Methodology for Object Oriented Database Environments," Hawaii International Conference on System Sciences, January 1986.Google Scholar