The argument for developing the system: the market and customers, the problem it solves, expected revenue, development and unit costs, investment, timing and the main risks, approved at concept and refined when the plan is agreed.
Agreement or business case Work product in the System development lifecycle
It decides whether the system is worth building and sets the targets that later trade-offs are measured against. A business case that is never refreshed lets a programme continue long after the assumptions behind it have failed.
The full lifecycle detail, with its charts, flows, tables and every section, is for registered members. Registration is free and takes a minute. You come back to this page afterwards.