Content deleted Content added
→Sofwert ip: new section |
Stevebroshar (talk | contribs) |
||
| (4 intermediate revisions by 3 users not shown) | |||
Line 33:
I suggest that the ISO/IEC definition of "methodology" should be our reference definition for improvements on this article. see [https://www.iso.org/obp/ui#iso:std:iso-iec:24744:ed-2:v1:en ISO 24744 - Preview]
--[[User:Dobinator|Dobinator]] ([[User talk:Dobinator|talk]]) 09:20, 1 May 2022 (UTC)
== Software development is not a compound word ==
Line 47 ⟶ 44:
"Most modern development processes can be vaguely described as agile. Other methodologies include waterfall, prototyping, iterative and incremental development, spiral development, rapid application development, and extreme programming." [[User:Olaeld|Olaeld]] ([[User talk:Olaeld|talk]]) 08:59, 20 September 2023 (UTC)
== Process is not the same as lifecycle ==
The article starts with "a software development process or software development life cycle (SDLC) is ..." which clearly conflates the two terms. They are highly related, yes, but not the same.
The lifecycle is a description of what happens during the life of a software thing. A process, a formal process, is the self-imposed, agreed upon way to go about creating and maintaining a software thing. The lifecycle is more natural (as natural as software gets) and process is more artificial -- something developers self-impose onto themself in order to create/maintain the software ... throughout its lifecycle. One more subtlety: even if there is no agreed upon process or in spite of an agreed upon process (!), there is still a process that occurs; an ad hoc process. The article should not gloss over (conflate) these different aspects. This article seems focused only on formal process; giving the reader a false impression. [[User:Stevebroshar|Stevebroshar]] ([[User talk:Stevebroshar|talk]]) 11:24, 25 July 2025 (UTC)
| |||