Volume 1, Issue 4

Seamless Service Delivery Solution for mHealth Application (pp. 131-143)

Boškovic, D., Kovacevic, M., Ilic,T., Arges, D.,Wisz, M.
ICT opens up many new opportunities for higher-value products and services, of which Personal Health System (PHS) is just one of the possibilities. PHS for remote management of diseases, treatment and rehabilitation, outside hospitals and care centers is based on closed-loop approaches and integrates wearable, portable or implantable devices into a subsystem coupled with appropriate platforms and services. This article discusses such subsystem that we called mHealth Console and puts an accent on gathering and analysis, interpretation and use of the multiparametric data, in conjunction with established or newly created medical knowledge, for shared patient-doctor decision support systems. After discussing business motivation for remote provisioning of healthcare services in Section1, the paper continues by describing a framework for ICT deployment on Section 2. The proposed service delivery architecture is based on Over the Top (OTT) delivery principles and enables perspective mHealth provider to reach service users (e.g. patients, health insurance, health providers, employers, pharmacies etc ) irrespective of their locations and type of physical connectivity in that location. The Section 3 continues by offering a detailed functional architecture for mHealth Console and Portal, description of signalling message flows for different SIP and DLNA based use cases. The article concludes that mHealth system is a powerful ICT based solution that process comprehensive sensor data, both environmental and behavioral, and is critical component enabling provision of monitoring and rehabilitation services to the patients. The features of the proposed solution such as independent communication session initiation, seamless and automated exchange of stored and real time information and use of devices of affordable price, makes the proposed architecture a viable solution for seamless delivery of mHealth services.

Print Email

Locawe – Developing Platform for Mobile Ubiquitous Services (pp. 145-153)

Luimula, M., Markkula, J., Kuutti, K.
Development of new advanced mobile ubiquitous multimedia services presents number of challenges which needs to be addressed in service platform design. We have been developing our Locawe platform for this goal in several research projects using systematic develop-evaluate design cycle as a research approach. During the development we have build an adaptive architecture, which we have learned to be a key requirement for a usable and sustainable service platform. The result of a number of field studies, including various field experiments and industrial pilots, have verified our solutions and proven our approach to be successful. Our Locawe platform has shown to be applicable and useful for developing different types of mobile ubiquitous services that utilise the latest technological possibilities.

Print Email

Requirements-Based Testing Process in Practice (pp. 155-161)

Skokovic, P., Rakic-Skokovic, M.
In many organizations, testing, regarded as quality verification, begins only once code has been completed. However, errors found in requirements are the leading cause of project failures, defects and rework. Even though many companies use some method of requirements management and some form of software quality testing, most of them cannot (or do not) link them together. While searching for an application lifecycle management (ALM) methodology that might give us an answer to these problems, Requirements-Based Testing (RBT) emerged as a possible solution. RBT provides a set of quality assurance activities and management tools that enable getting requirements right from the outset. This paper presents lessons learned while introducing requirements-based testing methodology, in order to put the project in control and deliver applications on time.

Print Email

A Comparative Overview of the Evolution of Software Development Models (pp. 163-172)

Matkovic, P., Tumbas, P.
Information system (IS) development began as early as 1940. Up to the 1960s, IS development was based on IT pioneers’ individual knowledge, so that this period is referred to as pioneer era, and some sources even use the term heroic age. The emergence of software crisis also saw the first forms of organised and systematised software development. Systematizing and organising the development efforts was concretised through a multitude of methodologies which appeared in the meantime, and were used for determining the structure, as well as planning and monitoring development procedures. Academic and professional literature offers a multitude of definitions of the term methodology. Most definitions explain this term as a set of clear rules and principles for the application of methods and/or procedures, with the aim of resolving various problems. More specifically, in the software development area, methodologies can be viewed as a set of rules and principles for using methods and/or procedures applied when conducting development activities by pre-defined roles in the software development process, with the use of input artifacts, aimed at obtaining output artifacts as the constituent elements of the future software. Methodologies are built on theoretical foundations, and are all based on one or more development models. In this paper, the term model refers to a systematic and logical description of a development process, without detailed elaboration of activities, performers, inputs and outputs. The paper provides an evolutional overview of development models, with their comparisons, and considers the expected avenues of future development.

Print Email