Iterative Software Development Research Articles

Sistem Rancangan Pendataan Yatim, Fakir Miskin dan Lansia pada Kantor Desa Baet Kecamatan Baitussalam Kabupaten Aceh Besar

This study discusses the design of a data collection system for orphans, the poor, and the elderly at the Baet Village Office, Baitussalam District, Aceh Besar. The problem discussed is how to use computer technology to enter data into the data collection system. The purpose of this study was to determine the use of the data collection system. The data for this study were collected through a literature study which involved reviewing books and materials related to the topic. In addition, field studies were also carried out by conducting interviews and direct observation of objects related to this research report. Apart from that, in this study, the authors also utilized the Extreme Programming (XP) method in the process of developing a data collection system. The XP method is an Agile method that enables adaptive, collaborative, and iterative software development. The results showed that the use of computer technology and the XP method in the development of a data collection system was able to speed up the process of collecting and processing data, as well as increasing work efficiency and effectiveness. In addition, the developed data collection system is also able to produce more accurate and integrated data, so that it can assist the village government in planning and making more appropriate decisions related to community services, especially orphans, the poor, and the elderly.

Stakeholder Engagement to Drive Iterative Software Development of the ART-Access Web-Based Application for Community Pharmacy Dispensing of Anti-Retroviral Therapy

Introduction: Significant advances in combination anti-retroviral therapy have been instrumental in improving the quality of lives and life expectancy for people living with HIV. However, in the absence of a cure, sustained investment and innovation is required to improve adherence and quality of life for people living with HIV. We developed ARTAccess, a web-based application that links patient information on anti-retroviral therapy and viral load to an algorithm that guides a private community pharmacist on anti-retroviral therapy refills without the need for an additional nurse in the pharmacy. The aim of this paper is to describe the present the development process of the ARTAccess application and the exploration of the perceptions about its use by end users. Methods: Between October–December 2018, we conducted a qualitative observational study to document the processes of the ART-Access™ application development. Using theoretical frameworks of participatory action research and human-centred design, we undertook structured and unstructured observations of the application development review meetings. We observed and had interactions in 12 stakeholder meetings. Three observers attended each development meeting and independently drafted a reflective narration of the transcript and separately conducted their own analyses. ARTAccess was launched in January 2019 and in March 2019, three in-depth interviews were conducted with the nurse dispensers running the refill program at the three pharmacies where ARTAccess was piloted. Results: The ARTAccess application development meetings generated emerging themes. Introduction of a mHealth application for efficiency introduced job insecurity fears of health workers which needed to be addressed, to allow for increased engagement by health worker stakeholders. Stakeholder meetings provided important perceived gaps and needs for improvement at each stage of the ARTAccess application development. The user-centred design process led to five application versions; three more than the two originally planned; the feedback on the ARTAccess application became more positive as later versions were presented to stakeholders. Conclusions: The study provides evidence that participatory action research in a human-centred design approach enhanced the application development process of a new technology for health. In resource limited settings, where digital technologies may be used to support overstretched health systems, health workers need re-assurance that digital tools being developed will not threaten their employment.

Fitverse: A Fitness Assistant Application using Flutter

Abstract: With reference to this document, it describes the process and components of the development of the project. A fitness schedule is any behavioral pattern that one often and regularly does, by and large automatically; and Fitverse- the fitness assistant application, is a tool that aids the user in their fitness journey by providing them with customized diet recommendations and workout schedules. It also monitors if and when you complete your desired diet and fitness targets and acts as a guide in one’s journey to achieve the aspired fitness goals. Turning good behaviors into habits makes them our default, automatic choices of action. This all but eliminates the willful effort required to repeat them. It aids users with their fitness journey by being the virtual fitness trainer. Fitverse is an android-based application built using Flutter that helps in achieving fitness goals and building concrete habits. The Prototype Model is used to develop this system along with iterative software development model. As for the software used to develop this system is Visual studio code and programming language used is Dart with Firebase as the database. This technology can transform the current daunting task to develop a fitness schedule or a habit and make it more efficient and easier. Keywords: Dart language, Flutter, Iterative Software Development Model, Prototype Model, Firebase

Analyzing Uncertainty in Release Planning: A Method and Experiment for Fixed-Date Release Cycles

