National Journal of System and Information Technology

Open Access Open Access  Restricted Access Subscription Access
Open Access Open Access Open Access  Restricted Access Restricted Access Subscription Access

Defining a Database Upgrade Design Methodology


     

   Subscribe/Renew Journal


Databases are they key component in any product or Enterprise system. As multiple versions of these products and systems have been rolled out over the years, a need has been felt to define a database upgrade methodology to overcome the multiple issues that ISVs (Independent Software Vendors) face with ad-hoc upgrade strategies. This paper attempts to summarize the drawbacks of the conventional upgrade approach; recommend the key components of a database upgrade and define their boundaries, roles and responsibilities. Finally, the paper also presents recommendations for changes to the conventional SDLC (Software Development Life Cycle).

Keywords

Databases, Upgrade, Methodology, Transformation, Product, Software Development, SDLC, ISV
Subscription Login to verify subscription
User
Notifications
Font Size


  • Christy Pettey, Ben Tudor, “Data Growth as the Largest Data Center Infrastructure Challenge”, Gartner Survey , http://www.gartner.com/ it/page.jsp?id=1460213

  • Markus Zirn, "Application Upgrades and Service Oriented Architecture", Oracle Corporation, April 2008, http://www.cio.com/whitepaper/ 646494/Application_Upgrades_and_ Service_Oriented_Architecture

  • “Control application data growth before it controls your business”, IBM, September 2010

  • PCI Standards - https://www.pcisecuritystandards.org/security_ standards/index.php


Abstract Views: 274

PDF Views: 2




  • Defining a Database Upgrade Design Methodology

Abstract Views: 274  |  PDF Views: 2

Authors

Abstract


Databases are they key component in any product or Enterprise system. As multiple versions of these products and systems have been rolled out over the years, a need has been felt to define a database upgrade methodology to overcome the multiple issues that ISVs (Independent Software Vendors) face with ad-hoc upgrade strategies. This paper attempts to summarize the drawbacks of the conventional upgrade approach; recommend the key components of a database upgrade and define their boundaries, roles and responsibilities. Finally, the paper also presents recommendations for changes to the conventional SDLC (Software Development Life Cycle).

Keywords


Databases, Upgrade, Methodology, Transformation, Product, Software Development, SDLC, ISV

References