http://www.sitepoint.com/forums/showthread.php?t=193797
1) Requirements are written on a word processor (usually word).
2) The use cases are best communicated as stories.
3) If you want to have a project to be flexible along the lines of the problem domain, then the names of classes/interfaces should match the language of the domain.
4) Use cases for web apps. are easy to describe after the initial discussions, but tend to get very detailed. Click here, then there, etc.
5) If you want to monitor project progress then the only reliable indicator is working code.
6) A measure of working code that both business people and programmers understand is a runnable use case.
博客围绕Web项目开发展开,提到需求可用文字处理器编写,用例以故事形式沟通最佳。指出类和接口命名应契合问题领域语言,Web应用用例初始讨论后易描述且会很详细。还表明监控项目进度可靠指标是工作代码,可运行用例是商人和程序员都理解的衡量方式。
1874

被折叠的 条评论
为什么被折叠?