Release planning—deciding what features to implement in upcoming releases of a software system—is a critical activity in iterative software development. Many release planning methods exist, but most ignore the inevitable uncertainty in estimating software development effort and business value. The article’s objective is to study whether analyzing uncertainty during release planning generates better release plans than if uncertainty is ignored. To study this question, we have developed a novel release planning method under uncertainty, called BEARS, that models uncertainty using Bayesian probability distributions and recommends release plans that maximize expected net present value and expected punctuality. We then compare release plans recommended by BEARS to those recommended by methods that ignore uncertainty on 32 release planning problems. The experiment shows that BEARS recommends release plans with higher expected net present value and expected punctuality than methods that ignore uncertainty, thereby indicating the harmful effects of ignoring uncertainty during release planning. These results highlight the importance of eliciting and analyzing uncertainty in software effort and value estimations and call for increased research in these areas.

Organizational and Economic Mechanism of Development and Promotion of IT Products in Ukraine

Software development and the implementation of IT industry products are usually a very complicated and complex process. In recent years, software requirements' nature and complexity have changed dramatically, as have user demands for cost, performance, and quality. These three parameters can be considered key, and keeping them at an appropriate level for consumers is possible only through optimal design using well-established software development methodologies.The search for ways to optimize labour and financial costs leads managers worldwide to the need to use in practice a variety of techniques and approaches. With this approach, the scientific and economic substantiation of the advisability of choosing one or another organizational and financial mechanism for organizing a team of developers and marketers becomes especially important.The authors of the article studied Dynamics of export growth of Ukrainian IT products, the relationship between the IT product market elements, the main and auxiliary stages of creating an IT product. For the development and promotion of IT products, the authors proposed a methodology for iterative software development based on prototyping, using elements of the SCRUM system, which was tested at a private Ukrainian IT company. The modified version of the agile development system proposed in the article showed promising results in practice, both IT company managers and specialists positively assessed the experience of its use. Based on the already proven technology of agile development, this technique was able to add some mechanics that made it possible to neutralize several negative factors inherent in other approaches.

New failure rate model for iterative software development life cycle process

Software reliability models are one of the most generally used mathematical tool for estimation of reliability, failure rate and number of remaining faults in the software. Existing software reliability models are designed to follow waterfall software development life cycle process. These existing models do not take advantage of iterative software development process. In this paper, a new failure rate model centered on iterative software development life cycle process has been developed. It aims to integrate a new modulation factor for incorporating varying needs in each phase of iterative software development process. It comprises imperfect debugging with the possibility of fault introduction and removal of multiple faults in an interval as iterative development of the software proceeds. The proposed model has been validated on twelve iterations of Eclipse software failure dataset and nine iterations of Java Development toolkit (JDT) software failure dataset. Parameter estimation for the proposed model has been done by hybrid particle swarm optimization and gravitational search algorithm. Experimental results in-terms of goodness-of-fit shows that proposed model has outperformed Jelinski Moranda, Shick Wolverton, Goel Okummotto Imperfect debugging, GS Mahapatra, Modified Shick Wolverton in 83.33% of iterations for eclipse dataset and 77.77% of iterations for JDT dataset.

Accessibility by proximity: Addressing the lack of interactive accessibility instruments for active mobility

The rise of concepts such as the 15-minute-city represents the growing importance of accessibility by active mobility. In order to promote accessibility, accessibility instruments are developed that have substantial potential to assist practitioners in decision making processes. Therefore, this research starts with an up-to-date overview on the suitability of accessibility instruments when planning for active mobility. It was found that accessibility instruments were significantly further developed in the last few years and there is a rising number of tools that contain novel features. However, it was identified that there is a clear lack of tools specifically designed for modeling active mobility that are open source, include interactive scenario building, and can easily be transferred to new study areas.Therefore, an interactive accessibility instrument named GOAT (Geo Open Accessibility Tool) was developed, which is open source, transferable, and has an easy-to-use web interface. This instrument has been developed following an iterative software development process in close cooperation with practitioners from three municipalities in the region of Munich, Germany. The practitioners tested the tool independently in numerous workshops in order to provide feedback, which was integrated into the development. Furthermore, the tool was tested and transferred to more than 20 German municipalities, the City of Bogotá (Colombia) and Matosinhos (Portugal). First results show that the collaborative and open development process produced a user-centric solution, which bears the high potential to make planning for active mobility more effective and efficient.

A/B testing as an effective instrument for adaptation of the user interface at the iterative model of developing applications for mobile devices

