Refine Refactor documentation » History » Version 5
Amber Herold, 07/06/2011 01:08 PM
| 1 | 1 | Amber Herold | h1. Refine Refactor documentation |
|---|---|---|---|
| 2 | 2 | Amber Herold | |
| 3 | 5 | Amber Herold | h2. Sequence Diagram |
| 4 | |||
| 5 | The following sequence diagram shows how the Form and Parameter classes work together to display a form, validate the user input, and create a command string. |
||
| 6 | |||
| 7 | 3 | Amber Herold | !refine_sequence_diagram.png! |
| 8 | 5 | Amber Herold | |
| 9 | h2. Class Diagram |
||
| 10 | |||
| 11 | The following class diagram shows the BasicForm class with it's extended classes as well as the FormParameter class and it's extended classes. |
||
| 12 | It also shows associations among the classes. |
||
| 13 | Notice that the specific refine parameter classes use polymorphism to override the validate() function. This allows the extended classes to provide more complex validations than a typical form requires. |
||
| 14 | Other forms, such as RunParameters and stack prep, just use the base FormParameters class that their parent, BasicForm, uses. |
||
| 15 | 4 | Amber Herold | |
| 16 | !refineClassDiagram.png! |