Article

Toward an architectural knowledge base for wireless service engineering

VTT Tech. Res. Centre of Finland, Oulu, Finland
IEEE Transactions on Software Engineering (Impact Factor: 2.59). 06/2005; DOI: 10.1109/TSE.2005.60
Source: IEEE Xplore

ABSTRACT Wireless services are software-based services that exploit distribution infrastructure embedded in our everyday life as various communication and computing technologies. Service architecture defines concepts and principles to develop and maintain services to obtain the quality issues with minimum cost and faster time-to-market. In order to boost the development of wireless services, more effective means of using existing architectural know-how and artifacts are required. Our contribution is the architectural knowledge base that introduces three cornerstones: the service taxonomy, reference service architecture, and basic services that alt together provide an efficient means of creating added value with wireless services. The service taxonomy assists in identifying the required functional and quality properties of services and the constraints of the underlying technology platforms. The reference architecture realizes the required properties, based on a selected set of architectural styles and patterns, and provides a skeleton upon which a new end-user service can be developed faster and more easily by using partially ready-made solutions, and furthermore, to keep the architectural knowledge base evolving at the same time. The architectural knowledge base has been validated in several research projects with industrial companies.

0 Bookmarks
 · 
65 Views
  • [Show abstract] [Hide abstract]
    ABSTRACT: The content of this paper addresses the issue of how to perform analysis of a cross domain reference architecture. The cross domain reference architecture is designed based on the domains requirements and features modeling. The definition of a cross domain reference architecture is based on well known concepts from software architecture description, service orientation and product line. We apply a method based on change scenarios to analyze variability at the architectural level. In order to handle complexity in analysis we propose categories of change scenarios to be derived from each problem domain and we provide informal guidelines for each step of the analysis method.
    Software Architecture, 5th European Conference, ECSA 2011, Essen, Germany, September 13 - 16, 2011. Companion Volume; 01/2011
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: This paper addresses the issues of distributed interactions in a simulation based medial training environment, where a team of doctors, nurses and assistants are trained for handling difficult delivery situations using simulations. A scripting language is proposed, using a metaphor of play, with which the timing and mapping issues in distributed presentations are covered. A generic architecture for the systems is also presented, which covers the timing and mapping issues of conducting such a script in a medical training environment. The difference between playing a medical training scenario and playing a multimedia entertainment scenario is discussed, based on which the future research and development are proposed. KeywordsDistribution-multi-agent-delivery simulator-medical training
    01/2010: pages 105-115;
  • [Show abstract] [Hide abstract]
    ABSTRACT: Modelling and evaluating quality properties of software is of high importance, especially when our every day life depends on the quality of services produced by systems and devices embedded into our surroundings. This paper contributes to the body of research in quality and model driven software engineering. It does so by introducing; (1) a quality aware software architecting approach and (2) a supporting tool chain. The novel approach with supporting tools enables the systematic development of high quality software by merging benefits of knowledge modelling and management, and model driven architecture design enhanced with domain-specific quality attributes. The whole design flow of software engineering is semi-automatic; specifying quality requirements, transforming quality requirements to architecture design, representing quality properties in architectural models, predicting quality fulfilment from architectural models, and finally, measuring quality aspects from implemented source code. The semi-automatic design flow is exemplified by the ongoing development of a secure middleware for peer-to-peer embedded systems.
    Information and Software Technology 01/2010; 52(6):577-601. · 1.52 Impact Factor

Full-text

View
10 Downloads
Available from
May 17, 2014