| Transformation of UML models for service-oriented software architectures (2005) | |||||||||||
Abstract | |||||||||||
| Transformation UML Models for Service Oriented Software Architectures Ricardo Machado Fernandes Paula Monteiro Helena Rodrigues Dep Sistemas Informa Dep Inform tica Escola Engenharia Universidade Minho Braga Portugal Abstract The main aim this paper present how transform user requirements models into software architecture for mobile applications The technique called SRS essentially based the mapping UML use case diagrams into UML object diagrams UML sequence activity and state diagrams and other artifacts can also considered within the transformation decisions The applicability this technique illustrated presenting some results from government mobile application The development mobile applications typically follow service oriented approach service software entity running one more machines and providing particular type function priori unknown clients These services must communicate with each other whose combination makes service oriented architecture The communication can involve either simple data passing could involve two more services coordinating some activity Some means connecting services each other needed workflow critical part making services effective When those services react changes user context application are context aware For mobile applications the definition the underlying service oriented software architecture must consider the services themselves user requirements well the mobile operators entry points and the final clients interfaces and use them characteriz. The main aim of this paper is to present how to transform user requirements models into a software architecture for mobile applications. The technique (called "4SRS") is essentially based on the mapping of UML use case diagrams into UML object diagrams. UML sequence, activity, and state diagrams and other artifacts can also be considered within the transformation decisions. The applicability of this technique is illustrated by presenting some results from an e-government mobile application. The development of mobile applications typically follow a service-oriented approach. A service is a software entity running on one or more machines and providing a particular type of function to a priori unknown clients. These services must communicate with each other, whose combination makes up a service-oriented architecture. The communication can involve either simple data passing or it could involve two or more services coordinating some activity. Some means of connecting services to each other is needed, so workflow is a critical part of making services effective. When those services react to changes on user context, application are context-aware. For mobile applications, the definition of the underlying service-oriented software architecture must consider the services themselves as user requirements, as well as the mobile operators entry-points and the final clients interfaces, and use them to characterize the platform.. USE-ME.GOV - IST-2002-002294 ; Fundação para a Ciência e a Tecnologia - METHODES (POSI/CHS/37334/2001), STACOS (POSI/CHS/48875/2002). | |||||||||||
Publication details | |||||||||||
| |||||||||||
Cited publications (2) | |||||||||||
| |||||||||||