Marcus在召集PHP开发工具的志愿者

博客围绕Web项目开发展开,提到需求可用文字处理器编写,用例以故事形式沟通最佳。指出类和接口命名应契合问题领域语言,Web应用用例初始讨论后易描述且会很详细。还表明监控项目进度可靠指标是工作代码,可运行用例是商人和程序员都理解的衡量方式。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

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.

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值