mic_none

Talk:Software development Source: en.wikipedia.org/wiki/Talk:Software_development

Introduction

[edit]

Why are there two conflicting definitions of software development in the introduction? Either two separate viewpoints should be described with rationale for each one, or one definition should be chosen. — Preceding unsigned comment added by 85.76.66.183 (talk) 09:41, 20 January 2018 (UTC)[reply]

Merge in of Software development methodology

[edit]

Note: The content of software development methodology moved to software development process, so that is now the article to merge from. 

* Oppose There are two distinct topics here. Programming (which you can do alone) and Process. We need a page that managers can come to read, because process is in their domain of expertise.  — Preceding unsigned comment added by 184.71.8.218 (talk) 19:02, 26 February 2015 (UTC)[reply]
  • Support I think at 10K this article is actually too short. Its only content is a summary of software development methodology, including the activities and approaches described in (slightly too much) detail there, and a section on the role of marketing in software development. It doesn't make much sense to me to have an overview in this article and then all the details that support that overview in a different article. -- Beland (talk) 16:28, 21 August 2014 (UTC)[reply]
  • Oppose: This article describes roughly what software development is in a very high-level, incomplete, partial, superficial and not very structured manner, whereas the other article also focuses more in describing the different methodologies (Waterfall, Agile, etc), and thus is more useful for people studying, for example, computer science. I think software development and software development process can be two distinct articles, but they could definitely be improved, and be more focused and structured in describing respectively what software development and a software development process are. Moreover, the article software development process could be a sub-article of software development, since, indeed, in the field of software development there are different models, processes, or whatever way you want to call these methodologies, used to develop software. Nbro (talk) 14:52, 20 February 2017 (UTC)[reply]
  • Support: Combine them into one page. High-level info for managers belongs in the Intro and Overview sections at the top of the page, followed by sections with the details and specifics. No need for two pages. 131.119.15.14 (talk) 21:02, 22 June 2022 (UTC)[reply]
  • Comment: I just prodded Software development (disambiguation) because the articles listed there are about roughly the same topic. From the history of that dab page, I think we could also merge this article with Software engineering and Computer programming as well. Duckmather (talk) 14:50, 11 July 2022 (UTC)[reply]
[edit]

Hello fellow Wikipedians,

I have just modified 2 external links on Software development. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 15:59, 9 December 2017 (UTC)[reply]

Untitled

[edit]

[1][2][3] [4] — Preceding unsigned comment added by Buidhe paid (talk • contribs) 04:01, 1 March 2024 (UTC)[reply]

References

  1. ^ Tucker, Allen; Morelli, Ralph; de Silva, Chamindra (2011). Software Development: An Open Source Approach. CRC Press. ISBN 978-1-4398-8460-7.
  2. ^ Vishnu, Pendyala (20 December 2019). Tools and Techniques for Software Development in Large Organizations: Emerging Research and Opportunities: Emerging Research and Opportunities. IGI Global. ISBN 978-1-7998-1865-6.
  3. ^ Royce, Walker; Bittner, Kurt; Perrow, Mike (23 March 2009). The Economics of Iterative Software Development: Steering Toward Better Business Results. Pearson Education. ISBN 978-0-321-63768-0.
  4. ^ Merkow, Mark S.; Raghavan, Lakshmikanth (2010). Secure and Resilient Software Development. CRC Press. ISBN 978-1-4398-2697-3.

Edit request

[edit]

Please replace the current content of the article, above the categories, with User:Buidhe paid/sandbox. I've rewritten the article to expand its content and address the concerns in the banner. Buidhe paid (talk) 23:52, 12 March 2024 (UTC)[reply]

I will try to get to this later tonight, if nobody beats me to it. HouseBlaster (talk · he/him) 14:27, 27 March 2024 (UTC)[reply]

Wiki99 summary

[edit]

Summary of changes as a result of the Wiki99 project (before, after, diff)

  • Underwent complete rewrite, except for the "View model" section
  • Greatly expanded the methodology section to give an overview of different development methodologies
  • Summarized all development steps in the "steps" section
  • Rewrote "workers" section based on reliable sources
  • Removed some unsourced content from the rest of the article, but added sourced sections on IDEs, version control, documentation, intellectual property issues etc.
  • Included content on open-source software development throughout the article

For other editors to consider doing in the future:

  • Reorganize the "models and tools" section—although I'm not sure what the best organization is, I think it is possible to do better
  • Despite the expansion, the article is still fairly short at just over 2000 words. It could be expanded with more information.
  • Alternately, it is possible to revisit the decision to separate this article from software development process to minimize content duplication.

Buidhe paid (talk) 03:18, 28 March 2024 (UTC)[reply]

Re-wrote intro

[edit]

The intro was confusing and misleading IMO so I re-wrote it. I stayed with the referenced info from Dooley. I included the source info below since it's hard to find the book text online. Also, the info in the intro was organized poorly; not in coherent paragraphs.

Dooley page 1: 

Here’s the definition of software development that we’ll use in this book: software development is the process of taking a set of requirements from a user (a problem statement), analyzing them, designing a solution to the problem, and then implementing that solution on a computer. Isn’t that programming, you ask? No. Programming is really the implementation part, or possibly the design and implementation part, of software development. Programming is central to software development, but it’s not the whole thing. Well, then, isn’t it software engineering? Again, no. Software engineering also involves a process and includes software development, but it also includes the entire management side of creating a computer program that people will use, including project management, configuration management, scheduling and estimation, baseline building and scheduling, managing people, and several other things. Software development is the fun part of software engineering. So, software development is a narrowing of the focus of software engineering to just that part concerned with the creation of the actual software. And it’s a broadening of the focus of programming to include analysis, design, and release issues. Stevebroshar (talk) 15:24, 3 November 2024 (UTC)[reply]

Proposed addition: AI-based estimation tools in the Planning section

[edit]

Hello,

I'd like to propose a small addition to the “Planning” section of the Software development article to reflect recent developments in estimation techniques.

With the increasing use of machine learning and AI in software project planning, several tools now offer cost and effort estimation based on selected technical parameters and historical project data. These tools are particularly relevant in early-stage product planning, where traditional in-house estimation may be unavailable.

Proposed sentence:

> During the planning phase, development teams often use cost estimation tools to define budgets and timelines. Recent tools apply AI techniques to analyze inputs such as feature sets, platform requirements, and historical data to generate structured effort predictions."AI-Powered App Cost Estimation: Plan Your Project Accurately in 2025". Calculators.tech. 2025-04-08."App Development Planning with AI: Costs, Timelines, and Key Steps for Success". Utilities Online. 2025-03-07.

Happy to revise the phrasing or adjust placement if needed. Appreciate your feedback. SoftDevAnalyst (talk) 08:18, 21 April 2025 (UTC)[reply]

Both of these sources are just ads disguised as blog posts. They are not reliable sources. —  HELLKNOWZ ∣ TALK 09:31, 21 April 2025 (UTC)[reply]
Thanks for your feedback — fair point. I’ll work on sourcing from more reliable, editorially independent publications and revise accordingly. SoftDevAnalyst (talk) 10:55, 21 April 2025 (UTC)[reply]