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
|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:
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 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.
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:
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|
|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|
|Feasible (per Req 5)||Definition||Citation||Notes|
|Interaction||TBD: define what an interaction is in context to UXC reqs||Citation||Notes|