Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PMF/UserCase"
(→Requirements) |
(→Requirements) |
||
| (9 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
=== Purposes === | === Purposes === | ||
| − | The purpose of this User case is to illustrate | + | The purpose of this User case is to illustrate the concepts for Static design and Control Scenario design. It doesn't deal with the page flow design. |
==== Static design ==== | ==== Static design ==== | ||
| − | Data presentation | + | It should illustrate the following capabilities: |
| + | *Data presentation | ||
| + | *Embeddibility | ||
| + | *Presentation management like mutilple presentation support. For example, the Address may have 2 presentations and it is possible to switch from one to another through some business logic conditions | ||
| − | * | + | From point of view of UI structure, it should be possible: |
| + | |||
| + | *Change the layout: TabFolder, Group, Grid etc. | ||
*Field input control for example for telephone, email, date | *Field input control for example for telephone, email, date | ||
*Feeback of the error using the Decoration of fields, ToolTips | *Feeback of the error using the Decoration of fields, ToolTips | ||
| Line 22: | Line 27: | ||
The application should provide all information in one page. The page consists of three blocks: | The application should provide all information in one page. The page consists of three blocks: | ||
* Customer | * Customer | ||
| − | * Order | + | * Order items |
* Shipping | * Shipping | ||
| Line 29: | Line 34: | ||
It is necessary to access the online helps, in tooltip, or hyperlink | It is necessary to access the online helps, in tooltip, or hyperlink | ||
| − | The required field must be indicated with | + | The required field must be indicated with a visible way: color, marker etc. The choice can be decided in PMF tools. |
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. | ||
Latest revision as of 10:32, 20 November 2009
Contents
Purchase order
Purposes
The purpose of this User case is to illustrate the concepts for Static design and Control Scenario design. It doesn't deal with the page flow design.
Static design
It should illustrate the following capabilities:
- Data presentation
- Embeddibility
- Presentation management like mutilple presentation support. For example, the Address may have 2 presentations and it is possible to switch from one to another through some business logic conditions
From point of view of UI structure, it should be possible:
- Change the layout: TabFolder, Group, Grid etc.
- Field input control for example for telephone, email, date
- Feeback of the error using the Decoration of fields, ToolTips
- Transaction edition
Control Scenario design
- Show/hide some fields through user interactions
- Enable/disable the edition for some fields through user interactions
- Address should have two mode of presentation: one for read only and another for edition.
Requirements
The application should provide all information in one page. The page consists of three blocks:
- Customer
- Order items
- Shipping
The follwing layout should be possible: Grid, GroupBox, ExpendBar and TabFolder. It should be possible to add other layout. The designer have the possibility to switch from one to another.
It is necessary to access the online helps, in tooltip, or hyperlink
The required field must be indicated with a visible way: color, marker etc. The choice can be decided in PMF tools.
The purchase order handles two modes of payment and has the possibility to provide a different shipping address.
Model
