AnalysisForUseCases
Timothy Lethbridge edited this page Jun 14, 2016
·
2 revisions
General
- Wiki Home
- FAQ Frequently asked questions
- Examples
- Presentations
- PhilosophyAndVision
- Best practices for using Umple
- Publications and theses
- Tutorials
- Installing Eclipse plugin
Developers
- Developer Setup
- UmpleOnline Setup
- Contribution Process
- Architecture
- Cheat sheet
- Umpleonline manual tests
- Planned development
- DraftManualPages
Server maintenance
External
Other
Clone this wiki locally
Analysis for Use Cases
Introduction
This page is to present samples and analysis of the feature to add use cases to Umple. This is the first phase of implementing various different requirements capabilities.
Search for relevant issues in the issues list, where this topic may be covered too.
Phase 1: Samples of syntax that we intend to allow and metamodel elements
Declaration of an actor
actor regularUser;
Umple metamodel for representing actors
class Actor {
name;
}
Declaration of the existence of a use case. id can be any identifier to be used to describe the use case
usecase usecaseid {}
Declaration in a class, interface, trait, etc.
class X {
implements usecaseid;
}
Declaration of the relationship between a use case and an actor
usecase usecaseid {
doneby regularUser;
}
Metamodel entries for use cases
class UseCase {
name;
* -- * Actor;
* -- * UmpleClassifier implementingUseCases;
}