5. Graphical Interface
• The “web” management interface
–Lightweight & fast
• Core interaction patterns & metaphors
–Foster understanding of management model
• Style & branding
–Community vs. Product look & feel
• Accessibility requirements
–508 compliance
5
6.
7.
8. A Framework to build on
• Web based tooling
–reusable components (Project Ballroom)
–conduct UX constraints
• Extension & integration points
–Layered products
8
12. Drawbacks
• Lack of customizable workflows
• Lack of runtime extensions
• Doesn’t adapt to context of use
• Very limited vertical reach
–i.e. shared use cases with JON
12
13. Customizable workflows
• aka “Task based” approach
–Repetitive tasks (i.e web+ds)
–Custom workflows (organizational constraints)
• Think CLI scripts within the console
–Repository of tasks
–Stock & community ones
–Growing ecosystem
• Problem setting by the community/users
13
14. Runtime extensions
• Currently compile time
–Extensions are build using java code
–Requires GWT knowledge
–Works but doesn’t scale
• Lacks support for:
–Transformation, Remoulding of the UI
14
15. Context of use
• User
–i.e security, authorization
• Platform, Environment
–i.e. versioning, extensions, etc
• How does the GUI adapt in these cases?
15
21. Use cases
• Realize plugin descriptors
–i.e XML based (can be loaded at runtime)
–exchange format between tools (JON, Eclipse)
• Modeling custom workflows
–Structure & Behavior
–Combination of Task & interface model
• Method engineering
–Establishing UX methods & deliverables
21