Abstract

Scenarios have been seen to be a useful way of identifying requirements in the software development domain. This paper discusses how scenarios may be helpful in identifying requirements in the software development process-modeling domain, and shows how multiple levels of scenarios may be useful. Based on some sample scenarios, the value of incorporating organizational goals into the process-modeling domain is described. Implications for process-modeling constructs and approaches are discussed.

Share

COinS