Planning user interaction and presentation strategy (17 percent)
- Design application content flow. It may include but is not limited to:
- user navigation,
- user interface goals,
- layout techniques (dynamic layout techniques),
- components not part of control data class (ToolTipProvider, ErrprProvider, HelpProvider)
- Plan data capture. It may include but is not limited to:
- validating input (type converters, regular expressions, apply business rules),
- responding to mouse and keyboard input,
- pick list (combo boxes, list boxes, auto-fill text boxes)
- Design a reporting strategy. It may include but is not limited to:
- MicrosoftReportViewer,
- CrystalReportViewer,
- print classes,
- embedded vs. external server-generated reports
- Design user interface components. It may include but is not limited to:
- common dialog boxes,
- designing navigation by using menus,
- SDI and MDI (multiple monitor configuration, implementing master and detail),
- single vs. multiple instances of the application,
- implementing data binding,
- abstracting with custom controls (abstract base classes),
- using and creating user controls (extend a custom control to add functionality, creating a custom DataGridView column),
- integrating with non-Forms UI elements
- Design a data-binding strategy. It may include but is not limited to:
- populating from XML,
- populating from SQL,
- populating from object data source and entity
- , lazy loads,
- updating bound data (concurrency management, late commits, lazy commits),
- data context
- Design forms inheritance.
- May include but is not limited to:
- visual inheritance,
- functionality common across forms
