Content deleted Content added
Reply |
Relationship between Life-cycle & Methodology |
||
Line 4:
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. [[User:Psb777|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 and incremental development|iterative]] life-cycles use more [[agile software development|agile]] methodologies whereas waterfall life-cycles use more traditional and structured ones. [[User:Canderra|Canderra]] 00:09, 7 December 2005 (UTC)
== System/Software Design/Development Process/Life/Cycle Merger Discussion ==
| |||