Diclib.com
Diccionario ChatGPT

Búsqueda en el diccionario Soluciones personalizadas

Ingrese una palabra o frase en cualquier idioma 👆

Idioma:

Traducción y análisis de palabras por inteligencia artificial ChatGPT

En esta página puede obtener un análisis detallado de una palabra o frase, producido utilizando la mejor tecnología de inteligencia artificial hasta la fecha:

cómo se usa la palabra
frecuencia de uso
se utiliza con más frecuencia en el habla oral o escrita
opciones de traducción
ejemplos de uso (varias frases con traducción)
etimología

Qué (quién) es user-obsequious - definición

NARRATIVE OF FORESEEABLE INTERACTIONS OF USER ROLES AND THE TECHNICAL SYSTEM, WHICH USUALLY INCLUDES COMPUTER HARDWARE AND SOFTWARE

User scenario; User scenarios

user-obsequious

<jargon> Emphatic form of user-friendly. Connotes a system so verbose, inflexible, and determinedly simple-minded that it is nearly unusable. "Design a system any fool can use and only a fool will want to use it." See WIMP, Macintrash. See also user-unctuous. [Jargon File] (1999-06-27)

user name

PERSON WHO USES A COMPUTER OR NETWORK SERVICE

Screen name (computing); User name; Username; Computer user; Account (computing); UserName; User Name; User-name; User-Name; Normal user; Screenname; User name policy; Internet pseudonym; User area; Computer logon; Computer users; My account; Screenames; Aol screen names; AOL screen names; Usernames; User Account; User Accounts; User accounts; User preferences; Changing Username; User names; Switching usernames; Switching user names; User account; User (system); Software users; Changing username; Login name; In-game name; Account name; Warmware

<operating system, security> (Or "logon") A unique name for each user of computer services which can be accessed by several persons. Users need to identify themselves for accounting, security, logging, and resource management. Usually a person must also enter a password in order to access a service. Once the user has logged on the operating system will often use a (short) user identifier, e.g. an integer, to refer to them rather than their user name. User names can usually be any short string of alphanumeric characters. Common choices are first name, initials, or some combination of first name, last name, initials and an arbitrary number. User names are often assigned by {system administrators} according to some local policy, or they may be chosen by the users themselves. User names are often also used as mailbox names in electronic mail addresses. (1997-03-16)

Power user

COMPUTER USER WHO USES MORE ADVANCED FEATURES OF COMPUTER HARDWARE, OPERATING SYSTEMS, PROGRAMS, OR WEB SITES THAN THE AVERAGE USER

Poweruser; Power users; Power User; Experienced computer user; Experienced user

A power user is a user of computers, software and other electronic devices, who uses advanced features of computer hardware, operating systems, programs, or websites which are not used by the average user. A power user might not have extensive technical knowledge of the systems they use but is rather characterized by competence or desire to make the most intensive use of computer programs or systems.

https://en.wikipedia.org/wiki/Power_user

Wikipedia

Scenario (computing)

In computing, a scenario (UK: , US: ; loaned from Italian scenario (pronounced [ʃeˈnaːrjo]), from Latin scena 'scene') is a narrative of foreseeable interactions of user roles (known in the Unified Modeling Language as 'actors') and the technical system, which usually includes computer hardware and software.

A scenario has a goal, which is usually functional. A scenario describes one way that a system is used, or is envisaged to be used, in the context of an activity in a defined time-frame. The time-frame for a scenario could be (for example) a single transaction; a business operation; a day or other period; or the whole operational life of a system. Similarly the scope of a scenario could be (for example) a single system or a piece of equipment; an equipped team or a department; or an entire organization.

Scenarios are frequently used as part of the system development process. They are typically produced by usability or marketing specialists, often working in concert with end users and developers. Scenarios are written in plain language, with minimal technical details, so that stakeholders (designers, usability specialists, programmers, engineers, managers, marketing specialists, etc.) can have a common ground to focus their discussions.

Increasingly, scenarios are used directly to define the wanted behaviour of software: replacing or supplementing traditional functional requirements. Scenarios are often defined in use cases, which document alternative and overlapping ways of reaching a goal.

https://en.wikipedia.org/wiki/Scenario (computing)