User analysis

Last updated

In systems design, user analysis is the means by which scientists, engineers and technical writers determine the characteristics of users which will influence the development of software systems or other technological products. [1] During the process, developers in technical fields gather information about users of their products through interviews, focus groups and other forms of qualitative research. This is typically performed by forming use cases based upon the actual work flow tasks which the users will perform while using a given piece of technology. Such analyses are vital to the composition of software documentation.

Contents

Though very distinct, user analysis is related to task analysis.

Approach

When developing new technology or software, identifying the potential users of a system and their attributes is necessary in order to ensure that said technology or software will be more user friendly.

During this development, the user analysis is the basic research phase which takes place before actual drafting of the technology's technical documentation. [2] In this way, it's typically the first step of the document composition process. Such an analysis is intended to result in tacit knowledge, or a set of facts regarding the users' values, behaviors, knowledge of the documentation and product and motivation for using said documentation and product. [3] Revealing the tacit knowledge of users' activities, as opposed to the simple operations which a given technology can perform, is often referred to as an unspoken but understood trick of the trade for the technical communicators who conduct user analyses. [4]

A good technical communicator will perform a user analysis aimed at finding both what exactly a user needs to do, and what the user would do with the technology in question. Some experts in the field of user analysis have emphasized the importance of understanding the transfer of learning during this process, [5] though the concept itself is a controversial one. [6]

Interacting with users

User analysis is a process which calls for qualitative research. Because such research usually (though not always) centers around human subjects, the degree of formality and personalness is an issue. [7] In the modern era, users are often reached via virtual communities, which themselves often form around the use of a particular technology.

Statistical analysis of usage

Besides traditional way to interacting with users, analysis can be done with statistical analysis of the usage of log of users. With artificial techniques like machine learning, tremendous analysis results can be generated in parallel. [8]

Citations

  1. CS 3041 - User Analysis & Task Analysis, Worcester Polytechnic Institute. Tuesday, March 7, 2006.
  2. Thomas T. Barker, Writing Software Documentation Archived 2013-05-13 at the Wayback Machine , pg. 118. Part of the Allyn & Bacon Series in Technical Communication, 2nd ed. Upper Saddle River: Pearson Education, 2003. ISBN   0321103289
  3. Barker, pg. 123.
  4. Barbara Mirel, "Applied Constructivism for User Documentation: Alternatives to Conventional Task Orientation." Journal of Business and Technical Communication, vol. 12, #1, pg. 31. 1998.
  5. Barker, pg. 122.
  6. S. Helfenstein, Transfer: review, reconstruction, and resolution, 2005.
  7. Barker, pg. 133.
  8. H. Wang. Behavior analysis of low-literate users of a viral speech-based telephone service

Related Research Articles

Software documentation is written text or illustration that accompanies computer software or is embedded in the source code. The documentation either explains how the software operates or how to use it, and may mean different things to people in different roles.

Documentation is any communicable material that is used to describe, explain or instruct regarding some attributes of an object, system or procedure, such as its parts, assembly, installation, maintenance and use. Documentation can be provided on paper, online, or on digital or analog media, such as audio tape or CDs. Examples are user guides, white papers, online help, and quick-reference guides. Paper or hard-copy documentation has become less common. Documentation is often distributed via websites, software products, and other online applications.

Usability Capacity of a system to provide a condition for its users to perform the tasks safely, effectively, and efficiently while enjoying it

Usability can be described as the capacity of a system to provide a condition for its users to perform the tasks safely, effectively, and efficiently while enjoying the experience. In software engineering, usability is the degree to which a software can be used by specified consumers to achieve quantified objectives with effectiveness, efficiency, and satisfaction in a quantified context of use.

A technical writer is a professional information communicator whose task is to transfer information between two or more parties, through any medium that best facilitates the transfer and comprehension of the information. Technical writers research and create information through a variety of delivery media. Example types of information include online help, manuals, white papers, design specifications, project plans and software test plans. With the rise of e-learning, technical writers are increasingly becoming involved with creating online training material. Source data premisable if understood and tangible

Implementation is the realization of an application, or execution of a plan, idea, model, design, specification, standard, algorithm, or policy.

Requirements analysis Engineering process

In systems engineering and software engineering, requirements analysis focuses on the tasks that determine the needs or conditions to meet the new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating and managing software or system requirements.

