Talk:Software maintenance/GA1

GA Review

Passed. Sohom (talk) 14:11, 24 June 2024 (UTC)[reply]

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Article (edit | visual edit | history) · Article talk (edit | history) · Watch

Nominator: Buidhe paid (talk · contribs) 03:20, 7 May 2024 (UTC)[reply]

Reviewer: Sohom Datta (talk · contribs) 03:46, 11 May 2024 (UTC)[reply]

I'll try to tackle this over this weekend. sohom@enwiki 03:46, 11 May 2024 (UTC)[reply]

Noting that I had forgotten about this, I'll try to get to it this week. (Feel free to ping me liberally if I don't) Sohom (talk) 03:09, 28 May 2024 (UTC)[reply]

No worries, I've been quite busy too! Buidhe paid (talk) 00:44, 29 May 2024 (UTC)[reply]

Buidhe paid I've gone through and raised a few concerns :) Sohom (talk) 00:07, 9 June 2024 (UTC)[reply]

Note: If you were not already aware, you should know about this comment Buidhe paid (talk) 14:05, 24 June 2024 (UTC)[reply]

Review

On reading through the article, one thing in particular jumps out to me. It feels like article sort of assumes that the waterfall model is the default (and only) model used in software development. The article very briefly mentions the fact that software is often delivered in a incomplete state nowadays but doesn't address the elephant in the room i.e. the fact that a lot of the software development that happens today happens in a iterative manner utilizing frameworks like the agile software development and often the maintainence phase is done alongside the rest of the phases.
- My understanding is that waterfall versus agile methodology is more relevant to the pre-delivery software development, rather than the scope of this artile that is about post-delivery changes driven by change requests rather than requirements. Given that the definition for software maintenance is "the modification of a software product after delivery", agile or FOSS products that are delivered early and undergo refinement after delivery could also count as maintenance. However, it does not tend to be called maintenance in sources, making it harder to cover. Also, "the agile software development lifecycle lacks a dedicated maintenance plan" 2024.

I think that fact itself should be mentioned (that newer SDLCs do not actually have a maintainance phase at all)

Done Buidhe paid (talk) 14:04, 24 June 2024 (UTC)[reply]

The article should probably give some context on where/how the offshoring/outsourcing happens. Currently, the article has a slight bit of a globalization issue, as it mentions offshoring and outsourcing the maintainance of software to other countries without any context of which countries do it when I'm pretty sure it tends to be mostly the anglosphere.
- I think you're correct that offshoring tends to be from countries with higher cost of living to those with a lower cost of living, but I'm having a really hard time finding sources that say this explicitly for software maintenance.
  - Added
that maintenance is not be practical or economical
- Done
The section Alternatives to maintenance should probably be prosified with context on when those list options are chosen.
- The source does not cover this information; I will look elsewhere. I do think that bullet points are appropriate because each of these does not have enough content to be a separate paragraph.
- Update: I've added as much information as I can find. Buidhe paid (talk) 14:04, 24 June 2024 (UTC)[reply]
Sources seem good, there is a extraneous citation above the lede, that could be removed.
- Fixed Buidhe paid (talk) 14:04, 24 June 2024 (UTC)[reply]

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.