Skip to main content

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.

Jump to: navigation, search

PMF/UserCase

Revision as of 12:38, 9 November 2009 by Yves.yang.soyatec.com (Talk | contribs) (Static design)

Purchase order

Purposes

The purpose of this User case is to illustrate the concepts for Static design and Control Scenario design.

Static design

It should include teh capabilities:

  • Data presentation
  • Embeddibility
  • Presentation management like mutilple presentation support. For example, the Address may have 2 presentations

From point of view of UI structure, it should be possible:

  • Possible to change the presentation 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
  • 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

PurchaseOrder.png

Back to the top