Talk:Software development process

This is an old revision of this page, as edited by Dzonatas (talk | contribs) at 12:21, 17 January 2006 (System/Software Design/Development Process/Life/Cycle Merger Discussion). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Hm, what is the relationship bewteen software development process and project lifecycle? Much duplication between these pages, needs to be clarified. - Guppie

Also, what is relationship between methodology and software development process?

It all comes down to definition. Project lifecycle is to with project, not necessarily software. And software is often only one component of a system (requirements definition, analysis, design, hardware, network infrastructure, disaster recovery, operations manuals, user manuals, marketing, training, etc etc). And a methodology can apply to any one or any subset of all these. Or to the project. You could even have a project to develop a methodology. We have different words for different things! Luckily. Paul Beardsell 16:45, 20 Feb 2004 (UTC)


A life-cycle organises the various processes, methods and sub-components and is mainly focused on the order and priority with which they should be completed e.g. when to design, when to develop, when to test (kind of like an animals life-cycle: birth, growth, adulthood, old-age, death). A methodology on the other hand defines exactly how the project and its sub-components should be carried out (how often the whole team should meet, who's in charge of each bit, who keeps tabs, how new feature requests should be handled etc). Specific methodologies are often used with specific life-cycles (i.e. evolutionary and iterative life-cycles use more agile methodologies whereas waterfall life-cycles use more traditional and structured ones. Canderra 00:09, 7 December 2005 (UTC)Reply


System/Software Design/Development Process/Life/Cycle Merger Discussion

Here is the single point of discussion for the merger of the following articles with Google results:

  1. "Software development process" - 912,000 results
  2. "Project lifecycle" - 383,000 results
  3. "Software development life cycle" - 300,000 results
  4. "Software development cycle" - 160,000 results
  5. "System Development Life Cycle" - 112,000 results
  6. "Systems development life cycle" - 105,000 results
  7. "System Design Life Cycle" - 925 results

How shall we deal with them? -- Zondor 03:37, 22 October 2005 (UTC) -- Zondor 03:48, 22 October 2005 (UTC)Reply

  • Consider also Project management. It got 65M hits on Google and is quite tightly related to the Project lifecycle (or ought to be). Development process and lifecycle are closely related to each other on the system level (ISO 15288 "System life cycle processes") as well as on the software level (ISO 12207 "Software life cycle processes"). My humble proposal would hence be to aim for the three main articles covering systems, software and projects respectively. Daniel.wengelin 07:55, 4 January 2006 (UTC)Reply
  • Projects are not always IT based. Although Wiki is very IT-centric, a Project Lifecycle is not always software or hardware based. Project Lifecycle is a sub component of Project Management. These items need to be distinguished. Paul Jones January 4, 2006.
  • Don't merge. Systems and software are like fruits and seeds. SDLC goes beyond software with consideration for hardware and other platform implementation needs, for example. SDLC is not limited to just software. ISO 15288 is only limited to information systems, but it sounded good. — Dzonatas 12:21, 17 January 2006 (UTC)Reply