- Business requirements describe why the product is being built and identify the benefits for both customers and the business.
- User requirements describe the tasks or business processes a user will be able to perform with the application/product.
- Functional requirements describe the specific system behaviors that must be implemented.
- Non-Functional requirements describe the specific system constraints that must be adhered to by the application/product.
2009年3月12日 星期四
軟體需求種類
Four levels of requirements
開發工作的典型成本分佈
| Planning and management | 15% |
| Analysis/requirements | 10% |
| Design/integration | 15% |
| Implementation/functional tests | 30% |
| Measurement/assessment/acceptance test | 15% |
| Tools/environment/change management | 10% |
| Maintenance (fixes during development) | 5% |
開發階段的成本與時間
| Inception | Elaboration | Construction | Transition | |
| Effort | 5% | 20% | 65% | 10% |
| Schedule | 10% | 30% | 50% | 10% |
2009年2月18日 星期三
2008年11月29日 星期六
訂閱：
文章 (Atom)
