TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Why software development is hard

2 点作者 eVizitei超过 17 年前

3 条评论

edw519超过 17 年前
The article doesn't mention the most important thing to do in requirements gathering: putting all the stakeholders in a room at the same time with a professional facilitator extracting REAL needs until everyone agrees, locking the door so no one gets out, and feeding them (so they don't notice that the door is locked).<p>What most analysts fail to realize is that there usually is NO ONE person with all the answers. And most people have DIFFERENT answers. So they don't see the need for this. And do see the need for everything else that doesn't work: UML, DFDs, Rational Rose, Microsoft project, etc., etc., etc.<p>Comprehensive requirements gathering makes all the other headaches go away. Anything less is an endless loop.
xirium大约 17 年前
The requirements specification can pass from the customer/user (CU), to the customer's manager (CM), to a customer advocate (CA), to a business analyst (BA), to a project manager (PM), to a development team (DM) to the Developers. Well, a man with many masters is slave to none. Likewise for code.
randrews超过 17 年前
"Programming is not complicated because computers are complicated—it’s complicated because your requirements are complicated (even if you don’t know it yet)."<p>--Chris Ashton