Artificial Intelligence (AI) is shifting software engineering from tool-supported processes towards AI-first collaboration, where authority is dynamically distributed across human and artificial actors. However, existing method engineering approaches assume static, human-centric control and provide limited support explicitly capturing evolving autonomy. This paper presents a vision for autonomy-aware method engineering by proposing a metamodel that treats autonomy not as a fixed property of an actor, but as a derived, situation-dependent authority assignment determined by task, context, and collaboration pattern. The metamodel formalizes autonomy through four authority dimensions: task execution, task decomposition, task initiation, and collaboration reconfiguration. Through an analytical instantiation with a multi-agent requirements analysis tool, we illustrate how the metamodel supports dynamic authority assignment. This work provides a conceptual foundation for governance-aware, adaptable, and AI-first software engineering methods.
Cloud-based accessing of Quantum-as-a-Service (QaaS) platforms such as IBM Quantum, IonQ Cloud, and Amazon Braket is becoming popular day by day. Hybrid quantum-classical algorithms (VQE, QAOA, QML) transfer data via a long layered pipeline of orchestration, compilation, and execution. Recent works have demonstrated various critical attacks at individual stages: Calibration tampering, SWAP attacks, QubitHammer, and so on. However, these attacks remain separated because of their own terminology, and existing STRIDE-based threat modeling in the context of quantum lacks a structured view towards the QaaS stack itself. We address this concern by decomposing the workflow into six-stage model with STRIDE threat modeling. Our matrix demonstrated attack vectors in quantum-specific, inherited classical, and plausible tiers for each of the stages. We further investigate the underexplored sections (repudiation and elevation-of-privilege) and distinguish three different cross-stage attack chains with higher impacts.
Badhon Rahman, Majid Haghparast, T. Mikkonen· 1 citation
This research highlights the heightened threats to data integrity and stakeholder trust in these evolving ecosystems through an intensive examination of the literature, initiating a pioneering discourse emphasizing fostering a foundation for developing secure and trustworthy Liquid AI environments.
M. Agbese, Niko Mäkitalo, Muhammad Waseem et al.· IoT· 6 citations· ⚡1
Carbon-Aware Governance Gates (CAGG), an architectural extension that embeds carbon budgets, energy provenance, and sustainability-aware validation orchestration into human-AI governance layers, is proposed.
M. Abbasi, T. Mikkonen, Petri Ihantola et al.· 2026 IEEE 23rd International...· 0 citations
It is argued that AI software is still software and needs to be approached from the software development perspective, and whether the focus should be on AI ethics or the quality of an AI system, called a maturity model for the development of AI systems is discussed.
Ville Vakkuri, Marianna Jantunen, Erika Halme et al.· SafeAI@AAAI· 17 citations· ⚡1
This paper reports a study where realism was combined with control over certain context and process factors to identify the most important relationships among process, context and outcome.
P. Abrahamsson, Andreas Jedlitschka, A. Duc et al.· Lecture Notes in Computer Sc...· 3 citations
Cyber Physical Systems (CPS) development approaches tend to start from the physical (hardware) perspective, and the software is the final element in the process. However, this approach is unfit for the more software-intensive world that is increasingly iterative, connected, and constantly online. Many constraints prevent the application of iterative, incremental, and agile development methodologies, which now are the norm for many other fields of software. Time-consuming system validation can only start when both hardware and software components are ready, which implies that the software delivery and quality is almost always the final bottleneck in the CPS development and integration. Also organizational issues raise concerns - CPS development teams are nowadays often geographically distributed, which can result in delays in the process, shortcomings, and even mistakes. In this paper, we propose using our envisioned open-source Virtual Reality-based Integrated software Development Environment (VRIDE) for developing the next generation, increasingly software-intensive CPSs in efficient ways.
T. Mikkonen, Kai-Kristian Kemell, Petri Kettunen et al.· EUROMICRO Conference on Soft...· 3 citations
Containers are most often discussed in the context of cloud computing, performance and DevOps, and it is found that what is currently missing is more deeply focused research.
Mikael Koskinen, T. Mikkonen, P. Abrahamsson· International Conference on...· 15 citations· ⚡1
The study shows that, because security is a cross-cutting property in complex CPSs, its proficient management requires system-wide competencies and capabilities across the CPSs development and operation.
P. Abrahamsson, Goetz Botterweck, Hadi Ghanbari et al.· International Journal of Sys...· 14 citations
Overall, the results suggest that epic-organized generation can improve perceived Gherkin quality while maintaining comparable semantic coverage, although broader replication is needed before generalizing this finding.
Shahbaz Siddeeq, M. Abbasi, Jussi Rasku et al.· arXiv.org· 0 citations
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.