Add to ORKGA 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
This paper presents our experiences of using use cases in real software projects. The projects, whic...
Use cases are promising vehicles for specifying requirements. However, obtaining well-organized use ...
Abstract. Use cases are commonly used as notation for capturing func-tional requirements through sce...
Use cases can be used to capture requirements and to subdivide IT-systems into functionally coherent...
Abstract. Correctly written use cases can be an important artifact for describing how a software sys...
case modeling is an accepted andwidespread technique to capture the business processes and requireme...
This paper is focused on the application of the well-known technique of use cases and especially on ...
Abstract. Use Cases have achieved wide use as a specification tool for observable behavior of system...
Abstract. We explore common problems that exist in the practice of use case modeling: lack of consis...
The paper begins by reviewing the application of use cases in the analysis and design phases of soft...
An alternate approach to use case textual specifications based on interaction modeling is presented....
This Master's thesis investigates how project teams apply Use Cases and what problems they encounter...
Although widely used, traditional use case modeling does not provide explicit means which could be e...
We seek to clarify the notion of use case and the related terminology by means of a specification wr...
Use case point (UCP) method has been proposed to esti-mate software development effort in early phas...
This paper presents our experiences of using use cases in real software projects. The projects, whic...
Use cases are promising vehicles for specifying requirements. However, obtaining well-organized use ...
Abstract. Use cases are commonly used as notation for capturing func-tional requirements through sce...
Use cases can be used to capture requirements and to subdivide IT-systems into functionally coherent...
Abstract. Correctly written use cases can be an important artifact for describing how a software sys...
case modeling is an accepted andwidespread technique to capture the business processes and requireme...
This paper is focused on the application of the well-known technique of use cases and especially on ...
Abstract. Use Cases have achieved wide use as a specification tool for observable behavior of system...
Abstract. We explore common problems that exist in the practice of use case modeling: lack of consis...
The paper begins by reviewing the application of use cases in the analysis and design phases of soft...
An alternate approach to use case textual specifications based on interaction modeling is presented....
This Master's thesis investigates how project teams apply Use Cases and what problems they encounter...
Although widely used, traditional use case modeling does not provide explicit means which could be e...
We seek to clarify the notion of use case and the related terminology by means of a specification wr...
Use case point (UCP) method has been proposed to esti-mate software development effort in early phas...
This paper presents our experiences of using use cases in real software projects. The projects, whic...
Use cases are promising vehicles for specifying requirements. However, obtaining well-organized use ...
Abstract. Use cases are commonly used as notation for capturing func-tional requirements through sce...