Digital Woes: Why We Should Not Depend on Software

Authors:
Lauren Ruth Wiener
Affiliations:
-
Venue:
Digital Woes: Why We Should Not Depend on Software
Year:
1993

Citing 0
Cited 13

Illustrative risks to the public in the use of computer systems and related technology

ACM SIGSOFT Software Engineering Notes
Enumerating the risks of reengineered processes

CSC '96 Proceedings of the 1996 ACM 24th annual conference on Computer science
Inside risks: a risks-related bookshelf

Communications of the ACM
IC Failure Analysis: Magic, Mystery, and Science

IEEE Design & Test
Information Systems That also Project into the Future

DNIS '02 Proceedings of the Second International Workshop on Databases in Networked Information Systems
Assessing the risks of IT-enabled jobs

Managing the human side of information technology
Executive information systems use in organisational contexts: an explanatory user behaviour testing

Information management
Grounding a new information technology implementation framework in behavioral science: a systematic analysis of the literature on IT use

Journal of Biomedical Informatics
Factors affecting engineers' acceptance of asynchronous e-learning systems in high-tech companies

Information and Management
A survey of linguistic structures for application-level fault tolerance

ACM Computing Surveys (CSUR)
Free and open-source software: Opening and democratising e-government's black box

Information Polity
A technological acceptance of e-learning tools used in practical and laboratory teaching, according to the European higher education area

Behaviour & Information Technology
Explaining the influence of user personality on the evaluation of it usage drivers and it usage consequences

Proceedings of the 49th SIGMIS annual conference on Computer personnel research

Quantified Score

Hi-index	0.02

Visualization

Abstract

From the Publisher:The book you are now holding presents, in clear and sometimes entertaining language, a basic background useful for understanding software. It explains why we should be cautious about introducing software into systems, and suggests criteria we might use to evaluate proposals to do so.