Requirements Process Patterns Via Events/Use Cases

Suzanne Robertson
The Atlantic Systems Guild Ltd
11 St MaryUs Terrace
London W2 1SU
Phone: 0171 262 3395
email:100065.2304@compuserve.com

Abstract 

This paper illustrates how event/use case modelling is used to
identify, define and access requirements process patterns. Event/use
case partitioning is widely used as a way of breaking a system into
manageable, business-related chunks.  Each event/use case is then the
subject of detailed analysis, design and implem entation. This paper
illustrates how event/use case modelling can also be used as the basis
for identifying and defining requirements process patterns. A proc ess
pattern is also used to identify the appropriate requirements data
pattern.  Given a book of requirements process patterns, each project
uses context analysis and event/use case partitioning as a way of
accessing relevant patterns.

Note: the terms event (reference McMenamin and Palmer T84) and Ruse
caseS (Jacobson T92) to mean the same thing. I acknowledge that there
are some differences in application and notation, but for the purpose
of identifying and using proc ess patterns the models are
interchangeable.

Keywords: requirements process pattern, event, use case, requirements
analysis.

Copyright ) 1996 The Atlantic Systems Guild Ltd. All rights
reserved. No part of this material may be reprinted, reproduced or
utilised in any form without permission in writing