Hawaii International Conference on System Sciences

Information systems development and data modeling: Conceptual and philosophical foundations

International Journal of Electronic Government Research: Guest editorial preface

The signal and the noise

Context The software architecture of a system is the result of a set of architectural decisions. The topic of architectural decisions in software engineering has received significant attention in recent years. However, no systematic overview exists on the state of research on architectural decisions. Objective The goal of this study is to provide a systematic overview of the state of research on architectural decisions. Such an overview helps researchers reflect on previous research and plan future research. Furthermore, such an overview helps practitioners understand the state of research, and how research results can help practitioners in their architectural decision-making. Method We conducted a systematic mapping study, covering studies published between January 2002 and January 2012. We defined six research questions. We queried six reference databases and obtained an initial result set of 28,895 papers. We followed a search and filtering process that resulted in 144 relevant papers. Results After classifying the 144 relevant papers for each research question, we found that current research focuses on documenting architectural decisions. We found that only several studies describe architectural decisions from the industry. We identified potential future research topics: domain-specific architectural decisions (such as mobile), achieving specific quality attributes (such as reliability or scalability), uncertainty in decision-making, and group architectural decisions. Regarding empirical evaluations of the papers, around half of the papers use systematic empirical evaluation approaches (such as surveys, or case studies). Still, few papers on architectural decisions use experiments. Conclusion Our study confirms the increasing interest in the topic of architectural decisions. This study helps the community reflect on the past ten years of research on architectural decisions. Researchers are offered a number of promising future research directions, while practitioners learn what existing papers offer.

/pdf/past-and-future-of-software-architectural-decisions-a-3askkl0h6a.pdf

Past and future of software architectural decisions - A systematic mapping study

There is a lack of knowledge concerning the low-code autoML (automated machine learning) frameworks that can be used to enrich data for several purposes concerning either data engineering or software engineering. In this paper, 34 autoML frameworks have been reviewed based on the latest commits and augmentation properties of their GitHub content. The PyCaret framework was the result of the review due to requirements concerning adaptability by Google Colaboratory (Colab) and the BI (business intelligence) tool. Finally, the low-code autoML-augmented data pipeline from raw data to dashboards and low-code apps has been drawn based on the experiments concerned classifications of the “Census Income” dataset. The constructed pipeline preferred the same data to be a ground for different reports, dashboards, and applications. However, the constructed low-code autoML-augmented data pipeline contains changeable building blocks such as libraries and visualisations.

Low-code autoML-augmented data pipeline - a review and experiments

To identify the Open Source maintenance process two well known Open Source projects Apache HTTP server and Mozilla web browser were studied. The Open Source software maintenance process is formal even anyone can submit modifications or defect reports to Open Source software projects. We assume that the Open Source maintenance process is similar to the maintenance process defined by the ISO/IEC. In the case studies. four activities were found similar to the activities of the ISO/IEC Maintenance process. This paper presents the Open Source maintenance process framework. The framework is exemplified with the ISO/IEC Maintenance process framework.

/pdf/open-source-software-maintenance-process-framework-41gp76ugop.pdf

Open source software maintenance process framework

While Open Source Software are becoming evermore widespread and used these days, their maintenance is coming important issue. Earlier studies have shown that defect and version management systems are rich and valuable sources for evaluation of maintenance but they have not studied the use of separate management system for support and feature request. Therefore, in this research we study defect reports, support and feature requests of Open Source Software projects through four case studies from SourceForge. Results showed that most of the case studies used actively those systems but discussion forums were even more active. Although reports and requests were submitted, most of them did not cause any changes or further actions because they were closed shortly as duplicates, invalid or without any resolution.

Exploring the Maintenance Process through the Defect Management in the Open Source Projects - Four Case Studies

IT service provider organizations need both IT service management (ITSM) and IT service governance (ITSG) to ensure successful service provision for their customers. However, current service science literature has not adequately addressed how these activities differ from each other. Focusing solely on IT service management and ignoring service governance aspects may cause difficulties in measuring the performance of service management, defining and deploying the roles and responsibilities of service management, allocating the resources for right service improvements and adopting the service-oriented process culture. The research problem of this study is: How does IT service management differ from IT service governance? The main contribution of the study is a framework for IT service governance and a roadmap of IT service management frameworks and standards that can be utilized in establishing IT service governance activities. The theory-based framework is validated in an IT service change management case study with five Finnish IT service provider organizations. The results of this study may be used by top management, service directors and the IT service managers of IT service companies to better identify different aspects of IT service management and IT service governance.

Defining the relationships between IT service management and IT service governance

Governments all over the world have started eGovernment programmes. Enterprise architecture (EA) work has emerged as a solution to make a better eGovernment. We investigated the role of EA in the Finnish eGovernment programme called the National Project for IT in Social Services (Tikesos). This study reports what kind of role EA has played in group decisions made by the executive group of Tikesos project. Further, it highlights what has been the main emphasis of the Tikesos project. The research approach is qualitative. We analyzed contents and identified themes from the records of the Tikesos executive group. We found out that EA has not guided the group decisions made by the Tikesos executive group although it has been featured in the plans of the project. Further, we identified three themes: buck-passing, instability in decision making and role of EA.

Does Enterprise Architecture Form the Ground for Group Decisions in eGovernment Programme? Qualitative Study of the Finnish National Project for IT in Social Services

Virpi Hotti

Papers

Low-code autoML-augmented data pipeline - a review and experiments

Open source software maintenance process framework

Exploring the Maintenance Process through the Defect Management in the Open Source Projects - Four Case Studies

Defining the relationships between IT service management and IT service governance

Does Enterprise Architecture Form the Ground for Group Decisions in eGovernment Programme? Qualitative Study of the Finnish National Project for IT in Social Services