AS7 Console 2013


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

AS7 Console 2013

  1. 1. AS7 Console 2013 Heiko Braun <> Nov 2012
  2. 2. Clarification on ...• The current status• Next generation goals• User experience & usability 3
  3. 3. Requirements“Working towards the initial AS7 release”
  4. 4. 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
  5. 5. A Framework to build on• Web based tooling –reusable components (Project Ballroom) –conduct UX constraints• Extension & integration points –Layered products 8
  6. 6. + Teiid
  7. 7. Console, first generation• Most viable product –Does what you would expect –Provides extension points• Delivered on time• Easy to maintain 10
  8. 8. Web Console 2.0“Moving towards a framework”
  9. 9. 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
  10. 10. 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
  11. 11. 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
  12. 12. Context of use• User –i.e security, authorization• Platform, Environment –i.e. versioning, extensions, etc• How does the GUI adapt in these cases? 15
  13. 13. Context of Products EAP6 JONBRMS EDS JDG SOA 16
  14. 14. Model based UI’s“The missing layer of indirection”
  15. 15. Interface Models• Platform independent description –Task Model • The high level use case (CTT models) –Abstract interface model • Structure (composition, ordering) • Behavior (function calls, navigation)• Mapping toward domain, security models –i.e. AS7 Resource Model mapping 18
  16. 16. CTT Task Model19
  17. 17. Useware Dialog Model20
  18. 18. 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
  19. 19. UX Methodology• Formal –Personas, use cases, wireframes –Interaction Patterns, metaphors• Technical –Building blocks, styles guides –Widgets, UI structure 22
  20. 20. UX benefits from models• Formal –Models support the formal methods –Establish terms, documents and deliverables –Prototyping• Technical –Model & enforce constraints –Generate interfaces (aka model driven) –Allow remoulding & runtime transformations • Context of use (i.e security) 23
  21. 21. Next generation• Simplified, yet expressive extension mechanism –Based on abstract interface model –Possible exchange format (i.e AS7>JON)• Customizable workflows –Task Repositories, Customizations• Establish UX constraints across products –Inherited Quality criteria (Style, Usability, Accessibility) 24