Upgrading to JBoss AS7 Amit Sharma AXS USA LLC [email protected] MCJUG on 20 th Feb 2013 .
AS7 Console 2013
-
Upload
hbraun -
Category
Technology
-
view
1.023 -
download
0
Transcript of AS7 Console 2013
Clarification on ...
• The current status• Next generation goals• User experience & usability
3
Requirements
“Working towards the initial AS7 release”
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 compliance5
A Framework to build on
• Web based tooling–reusable components (Project Ballroom)–conduct UX constraints
• Extension & integration points–Layered products
8
+ Teiid
Console, first generation
• Most viable product –Does what you would expect–Provides extension points
• Delivered on time• Easy to maintain
10
Web Console 2.0
“Moving towards a framework”
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
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/users13
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
Context of use
• User–i.e security, authorization
• Platform, Environment–i.e. versioning, extensions, etc
• How does the GUI adapt in these cases?
15
Context of Products
16
EAP6
BRMS EDS JDG SOA
JON
Model based UI’s
“The missing layer of indirection”
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
19
CTT Task Model
20
Useware Dialog Model
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
UX Methodology
• Formal–Personas, use cases, wireframes–Interaction Patterns, metaphors
• Technical–Building blocks, styles guides–Widgets, UI structure
22
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
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