Matti Rossi

Mobile banking services

Adopting new and innovative mobile financial applications and service provisioning methods.

An empirical investigation of mobile ticketing service adoption in public transportation

In this paper, we present results from a study of mobile ticketing service adoption in public transportation. The theoretical background of the study is based on technology adoption and trust theories, which are augmented with concepts of mobile use context and mobility. Our empirical findings from analyses of a survey data suggest that compatibility of the mobile ticketing service with consumer behavior is a major determinant of adoption. Mobility and contextual factors, including budget constraints, availability of other alternatives, and time pressure in the service use situation were also found to have a strong effect on the adoption decision. Our findings suggest that contextual and mobile service-specific features are important determinants of mobile service adoption and should thus be integrated into the traditional adoption models.

The Impact of Use Situation and Mobility on the Acceptance of Mobile Ticketing Services

This paper presents results from a study of mobile ticketing service acceptance in public transportation. The theoretical background of the study was drawn from technology acceptance and diffusion of innovation theories, which were augmented with issues related to mobile service features, as well as the mobile use situation. The resulting research model was tested with data gathered through a self-administered mail survey with 360 subjects. Our findings suggest that usefulness and benefits of the mobile ticketing service are perceived differently in different use situations and that use situation has a significant effect on use intention. The results indicate that traditional adoption models should be augmented with the use situation and mobility constructs to better understand and explain the specific factors, which determine the use of mobile services.

Architecture as a Coordination Tool in Multi-site Software Development

A widely held understanding of coordination in software development is that it focuses on coordinating development activities to achieve a common goal. Our study, a case study in an international ICT company, suggests that in multi-site environment, it is not enough to coordinate development activities to achieve a common goal. Rather, more emphasis should be put on coordinating interdependencies between activities. Shifting the interest from activities (and subsystems) toward system-level dependencies requires software architects and developers to have a common understanding of the software architecture. Our findings reflect coordination challenges in multi-site environment with geographically dispersed teams. On the basis of the findings, we claim that architecture could be used to coordinate distributed development. However, this requires that the chief architect is capable of maintaining the integrity of the architecture and of communicating it. Furthermore, we list some requirements for a development methodology that uses architecture to support the coordination. Copyright

Is extreme programming just old wine in new bottles: A comparison of two cases

This article explores extreme programming (XP) as an information systems development approach and argues that it is mainly old wine in new bottles. We take an interpretive and critical view of the phenomenon. We made an empirical study of two companies that apply an XP-style development approach throughout the information systems development life cycle. The results of our research suggest that XP is a combination of best practices of traditional information systems development methods. It is hindered by its reliance on talented individuals, which makes its large-scale deployment as a general-purpose method difficult. We claim that XP can be useful for small teams of domain experts who are physically close together and able to communicate well with the end users, and who are good designers and implementers. However, these skilled and motivated individuals with high working moral can exhibit high productivity regardless of the methods used if they are not overly constrained by bureaucracy.

Design of emerging digital services: a taxonomy

There has been a gigantic shift from a product based economy to one based on services, specifically digital services. From every indication it is likely to be more than a passing fad and the changes these emerging digital services represent will continue to transform commerce and have yet to reach market saturation. Digital services are being designed for and offered to users, yet very little is known about the design process that goes behind these developments. Is there a science behind designing digital services? By examining 12 leading digital services, we have developed a design taxonomy to be able to classify and contrast digital services. What emerged in the taxonomy were two broad dimensions; a set of fundamental design objectives and a set of fundamental service provider objectives. This paper concludes with an application of the proposed taxonomy to three leading digital services. We hope that the proposed taxonomy will be useful in understanding the science behind the design of digital services.

Information modeling in the new millennium

We may not be able to make you love reading, but information modeling in the new millennium will lead you to love reading starting from now. Book is the window to open the new world. The world that you want is in the better stage and level. World will always guide you to even the prestige stage of the life. You know, this is some of how reading will give you the kindness. In this case, more books you read more knowledge you know, but it can mean also the bore is full.

Software Architectures: Blueprint, Literature, Language Or Decision?

This study questions the traditional view of software architecture as a specification that needs only be understood by software architects and engineers. Based on an intensive study of three software-producing organizations, we identify multiple metaphors (‘Blueprint,’ ‘Literature,’ ‘Language’ and ‘Decision’) that stakeholders use to understand the term software architecture, which in turn, allows them to effectively participate in its creation and use. Our results point to new research directions that may better encompass a broader view of software architecture.

Situational Method Engineering

While previously available methodologies for software like those published in the early days of object technology claimed to be appropriate for every conceivable project, situational method engineering (SME) acknowledges that most projects typically have individual characteristics and situations. Thus, finding the most effective methodology for a particular project needs specific tailoring to that situation. Such a tailored software development methodology needs to take into account all the bits and pieces needed for an organization to develop software, including the software process, the input and output work products, the people involved, the languages used to describe requirements, design, code, and eventually also measures of success or failure. The authors have structured the book into three parts. Part I deals with all the basic concepts, terminology and overall ideas underpinning situational method engineering. As a summary of this part, they present a formal meta-model that enables readers to create their own quality methods and supporting tools. In Part II, they explain how to implement SME in practice, i.e., how to find method components and put them together and how to evaluate the resulting method. For illustration, they also include several industry case studies of customized or constructed processes, highlighting the impact that high-quality engineered methods can have on the success of an industrial software development. Finally, Part III summarizes some of the more recent and forward-looking ideas. This book presents the first summary of the state of the art for SME. For academics, it provides a comprehensive conceptual framework and discusses new research areas. For lecturers, thanks to its step-by-step explanations from basics to the customization and quality assessment of constructed methods, it serves as a solid basis for comprehensive courses on the topic. For industry methodologists, it offers a reference guide on features and technologies to consider when developing in-house software development methods or customising and adopting off-the-shelf ones.

Towards an understanding of the use of problem and design spaces during object- oriented system development

The importance of, and distinction between, problem and design spaces has been recognized in studies of information systems development (ISD). With increasing acceptance of objectoriented techniques, which promise close mirroring of real-world concepts in the IS artifacts, this distinction becomes even more important. In spite of a rich literature stream dealing with the general notion of ‘design,’ several inadequacies remain in our understanding of the ISD processes—one of these is the recognition and impact of problem and design spaces. In this paper, we analyze processes followed by two developers engaged in a non-trivial development task using the object-oriented modeling techniques—with a view to understanding their use of, and explorations in, problem and design spaces. Our analysis provides evidence for a distinction between the two spaces, and interprets the developers’ engagements and behaviors to structure the two spaces with the help of object-oriented modeling techniques. Several interesting findings emerge from our analysis, including the overlapping of spaces due to the use of object-orientation, disturbing patterns such as design fixation, interplay between simulation, expansion and validation in the design space, and the varying use of modeling techniques to structure the two spaces. Our analysis, supported by prior literature, provides a grounded description of some phenomena that have, hitherto, had only intuitive or prescriptive support. Based on these, we argue for more methodological and tool support for explorations of problem