| Commit | Date | |
|---|---|---|
| 2016-05-24 10:36:14 | Tree | |
|
[r105]
by
eziomacmanus
CreateBehaviorView now successfully traces to activities of interest and creates behavior activities, haven't solved the CallBehaviorAction issues yet |
2016-05-19 12:11:43 | Tree |
|
[r104]
by
j-lamm
Trace to use case activity instead of use case (decision from FAS-behavior teleconference 2016-04-27) |
2016-04-30 09:38:14 | Tree |
|
[r103]
by
eziomacmanus
The button should create an empty Activity Diagram for each Behavior Activity now and create a <<trace>> relation from each Behavior Activity to their UseCase. I haven't been able to successfully trace Activities to their UseCases yet, so there still aren't any Behavior Activities created. |
2016-04-27 09:10:26 | Tree |
| 2016-04-14 14:12:23 | Tree | |
|
[r101]
by
j-lamm
first candidate of added requirements about positioning call behavior actions on activity diagrams |
2016-04-05 23:03:38 | Tree |
|
[r100]
by
eziomacmanus
added dummy button for behavior view creation and added md1803-classpath.xml for future reference |
2016-04-04 19:45:35 | Tree |
| 2016-03-31 00:15:14 | Tree | |
| 2016-03-30 23:32:46 | Tree | |
| 2016-03-30 21:54:56 | Tree |