April 2008
·
11 Reads
·
4 Citations
Insight
This page lists works of an author who doesn't have a ResearchGate profile or hasn't added the works to their profile yet. It is automatically generated from public (personal) data to further our legitimate goal of comprehensive and accurate scientific recordkeeping. If you are this author and want this page removed, please let us know.
April 2008
·
11 Reads
·
4 Citations
Insight
September 2007
·
574 Reads
·
167 Citations
The focus of Software for Dependable Systems is a set of fundamental principles that underlie software system dependability and that suggest a different approach to the development and assessment of dependable software. Unfortunately, it is difficult to assess the dependability of software. The field of software engineering suffers from a pervasive lack of evidence about the incidence and severity of software failures; about the dependability of existing software systems; about the efficacy of existing and proposed development methods; about the benefits of certification schemes; and so on. There are many anecdotal reports, which-although often useful for indicating areas of concern or highlighting promising avenues of research-do little to establish a sound and complete basis for making policy decisions regarding dependability. The committee regards claims of extraordinary dependability that are sometimes made on this basis for the most critical of systems as unsubstantiated, and perhaps irresponsible. This difficulty regarding the lack of evidence for system dependability leads to two conclusions: (1) that better evidence is needed, so that approaches aimed at improving the dependability of software can be objectively assessed, and (2) that, for now, the pursuit of dependability in software systems should focus on the construction and evaluation of evidence. The committee also recognized the importance of adopting the practices that are already known and used by the best developers; this report gives a sample of such practices. Some of these (such as systematic configuration management and automated regression testing) are relatively easy to adopt; others (such as constructing hazard analyses and threat models, exploiting formal notations when appropriate, and applying static analysis to code) will require new training for many developers. However valuable, though, these practices are in themselves no silver bullet, and new techniques and methods will be required in order to build future software systems to the level of dependability that will be required. © 2007 by the National Academy of Sciences. All rights reserved.
July 2007
·
308 Reads
·
75 Citations
Privacy is a growing concern in the United States and around the world. The spread of the Internet and the seemingly boundaryless options for collecting, saving, sharing, and comparing information trigger consumer worries. Online practices of business and government agencies may present new ways to compromise privacy, and e-commerce and technologies that make a wide range of personal information available to anyone with a Web browser only begin to hint at the possibilities for inappropriate or unwarranted intrusion into our personal lives. Engaging Privacy and Information Technology in a Digital Age presents a comprehensive and multidisciplinary examination of privacy in the information age. It explores such important concepts as how the threats to privacy evolving, how can privacy be protected and how society can balance the interests of individuals, businesses and government in ways that promote privacy reasonably and effectively? This book seeks to raise awareness of the web of connectedness among the actions one takes and the privacy policies that are enacted, and provides a variety of tools and concepts with which debates over privacy can be more fruitfully engaged. Engaging Privacy and Information Technology in a Digital Age focuses on three major components affecting notions, perceptions, and expectations of privacy: technological change, societal shifts, and circumstantial discontinuities. This book will be of special interest to anyone interested in understanding why privacy issues are often so intractable. © 2007 by the National Academy of Sciences. All rights reserved.
January 2007
·
6 Reads
·
3 Citations
... Articulating clear and complete requirements is a known challenge in software engineering [37,44,46], and poor requirements often cause software failures [42]. This difficulty is amplified by the unpredictable nature of LLMs, which complicates controlling outputs [12,15]. ...
September 2007
... Government Regulation: Governmental role is crucial in crafting and enforcing adaptable privacy laws, like the EU's GDPR, in response to evolving tech [100]. ...
July 2007
... • In the United States, the "DO-178C Software Considerations in Airborne Systems and Equipment Certification" document and the "MIL-STD-882E Standard Practice for System Safety" military standard are commonly used references. • According to a report completed for U.S. National Academies (Jackson et al., 2007), certification of the dependability of software-based systems is considered to typically rely more on assessments of the development processes than on properties of the system itself, due to the difficulty of assessing the dependability of software. ...
April 2008
Insight
... No other hazardous industry would deploy technology in this manner, putting the burden of proof on the user to prove that a device is hazardous, rather than on the vendor to prove that it is not. 22 If one takes a systems approach to designing a medical device in a user-centered manner, then the device would match the way practitioners think, the way they operate in their daily Volume , . : November practice, and the limitations of their environment and working conditions. ...
January 2007