From Use Cases to Activity Cases

Lars Bækgaard

Publikation: Working paperForskning

Resumé

A use case defines a system in terms of its activity and its interaction with actors in its environment. Use cases can be used to capture requirements and to subdivide IT-systems into functionally coherent units. Information systems are activity systems that carry out important business activities. Many systems development methods recognize activity modeling as an important development activity. Use cases are based on a set of assumptions that makes them unsuitable for general activity modeling. The purpose of the paper is to analyze the strengths and weaknesses of use cases with respect to activity modeling. We introduce activity cases as a more general modeling tool that can be used to supplement use cases.
OriginalsprogEngelsk
StatusUdgivet - 2004

Fingerprint

Information systems
Industry

Citer dette

Bækgaard, L. (2004). From Use Cases to Activity Cases.
Bækgaard, Lars. / From Use Cases to Activity Cases. 2004.
@techreport{3c2dd6a09c2d11db8ed6000ea68e967b,
title = "From Use Cases to Activity Cases",
abstract = "A use case defines a system in terms of its activity and its interaction with actors in its environment. Use cases can be used to capture requirements and to subdivide IT-systems into functionally coherent units. Information systems are activity systems that carry out important business activities. Many systems development methods recognize activity modeling as an important development activity. Use cases are based on a set of assumptions that makes them unsuitable for general activity modeling. The purpose of the paper is to analyze the strengths and weaknesses of use cases with respect to activity modeling. We introduce activity cases as a more general modeling tool that can be used to supplement use cases.",
author = "Lars B{\ae}kgaard",
year = "2004",
language = "English",
type = "WorkingPaper",

}

From Use Cases to Activity Cases. / Bækgaard, Lars.

2004.

Publikation: Working paperForskning

TY - UNPB

T1 - From Use Cases to Activity Cases

AU - Bækgaard, Lars

PY - 2004

Y1 - 2004

N2 - A use case defines a system in terms of its activity and its interaction with actors in its environment. Use cases can be used to capture requirements and to subdivide IT-systems into functionally coherent units. Information systems are activity systems that carry out important business activities. Many systems development methods recognize activity modeling as an important development activity. Use cases are based on a set of assumptions that makes them unsuitable for general activity modeling. The purpose of the paper is to analyze the strengths and weaknesses of use cases with respect to activity modeling. We introduce activity cases as a more general modeling tool that can be used to supplement use cases.

AB - A use case defines a system in terms of its activity and its interaction with actors in its environment. Use cases can be used to capture requirements and to subdivide IT-systems into functionally coherent units. Information systems are activity systems that carry out important business activities. Many systems development methods recognize activity modeling as an important development activity. Use cases are based on a set of assumptions that makes them unsuitable for general activity modeling. The purpose of the paper is to analyze the strengths and weaknesses of use cases with respect to activity modeling. We introduce activity cases as a more general modeling tool that can be used to supplement use cases.

M3 - Working paper

BT - From Use Cases to Activity Cases

ER -