Pattern Format

Problem Summary: Provides a short scenario of the interface issue from the perspective of what a user is trying to accomplish and how the user encounters this interface issue.
Pattern Key: Provides a unique key that is given to each pattern so that it can be easily referenced in documentation.
Example: Provides a graphical representation of solution which adheres to ASI style standards.
Use When: Provides the context for when a pattern should be employed.
Solution: Provides the to do list in order to make use of the pattern.
Rationale: Explains why the pattern is needed.
Accessibility: Explains how the pattern addresses accessibilty concerns or is consistent with accessibility standards.
Internationalization: Explains how the pattern addresses internationalization concerns or is consistent with internationalization standards.
Supporting Examples: Provides examples of pattern in use outside of iMIS.
Where Used: Provides examples of where the pattern is already in use within iMIS.

Items of Note: Explains exceptions or special rules.

Put to Use

Code Base Solution: Provides names or information for specific code/controls that incorporate the pattern so that developers can access easily and use.

Status: Lists where pattern is in lifecycle. Creation, Collaboration, Review, Finzalized

Adherence Rating: Represents the expectation of the UX team given their determination of pattern's importance for maintaing standards, usability, accessibility, and internationalization. Provides another context for use, based on UX experience, for dev team to consider when implementing.

Used in Conjunction with: Provides additional patterns when one pattern in and of itself does not necessarily present a comprehensive solution.

Related Patterns: Provides examples of similar patterns that address a similar problem.

How Useful is this pattern? Future feature. Will allow user to submit rating and show scale based on all user input.