IEEE Software · 2003 · 329 citations · 10 references
Software MaintenanceSafety CaseEngineeringInformation SecuritySafety ScienceLawSoftware EngineeringTechnology LawSoftware AnalysisCritical ComputingSafety-critical SystemReliability EngineeringSystems EngineeringNonfunctional RequirementsSoftware System SafetyDesignUse CaseMisuse CaseSoftware DesignSoftware TestingMisuse CasesSocial Engineering (Security)Case AnalysisSystem Software
Humans have analyzed negative scenarios ever since they first sat around Ice Age campfires debating the dangers of catching a woolly rhinoceros: "What if it turns and charges us before it falls into the pit?" A more recent scenario is "What if the hackers launch a denial-of-service attack?" Modern systems engineers can employ a misuse case, the negative form of a use case, to document and analyze such scenarios. A misuse case is simply a use case from the point of view of an actor hostile to the system under design. Misuse cases have many possible applications and interact with use cases in interesting and helpful ways. The paper discusses the elicitation of safety requirements from failure cases and considers the interplay of design, functional, and nonfunctional requirements.
10
Mordechai Ben-Menachem · ACM SIGSOFT Software Engineering Notes · 2001 · 1K citations
Eliciting security requirements by misuse cases
Guttorm Sindre, Andreas L. Opdahl · 2002 · 328 citations
Templates for Misuse Case Description
Guttorm Sindre, Andreas L. Opdahl · 2001 · 143 citations
Deriving safety requirements using scenarios
K. Allenby, Tim Kelly · 2002 · 130 citations