Knowledge workers are workers whose main capital is knowledge. Examples include programmers, physicians, pharmacists, architects, engineers, scientists, design thinkers, public accountants, lawyers, and academics, whose job is to "think for a living".

Technical writing is writing or drafting technical communication used in technical and occupational fields, such as computer hardware and software, engineering, chemistry, aeronautics, robotics, finance, medical, consumer electronics, biotechnology, and forestry. Technical writing encompasses the largest sub-field in technical communication.

Technical communication is a means to convey scientific, engineering, or other technical information. Individuals in a variety of contexts and with varied professional credentials engage in technical communication. Some individuals are designated as technical communicators or technical writers. These individuals use a set of methods to research, document, and present technical processes or products. Technical communicators may put the information they capture into paper documents, web pages, computer-based training, digitally stored text, audio, video, and other media. The Society for Technical Communication defines the field as any form of communication that focuses on technical or specialized topics, communicates specifically by using technology or provides instructions on how to do something. More succinctly, the Institute of Scientific and Technical Communicators defines technical communication as factual communication, usually about products and services. The European Association for Technical Communication briefly defines technical communication as "the process of defining, creating and delivering information products for the safe, efficient and effective use of products ".

Audience analysis is a task that is often performed by technical writers in a project's early stages. It consists of assessing the audience to make sure the information provided to them is at the appropriate level. The audience is often referred to as the end-user, and all communications need to be targeted towards the defined audience. Defining an audience requires the consideration of many factors, such as age, culture and knowledge of the subject. After considering all the known factors, a profile of the intended audience can be created, allowing writers to write in a manner that is understood by the intended audience.

Task analysis is the analysis of how a task is accomplished, including a detailed description of both manual and mental activities, task and element durations, task frequency, task allocation, task complexity, environmental conditions, necessary clothing and equipment, and any other unique factors involved in or required for one or more people to perform a given task.

A subject-matter expert (SME) is a person who is an authority in a particular area or topic.

User interface design

User interface (UI) design or user interface engineering is the design of user interfaces for machines and software, such as computers, home appliances, mobile devices, and other electronic devices, with the focus on maximizing usability and the user experience. The goal of user interface design is to make the user's interaction as simple and efficient as possible, in terms of accomplishing user goals.

Software project management is an art and science of planning and leading software projects. It is a sub-discipline of project management in which software projects are planned, implemented, monitored and controlled.

Virtual engineering (VE) is defined as integrating geometric models and related engineering tools such as analysis, simulation, optimization, and decision making tools, etc., within a computer-generated environment that facilitates multidisciplinary collaborative product development. Virtual engineering shares many characteristics with software engineering, such as the ability to obtain many different results through different implementations.

Guided selling is a process that helps potential buyers of products or services to choose the product best fulfilling their needs and hopefully guides the buyer to buy. It also helps vendors of products to actively guide their customers to a buying decision and thus increases their conversion rate.

Work system has been used loosely in many areas. This article concerns its use in understanding IT-reliant systems in organizations. A notable use of the term occurred in 1977 in the first volume of MIS Quarterly in two articles by Bostrom and Heinen (1977). Later Sumner and Ryan (1994) used it to explain problems in the adoption of CASE. A number of socio-technical systems researchers such as Trist and Mumford also used the term occasionally, but seemed not to define it in detail. In contrast, the work system approach defines work system carefully and uses it as a basic analytical concept.

Technical translation is a type of specialized translation involving the translation of documents produced by technical writers, or more specifically, texts which relate to technological subject areas or texts which deal with the practical application of scientific and technological information. While the presence of specialized terminology is a feature of technical texts, specialized terminology alone is not sufficient for classifying a text as "technical" since numerous disciplines and subjects which are not "technical" possess what can be regarded as specialized terminology. Technical translation covers the translation of many kinds of specialized texts and requires a high level of subject knowledge and mastery of the relevant terminology and writing conventions.

View model

A view model or viewpoints framework in systems engineering, software engineering, and enterprise engineering is a framework which defines a coherent set of views to be used in the construction of a system architecture, software architecture, or enterprise architecture. A view is a representation of a whole system from the perspective of a related set of concerns.

SAP implementation refers to the name of the German company SAP SE, and is the whole of processes that defines a method to implement the SAP ERP enterprise resource planning software in an organization. The SAP implementation method described in this entry is a generic method and not a specific implementation method as such. It is based on best practices and case studies from various literature sources and presents a collection of processes and products that make up a complete implementation method to allow any organization to plan and execute the implementation of SAP software.