Enduser computing

1 / 16
About This Presentation
Title:

Enduser computing

Description:

... in which that system exists, prompting the emergence of changing requirements. ... through specification of key parameters (eg discount % for prompt payment) ... – PowerPoint PPT presentation

Number of Views:1271
Avg rating:3.0/5.0
Slides: 17
Provided by: suesto

less

Transcript and Presenter's Notes

Title: Enduser computing


1
End-User Computing (EUC)
2
End-User Computing (EUC)
  • The main objective in introducing this topic is
    to ensure that you understand the vital role that
    the concept of EUC can play in the strategic
    management of organisations if it is managed
    effectively, and the enormous damage it can do if
    it is not.
  • Traditionally, the only people who had direct
    contact with computers were the systems
    professionals (programmers, systems analysts
    etc.). The introduction of personal computers,
    terminals, networks, user-friendly software,
    databases has altered the position dramatically
    and has led to the growth of end-user computing.

3
What is EUC?
  • EUC Definition
  • EUC is an environment in which the user has free
    control and latitude over the process. He may use
    data that is interchanged through the mainframe
    of the MIS division, or he may create his own
    data. But he is in control, he is responsible for
    the product and the effectiveness of the use of
    the equipment.

4
End-User Development (EUD)
  • specifically the practice of users developing
    their own information systems, often but not
    always with the support of professional systems
    developers.
  • The practical involvement of end-users in
    application development necessitates the easy
    access to computing facilities. This may be
  • timesharing on a centralised mainframe
  • the use of stand alone personal computers
  • the use of personal computers which are connected
    to local area networks and mainframes.

5
End-User Development (EUD) (cont)
  • In addition to being provided with hardware and
    software, extra facilities are a necessary
    condition of successful end-user applications
    development. In particular
  • education and training on the use of software
    tools
  • assistance in the technical aspects of writing,
    testing, and debugging applications
  • availability of reference material
  • aid in accessing the corporate database

6
Why EUC?
  • The major advantages attributed to EUC include
  • (a) - enhanced productivity of professional and
    white-collar workers.
  • (b) - overcoming the shortage of DP
    professionals.
  • (c) - provision of user-friendly and responsive
    systems.
  • (d) - overcoming the implementation problems by
    transferring this process to the user.
  • System implementation has always been a major
    problem for developers. If users develop their
    own systems, clearly the implementation problem
    goes away.

7
Who Are The End Users?
  • Nonprogramming
  • Command level
  • End-user programmers (including senior management
    professionals)
  • Functional support personnel
  • End-user computing support personnel
  • DP Programmers
  • This list covers a very wide range of personnel
    carrying out a wide range of tasks throughout
    organisation - and the list continues to grow.

8
Why are they end-users?
  • When the large data processing type applications
    (payroll, inventory etc.) had been developed on
    large machines, a demand arose for Management
    Information. The users were potentially
    sophisticated professionals.
  • As stated above, the traditional IS department
    development time was too long, and there is a
    shortage of trained analysts and developers.
  • IS customers are often dissatisfied with the
    performance of delivered application systems
  • - these systems often take so long to develop
    that organisational and/or market requirements
    have completely changed by the time they are made
    available to the users.
  • - even though significant care is taken by
    trained analysts to ensure that user requirements
    are well defined, it is often the case that
    misunderstandings occur.
  • - the traditional methodologies generally do not
    allow requirements to be changed during
    development, whereas in practice, the systems
    requirements are often unstable, requiring a
    flexible approach to analysis and design.
  • - the very fact of the existence of a new system
    will change the environment in which that system
    exists, prompting the emergence of changing
    requirements. (Beynon-Davies et al, 1996)

9
Applications Suitable for End-User Development
  • Applications suitable for end-user development
    can be grouped into the following 5 categories
  • One time enquiries
  • Simple Reports
  • Minor Changes to Reports or Enquiries
  • Presentation of Data in Alternate Forms
  • 'What if' Analyses

10
Applications not suitable for end-user
development
  • data entry involving organisation files and
    databases (where the data must be validated for
    accuracy and reliability)
  • high volumes of transactions, requiring
    processing efficiency and multiple processing
    steps
  • use of 'traditional' computer languages designed
    for use by professional programmers, requiring
    detailed statement of processing procedures and
    controls
  • changing of data values in existing databases and
    files
  • applications spanning several departments or
    divisions in the organisation
  • applications requiring formal documentation
  • applications requiring a long development process
  • applications requiring detailed formal
    specifications.

11
Identify the Risks
  • Errors in analysis. Poorly trained End-users
    often are incapable of correctly analyzing data
    or systems (Davis, 1984). Resulting DS software
    is therefore often of questionable quality.
  • Lack of documentation. Most End-users are not
    trained in formal techniques of analysis and
    design. Documentation is often inadequate or even
    non-existent, making maintenance difficult and
    expensive. (Davis, 1984).
  • Faulty Model. Many Decision Support Systems (DSS)
    rely on corporate models developed by End-users
    for use with spreadsheets. Recent research has
    indicated (Panko, 1996) that as many as 38 of
    these spreadsheets may contain errors. As these
    systems are used by senior executives as aids in
    strategic decision-making, the consequences are
    not difficult to asses

12
Risks and Potential Control Mechanisms (after
Alavi and Weiss)
13
End-user Computing Tools
  • There are 2 major classes of end-user computing
    tools
  • application packages
  • fourth generation languages

14
Application Packages
  • These are pre-written software packages that are
    marketed commercially. They are available to
    support common business functions such as
    payroll, purchas ledger, sales ledger, production
    scheduling, inventory control etc. Many of the
    packages allow for some customisation through
    specification of key parameters (eg discount
    for prompt payment).

15
Fourth Generation Programming Languages
  • These languages allow users to develop their own
    computer programs and even link a series of them
    together to form a small system. These languages
    can be run on most types of computer.
  • There are many classes of fourth generation
    languages
  • query language/report writers
  • graphics languages
  • statistical analysis packages
  • decision support/financial modelling tools

16
References.
  • Alavi M, Nelson R. R., Weiss I. R. Strategies for
    End-User Computing An Integrative Framework.
    Journal of MIS, 1988
  • Beynon-Davies P., Mackay H, and Slack R. User
    Involvement in Information Systems Development
    The Problem of Finding the Right User.
    University of Glamorgan, 1996
  • Danberg A. End-User Computing MIS Answers the
    Call. Computerworld, 1986
  • Davis G. B. Caution User-Developed Systems Can
    Be Dangerous To Your Organisation. University of
    Minnesota, 1984
  • McLean E. R. End Users as Application Developers.
    MIS Quarterly, 1979
  • McClean E.R., Kappelman L.A. and Thompson J.P.
    End-User Computing Revisited Lattanze Research,
    1991
  • Panko R. R. Hitting the Wall Errors in
    Developing a Simple Spreadsheet Model.
    Proceedings of the 29th Hawaii International
    Conference on System Sciences, 1996
  • Rockart J. F., Flannery L. S. The Management of
    End-User Computing. ACM, 1983
Write a Comment
User Comments (0)