ST&QA 2011年1月到2月的杂志中发布了JAMA软件调查(JAMA Software Survey)结果
2011-04-30 18:17
309 查看
ST&QA 2011年1月到2月的杂志中发布了JAMA软件调查(JAMA Software Survey)结果:
I found some of the results very interesting. For example,72% of respondents believed
gaining a clear understanding of what customers want from software is one of their
biggest challenges.
需求不清晰是个老大难问题。
It looks like collaboration on teams is working. 76.9% of respondents say everyone on
the team is in sync regarding the latest versions of the requirements.
内部需求的同步和沟通做得还可以。
83.2% of respondents track requirements via spreadsheets and documents. This is in
contrast to respondents that use a specific technical solution.
83.2%的企业还是用Excel等文档方式记录和跟踪需求。看来需求工具还是有不少市场的。60%的企
业有意向采购需求管理工具。
For software vendors, 60% of respondents suggest they will be shopping for a tool to
help manage the collaboration of requirements.
Regarding software development process, the largest response was 39.9% stating they
use a mix of processes. Waterfall was at 25.9% and Agile came in at 19.2%. Only 3%
didn’t believe in process.
基本上都认为流程还是很重要的。传统瀑布模型、敏捷的采用者都不少,更多的是采用两者结合的
研发流程。
注:
ST&QA 2011年1-2期的杂志已经上传到www.AutomationQA.com资源共享中:
http://www.automationqa.com/resources/113-staqa-2011-12.html
I found some of the results very interesting. For example,72% of respondents believed
gaining a clear understanding of what customers want from software is one of their
biggest challenges.
需求不清晰是个老大难问题。
It looks like collaboration on teams is working. 76.9% of respondents say everyone on
the team is in sync regarding the latest versions of the requirements.
内部需求的同步和沟通做得还可以。
83.2% of respondents track requirements via spreadsheets and documents. This is in
contrast to respondents that use a specific technical solution.
83.2%的企业还是用Excel等文档方式记录和跟踪需求。看来需求工具还是有不少市场的。60%的企
业有意向采购需求管理工具。
For software vendors, 60% of respondents suggest they will be shopping for a tool to
help manage the collaboration of requirements.
Regarding software development process, the largest response was 39.9% stating they
use a mix of processes. Waterfall was at 25.9% and Agile came in at 19.2%. Only 3%
didn’t believe in process.
基本上都认为流程还是很重要的。传统瀑布模型、敏捷的采用者都不少,更多的是采用两者结合的
研发流程。
注:
ST&QA 2011年1-2期的杂志已经上传到www.AutomationQA.com资源共享中:
http://www.automationqa.com/resources/113-staqa-2011-12.html
相关文章推荐
- ST&QA 2011年1-2期的杂志 已上传到AutomationQA资源共享
- [翻译Joel On Software]无痛软件规范-第二部分:什么是规范/Painless Functional Specifications -Part 2: What's a Spec?
- 敏捷软件开发宣言–Manifesto for Agile Software Development
- 国土资源部2009.12.31 关于县(市)级土地调查数据库建库软件数据更新功能测试结果(第一批)的公告
- 软件开发模型(Software Devel…
- 敏捷软件开发宣言–Manifesto for Agile Software Development
- Eclipse社区调查结果发布
- Software release life cycle 软件发布生命周期
- 【译】信息图 - 软件测试领导力问卷调查结果
- 关于县(市)级土地调查数据库管理系统软件测评结果(第一批)的公告
- The results of a survey of computer professionals around USA(美国计算机行业的工资调查结果)
- Scribus 1.4.2 发布,开源电子杂志制作软件
- 软件发布生命周期 Software release life cycle
- 发布一个"文本/文件朗读"小软件
- 发布iOS应用(xcode5)到App St…
- 软件发布的生命周期(software release life cycle)
- Shodan新工具发布:木马恶意软件C&C服务器搜索引擎
- 【Todo】抽象渗漏法则 & 找到理想员工 & 软件开发成功 12 法则 & Joel on Software
- 《PHP&MORE》--第一本中文PHP电子杂志创刊号发布
- [投票]3·15消费者日 《程序员》杂志之现状调查