Changing the user interface always entails risks of decreasing application ergonomics and user churn. The purpose of this work is to find methods for changing the user interface without the need to use and increase the number of active users. Using Alpha/Beta testing and analysis of application metrics, it is possible to include design in each iteration and remotely manage the application configuration, which improves the user interface of the application. The way to integrate the UI modification and adaptation phase into an iterative software development model is proposed in this article. The successful user interface improvement experiments that have improved application metrics are described. In this work, the problem was highlighted, lack of information and control over user purchases, which negatively affected the number of purchases. A hypothesis is put forward that the user must have an effective visualization and control tool in the application. As a result of the experiment, the hypothesis was confirmed by an increase in the number of purchases and user activity. There was also a data security issue in the application, which put users at risk of data loss. An experiment was conducted to change the default value of user settings, which led to an increase of the positive metrics for using the data reservation functionality. The problem of polling users is also considered, which is an important component in the process of improving the ergonomics of an application. The method of remote user polling was used, which allowed to receive quick feedback from users and quickly respond to requests from users. The result of the work is the confirmation of the hypothesis of changes in the user interface in the cycles of the iterative development model, the positive dynamics of application metrics, as well as the satisfaction of users with the changes.

Security in agile software development: A practitioner survey

Abstract Context: Software security engineering provides the means to define, implement and verify security in software products. Software security engineering is performed by following a software security development life cycle model or a security capability maturity model. However, agile software development methods and processes, dominant in the software industry, are viewed to be in conflict with these security practices and the security requirements. Objective: Empirically verify the use and impact of software security engineering activities in the context of agile software development, as practiced by software developer professionals. Method: A survey ( N = 61 ) was performed among software practitioners in Finland regarding their use of 40 common security engineering practices and their perceived security impact, in conjunction with the use of 16 agile software development items and activities. Results: The use of agile items and activities had a measurable effect on the selection of security engineering practices. Perceived impact of the security practices was lower than the rate of use would imply: This was taken to indicate a selection bias, caused by e.g. developers’ awareness of only certain security engineering practices, or by difficulties in applying the security engineering practices into an iterative software development workflow. Security practices deemed to have most impact were proactive and took place in the early phases of software development. Conclusion: Systematic use of agile practices conformed, and was observed to take place in conjunction with the use of security practices. Security activities were most common in the requirement and implementation phases. In general, the activities taking place early in the life cycle were also considered most impactful. A discrepancy between the level of use and the perceived security impact of many security activities was observed. This prompts research and methodological development for better integration of security engineering activities into software development processes, methods, and tools.

CONTROL AND ACCOUNTING ASPECTS OF INTRODUCING AGILE-METHODOLOGY FOR SOFTWARE DEVELOPMENT PROJECTS

Abstract. The article considers the Agile methodology, its conceptual principless and studies the main accounting aspects of its implementation in realizing the projects of software development. In order to meet the modern requirements of the economic environment, the IT companies are turning to Agile-methodologies with accent on iterative and incremental software development. The software development on the basis of a flexible approach has numerous advantages, in particular centering on clients’ needs, reducing risks and costs, providing a transparent process. However, using Agile-methodology can make accounting a complicated task. The existing accounting principles involve software development in a long-term perspective and in more discrete phases. The article analyzes the popularity of practical use of Agile approach and determines the advantages from its use as well as defines the accounting related problems. The ways of eliminating the complications of using the flexible approach in project management in financial accounting are defined. The main ideological aspects of Agile Manifesto are considered. In modern conditions, almost all businesses are in a state of constant change. There are purposeful transformations of both their individual elements and the management system in general, which requires manageability of change, which is difficult to achieve even within individual projects, often unique and innovative. In addition, the world economy has undergone significant changes in the economic environment, due to the globalization of business, informatization of society and the transition to a new model of economic growth. It is investigated that with modern optimization of financial processes Agile-technologies are built in such a way that changes are welcomed and uncertainty is recognized. And this did not bypass the internal audit. The growing needs of customers, the need to change process technologies, the introduction of new methodologies in the activities of departments adjust the internal audit to change approaches to testing and analysis of materials, as well as active participation in new projects. Keywords: Agile-methodology, Agile-team, Internal audit, value-centered approach, accounting system, costs capitalization. JEL Classification M40, M41, L86 Formulas: 0; fig.: 4; tabl.: 0; bibl.: 13.

