Writing Effective Use Cases
Model-Based Systems Engineering
Model-Based Systems Engineering
The hybrid process that combines traditional requirements and use cases
Systems Engineering
Quantitative methods for tradeoff analyses: Regular Papers
Systems Engineering
When are observable states necessary?
Systems Engineering
Ameliorating mental mistakes in tradeoff studies
Systems Engineering
Risk Modeling, Assessment, and Management
Risk Modeling, Assessment, and Management
Principles of complex systems for systems engineering
Systems Engineering
Attribute substitution in systems engineering
Systems Engineering
The design-methods comparison project
IEEE Transactions on Systems, Man, and Cybernetics, Part C: Applications and Reviews
Re-evaluating systems engineering concepts using systems thinking
IEEE Transactions on Systems, Man, and Cybernetics, Part C: Applications and Reviews
| Hi-index | 0.00 |
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 © 2012 Wiley Periodicals, Inc.