2008
DOI: 10.1007/978-3-540-92698-6_11
|View full text |Cite
|
Sign up to set email alerts
|

Getting SW Engineers on Board: Task Modelling with Activity Diagrams

Abstract: Abstract. This paper argues for a transfer of knowledge and experience gained in task-based design to Software Engineering. A transformation of task models into activity diagrams as part of UML is proposed. By using familiar notations, software engineers might be encouraged to accept task modelling and to pay more attention to users and their tasks. Generally, different presentations of a model can help to increase its acceptance by various stakeholders. The presented approach allows both the visualization of … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2012
2012
2016
2016

Publication Types

Select...
5
2

Relationship

1
6

Authors

Journals

citations
Cited by 14 publications
(6 citation statements)
references
References 12 publications
0
6
0
Order By: Relevance
“…Alternatives to tree visualizations of CTT are proposed in [4] and [14]. Former approach uses activity diagrams from the Unified Modeling Language (UML) specification, whereas in the latter case tasks are expressed using the Business Process Modeling Language (BPMN) notion.…”
Section: Task Models -Developmentmentioning
confidence: 99%
“…Alternatives to tree visualizations of CTT are proposed in [4] and [14]. Former approach uses activity diagrams from the Unified Modeling Language (UML) specification, whereas in the latter case tasks are expressed using the Business Process Modeling Language (BPMN) notion.…”
Section: Task Models -Developmentmentioning
confidence: 99%
“…To realize that, we employ the UML activity diagram notation (UML, 2011). The authors in (Brüning, 2008) tackle the idea of bridging the gap between software engineering domain and task models by providing a valid transformation from task models to activity diagrams. A corresponding transformation rule for every temporal operator in CTT to an activity fragment is proposed.…”
Section: Execution Constraints Visualizationmentioning
confidence: 99%
“…Then for a given task, two types of constraints can be assigned. First, we have the temporal constraints which express the order of execution of this action relatively to the other ones and which are represented following the rules in (Brüning, 2008). Secondly, we have the environmental constraints related to this action's execution and which we suggest to manifest using notes enabling the assignment of preconditions and effects in a formal way.…”
Section: Execution Constraints Visualizationmentioning
confidence: 99%
“…[23,8] propose some informal transformations between activity diagrams and task model. But transformations are more commonly used to produce code.…”
Section: Transformations Proposed In Hcimentioning
confidence: 99%