Understanding the Interactions between the Scrum Master and the Development Team: A Game-Theoretic Approach

Scrum methodology is widely used in the information technology (IT) industry for the purposes of team-based iterative software development. However, limited studies have been conducted to explore the nature of interactions between a Scrum Master and other team members and the effect of these interactions on team effectiveness. The aim of this study is to understand the interactions between the Scrum Master and other team members in an educational setting and propose and demonstrate an application of cooperative game theory for the same. Cooperative game theory can model scenarios where other team members can benefit from cooperating. Through the lens of the cooperative game-theoretic model, we investigated the strategies employed by the Scrum Master and other team members when involved in a semi-capstone IT project. Specifically, the study explored the team interaction between a Scrum Master and other team members at three different levels of team effectiveness: least effective, partially effective, and most effective. Our results indicate that a Scrum Master should be active to maximize their payoff as well as the teams’ overall payoff. Contrary to this, other team members should be active in the most and partially effective teams, while being passive in the least effective teams at higher costs of interpersonal relations and the processes. The results of the study represent a novel application of game-theoretic modeling for understanding the Scrum Master and other team member interactions. These results are applicable not just in an educational setting but also to the wider area of software development by identifying the right set of strategies by the Scrum Master, and other team members in order to help IT professionals to maximize their payoff.

User-Centered Design of a Mobile Health Intervention to Enhance Exacerbation-Related Self-Management in Patients With Chronic Obstructive Pulmonary Disease (Copilot): Mixed Methods Study.

BackgroundAdequate self-management skills are of great importance for patients with chronic obstructive pulmonary disease (COPD) to reduce the impact of COPD exacerbations. Using mobile health (mHealth) to support exacerbation-related self-management could be promising in engaging patients in their own health and changing health behaviors. However, there is limited knowledge on how to design mHealth interventions that are effective, meet the needs of end users, and are perceived as useful. By following an iterative user-centered design (UCD) process, an evidence-driven and usable mHealth intervention was developed to enhance exacerbation-related self-management in patients with COPD.ObjectiveThis study aimed to describe in detail the full UCD and development process of an evidence-driven and usable mHealth intervention to enhance exacerbation-related self-management in patients with COPD.MethodsThe UCD process consisted of four iterative phases: (1) background analysis and design conceptualization, (2) alpha usability testing, (3) iterative software development, and (4) field usability testing. Patients with COPD, health care providers, COPD experts, designers, software developers, and a behavioral scientist were involved throughout the design and development process. The intervention was developed using the behavior change wheel (BCW), a theoretically based approach for designing behavior change interventions, and logic modeling was used to map out the potential working mechanism of the intervention. Furthermore, the principles of design thinking were used for the creative design of the intervention. Qualitative and quantitative research methods were used throughout the design and development process.ResultsThe background analysis and design conceptualization phase resulted in final guiding principles for the intervention, a logic model to underpin the working mechanism of the intervention, and design requirements. Usability requirements were obtained from the usability testing phases. The iterative software development resulted in an evidence-driven and usable mHealth intervention—Copilot, a mobile app consisting of a symptom-monitoring module, and a personalized COPD action plan.ConclusionsBy following a UCD process, an mHealth intervention was developed that meets the needs and preferences of patients with COPD, is likely to be used by patients with COPD, and has a high potential to be effective in reducing exacerbation impact. This extensive report of the intervention development process contributes to more transparency in the development of complex interventions in health care and can be used by researchers and designers as guidance for the development of future mHealth interventions.

The Development of Web-Based Emotion Detection System Using Keyboard Actions (EDS-KA)

Emotions is one of the user experience key factors. Emotions is subjective feeling and it is difficult to determine human’s emotions. Thus, there is a need to have a system that could automatically detect human emotions. Nowadays, most of the emotion detection systems are obtrusive, complex and expensive. Besides that, most of the data collection and analysis process for research has been done manually. Therefore, Web-based Emotion Detection System using Keyboards Actions (EDS-KA) has been developed to detect human emotions without their awareness, uncomplicated and inexpensive in which, it is based on human actions using computer keyboard. In addition, this system could assist researchers in data collection and analysis, whereas, data could be collected and analyzed automatically. Further, the analysis results were saved in the database and could be printed out. EDS-KA adopted the Rational Unified Process (RUP) system development methodology. The RUP has been selected for EDS-KA development because it is an iterative software development process. Therefore, it enable produce a well-defined system requirements and reduced the software risk. EDS-KA was a web-based system. Thus, users could access the system at any time and places that have internet connection. In terms of emotional considerations, EDS-KA focuson five (5) basic emotional states, namely happy, sad, afraid, relaxed and neutral (emotionless). Taken together, this system could assist the researchers’ tasks in conducting emotions detection research more efficient, taking less time and inexpensive.

