1 / 25

Approach

Design Patterns for Enterprise UI Architectures | IA Summit b2005: Montreal Karl Mochel | Oracle Corporation | karl.mochel@oracle.com. Approach. Take an overview of three architectures Discuss issues in evolution of a Marketing application

kevyn-maxwell
Download Presentation

Approach

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Design Patterns for Enterprise UI Architectures|IA Summit b2005: MontrealKarl Mochel | Oracle Corporation | karl.mochel@oracle.com

  2. Approach • Take an overview of three architectures • Discuss issues in evolution of a Marketing application • Comment on the evolution of enterprise information architecture

  3. Introduction • Enterprise applications are transactional systems • Two flavors: Self-service and Professional • Can easily have hundreds of pages • Processes are often convoluted and indeterminate

  4. PTA - Persistent Tab Architecture • Objects: Complex, but with little external relationships • Tasks: Tend to be object-centric • Good for applications whose objects are naturally siloed

  5. Current State of the Industry

  6. TLA – Tabless Architecture • Objects: Simple, Hub and Spoke • Tasks: • Generally simple, without long processes that drill down several levels • Checklists • Good for applications with short-term processes and internalized structures

  7. CTA – Contextual Tab Architecture • Objects: Single primary object with relationships to many other objects • Tasks: Complex and part of a larger process • Good for complex applications that have a monolithic object with long-term processes and externalized structure

  8. The Then > values in the database • Information architecture directly reflects objects in database • Functionality is derived from direct actions against objects • Views and actions are tactical

  9. A Detailed Marketing Example

  10. Campaigns Events Programs Schedules Structural Issues • Structure confuses relationships of objects • Hierarchy of significant objects not apparent • Business processes not apparent • Attributes of every type of object are visible • Each tab aggregates every instance of each object type Plan > Implement > Execute > Track

  11. Real Estate Issues 1024 x 768

  12. Flow Issues • Assumes important actions are tactical updates • Requires steps to find and verify actions’ appropriateness

  13. Design Approaches • Remove chafe • Make decision-making accessible • Shift architectural weight off tabs into virtual structures • Normalize primary objects: Programs, Campaigns, Activities, Schedules • Move to contextual architecture

  14. Restructuring Marketing…Visually

  15. Architectural Shift New Old

  16. Effect • Programs, Campaigns, Schedules, and Events are templates • User can make decisions about elements in comparison and in context • Processes are reflected using tabs • Navigation paths are perceived to be shorter • Reduction in architectural weight • Reduction in perceived page count

  17. The Now > data in context • Information architecture reflects business processes • Additional functionality has been added to evaluate and act on state of processes • Strategic views with tactical actions

  18. Information Flow • Decisions are enabled (darkest blue) • Easy access to updates enabled • Secondary emphasis on creating and evaluating relationships between objects (light blue)

  19. Issues With Current Architectures • Lack of a holistic view into the state of the process • Current • Trends • Strategic Planning and Editing still decoupled

  20. Design Approaches • Design visualizations that enable planning and decision making • Collapse architectural space around the visualization space • Enable aggregate actions

  21. The Future > usable information • Visualization provides views based on business decisions, architecture supports. • Interactive visualization provides basis for evaluating and acting on relationships between processes • Addition of strategic actions

  22. Knowledge Flow • Strategic actions are now enabled (darkest blue) • Updates happen in concert (light blue)

  23. Enabling Visualization

  24. Conclusion Enterprise UI architecture is still immature Keep in mind… • The users questions, not their tasks • Whether it is appropriate to split an application into multiple spaces • Different dimensions around which to structure the IA • Planning, decision making, and comparison activities can be well served by visualization • Look for an ontology of taxonomies that can provide a language to depict different applications spaces similarly but with the flexibility needed to present each spaces unique structures • Information architecture issues have many solutions

  25. Q&A Q & A www.kalmdesigns.com/iasummit2005_kalm.ppt

More Related