Pattern Library - List of Requirements
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

View only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
2
Opportunities (from Journey Map)User Story
3
All UsersFiles are not centralized or searchable. People often use informal means (like an email out to the team or a chat message) to see if there are examples of existing patterns.(As a UX designer, creative, and developer) When working on a new project, I want to be able to see and use relevant examples (creative or functionally) within the organization's repository.
4
All UsersThe association between the pattern’s wireframe, final design file, and code base is lost as all files are stored at a departmental level across the organization
5
UX/CreativeTime is spent creating patterns and PSD files from scratch. Many features such as forms and safety information modals are essentially ubiquitous across projects within the pharmaceutical industry.
6
DevelopmentTime is spent assessing if code from the past can be leveraged. This is time consuming as different people working on projects can provide different creative files and annotations.
7
UXTime is spent on annotations for repeating patterns.
8
UXTime is spent creating prototypes to explain features to internal and client stakeholders.As a UX designer I want to provide live links of the patterns to internal/external stakeholders so that I do not need to re-create a prototype
9
CreativeTime is spent searching for documentation and guidelines as work is passed from designer to designer.As a creative, I want all brand and hand-off guidelines in one place.
10
DevelopmentTime is spent assessing and creating tech specs.
11
12
DepartmentsRequirementsPriority
13
CreativeAll states of the pattern in the Sketch/PSD filemust have
14
CreativeAnimation direction documented in the patternoptional
15
CreativeThe creative file (Sketch/PSD) should include Grid/columnsmust have
16
CreativeNaming system: should follow the current naming systemmust have
17
CreativeReadme section in the file, that states how the file should be set and used.must have
18
CreativeFiles available in Sketch/PSDmust have
19
CreativeUsers will be able to access one design file per viewport (PSD)
20
CreativeHome page or other page that allows users to view multiple components and browse quicklymust have
21
Creative/Dev/UXChannel (e.g. IVA, Website, etc) is a tagfuture
22
Creative/Dev/UXVersion Controlmust have
23
Creative/Dev/UXDefining the limitations of the Pattern and filemust have
24
Creative/Dev/UXPatterns will be categorized by component in a brand agnostic waymust have
25
Creative/Dev/UXPatterns will be searchablefuture
26
Creative/Dev/UXChange log / notificationsfuture
27
DevDevice list that the pattern supportsmust have
28
DevBrowser support list that the pattern supportsmust have
29
DevClient mail support list that the pattern supportsmust have
30
DevWebsite examples that the pattern was implementedmust have
31
DevQuick start guide and implementation guide with Code examplesmust have
32
DevDisplay the Breakpoint supportmust have
33
DevOS support list that the pattern supportsmust have
34
DevNpm install must have
35
UXAnnotations of the functionality of the pattern(in the patternlab and the sketch file)must have
36
UXPreview of the Pattern that you can interact and see all the states of the patternmust have
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
Main menu