有关软件开发生命周期的问题

本文介绍了有关软件开发生命周期的问题的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

软件开发生命周期和软件过程模型之间有什么区别?

What is the difference between software development life cycle and software process model?

推荐答案

这取决于您正在评估的教科书. 大致上，它们是同一回事. It depends on the text book you are being evaluated on. Broadly they are the same thing.

与往常一样，"{0}和{1}之间的区别是什么"形式的问题在原则上是不正确的.苹果和苹果有什么区别? 在这种情况下，我不是100％同意这两个术语基本上是同一回事. 是的，软件开发过程"和软件开发生命周期"基本相同，请参见 en.wikipedia/wiki/Software_development_process [^ ]. 但是，软件过程模型"却有所不同. 软件开发过程"和软件开发生命周期"表示在软件开发过程中实际发生的一些自然现象，而软件过程模型"反映了一些人们试图实践的关于软件开发的构想 .我会说，通常是一个误解:-). Answers将软件过程模型"定义为软件过程的简化描述"，请参见 wiki.answers. com/Q/What_are_the_software_process_model [ ^ ]，但我会说，首先，这种描述源于某些构想. 我强调这种差异是因为我开始理解，实际的软件开发方法通常会遭受巨大的误解和领导者提出或推动这些概念而不是实际知识或科学的野心勃勃的野心.所有这些都牺牲了实际和针对项目的考虑因素，人为因素和其他重要方面.这就解释了为什么这些概念如此频繁地成为时尚和变化的主题. 同时，缺乏概念上的思考会使情况变得更糟，并且无论是在管理工作上还是经常与管理工作相反，似乎都导致大量无法控制的项目失控.应该创建开发概念，但是它们应该更加现实，与每组具体的开发目标和开发团队成员的素质相关.在这方面已经有太多的假知识了.就目前而言，我认为最好的发展构想是:没有灵丹妙药".

—SA

As always, the question in the form "what''s the difference between {0} and {1}" is incorrect in principle. What''s the difference between apple and Apple? In this particular case, I''m not 100% agree that the two terms are basically the same thing. Yes, "Software Development Process" and "Software Development Life Cycle" are basically the same, see en.wikipedia/wiki/Software_development_process[^]. However, "Software Process Model" is something different. "Software Development Process" and "Software Development Life Cycle" mean some phenomena of nature which actually happens during software developing, while "Software Process Model" reflects some conception about software development which someone tries to put into practice. I would say, very often a misconception :-). Answers defined "Software Process Model" as a "a simplified description of a software process", see wiki.answers/Q/What_are_the_software_process_model[^], but I would say, first of all this description grows from some conception. I stress this difference because I come to understanding that actual software development method generally suffer from huge misconceptions and baseless ambitions of the leaders putting forward or pushing those conceptions rather then actual knowledge or science. All this is done sacrificing practical and project-specific considerations, human factor and other important aspects. This explains why those conceptions are subject of fashion and change so often. At the same time, lack of conceptual thinking makes things even worse and massively produce unsupportable projects going out of control seemingly regardless or often contrary to management effort. Development conceptions should be created, but they should be more realistic, more related to each concrete set of development goals and qualities of the members of development team. There is too much of fake knowledge in this area already. For now, I think the best development conception is: "there is no a silver bullet".

—SA