Writing effective use cases

By M. Ben-Menachem. SOEN, 2001

1,074 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Research Directions in Requirements Engineering (2007, background): “Notations Goals [18, 150] Policies [17] Scenarios [2, 31, 41] Enterprise models [45] Logics [47] Model checking [19, 48]”
Engineering and Managing Software Requirements (2005, methodology): “It is strongly related to the context in which it is conducted and specific characteristics of the project, organization, and environment [11].”
Agile modeling: effective practices for extreme programming and the unified process (2002, background): “For example: When you are exploring requirements, you may need to decide to develop a use case (Jacobson et. al. 1992; Cockburn 2001a) as you see in Figure 5.”
Eliciting security requirements with misuse cases (2000, methodology): “The lightweight approach embeds the description of misuse within a regular use - case template , such as the templates proposed by Kulak and Guiney [ 5 ] , Cockburn [ 3 ] , or RUP [ 29 ] , by extending them with a field called Threats .”