Revision as of 20:54, 26 May 2007 edit Afbcasejr (talk \| contribs) 27 edits Created separate article on Cap Gemini SDM. It is inappropriate for Cap Gemini to hijack a generic term like system development methodlogy to pitch 1 method. ← Previous edit		Revision as of 21:01, 26 May 2007 edit undo Afbcasejr (talk \| contribs) 27 edits No edit summary Next edit →
Line 1: '''System Development Methodology''' is a general term applied to a variety of structured, organized processes for developing information technology and embedded software systems. Over the years there have been many system development methodologies including [[Cap ~~Gemiin~~Gemini SDM]] and SDM2, developed by [[PANDATA]], now part of Cap Gemini, ''PRIDE: Profitable Informatoin by DEsign,'' the first commercially available SDM, [[SSADM]] [[Structured Analysis and Design Method]], [[SDM70]] by Atlantic Management Systems, [[Spectrum Structured]] by Spectrum Systems, and many more. Early SDMs were focused on project management - and defining the phases, tasks and worksteps, or [[hierarchical work breakdown stucture]] or [[Waterfall Model]] of a typical information technology project, and were analysis and design technique agnostic. Many of these project management based methodologies were, in fact, based on either [[critical path method]] ([[CPM]]) or the Navy's [[Program Evaluation and Review Technique]] ([[PERT]]).

System Development Methodology: Difference between revisions