PROBLEMS OF SMALL AND MID-SIZED ENTERPRISES IN JAPAN’S SOFTWARE INDUSTRY

This paper examines the reasons that most small and mid-sized enterprises (SMEs) in Japan’s software industry do not develop into large firms. Thousands of SMEs are informally organized under several large companies. Those SMEs have experienced difficulty developing into large firms. This industrial structure has remained for several decades. Several papers have already suggested reasons for this phenomenon, but each paper in the literature has given few reasons. This paper analyzes the issue more comprehensively. First, this article surveys the literature and determine several factors that contribute to the issue. Then, this paper demonstrates how they complicate the issue and make it difficult to solve. Finally, the paper illustrates several approaches in an effort to find solutions. The first method is introducing agile modeling and other iterative software development processes. Agile modeling adjusts design change more easily compared with other software development processes. Other iterative software development processes also adjust design change easily compared to the waterfall model. By using these processes, software engineers can avoid long overtime work, which contributes to the difficulties in securing human resource. The second method is for software firms to demand appropriate compensation for each design change. If many Japanese firms did this, overtime work would be shorter, and the working environment of SMEs would improve. Then, SMEs obtain excellent workers. This will help SMEs to grow to large firms.

Глобальная визуальная трансформация информационных систем здравоохранения на примере британского госпиталя женского здоровья

Objective. This essay describes the development of a wholly new form of timeline structured iconographic interface for the electronic patient record (EPR). This provides a fast and highly efficient means through which to view complex medical records from multiple data sources, with global health applications. Methods. Using a simple concept as the design framework, we have worked from first principles of agile and iterative software development to upcycle large quantities of electronic clinical data into a visually intuitive and efficient EPR format, with a wide range of practical clinical applications. The system was built within the existing Clinical Data Estate (CDE) and IT systems of a UK NHS University Hospital, by a small volunteer team at negligible cost. Results. Over ten years, we have developed the system from initial concept to a live EPR interface at the centre of our CDE for some 5,000 authorised users, to display some 2.5 million individual patient e-records in real time. We have also built a derivative exemplar data system for the “whole of life” study of chronic diseases of childhood and adulthood, using a dynamic data set of 18,000 locally treated breast cancer cases within our Women’s Health service. Conclusions. Agile software development puts the true user of information at the centre of digital design. When combined with the key principles of e-data visualisation, it can produce transformative clinical systems. The early sharing of insights and solutions will help accelerate beneficial change in our understanding of individual and population health.

A Collaboration Between Game Developers and Rehabilitation Researchers to Develop a Web-Based App for Persons With Physical Disabilities: Case Study.

BackgroundIndividuals with a disability and their partners, who often provide care, are both at risk for depression and lower quality of life. Mobile health (mHealth) interventions are promising to address barriers to mental health care. Rehabilitation researchers and software development researchers must collaborate effectively with each other and with clinical and patient stakeholders to ensure successful mHealth development.ObjectiveThis study aimed to aid researchers interested in mHealth software development by describing the collaborative process between a team of rehabilitation researchers, software development researchers, and stakeholders. Thus, we provide a framework (conceptual model) for other teams to replicate to build a Web-based mHealth app for individuals with physical disability.MethodsRehabilitation researchers, software development researchers, and stakeholders (people with physical disabilities and clinicians) are involved in an iterative software development process. The overall process of developing an mHealth intervention includes initial development meetings and a co-design method called design box, in which the needs and key elements of the app are discussed. On the basis of the objectives outlined, a prototype is developed and goes through scoping iterations with feedback from stakeholders and end users. The prototype is then tested by users to identify technical errors and gather feedback on usability and accessibility.ResultsIllustrating the overall development process, we present a case study based on our experience developing an app (SupportGroove) for couples coping with spinal cord injury. Examples of how we addressed specific challenges are also included. For example, feedback from stakeholders resulted in development of app features for individuals with limited functional ability. Initial designs lacked accessibility design principles made visible by end users. Solutions included large text, single click, and minimal scrolling to facilitate menu navigation for individuals using eye gaze technology. Prototype testing allowed further refinement and demonstrated high usability and engagement with activities in the app. Qualitative feedback indicated high levels of satisfaction, accessibility, and confidence in potential utility. We also present key lessons learned about working in a collaborative interdisciplinary team.ConclusionsmHealth promises to help overcome barriers to mental health intervention access. However, the development of these interventions can be challenging because of the disparate and often siloed expertise required. By describing the mHealth software development process and illustrating it with a successful case study of rehabilitation researchers, software development researchers, and stakeholders collaborating effectively, our goal is to help other teams avoid challenges we faced and benefit from our lessons learned. Ultimately, good interdisciplinary collaboration will benefit individuals with disabilities and their families.

