Knowledge-based system requirements

https://doi.org/10.1016/0950-7051(93)90007-GGet rights and content

Abstract

There is a growing demand both for greater ‘ease of use’ and ‘support in use’ as existing software packages are employed for more complex tasks. End users are faced with both the intricacies of the existing software, and the increasing complexity of the application-problem domains. As a result, there are important implications for the design of support systems for the professional user. The paper describes an approach to the identification of user requirements for knowledge-based front ends to existing software systems. The development of KBFEs is a software re-use technique that involves the integration of existing systems and services to provide specific users and user groups with a tailored solution. As a result, a KBFE enables a greater number and variety of users to have access to existing software and its functionality. This has implications for the requirements-elicitation methods employed. Investigations requirements that assume the use of existing software are described, and a framework for the structuring of the user requirements obtained is presented.

References (16)

  • S. Harker et al.

    Task anlysis and the definition of user needs

  • E.A. Edmonds et al.

    An architecture for knowledge-based front-ends

    Knowledge-Based Systems

    (1990)
  • E.A. Edmonds et al.

    Constructing front-ends to existing software systems

  • E.A. Edmonds et al.

    The re-use and integration of existing software: a central role for the intelligent user interface

  • B.S. Murray et al.

    SEPSOL: an experimental knowledge-based front end developed using the FOCUS architecture and tool-kit

  • C. Fischer et al.

    Using critics to empower users

  • I. McLoughlin et al.

    Technological Change at Work

    (1989)
  • D. Berry et al.

    Evaluating expert systems

    Expert Systems

    (1990)
There are more references available in the full text version of this article.

Cited by (6)

  • Incorporating personality in user interface design: A review

    2020, Personality and Individual Differences
    Citation Excerpt :

    In order to capture the mental model, firstly we have to define the users who will use the system. After they have been identified, we can define their requirements, which should consider the type of user, the tasks they perform, and the social and dynamic environment in which they interact (Jones et al., 1993). Nonetheless, it is hard for designers to create a unified user mental model that takes all user requirements into account.

  • The influence of analyst communication in IS projects

    2013, Journal of the Association for Information Systems

  • Research and design of knowledge service-oriented information system

    2010, 2010 2nd International Conference on Industrial and Information Systems, IIS 2010

  • Research on knowledge service-oriented e-Learning system

    2010, 2010 International Conference on Networking and Digital Society, ICNDS 2010

  • A contingency model for requirements development

    2007, Journal of the Association for Information Systems

  • Is it time to re-evaluate the connection between bounded rationality and requirements elicitation?

    2006, Association for Information Systems - 12th Americas Conference On Information Systems, AMCIS 2006
View full text
Copyright © 1993 Published by Elsevier B.V.