Diogenes, a process for identifying unintended consequences

A. Terry Bahill

Systems Engineering, 2012, vol. 15, issue 3, 287-306

Abstract: Individuals, companies, and even governments often create procedures, processes, or products that solve a particular problem, only to discover that their solution has created a second problem, worse than the first. These secondary problems are called unintended consequences. Searching for unintended consequences, as a part of the development process, will likely increase safety, reduce financial risk, and improve customer satisfaction. This paper contains the design for a new process, named Diogenes, that will help systems engineers identify unintended, but foreseeable, consequences of a new system that is being designed. It contains the required behavior (functions), use cases, design diagrams, the test procedure, validation, and verification for Diogenes. © 2012 Wiley Periodicals, Inc. Syst Eng

Date: 2012
References: View references in EconPapers View complete reference list from CitEc
Citations:

Downloads: (external link)
https://doi.org/10.1002/sys.20208

Related works:
This item may be available elsewhere in EconPapers: Search for items with the same title.

Export reference: BibTeX RIS (EndNote, ProCite, RefMan) HTML/Text

Persistent link: https://EconPapers.repec.org/RePEc:wly:syseng:v:15:y:2012:i:3:p:287-306

Access Statistics for this article

More articles in Systems Engineering from John Wiley & Sons
Bibliographic data for series maintained by Wiley Content Delivery ().