Design Patterns – Definition Laura M. Smith AppsUX Associate Program Manager

Agenda What is a Design Pattern? How it differs from what you have used before Why are we using Design Patterns? What about BLAF Specs? What Design Patterns do not cover

Design Patterns - Definition Design patterns are common flows or page designs that are used across all product families. They are built according to common requirements, tested for usability, and delivered through JDeveloper as composite components to expedite the design process. Use the FusionGPS website to select which pattern is most appropriate for your product design.FusionGPS website

Agenda What is a Design Pattern? How they differ from what you have used before Why are we using Design Patterns? What about BLAF Specs? What Design Patterns are do not cover

Design Pattern – How are they different? BLAF+/ADF Tech Specs BLAF+ Technical Usage Specs Standards and Guidelines Design Patterns Fusion Applications

Design Patterns – Pre Fusion - Process In BLAF Patterns were represented as common flows Developers build / hand code using the examples RESULTS: Variances in code Needed UI testing User across product families/ apps - the same flow could be laid out differently Disconnected User Experience Extend the development cycle

Previous BLAF approach

Agenda What is a Design Pattern? How it differs from what you have used before Why are we using Design Patterns? What about BLAF Specs? What Design Patterns are do not cover

Design Pattern – Why are we using them? Saving dev time – pre coded Shorter development cycle Pre tested for UI Constancy for the user – common – only learn once

Fusion Approach

Agenda What is a Design Pattern? How it differs from what you have used before Why are we using Design Patterns? What about BLAF Specs? What Design Patterns are do not cover

Design Pattern - BLAF

Design Pattern - Guidance

Agenda What is a Design Pattern? How it differs from what you have used before Why are we using Design Patterns? What about BLAF Specs? What Design Patterns are do not cover

Design Pattern – What they are NOT Design patterns do not address every possible interaction needed by a product, just the common interactions that are seen frequently across all product families.

More information? FusionGPS Contact your AppsUX representative