From screen forms to RDM and from RDM to screen forms

doi:10.1016/0950-5849(92)90078-4

Information and Software Technology

Volume 34, Issue 4, April 1992, Pages 219-228

https://doi.org/10.1016/0950-5849(92)90078-4 Get rights and content

Abstract

A database is visible to users at the application interface level primarily through browse-and-edit screens. The gap between screen and database representations may be large for complex applications. To manage that complexity, two additional levels of representations are introduced — screen subschemas and database subschemas. A screen subschema is a data-model representation of the screen's data structure. A database subschema is a data model of the database subset used to support the screen design. A bidirectional semantical link between the screens and the database is used to design the database schema from screen visual representations (forms) and vice versa. Normalization is used to transform a screen subschema to a database subschema and absorption is applied to transform a database subschema to a screen subschema.

References (18)

C Gane et al.
Structured systems analysis: tools and techniques
(1977)
T DeMarco
Structured analysis and system specification
(1979)
E Yourdon et al.
Structured design
(1978)
C Batini et al.
A comparative analysis of methodologies for database schema integration
Comput. Surv.
(1986)
H Tardieu et al.
A method, a formalism, and tools for data base design
H Tardieu et al.
Conception d'un système d'information
(1984)
ML Brodie et al.
On the design and specification of database transactions
MA Jackson
Principles of program design
(1975)
Warnier J-D
Logical construction of systems
(1981)

There are more references available in the full text version of this article.

Cited by (6)

Components reuse for data-intensive business programs through an object-oriented architecture
1996, Journal of Systems and Software
This article proposes an object-oriented specification architecture to support components reuse for data-intensive business programs. In the architecture, we augment the general object model for modeling the objects in a program. The architecture is developed through adopting a domain-specific approach to take advantage from the characteristics of data-intensive business programs. It provides graphical composition for interconnecting modules to compose a program. With the use of the architecture to design data-intensive business programs, designers are encouraged to compose a program from modules that are functionally cohesive and reusable. This maximizes the opportunities to reuse existing reusable modules and to discover new reusable modules.
Group data base design: Addressing the view modeling problem
1995, The Journal of Systems and Software
Today's organizations increasingly depend on the use of data base technology to manage their operations. Advances in technology have resulted in increasing the number and complexity of these data bases. Despite their growing complexity, all data bases have one thing in common: each must have gone through either a formal or an informal design process. Data bases must mirror reality accurately, and thus the design process must better capture that reality. The heart of the design process is the conceptual design, data model mapping, and physical design. Our research focuses on providing automated support for the first of these, e.g., conceptual design. Conceptual design is known to be a very difficult and time-consuming phase in the development of data base applications. This article describes the architecture, implementation, and use of a distributed graphical group data base design system. The group view modeling system (GVMS) is implemented in Microsoft Windows for networked personal computers. The main purpose of GVMS is to allow multiple designers (or users) to share conceptual design information in real time and resolve design conflicts through the electronic medium. The underlying data model, semantic data model, is extended to include distribution information as well as transactions and is represented as an extended entity relationship model. Diagram management techniques are implemented to aid in simplifying large complex designs. A small study demonstrated that groups of data base designers who define their view collectively outperform individuals.
Recovery of object-oriented design from existing data-intensive business programs
1995, Information and Software Technology
Extracting object-oriented designs from non-object-oriented data-intensive business programs is an important issue in software re-engineering and maintenance. In this paper, an augmented object model for specifying data-intensive business programs is proposed. Consequently, a methodology for the recovery of a specification using the proposed model from an existing data-intensive business program is proposed. The specification recovered represents an object-oriented design of the program. The design is expressed in terms of real-world application objects and operations and can be reused in similar applications.
Towards a role-based framework approach for user interfaces
1996, Journal of Research and Practice in Information Technology
Towards a role-based framework approach for user interfaces
1996, Australian Computer Journal
GENIUS: Generating Software-ergonomic User Interfaces
1996, Plastics, Rubber and Composites Processing and Applications

View full text

From screen forms to RDM and from RDM to screen forms

Abstract

Structured systems analysis: tools and techniques

Structured analysis and system specification

Structured design

A comparative analysis of methodologies for database schema integration

Comput. Surv.

A method, a formalism, and tools for data base design

Conception d'un système d'information

On the design and specification of database transactions

Principles of program design

Logical construction of systems