25 February 2022 in Internet of Things
The use of face masks is an important way to fight the COVID-19 pandemic. In this paper, we envision the Smart Mask, an IoT supported platform and ecosystem aiming to prevent and control the spreading of COVID-19 and other respiratory viruses. The integration of sensing, materials, AI, wireless, IoT, and software will help the gathering of health data and health-related event detection in real time from the user as well as from their environment. In the larger scale, with the help of AI-based analysis for health data it is possible to predict and decrease medical costs with accurate diagnoses and treatment plans, where the comparison of personal data to large-scale public data enables drawing up a personal health trajectory, for example. Key research problems for smart respiratory protective equipment are identified in addition to future research directions. A Smart Mask prototype was developed with accompanying user application, backend and heath AI to study the concept.
25 March 2019 in Journal of Software: Evolution and Process
Requirements volatility is a major issue in software development, causing problems such as higher defect density, project delays, and cost overruns. Software architecture that guides the overall vision of software product is one of the areas that is greatly affected by requirements volatility. Since critical architecture decisions are made based on the requirements at hand, changes in requirements can result significant changes in architecture. With the wide adoption of agile software development, software architectures are designed to accommodate possible future changes. However, the changes has to be carefully managed as unnecessary and excessive changes can bring negative consequences. An exploratory case study was conducted to study the impact of requirements volatility on software architecture. Fifteen semistructured, thematic interviews were conducted in a European software company. The research revealed poor communication, information distortion, and external dependencies as the main factors that cause requirement volatility and inadequate architecture documentation, inability to trace design rationale, and increased complexity as the main implications of requirements volatility on software architecture. Insights from software teams' awareness of the requirement volatility, factors contribute to it, and possible ways to mitigate its implications will be utilized to improve the management of requirement volatility during software architecting process.
9 September 2025 in Journal of Systems and Software