Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
1.4
-
None
-
None
Description
These goals are at a high level. Problem statement, pain points and known use cases, user scenarios will help help identify goals.
Thinking through how we can rectify identified pain points will help define these goals. For example: Pain point might be "high cognitive load placed on user to remember original information before they edited it in the case they want to go back to original ". A design goal might be, "let the system remember and remind user of information versions".
Design goals should be documented on the wiki in the component design space.
Attachments
Issue Links
- depends on
-
FLUID-1152 Scope: Review user activities and use cases
-
- Closed
-
-
FLUID-1339 Scope: Review pain points
-
- Closed
-
-
FLUID-1340 Scope: Review user activities and use cases
-
- Closed
-
- is depended on by
-
FLUID-1151 Scope: Review pain points
-
- Closed
-
-
FLUID-1155 Scope: Show & Tell of Problem statement & high level design goals with project team
-
- Closed
-
-
FLUID-1343 Scope: Show & Tell of Problem statement & high level design goals with project team
-
- Closed
-