UXC Dictionary: Difference between revisions

From IDESG Wiki
Jump to navigation Jump to search
m (formatting fix)
No edit summary
 
(20 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=== UXC Dictionary ===
The UXC Dictionary defines words used in the UXCs Requirements and Supplemental Guidance and should be considered apart of the Guidance. <br>
<br>
The Dictionary refers to the NSTIC Document and terms that appear there and in our Dictionary. An annotated version of the NSTIC document noting terms in common with this Dictionary is located here. Page references below in definitions can be correlated here in this document as well.  https://www.idecosystem.org/idesgwiki/images/b/bc/Full_NSTIC_Strategy_Document_-_04152012_ARR_Annotated_for_user_centric.pdf
{| class="wikitable"
{| class="wikitable"
|-
|-
! Term !! Definition !! Notes !! Citations
! Term !! Definition !! Notes !! Citations
|-
|-
| '''User''' || Human. This does not include machines, algorithms, or other non-human agents or actors. ||  Our perspective is that this definition applies this way in any context in the IDESG framework. We suggest changing the use of USER for other meanings to another word. Note that the NSTIC document (see citation) names "user" as separate from devices and processes here on page 8: "Technology and processes for identification (establishing unique digital identities) and authentication (verifying the identity of a
| '''User'''   || Draft: Individual Human-Being. This does not include machines, algorithms, or other non-human agents or actors. Essential Equivalents:  Terms in the Common Semantic Domain found in the NSTIC Strategy include:
user, process, or device) are at the forefront of this Strategy " NSTIC Document: https://www.idecosystem.org/idesgwiki/images/b/bc/Full_NSTIC_Strategy_Document_-_04152012_ARR_Annotated_for_user_centric.pdf
* user
* user centric
* user centered
* user-centered
* human-centered
* human centered
* end-user
* end user
* individual user
* user-friendly ||  Our perspective is that this definition applies this way in any context in the IDESG framework. We suggest changing the use of USER for other meanings to another word. Note that the NSTIC document (see citation) names "user" as separate from devices and processes here on page 8: "Technology and processes for identification (establishing unique digital identities) and authentication (verifying the identity of a user, process, or device) are at the forefront of this Strategy "  
 
For defintions of user, user-centric and others look here: [[NSTIC Strategy]] and here: https://www.idecosystem.org/wiki/File:Full_NSTIC_Strategy_Document_-_04152012_ARR_Annotated_for_user_centric.pdf]
 
||  
||  
|-
|-
| '''User-centric''' || Example || Sample usage from NSTIC:
| '''User-centric''' || DRAFT: Systems, design and / or program processes that put the individual human being at the center of the activity. Rough Equivalents: user centric, user centered, user-centered, human-centered, human centered, end-user, end user, individual user, user-friendly.
*"The realization of this vision is the user-centric “Identity Ecosystem” described in this Strategy."P8
 
Sample usage from NSTIC Document Referenced above:
*"The realization of this vision is the user-centric “Identity Ecosystem” described in this Strategy." P8


* "Furthermore, the online environment today is not user-centric. Individuals tend to have little ability to manage their own personal information once it is released to service providers, and they often must calculate the tradeoffs among security, privacy, and gaining access to a service they desire." Page 12
* "Furthermore, the online environment today is not user-centric. Individuals tend to have little ability to manage their own personal information once it is released to service providers, and they often must calculate the tradeoffs among security, privacy, and gaining access to a service they desire." Page 12
Line 19: Line 39:
*"New privacy protections will shift the current model of application-specific collection of identity information to a distributed, user-centric model that supports an individual’s capability to manage an array of cyber identities and to manage and assert personal attributes without having to provide identifying data." Page 35
*"New privacy protections will shift the current model of application-specific collection of identity information to a distributed, user-centric model that supports an individual’s capability to manage an array of cyber identities and to manage and assert personal attributes without having to provide identifying data." Page 35
   
   
*Limit the retention of data to the time necessary for providing and administering the services to the individual end-user for which the data was collected, except as otherwise required by law; • Provide concise, meaningful, timely, and easy-to-understand notice to end-users on how providers collect, use, disseminate, and maintain personal information;" Page 36
*Limit the retention of data to the time necessary for providing and administering the services to the individual end-user for which the data was collected, except as otherwise required by law;  
|| The common semantic domain is roughly referred to here[http://as:https://en.wikipedia.org/wiki/User-centered_design as:https://en.wikipedia.org/wiki/User-centered_design]
:• Provide concise, meaningful, timely, and easy-to-understand end [[User Notice]] on how providers collect, use, disseminate, and maintain personal information;" Page 36  
 
The term "user-centric" design comes from the IDESG founding document the National Strategy for Trusted Identities in Cyberspace April 15, 2011. This term to be further described below exists in a common semantic domain with largely similar meanings in cyberspace that are central to the design of establishing trusted identities in cyberspace. This is the chief area of concern of the IDESG. <br>
 
||  == UCD models and approaches ==
 
For example, the user-centered design process can help software designers to fulfill the goal of a product engineered for their users. User requirements are considered right from the beginning and included into the whole product cycle. These requirements are
noted and refined through investigative methods including: ethnographic study, [[contextual inquiry]], prototype testing, [[usability testing]] and other methods. Generative methods may also be used including: card sorting, affinity diagramming and participatory design sessions. In addition, user requirements can be inferred by careful analysis of usable products similar to the product being designed.
 
* [[Cooperative design]]: involving designers and users on an equal footing. This is the Scandinavian tradition of design of IT artifacts and it has been evolving since 1970.<ref>Greenbaum&Kyng (eds): Design At Work - Cooperative design of Computer Systems, Lawrence Erlbaum 1991</ref>
* [[Participatory design]] (PD), a North American term for the same concept, inspired by Cooperative Design, focusing on the participation of users. Since 1990, there has been a bi-annual Participatory Design Conference.<ref>Schuler&Namioka: Participatory Design, Lawrence Erlbaum 1993 and chapter 11 in Helander’s Handbook of HCI, Elsevier 1997</ref>
* [[Contextual design]], “customer-centered design” in the actual context, including some ideas from Participatory design<ref>Beyer&Holtzblatt, ''Contextual Design'', Kaufmann 1998</ref>
 
All these approaches follow the ISO standard [http://www.iso.org/iso/catalogue_detail.htm?csnumber=52075 Human-centred design for interactive systems (ISO 9241-210, 2010)].
 
The ISO standard describes 6 key principles that will ensure a design is user centered:
 
# The design is based upon an explicit understanding of users, tasks and environments.
# Users are involved throughout design and development.
# The design is driven and refined by user-centered evaluation.
# The process is iterative.
# The design addresses the whole user experience.
# The design team includes multidisciplinary skills and perspectives.</br>
</br>
 
To Compare the Definitions in this domain look here [[User-centric:] https://www.idecosystem.org/idesgwiki/images/0/0e/User-centric_design_-_Yahoo_Search_Results.pdf]]
 
|| The common semantic domain is roughly referred to here at: https://en.wikipedia.org/wiki/User-centered_design
|-
| '''Entity / Entities''' || Any organization providing or using identity services. || Citation || Notes
|-
| '''System''' || An entity's system a user is interacting with at a particular time. || Citation || Notes
|-
|-
| '''Entity / Entities''' || Any organization providing identity services. || Example || Example
| '''Anonymous''' || An interaction designed such that the data collected is not sufficient to infer the identity of the user involved nor is such data sufficient to permit an entity to associate multiple interactions with a user or to determine patterns of behavior with a user. || Citation || Notes
|-
|-
| '''System''' || An entity's system a user is interacting with at a particular time. || Example || Example
| '''Third Parties''' || Definition || Citation || Notes: Regarding supplemental on Usable 3: research systems that display entities on a page or system. consider burden on user vs. accessibility of entities list
|-
|-
| '''Anonymous''' || An interaction designed such that the data collected is not sufficient to infer the identity of the user involved nor is such data sufficient to permit an entity to associate multiple interactions with a user or to determine patterns of behavior with a user. || Example || Example
| '''Third Party Tracking''' || Definition: The IDESG needs to define what constitutes an interaction and what 3rd party tracking is. Currently undefined. || NOTE: revisit as necessary per Privacy and other groups def.s  || Notes
|-
|-
| '''Third Parties''' || Example || re: supplemental on Usable 3: research systems that display entities on a page or system. consider burden on user vs. accessibility of entities list) || Example
| '''Pseudonymous''' || An interaction designed such that the data collected is not sufficient to allow the entity to infer the user involved but which does permit an entity to associate multiple interactions with the user’s claimed identity. || Citation || Notes
|-
|-
| '''Pseudonymous''' || An interaction designed such that the data collected is not sufficient to allow the entity to infer the user involved but which does permit an entity to associate multiple interactions with the user’s claimed identity. || Example || Example
| '''Verified identity''' || Definition || Citation || Notes
|-
|-
| '''Verified identity''' || Example || Example || Example
| '''Action''' || Might include providing information or a digital signature. || Citation || Notes
|-
|-
| Example || Example || Example || Example
| '''Pathway''' || A clear route or routes of events and / or actions leading to a defined result. || Citation || Notes
|-
|-
| Example || Example || Example || Example
| '''Reasonable Accommodation''' || Definition || Citation || Notes
|-
|-
| Example || Example || Example || Example
| '''Feasible''' (per Req 5) || Definition || Citation || Notes
|-
|-
| Example || Example || Example || Example
| '''Interaction''' || TBD: define what an interaction is in context to UXC reqs || Citation || Notes
|-
|-
| Example || Example || Example || Example
| '''Transparency''' || Definition || Citation || Notes
|-
|-
| Example || Example || Example || Example
| '''Implied Consent''' || Definition || Citation || Notes
|-
|-
| Example || Example || Example || Example
| '''Express Consent''' || Definition || Citation || Notes
|}
|}
[[Category:User Experience]]
[[Category:Glossary]]

Latest revision as of 16:21, 27 May 2020

UXC Dictionary

The UXC Dictionary defines words used in the UXCs Requirements and Supplemental Guidance and should be considered apart of the Guidance.

The Dictionary refers to the NSTIC Document and terms that appear there and in our Dictionary. An annotated version of the NSTIC document noting terms in common with this Dictionary is located here. Page references below in definitions can be correlated here in this document as well. https://www.idecosystem.org/idesgwiki/images/b/bc/Full_NSTIC_Strategy_Document_-_04152012_ARR_Annotated_for_user_centric.pdf

Term Definition Notes Citations
User Draft: Individual Human-Being. This does not include machines, algorithms, or other non-human agents or actors. Essential Equivalents: Terms in the Common Semantic Domain found in the NSTIC Strategy include:
  • user
  • user centric
  • user centered
  • user-centered
  • human-centered
  • human centered
  • end-user
  • end user
  • individual user
  • user-friendly || Our perspective is that this definition applies this way in any context in the IDESG framework. We suggest changing the use of USER for other meanings to another word. Note that the NSTIC document (see citation) names "user" as separate from devices and processes here on page 8: "Technology and processes for identification (establishing unique digital identities) and authentication (verifying the identity of a user, process, or device) are at the forefront of this Strategy "

For defintions of user, user-centric and others look here: NSTIC Strategy and here: https://www.idecosystem.org/wiki/File:Full_NSTIC_Strategy_Document_-_04152012_ARR_Annotated_for_user_centric.pdf]

User-centric DRAFT: Systems, design and / or program processes that put the individual human being at the center of the activity. Rough Equivalents: user centric, user centered, user-centered, human-centered, human centered, end-user, end user, individual user, user-friendly.

Sample usage from NSTIC Document Referenced above:

  • "The realization of this vision is the user-centric “Identity Ecosystem” described in this Strategy." P8
  • "Furthermore, the online environment today is not user-centric. Individuals tend to have little ability to manage their own personal information once it is released to service providers, and they often must calculate the tradeoffs among security, privacy, and gaining access to a service they desire." Page 12
  • "It also reflects the user-centric nature of the Identity Ecosystem, which provides greater transparency, privacy protection, flexibility,and choice to the individual." Page 21
  • "New privacy protections will shift the current model of application-specific collection of identity information to a distributed, user-centric model that supports an individual’s capability to manage an array of cyber identities and to manage and assert personal attributes without having to provide identifying data." Page 29
  • "Lack of secure, convenient, user-friendly options for authentication and identification;" Page15
  • "New privacy protections will shift the current model of application-specific collection of identity information to a distributed, user-centric model that supports an individual’s capability to manage an array of cyber identities and to manage and assert personal attributes without having to provide identifying data." Page 35
  • Limit the retention of data to the time necessary for providing and administering the services to the individual end-user for which the data was collected, except as otherwise required by law;
• Provide concise, meaningful, timely, and easy-to-understand end User Notice on how providers collect, use, disseminate, and maintain personal information;" Page 36

The term "user-centric" design comes from the IDESG founding document the National Strategy for Trusted Identities in Cyberspace April 15, 2011. This term to be further described below exists in a common semantic domain with largely similar meanings in cyberspace that are central to the design of establishing trusted identities in cyberspace. This is the chief area of concern of the IDESG.

== UCD models and approaches ==

For example, the user-centered design process can help software designers to fulfill the goal of a product engineered for their users. User requirements are considered right from the beginning and included into the whole product cycle. These requirements are noted and refined through investigative methods including: ethnographic study, contextual inquiry, prototype testing, usability testing and other methods. Generative methods may also be used including: card sorting, affinity diagramming and participatory design sessions. In addition, user requirements can be inferred by careful analysis of usable products similar to the product being designed.

  • Cooperative design: involving designers and users on an equal footing. This is the Scandinavian tradition of design of IT artifacts and it has been evolving since 1970.<ref>Greenbaum&Kyng (eds): Design At Work - Cooperative design of Computer Systems, Lawrence Erlbaum 1991</ref>
  • Participatory design (PD), a North American term for the same concept, inspired by Cooperative Design, focusing on the participation of users. Since 1990, there has been a bi-annual Participatory Design Conference.<ref>Schuler&Namioka: Participatory Design, Lawrence Erlbaum 1993 and chapter 11 in Helander’s Handbook of HCI, Elsevier 1997</ref>
  • Contextual design, “customer-centered design” in the actual context, including some ideas from Participatory design<ref>Beyer&Holtzblatt, Contextual Design, Kaufmann 1998</ref>

All these approaches follow the ISO standard Human-centred design for interactive systems (ISO 9241-210, 2010).

The ISO standard describes 6 key principles that will ensure a design is user centered:

  1. The design is based upon an explicit understanding of users, tasks and environments.
  2. Users are involved throughout design and development.
  3. The design is driven and refined by user-centered evaluation.
  4. The process is iterative.
  5. The design addresses the whole user experience.
  6. The design team includes multidisciplinary skills and perspectives.


To Compare the Definitions in this domain look here [[User-centric:] https://www.idecosystem.org/idesgwiki/images/0/0e/User-centric_design_-_Yahoo_Search_Results.pdf]]

The common semantic domain is roughly referred to here at: https://en.wikipedia.org/wiki/User-centered_design
Entity / Entities Any organization providing or using identity services. Citation Notes
System An entity's system a user is interacting with at a particular time. Citation Notes
Anonymous An interaction designed such that the data collected is not sufficient to infer the identity of the user involved nor is such data sufficient to permit an entity to associate multiple interactions with a user or to determine patterns of behavior with a user. Citation Notes
Third Parties Definition Citation Notes: Regarding supplemental on Usable 3: research systems that display entities on a page or system. consider burden on user vs. accessibility of entities list
Third Party Tracking Definition: The IDESG needs to define what constitutes an interaction and what 3rd party tracking is. Currently undefined. NOTE: revisit as necessary per Privacy and other groups def.s Notes
Pseudonymous An interaction designed such that the data collected is not sufficient to allow the entity to infer the user involved but which does permit an entity to associate multiple interactions with the user’s claimed identity. Citation Notes
Verified identity Definition Citation Notes
Action Might include providing information or a digital signature. Citation Notes
Pathway A clear route or routes of events and / or actions leading to a defined result. Citation Notes
Reasonable Accommodation Definition Citation Notes
Feasible (per Req 5) Definition Citation Notes
Interaction TBD: define what an interaction is in context to UXC reqs Citation Notes
Transparency Definition Citation Notes
Implied Consent Definition Citation Notes
Express Consent Definition Citation Notes
Retrieved from "https://wiki.idesg.org/index.php?title=UXC_Dictionary&oldid=14709"