Selecting Development Approach
SELECTING A DEVELOPMENT APPROACH
Original Issuance: February 17, 2005 Revalidated: March 27, 2008
Introduction
A system development methodology refers to the framework that is used to structure, plan, and control the process of developing an information system. A wide variety of such frameworks have evolved over the years, each with its own recognized strengths and weaknesses. One system development methodology is not necessarily suitable for use by all projects. Each of the available methodologies is best suited to specific kinds of projects, based on various technical, organizational, project and team considerations. CMS has considered each of the major prescribed methodologies in context with CMS’ business, applications, organization, and technical environments. As a result, CMS requires the use of any of the following linear and iterative methodologies for CMS systems development, as appropriate.
Acceptable System Development Methodologies
Waterfall
Initial Investigation Requirements Definition System Design Coding, testing,... Implementation Operation & Support
Framework Type: Linear Basic Principles: 1. Project is divided into sequential phases, with some overlap and splashback acceptable between phases. 2. Emphasis is on planning, time schedules, target dates, budgets and implementation of an entire system at one time. 3. Tight control is maintained over the life of the project through the use of extensive written documentation, as well as through formal reviews and approval/signoff by the
____________________________________________________________
_________________________________ Office of Information Services 1
user and information technology management occurring at the end of most phases before beginning the next phase. Strengths: 1. Ideal for supporting less experienced project teams and project managers, or project teams whose composition fluctuates. 2. The orderly sequence of development steps and strict controls for ensuring the
Original Issuance: February 17, 2005 Revalidated: March 27, 2008
Introduction
A system development methodology refers to the framework that is used to structure, plan, and control the process of developing an information system. A wide variety of such frameworks have evolved over the years, each with its own recognized strengths and weaknesses. One system development methodology is not necessarily suitable for use by all projects. Each of the available methodologies is best suited to specific kinds of projects, based on various technical, organizational, project and team considerations. CMS has considered each of the major prescribed methodologies in context with CMS’ business, applications, organization, and technical environments. As a result, CMS requires the use of any of the following linear and iterative methodologies for CMS systems development, as appropriate.
Acceptable System Development Methodologies
Waterfall
Initial Investigation Requirements Definition System Design Coding, testing,... Implementation Operation & Support
Framework Type: Linear Basic Principles: 1. Project is divided into sequential phases, with some overlap and splashback acceptable between phases. 2. Emphasis is on planning, time schedules, target dates, budgets and implementation of an entire system at one time. 3. Tight control is maintained over the life of the project through the use of extensive written documentation, as well as through formal reviews and approval/signoff by the
____________________________________________________________
_________________________________ Office of Information Services 1
user and information technology management occurring at the end of most phases before beginning the next phase. Strengths: 1. Ideal for supporting less experienced project teams and project managers, or project teams whose composition fluctuates. 2. The orderly sequence of development steps and strict controls for ensuring the
References: “System Development Methodologies for Web Enabled E-Business: A Customization Paradigm”; Linda Night, Theresa Steinbach, and Vince Kellen; November 2001; (http://www.kellen.net/SysDev.htm) “A Survey of System Development Process Models”; Darryl Green and Ann DiCaterino; Center for Technology in Government; February 1998; (http://www.ctg.albany.edu/publications/reports/survey_of_sysdev) “System Development Life Cycle Models and Methodologies”; Paul Fisher, James McDaniel, and Peter Hughes; Canadian Society for International Health Certificate Course in Health Information Systems, Module 3: System Analysis & Database Development, Part 3: Life Cycle Models and Methodologies; (http://famed.ufrgs.br/pdf/csih/mod3/Mod_3_3.htm) “Rapid Application Development: A Review and Case Study”; Paul Beynon-Davies; Kane Thompson Centre; December 1998; (http://www.comp.glam.ac.uk/SOC_Server/research/gisc/RADbrf1.htm) “Introduction to Systems Analysis, Topic 19, Rapid Application Development”; J. R. McBride; Copyright 2002 Prentice-Hall, Inc.;(http://www.csc.uvic.ca/~jmcbride/c375t19.pdf) ____________________________________________________________ _________________________________ Office of Information Services 10