Technology versus Methodology Support for Database Design: A Study of Designer Choice Related to Perception and Performance

Technology versus Methodology Support for Database Design: A Study of Designer Choice Related to Perception and Performance

Thomas E. Marshall, Michael L. Gibson
Copyright: © 1996 |Pages: 11
DOI: 10.4018/jdm.1996100101
OnDemand:
(Individual Articles)
Available
$37.50
Current Special Offers
No Current Special Offers
TOTAL SAVINGS: $37.50

Abstract

Information Systems (IS) designers often have to choose between directly applying design methods and/or using technology to support design methods. The purpose of this research is to develop a better understanding of how the choice between design approaches - design methods versus advanced technology - may impact the perceptions and performance of IS designers. The literature suggests that the scope of criteria useful in evaluating design methods and approaches is expanding. Research into methodology and technology support should include aspects addressing how a design approach impacts the designer, facilitates designeruser communications, and supports the implementation process of transforming conceptual models into more computeroriented forms. Through a laboratory experiment, this research investigates database design support by comparing a data modeling design approach (Kroenke Semantic Object approach) to a technology-based approach (Analyst designer software). The research findings provide insights into perceived and performance- based support provided by the different design approaches. In general, performance and perceptions with respect to type of support are not entirely consistent. There appears to be an underlying theme addressing the trade-offs between usability and the technical implementation support provided. When possible dysfunctional consequences exist regarding these trade-offs, IS managers should communicate to their designers that implementation integrity should not be sacrificed for increased usability, or vice-versa. Database designers need to be aware of these issues in design methods, especially those related to design performance, and seek means of mitigating any negative impact on the integrity of the databases designed.

Complete Article List

Search this Journal:
Reset
Volume 35: 1 Issue (2024)
Volume 34: 3 Issues (2023)
Volume 33: 5 Issues (2022): 4 Released, 1 Forthcoming
Volume 32: 4 Issues (2021)
Volume 31: 4 Issues (2020)
Volume 30: 4 Issues (2019)
Volume 29: 4 Issues (2018)
Volume 28: 4 Issues (2017)
Volume 27: 4 Issues (2016)
Volume 26: 4 Issues (2015)
Volume 25: 4 Issues (2014)
Volume 24: 4 Issues (2013)
Volume 23: 4 Issues (2012)
Volume 22: 4 Issues (2011)
Volume 21: 4 Issues (2010)
Volume 20: 4 Issues (2009)
Volume 19: 4 Issues (2008)
Volume 18: 4 Issues (2007)
Volume 17: 4 Issues (2006)
Volume 16: 4 Issues (2005)
Volume 15: 4 Issues (2004)
Volume 14: 4 Issues (2003)
Volume 13: 4 Issues (2002)
Volume 12: 4 Issues (2001)
Volume 11: 4 Issues (2000)
Volume 10: 4 Issues (1999)
Volume 9: 4 Issues (1998)
Volume 8: 4 Issues (1997)
Volume 7: 4 Issues (1996)
Volume 6: 4 Issues (1995)
Volume 5: 4 Issues (1994)
Volume 4: 4 Issues (1993)
Volume 3: 4 Issues (1992)
Volume 2: 4 Issues (1991)
Volume 1: 2 Issues (1990)
View Complete Journal Contents Listing