A Controlled Experiment with Novice Developers on the Impact of Task Description Granularity on Software Quality in Test-Driven Development

Background: Test-Driven Development (TDD) is an iterative software development process characterized by test-code-refactor cycle. TDD recommends that developers work on small and manageable tasks at each iteration. However, the ability to break tasks into small work items effectively is a learned skill that improves with experience. In experimental studies of TDD, the granularity of task descriptions is an overlooked factor. In particular, providing a more granular task description in terms of a set of sub-tasks versus providing a coarser-grained, generic description. Objective: We aim to investigate the impact of task description granularity on the outcome of TDD, as implemented by novice developers, with respect to software quality, as measured by functional correctness and functional completeness. Method: We conducted a one-factor crossover experiment with 48 graduate students in an academic environment. Each participant applied TDD and implemented two tasks, where one of the tasks was presented using a more granular task description. Resulting artifacts were evaluated with acceptance tests to assess functional correctness and functional completeness. Linear mixed-effects models (LMM) were used for analysis. Results: Software quality improved significantly when participants applied TDD using more granular task descriptions. The effect of task description granularity is statistically significant and had a medium to large effect size. Moreover, the task was found to be a significant predictor of software quality which is an interesting result (because two tasks used in the experiment were considered to be of similar complexity). Conclusion: For novice TDD practitioners, the outcome of TDD is highly coupled with the ability to break down the task into smaller parts. For researchers, task selection and task description granularity requires more attention in the design of TDD experiments. Task description granularity should be taken into account in secondary studies. Further comparative studies are needed to investigate whether task descriptions affect other development processes similarly.

Exploring the use of Gestalt’s principles in improving the visualization, user experience and comprehension of COBie data extension

Purpose Until now, the usage and usability factors associated with AEC–FM standards have remained largely overlooked. This oversight could be a potentially significant factor in the adoption rates as well as effective utilization of such advanced solutions in the AEC–FM industry. Therefore, from a conceptual and theoretical viewpoint, the purpose of this paper is to address this gap in understanding and enhancing the usability aspects of standards such as construction operations building information exchange (COBie) over its spreadsheet representation. Besides, findings from this study and the proposed theoretical fundamentals to enhance the usability and functionality of COBie spreadsheet representation could potentially lay the foundation for a VisualCOBie approach. Design/methodology/approach The iterative steps of design thinking and agile development are harmonized to form the main research methodology. Design thinking is useful in problem (re)formulation, and agile development is useful in iterative software development. The approach aims to identify and understand the needs and requirements of the AEC–FM users from the standardized approaches and associated IT solutions; and formulate the main features and functionalities of the proposed solution. The methodology supports the aim of generating a broad range of possible solutions instead of coming up with the “right” solution. Findings Despite the standards and associated IT developments, the AEC–FM industry still suffers from inefficient information management. To date, most initiatives have focused on utilization of the outputs from different IT solutions in terms of accuracy and completeness of the data defined in the standards. This research found that well-established standards such as COBie and corresponding IT solutions are not merely technical issues, but it is equally important to understand how the end-users cognitively perceive and process them. The developed solutions need to address user point of view to facilitate wider utilization of these standards in practice. Research limitations/implications In this research, Gestalt’s visual perception principles have been used to evaluate the usability issues of COBie spreadsheet. Although Gestalt principles provide a valid and proven viewpoint, there can be other cognitive principles that could also be taken into consideration. Originality/value The usage and usability factors associated with AEC–FM standards have remained largely overlooked, indicating a gap in the literature. This gap was considered as a potentially significant factor in the adoption as well as effective utilization of such standards and advanced solutions in the AEC–FM industry. By grounding the research in cognitive and usability perspectives of information exchange standards, the authors demonstrate how such theoretical underpinning can lead to innovative solutions.

