Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PMF/UserCase"
(→Requirements) |
|||
| Line 1: | Line 1: | ||
== Purchase order == | == Purchase order == | ||
| − | === Purposes === | + | === Purposes === |
| + | |||
The purpose of this User case is to illustrate | The purpose of this User case is to illustrate | ||
| − | * Static design | + | |
| − | Data presentation, embeddibility and presentation management. For example, the Address may have 2 presentations | + | *Static design |
| − | * Control Scenario design. | + | |
| + | Data presentation, embeddibility and presentation management. For example, the Address may have 2 presentations | ||
| + | |||
| + | *Control Scenario design. | ||
| + | |||
| + | The model is designed as following: | ||
=== Requirements === | === Requirements === | ||
The purchase order handles two modes of payment and has the possibility to provide a different shipping address. | The purchase order handles two modes of payment and has the possibility to provide a different shipping address. | ||
Revision as of 18:46, 8 November 2009
Purchase order
Purposes
The purpose of this User case is to illustrate
- Static design
Data presentation, embeddibility and presentation management. For example, the Address may have 2 presentations
- Control Scenario design.
The model is designed as following:
Requirements
The purchase order handles two modes of payment and has the possibility to provide a different shipping address.