Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "PMF/UserCase"

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
+
* Static design
  
 
Data presentation, embeddibility and presentation management. For example, the Address may have 2 presentations  
 
Data presentation, embeddibility and presentation management. For example, the Address may have 2 presentations  
 +
** 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  ===
  
*Control Scenario design.
+
The purchase order handles two modes of payment and has the possibility to provide a different shipping address.  
  
The model is designed as following:
+
=== Model  ===
  
=== Requirements ===
+
[[Image:PurchaseOrder.png]]
The purchase order handles two modes of payment and has the possibility to provide a different shipping address.
+

Revision as of 18:58, 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

    • 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 purchase order handles two modes of payment and has the possibility to provide a different shipping address.

Model

PurchaseOrder.png

Back to the top