ARCHITECTURE OF PORTS AND ADAPTERS IN ITERATIVE DEVELOPMENT WITH LIMITATIONS ON TIME

The application of ports and adapters architecture (other names bulbous, layered, hexagonal) in iterative software development is considered in accordance with the requirements that come in chronological order in the practical example. Each iteration is supported by the schema architecture, problems encountered and their solution. The expediency of using the considered architecture in the iterative development of software with time constraints is shown. The system of collecting data on the concentration of carbon dioxide of the environment and air temperature in real time from a distributed network of sensors with a predetermined geolocation for medical institutions was developed. Put sensor information (ID, commissioning date and end date) in the Google Sheets spreadsheet. The data from the sensors should be collected on the server by REST service. The process of PPP in a specific project with significant time constraints is investigated, applying the rules and principles laid down in the architecture of ports and adapters, using the basic metrics to evaluate the complexity of adding new functionality, testing, concurrent development, speed and ease of development; draw conclusions about the conditions when it is appropriate to apply the chosen software design approach, and the ability of such an approach to perceive software requirements changes. The architecture of ports and adapters is useful if the system has many external integrations (mail service, push messages, databases, reporting system, etc.). The one-way communication with adapters guarantees the integrity of the main algorithmic part of the program. A thorough knowledge of the domain allows you to immediately determine the domain layer. Building a system structure that optimally reflects the domain requires the most time, and it will be costly in the future to correct errors made during the process of defining system layers (interfaces and systems). Domain logic testing is fast due to Unit tests, other tests are easy to write due to the small connectivity between layers. This architecture is not a completely new approach, but it takes the best of OOP, SOLID, DDD and determines how to apply these principles in the best way.

A Stress Management App Intervention for Cancer Survivors: Design, Development, and Usability Testing

BackgroundDistress is prevalent in cancer survivors. Stress management interventions can reduce distress and improve quality of life for cancer patients, but many people with cancer are unfortunately not offered or able to attend such in-person stress management interventions.ObjectiveThe objective of this study was to develop an evidence-based stress management intervention for patients living with cancer that can be delivered electronically with wide reach and dissemination. This paper describes the design and development process of a technology-based stress management intervention for cancer survivors, including the exploration phase, intervention content development, iterative software development (including design, development, and formative evaluation of low- and high-level prototypes), and security and privacy considerations.MethodsDesign and development processes were iterative and performed in close collaboration with key stakeholders (N=48). In the exploration phase, identifying needs and requirements for the intervention, 28 participants gave input, including male and female cancer survivors (n=11) representing a wide age range (31-81 years) and cancer diagnoses, healthcare providers (n=8) including psychosocial oncology experts, and eHealth experts (n=9) including information technology design and developers. To ensure user involvement in each phase various user-centered design and service design methods were included, such as interviews, usability testing, and think aloud processes. Overall, participants were involved usability testing in the software development and formative evaluation phase, including cancer survivors (n=6), healthy volunteers (n=7), health care providers (n=2), and eHealth experts (n=5). Intervention content was developed by stress management experts based on well-known cognitive behavioral stress management strategies and adjusted to electronic format through multiple iterations with stakeholders. Privacy and security issues were considered throughout.ResultsThe design and development process identified a variety of stakeholder requirements. Cancer survivors preferred stress management through a mobile app rather than through a personal computer (PC) and identified usefulness, easy access, user friendliness, use of easily understandable language, and many brief sections rather than longer ones as important components of the intervention. These requirements were also supported by recommendations from health care providers and eHealth experts. The final intervention was named StressProffen and the hospital Privacy and Security Protection Committee was part of the final intervention approval to also ensure anchoring in the hospital organization.ConclusionsInterventions, even evidence-based, have little impact if not actively used. This study illustrates how user-centered design and service design can be applied to identify and incorporate essential stakeholder aspects in the entire design and development process. In combination with evidence-based concepts, this process facilitated development of a stress management intervention truly designed for the end users, in this case, cancer survivors.Trial RegistrationClinicalTrials.gov NCT02939612; https://clinicaltrials.gov/ct2/show/NCT02939612 (Archived at WebCite at http://www.webcitation.org/71l9HcfcB)