Welcome to the InfoSci Platform
Process Model for Round-trip Engineering with Relational Database

Process Model for Round-trip Engineering with Relational Database

Leszek A. Maciaszek
Copyright: © 2002 |Pages: 16
ISBN13: 9781931777124|ISBN10: 1931777128|EISBN13: 9781931777339
DOI: 10.4018/978-1-931777-12-4.ch005
Cite Chapter Cite Chapter

MLA

Maciaszek, Leszek A. "Process Model for Round-trip Engineering with Relational Database." Successful Software Reengineering, edited by Salvatore Valenti, IGI Global, 2002, pp. 76-91. https://doi.org/10.4018/978-1-931777-12-4.ch005

APA

Maciaszek, L. A. (2002). Process Model for Round-trip Engineering with Relational Database. In S. Valenti (Ed.), Successful Software Reengineering (pp. 76-91). IGI Global. https://doi.org/10.4018/978-1-931777-12-4.ch005

Chicago

Maciaszek, Leszek A. "Process Model for Round-trip Engineering with Relational Database." In Successful Software Reengineering, edited by Salvatore Valenti, 76-91. Hershey, PA: IGI Global, 2002. https://doi.org/10.4018/978-1-931777-12-4.ch005

Export Reference

Mendeley
Favorite

Abstract

Iterative and incremental development of client/server database systems requires a round-trip engineering support, in particular in a design-implementation cycle. This paper identifies some more difficult round-trip engineering scenarios and defines processes needed to handle those scenarios. The processes conform to the current state-of-the-practice in forward and reverse engineering with relational databases. The paper identifies limitations of a tool-driven round-trip engineering. The limitations can be linked to three reasons: (1) the inability of a CASE/4GL tool to always generate correct incremental code after schema has been changed, (2) the need for a CASE/4GL to understand the reverse-engineered procedural parts written (or modified) in the implementation phase, (3) the requirement that a database content (extension) be re-instated at the end of each design-implementation cycle. Technical limitations introduce a risk that design models and a database implementation become misaligned and the design-implementation cycle cannot be continued for iterative and incremental software production. Project managers need a process model to impose necessary rigour on design and programming teams to alleviate technical restrictions. The paper defines a project management strategy that enforces appropriate automated and manual processes on database development teams.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.