Stage-oe-small.jpg

Inproceedings3003: Unterschied zwischen den Versionen

Aus Aifbportal
Wechseln zu:Navigation, Suche
(Die Seite wurde neu angelegt: „{{Publikation Erster Autor |ErsterAutorNachname=Decker |ErsterAutorVorname=Michael }} {{Inproceedings |Referiert=True |Title= AIFB Lehre/Prüfung Personen Forsc…“)
 
Zeile 5: Zeile 5:
 
{{Inproceedings
 
{{Inproceedings
 
|Referiert=True
 
|Referiert=True
|Title= AIFB Lehre/Prüfung  Personen  Forschungsgruppen  Projekte  Berichte  Veranstaltungen  Stellenmarkt  Kooperationen  Kontakt  AIFB Home | Icon Fakultät für Wirtschaftswissenschaften | Logo Universität Karlsruhe | Icon English Version Publikationen > Publikation Michael Decker An UML Profile for the Modelling of mobile Business Processes and Workflows  
+
|Title=An UML Profile for the Modelling of mobile Business Processes and Workflows
 
|Year=2009
 
|Year=2009
 
|Month=September
 
|Month=September
|Address=Kingston upon Thames, U.K.
+
|Address=Kingston upon Thames, UK
 
|Booktitle=Proceedings of the Fifth International Mobile Multimedia Communications Conference (MobiMedia 09)
 
|Booktitle=Proceedings of the Fifth International Mobile Multimedia Communications Conference (MobiMedia 09)
 
}}
 
}}
 
{{Publikation Details
 
{{Publikation Details
|Abstract= Thanks to the progress in the ¯eld of mobile computing hardware (e.g. PDAs, smartphones, notebooks) and wireless data communication standards (e.g. UMTS, WLAN) in the recent years it is possible to provide access to information systems to mobile employees while they are working in the field or are on journeys. Further there are several technologies available to determine a mobile computer's location, e.g. the satellite-based Global Positioning System (GPS). In this article we look at mobile technologies from a process-centric viewpoint: we provide an extension to UML activity diagramms that enables the modeller to express statements concerning the locations where individual activities must or mustn't be performed. These statements are called location constraints. We discuss several classes of location constraints, e.g. static or dynamic location constraints and show that location constraints can also be used for UML usecase diagrams. Location constraints are motivated by several considerations: Since mobile computers have only a small display and restricted means for data input (e.g. no full keyboard) the user will appreciate it if only relevant data is provided by a mobile information system. But location constraints help also to mitigate specific security issues that are associated with the employment of mobile technologies: e.g. devices could get lost or stolen, so it is of advantage if there are location constraints that forbid the access to congfidential data at locations where it is not necessary or plausible to access that data.
+
|Abstract=Thanks to the progress in the ¯eld of mobile computing hardware (e.g. PDAs, smartphones, notebooks) and wireless data communication standards (e.g. UMTS, WLAN) in the recent years it is possible to provide access to information systems to mobile employees while they are working in the field or are on journeys. Further there are several technologies available to determine a mobile computer's location, e.g. the satellite-based Global Positioning System (GPS). In this article we look at mobile technologies from a process-centric viewpoint: we provide an extension to UML activity diagramms that enables the modeller to express statements concerning the locations where individual activities must or mustn't be performed. These statements are called location constraints. We discuss several classes of location constraints, e.g. static or dynamic location constraints and show that location constraints can also be used for UML usecase diagrams. Location constraints are motivated by several considerations: Since mobile computers have only a small display and restricted means for data input (e.g. no full keyboard) the user will appreciate it if only relevant data is provided by a mobile information system. But location constraints help also to mitigate specific security issues that are associated with the employment of mobile technologies: e.g. devices could get lost or stolen, so it is of advantage if there are location constraints that forbid the access to congfidential data at locations where it is not necessary or plausible to access that data.
 +
|Projekt=ModiFrame,
 
|Forschungsgruppe=Betriebliche Informations- und Kommunikationssysteme
 
|Forschungsgruppe=Betriebliche Informations- und Kommunikationssysteme
 
}}
 
}}
 
{{Forschungsgebiet Auswahl
 
{{Forschungsgebiet Auswahl
 
|Forschungsgebiet=Mobile Technologien
 
|Forschungsgebiet=Mobile Technologien
 +
}}
 +
{{Forschungsgebiet Auswahl
 +
|Forschungsgebiet=Geschäftsprozessmodellierung
 
}}
 
}}

Version vom 18. September 2009, 12:58 Uhr


An UML Profile for the Modelling of mobile Business Processes and Workflows


An UML Profile for the Modelling of mobile Business Processes and Workflows



Published: 2009 September

Buchtitel: Proceedings of the Fifth International Mobile Multimedia Communications Conference (MobiMedia 09)
Erscheinungsort: Kingston upon Thames, UK

Referierte Veröffentlichung

BibTeX

Kurzfassung
Thanks to the progress in the ¯eld of mobile computing hardware (e.g. PDAs, smartphones, notebooks) and wireless data communication standards (e.g. UMTS, WLAN) in the recent years it is possible to provide access to information systems to mobile employees while they are working in the field or are on journeys. Further there are several technologies available to determine a mobile computer's location, e.g. the satellite-based Global Positioning System (GPS). In this article we look at mobile technologies from a process-centric viewpoint: we provide an extension to UML activity diagramms that enables the modeller to express statements concerning the locations where individual activities must or mustn't be performed. These statements are called location constraints. We discuss several classes of location constraints, e.g. static or dynamic location constraints and show that location constraints can also be used for UML usecase diagrams. Location constraints are motivated by several considerations: Since mobile computers have only a small display and restricted means for data input (e.g. no full keyboard) the user will appreciate it if only relevant data is provided by a mobile information system. But location constraints help also to mitigate specific security issues that are associated with the employment of mobile technologies: e.g. devices could get lost or stolen, so it is of advantage if there are location constraints that forbid the access to congfidential data at locations where it is not necessary or plausible to access that data.


Projekt

ModiFrame



Forschungsgruppe

Betriebliche Informations- und Kommunikationssysteme„Betriebliche Informations- und Kommunikationssysteme“ befindet sich nicht in der Liste (Effiziente Algorithmen, Komplexitätsmanagement, Betriebliche Informationssysteme, Wissensmanagement, Angewandte Technisch-Kognitive Systeme, Information Service Engineering, Critical Information Infrastructures, Web Science und Wissensmanagement, Web Science, Ökonomie und Technologie der eOrganisation, ...) zulässiger Werte für das Attribut „Forschungsgruppe“.


Forschungsgebiet

Geschäftsprozessmodellierung, Mobile Technologien