Requirements
Initially, an application’s requirements are somewhat vague. In fact, they should be a little vague. They should focus on what needs to be done, not on how it should be done. That allows you the most flexibility in your design.
For instance, consider the requirements for a simple order tracking system, as demonstrated in the following example.
ExampleThe application should track customer orders. It should be able to list past orders by a given customer, display details for an order, and print an invoice for an order. When the customer orders an item that is not in stock, the system should display a message so the user can order new inventory. The system should produce reports giving order amounts. Optional report parameters should ... |
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access