No full-text available
To read the full-text of this research,
you can request a copy directly from the author.
A Spiral Model of Software Development and Enhancement
... Ряд вчених присвячували свої дослідження питанням реалізації проектів ДПП [1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17] Башкірова аналізує особливості державно-приватного партнерства на основі чинного законодавства. Вона зазначає, що закон не вимагає статусу приватних партнерів і не враховує статус державних партнерів або їхній досвід реалізації подібних проектів [3]. ...
... (розроблено автором на основі [1][2][3][4][5][6][7][8][9][10][11][12][13][14][15]) ...
... У спіральній моделі Бома на кожному кроці визначаються та оцінюються вимоги до проекту та плануються нові кроки [5,15]. На кожному етапі оцінюється якість проектних завдань, розраховується їхня вартість, ризики зацікавлених сторін і час, необхідний для завершення фази проекту. ...
Public-private partnership (PPP) is becoming a key tool in attracting construction companies to participate in construction projects in Ukraine. This form of cooperation between public authorities and the private sector has the potential to implement significant infrastructure facilities that contribute to economic recovery and raising the standard of living of the population. In the context of post-conflict reconstruction, PPPs enable the pool of resources, finance and expertise of the private sector to be mobilized for the rapid and effective recovery of affected areas. Construction companies can make a significant contribution to the reconstruction of infrastructure, housing stock, social and commercial facilities that have been destroyed or damaged as a result of the conflict. PPP creates favorable conditions for investment in construction and reconstruction, ensuring transparency, protection of investors' rights and stability of the conditions for concluding deals. In addition, this mechanism promotes the development of innovative approaches in the construction industry, the introduction of environmentally friendly technologies and the creation of new jobs. Thanks to the implementation of the PPP in the reconstruction process, Ukraine can carry out a quick and high-quality recovery of the economy and infrastructure, contributing to the stabilization of the situation in the affected territories and raising the standard of living of the population. The advantages of public-private partnership in this area are obvious. First, they can pool resources and expertise from both the public and private sectors. Secondly, the PPP promotes the development of competition and the improvement of the quality of work. When competitive conditions are created, the best quality and most efficient solutions are more easily chosen, leading to the improvement of the national infrastructure. In addition, PPP ensures transparency and openness in project implementation. This ends up building the confidence of both investors and the public, which is a factor in the success of large-scale infrastructure projects. After a period of conflict and crisis, building and restoring infrastructure has become a key challenge for Ukraine. This requires large-scale financial and technical resources, which the state cannot always provide. Therefore, the use of public-private partnership (PPP) becomes a strategic step towards restarting the construction and development of infrastructure.
... Song and Osterweil (1992) maintain that the second and fourth strategies are the most effective. [ (Boehm 1988;Cugola and Ghezzi 1998) Availability of concrete guidance for application Does the method mainly rely on abstract principles or does it provide concrete guidance: abstract principles vs. con- (Boehm 1988; Nandhakumar and Avison 1999) ...
... Song and Osterweil (1992) maintain that the second and fourth strategies are the most effective. [ (Boehm 1988;Cugola and Ghezzi 1998) Availability of concrete guidance for application Does the method mainly rely on abstract principles or does it provide concrete guidance: abstract principles vs. con- (Boehm 1988; Nandhakumar and Avison 1999) ...
... A software development life-cycle is a sequence of processes that an organization employs to conceive, design, and commercialize a software product (Boehm 1988;Cugola and Ghezzi 1998). The software development life-cycle perspective is needed to observe which phases of the software development process are covered by the agile methods under scrutiny. ...
Although agile software development methods have caught the attention of software engineers and researchers worldwide, scientific research still remains quite scarce. The aim of this study is to order and make sense of the different agile approaches that have been proposed. This comparative review is performed from the standpoint of using the following features as the analytical perspectives: project management support, life-cycle coverage, type of practical guidance, adaptability in actual use, type of research objectives and existence of empirical evidence. The results show that agile software development methods cover, without offering any rationale, different phases of the software development life-cycle and that most of these methods fail to provide adequate project management support. Moreover, quite a few methods continue to offer little concrete guidance on how to use their solutions or how to adapt them in different development situations. Empirical evidence after ten years of application remains quite limited. Based on the results, new directions on agile methods are outlined.
... В низці публікацій, серед яких праці [1][2][3][4][5][6][7], наголос робиться на виборі альтернативних та оптимальних варіантів продукування ПЗ серед відомих. У пропонованому дослідженні розглянуто дещо інший підхід, суть якого полягає у формуванні нечітких відношень попарних переваг між альтернативами, побудові перетину множин недомінованих альтернатив, максимальне значення функції належності якого визначає оптимальний варіант процесу розроблення програмного забезпечення. ...
... Аналіз останніх досліджень та публікацій У списку літературних джерел наведено частину іноземних публікацій, дотичних до тематики даної статті. Вони стосуються таких питань: [1] -одна з базових робіт з інженерії програмного забезпечення, містить відомості про різні підходи до розробки ПЗ, їх переваги та недоліки; [2] -офіційний маніфест гнучкої розробки, який визначає основні принципи та цінності гнучкого підходу до розробки ПЗ; [3] розглядає модель спіралі, яка є однією з альтернативних моделей розроблення ПЗ; [4] -описує різні підходи до розроблення ПЗ, вводячи класичні та об'єктно-орієнтовані методології; [5] -уособлює раціональний уніфікований процес як один із варіантів розроблення ПЗ; [6] -зосереджена на практиці використання історій користувачів у гнучких методологіях розроблення ПЗ; [7] -фундаментальна книга з інженерії програмного забезпечення та аспектів його розроблення. ...
... Функція належності згортки Z свідчить, що оптимальною альтернативою процесу розроблення програмного забезпечення із заданими вище відношеннями переваги корисності факторів є варіант 3 x , функція належності якого має максимальне значення. ...
Якість програмного забезпечення визначається через різні атрибути та характеристики, які впливають на його функціональну придатність, зручність використання, продуктивність або ефективність роботи, зручність супроводження, сумісність, надійність, безпеку, рівень тестування. Забезпечення високої якості програмного забезпечення є неперервним процесом, який вимагає планування, ресурсів і уваги до деталей на кожному етапі розроблення та підтримки програмного забезпечення. Від ефективної його реалізації залежить задоволення потреб користувачів та успіх програмного продукту на ринку. У поданій статті засобами теорії ухвалення рішень досліджено та застосовано інформаційну концепцію до вирішення проблеми формування якості програмного забезпечення, оскільки стандарт перераховує лише умови відповідності програмної продукції вказаним характеристикам, не розкриваючи шляхів отримання результату. Суть пропонованого підходу полягає у виокремленні із загальної множини характеристик якості програмної продукції підмножини Парето, що містить домінантні фактори пріоритетного впливу на досліджуваний процес. Для оптимізації процесу формування якості програмного забезпечення на етапі його проектування та розроблення використано метод багатокритеріальної оптимізації з теорії дослідження операцій, суть якого полягає у використанні для прийняття рішення нечітких відношень попарних переваг між альтернативами, ступінь яких можна задати числом на одиничному відрізку. З використанням методу багатокритеріальної оптимізації сформовано нечіткі відношення попарних переваг між альтернативами, що ідентифікуються функціями належності. На підставі засобів матричного аналізу теоретично обґрунтовано та розраховано функції корисності та функції належності згорток, що служать інструментом встановлення оптимального варіанту реалізації процесу розроблення програмного забезпечення. З використанням згорток відношень та множини недомінованих альтернатив розраховано функцію належності фінальної згортки, максимальне значення якої визначає оптимальну альтернативу процесу розроблення програмного забезпечення.
... Still, the challenge of how and when to apply these tools to bring the most value to the development work, remains a topic lacking further research. This has motivated a proposal for a development process [Wolff12] addressing the multi-disciplinary concerns of embedded systems using co-modeling, while adhering to a four phased iterative spiral structure [Boehm88]. Wolff, who suggested this development process, was lecturing one of the classes in the Modeling of Mission Critical Systems course prior to the writing of this thesis. During this course, he proposed a project involving the evaluation of his work. ...
... The development process to be applied during the Autonomous Robot System case study, is divided into the four phases model purpose and requirements, system decomposition, system modeling and validation and verification. Figure 3.1 outlines the corresponding structure, showing these phases in a spiral structure [Boehm88] to emphasize the iterative work-flow. This structure merely serves as a reference, for putting the methodological guidelines into context. ...
An embedded control system often requires a tight association between computational and physical system components. In such cases, embedded system development is difficult, as it requires the collaboration among stakeholders with different backgrounds (software engineers, mechanical engineers, managers etc.). With the constant increase in design complexity, caused by advances in implementation technologies, new ways of approaching embedded system development are needed.This thesis presents an evaluation of a tool-oriented development process and methodology, supporting embedded system development. The philosophy of the development process and methodology, is that design complexity can be managed through collaborative work and multi-disciplinary modeling. To obtain input for the evaluation work, the development process is applied during a case study, involving the development of a route following robot and a model of this. To demonstrate the value of this model, it is simulated to predict route completion times for the physical robot.The evaluation work identifies possibilities and challenges of the development process and methodology, with respect to traditional physicalprototyping. This will support developers in choosing the most optimal way of approaching development. In addition to this, suggestions for extensions to the methodology are provided. These intend to increasethe value the development process and methodology may bring thedevelopment work.
... The software development process model differs from the software development methodology. According to Boehm [3], a method controls through a stage (data specification, allocation of needs, control, etc.), while the model has an interest in providing guidance in a certain order (several steps) in carrying out the tasks that need to be done to complete a project software. ...
... Activities include: 1. Establish and consolidate the development team. 2. Determine the purpose and scope of development.3. Identify the problems that exist in system development. ...
Any organization that will develop software is faced with a difficult choice of choosing the right software development method. Whereas the software development methods used, play a significant role in the overall software development process. Software development methods are needed so that the software development process can be systematic so that it is not only completed within the right time frame but also must have good quality. There are various methods of software development in System Development Lyfe Cycle (SDLC). Each SDLC method provides a general guiding line about different software development and has different characteristics. Each method of software development has its drawbacks and advantages so that the selection of software development methods should be compatible with the capacity of the software developed. This paper will compare three different software development methods: V-Shaped Model, Parallel Development Model, and Iterative Model with the aim of providing an understanding of software developers to choose the right method.
... After proposing new solutions or models for IT infrastructure, tools, processes and actors, the next milestone was to integrate them into a comprehensive methodological framework that support the creation of cyber services. The blueprint of the proposed methodology is based on traditional Software Development Life Cycles (SDLCs), such as Waterfall [42], Spiral [43], Agile software development [44], rapid prototyping [45] and the incremental method [46]. Mapping traditional SDLC phases to the extended PSSDLC phases helps to recognize the design, development, testing and deployment phases of PSSDLC distinctively. ...
... The proposed strategy ensures the seamless exchange of knowledge among participants at different integration levels during design, development and deployment [47]. More detail on this approach is provided in [42][43][44] and [47]. ...
Product Service Systems (PSSs) introduce new business models for enterprises to promote tangible products along with intangible functions or services, thereby incentivising product sustainability with profitability, economic stability and customer satisfaction. However, the unique characteristics of a PSS challenge obsolete product development processes and demand a dynamic change in the complex building blocks of the underlying design and in the development infrastructure to attain high quality services. This implies a need for radical change in the team structure and the team collaboration model, in the organizational structure, technical infrastructure and in the complex process models by taking the complete product life cycle into consideration. This paper, firstly, identifies PSS unique features that challenge the capabilities of existing frameworks to design a standard PSS. In response, new business models are proposed to address the challenges relating to actors’ involvement, technology provision, organizational needs and process workflow modelling. Secondly, these proposed business models are combined into one comprehensive collaborative PSS design and development methodology by modifying existing modelling techniques. An assessment framework based on Goal-Question-Metrics approach and McCall Quality Model is successfully used to evaluate the PSS development methodology and subsequently, the developed framework through a use-case study analysis.
... Yet projects have always been important throughout history as the organizational form used to launch new ventures, develop new technologies and coordinate multiple parties involved in any largescale endeavour, such as building the first canal, railway and telegraph networks (Scranton, 2015;Davies, 2017). In a new synthesis of public and private power, scientists, politicians, "project society" (Boltanski and Chiapello, 2005;Lundin et al., 2015) and "project economy" (Nieto-Rodriquez, 2021) have been proposed to underline the significance of this global phenomenon. Although exact data is difficult to obtain, an indicator of the global economic activity undertaken as projects is fixed capital formation, which has been increasing steadily as a percentage of global GDP. ...
... In recent years, many innovations have been applied to improve the performance of projects in one industry before spreading to others, such as new product development in automotives based on heavyweight project management and concurrent engineering (Clark and Fujimoto, 1991), digital technologies offering a "single source of information" to coordinate complex projects in aerospace, collaborative models of integrated project delivery in construction (Whyte, 2019) and agile development in software (Boehm, 1988). Despite efforts to increase productivity by learning from the experience of executing an ever-increasing number of projects, surprisingly few achieve their cost, time, quality and longer-term objectives. ...
... 1. Requirement Analysis: This stage involved collecting data from stakeholders, including teachers and administrative staff, to understand the specific needs of the system. Interviews and surveys were conducted to gather information about the current challenges and desired features (Boehm, 2006). 2. System Design: The design phase involved creating UML diagrams such as use case diagrams, activity diagrams, and class diagrams to visualize the system's architecture and workflows. ...
The implementation of a web-based leave management system is essential for efficiently handling leave requests for teachers and civil servants in rural, multi-island regency. The existing manual processes are inefficient and prone to delays due to the geographical challenges and resource limitations. This study presents the development of a web-based application using Laravel, PHP, and MySQL to streamline the leave management process. The system allows users to submit, track, and receive notifications about their leave requests in real-time. This paper discusses the system's development, testing, and implementation phases, demonstrating how it significantly reduces administrative burdens and improves efficiency
... To develop this application software for the management and entry of preoperative assessment information, a general methodology was followed, adapting the spiral model for software development and improvement with modifications. (18) Briefly, the spiral model follows six iterative phases: 1) requirements definition, 2) application design, 3) application development, 4) testing and integration into processes, 5) implementation of developments, and 6) operation and maintenance. The development process considered that the application should have the scope of a clinical decision support system and not a complete medical record system. ...
Introduction: Preoperative assessment is fundamental in perioperative medicine, as inadequate evaluation and insufficient patient preparation can increase the risk of anesthetic complications. In Colombia, there are currently no interoperable preoperative clinical information systems that integrate cognitive aids and support for decision-making. Objective: The objective of this project was to develop a functional prototype of an application that integrates perioperative risk estimation and cognitive aids for entering information in the electronic medical record during preoperative assessment in adults. Methods: To develop the PreAnestesiApp® application software, the spiral model was used in six iterative phases: 1) requirements definition, 2) design, 3) development, 4) testing and integration, 5) implementation, and 6) operation. Results: The project enabled the development of a functional prototype of PreAnestesiApp®, an application software that integrates perioperative risk estimation and cognitive aids to prompt documentation in the electronic medical record during preoperative assessment in adults. Since its implementation in October 2013 until December 2023, PreAnestesiApp® has been used in five healthcare institutions, where more than 171,000 preoperative assessments have been performed. Conclusion: PreAnestesiApp® is an application software designed to assist in perioperative risk estimation in adults, with potential use in perioperative medicine education.
... The study revealed that projects with up-to-date UML documentation (Project A) experienced a 30% reduction in maintenance time compared to (Boehm, 1988) those with partial or no documentation (Projects B and C). This finding aligns with previous research by Forward and Lethbridge 1 , who emphasized the importance of visual documentation in improving program comprehension. ...
Software maintenance is a critical and resource-intensive phase in the software development lifecycle, often accounting for a significant portion of total software costs. The Unified Modeling Language (UML) has emerged as a widely adopted standard for modeling software systems, offering a visual representation of system architecture, behavior, and interactions. This study investigates the role of UML in enhancing software maintenance processes through a mixed-methods approach, including case study analysis and developer surveys. The findings reveal that UML diagrams, particularly class and sequence diagrams, significantly improve code comprehension, reduce maintenance time, and facilitate collaboration among developers. However, the effectiveness of UML depends on the accuracy and consistency of the documentation. Projects with up-to-date UML documentation experienced a 30% reduction in maintenance time compared to those without. The study concludes that UML diagrams play a vital role in improving software maintenance efficiency but require proper maintenance and integration into development workflows. Recommendations are provided for organizations to prioritize UML documentation, invest in training and tools, and adopt a balanced approach to maximize its benefits.
... However, these nowadays Since this specific project is highly affected by the stakeholders and context, it is key to have an iterative or feedback-heavy approach. The first can be achieved by applying the Spiral Model proposed by Boehm (1986). It contains similar steps to the waterfall model but repeats it after a feedback procedure on the last completed step. ...
An exploration into the needs and requirements within the professional cleaning sector (cleaners themselves, as well as the cleaning industry), focusing on the possibility of creating tools or technology that are designed for adoption. A Human Centered Design approach is implemented within a Systems Engineering framework to ensure the acceptance and adoption of our results. Several concepts are presented and evaluated with the sector, along with an evaluation of the approach used in this work. The sector is presented with a Market Level Technology Roadmap, and the End-Users with visualized scenarios to facilitate the adoption process.
... The spiral methodology: The spiral methodology was used. It was initially developed in 1986 and reported in paper by the mathematician and software engineering professor Barry Boehm (Boehm, 1995). The spiral methodology is designed to facilitate software development while also reducing the associated risks. ...
Introduction The critical problem of hearing and speech difficulties among thousands of Hondurans is a latent need, and in search of tools that allow the inclusion of the population with this condition is sought through the introduction of a convolutional neural network (CNN) designed for real-time detection and classification of the dactyl alphabet of the Honduran sign language (LESHO). This study represents an important step forward in promoting accessibility and inclusion of the Honduran deaf community, which faces few technological solutions adapted to their needs. Methods A proprietary dataset comprising more than 8,000 images with various angles and gestures was meticulously constructed, ensuring robust training and evaluation of the model. Spiral research methodology was employed to iteratively refine network performance, with an emphasis on accuracy and real-time deployment capabilities. Results The final model showed exceptional results during the testing, achieving a mean average precision (mAP) of 98.8%, a precision of 97.4%, and a recall of 97.7%. These metrics underscore the reliability of the CNN in recognizing both static and dynamic gestures with minimal errors. Conclusion The model’s capacity to generalize indicates its potential for further applications, such as full sign language interpretation and expanded vocabulary training
... The importance of risk management for software engineering in general and requirements engineering in particular has been addressed in several risk management approaches tailored to software engineering processes [8]. Already the spiral model of Boehm [9] explicitly includes risk management within software development. The Riskit method [10] provides a sound theoretical foundation of risk management with a focus on the qualitative understanding of risks before their possible quantification. ...
Background: The sensitivity of Requirements Engineering (RE) to the context makes it difficult to efficiently control problems therein, thus, hampering an effective risk management devoted to allow for early corrective or even preventive measures. Problem: There is still little empirical knowledge about context-specific RE phenomena which would be necessary for an effective context- sensitive risk management in RE. Goal: We propose and validate an evidence-based approach to assess risks in RE using cross-company data about problems, causes and effects. Research Method: We use survey data from 228 companies and build a probabilistic network that supports the forecast of context-specific RE phenomena. We implement this approach using spreadsheets to support a light-weight risk assessment. Results: Our results from an initial validation in 6 companies strengthen our confidence that the approach increases the awareness for individual risk factors in RE, and the feedback further allows for disseminating our approach into practice.
... To encourage re-use the MammoGrid software was delivered through a set of evolving prototypes following a form of 'spiral model' [19] development (including 'stages' of planning, specification, evaluation, and development for each prototype version) in which the clinical user community provided input in each loop of the spiral. Release of the staged prototypes was planned to coincide with project milestones and the delivery of tested MammoGrid services. ...
Objectives: Grid-based technologies are emerging as potential solutions for managing and collaborating distributed resources in the biomedical domain. Few examples exist, however, of successful implementations of Grid-enabled medical systems and even fewer have been deployed for evaluation in practice. The objective of this paper is to evaluate the use in clinical practice of a Grid-based imaging prototype and to establish directions for engineering future medical Grid developments and their subsequent deployment. Method: The MammoGrid project has deployed a prototype system for clinicians using the Grid as its information infrastructure. To assist in the specification of the system requirements (and for the first time in healthgrid applications), use-case modelling has been carried out in close collaboration with clinicians and radiologists who had no prior experience of this modelling technique. A critical qualitative and, where possible, quantitative analysis of the MammoGrid prototype is presented leading to a set of recommendations from the delivery of the first deployed Grid-based medical imaging application. Results: We report critically on the application of software engineering techniques in the specification and implementation of the MammoGrid project and show that use-case modelling is a suitable vehicle for representing medical requirements and for communicating effectively with the clinical community. This paper also discusses the practical advantages and limitations of applying the Grid to real-life clinical applications and presents the consequent lessons learned.
... A software process is a set of activities that leads to the production of a software product [11]. There are a number of different software processes such as the waterfall model [12], the Spiral Model [13], and the component-based model [14]. ...
This paper examines two senior capstone experiences developed as augmented reality tables over the past two years. Both projects were public facing efforts that required working implementations. The first project was deployed at an astronomy center and focused on interactions between land use and ecological aspects of Hawaii Island while the second project focused more on historical sites on the same island. Both projects leveraged brownfield development and existing code bases to allow for student success in spite of the impacts of the COVID19 pandemic.
... Figure 2 shows the exploratory design process as a cyclic model, which combines the double diamond of the British Design Council [16] and the innovation turbine [15], integrating older ideas of a spiral and iterative development process, e.g. described by Boehm [17]. The cycles of the exploratory design process are usually structured in two stages: Stage one is opening up the space and looks out for new solutions, stage two is closing down the space again to a manageable selection. ...
With ever-shorter product and technology lifecycles, companies are pressured to shorten the time-to-market for new products. This requires faster and more agile design processes both in product development and in setting up new production environments. Technological advances in the field of immersive technologies, such as extended-reality, provide tools to address these challenges and increase process agility. One tool is virtual prototyping. Virtual prototyping enables the involvement of users and other stakeholders early in the development process. Currently, the use of virtual prototypes is largely limited to design reviews and assessments of existing system concepts. Inspired by the paradigms of creative collaboration (co-creation) and exploration, we have developed a participatory design method where users and other stakeholders can explore and directly adapt virtual prototypes within the virtual environment to find the optimal design concept. In this paper, we present an exploratory and stakeholder-driven design paradigm and its application in the context of two industrial use-cases in product development and production training. We illustrate how virtual exploration environments can be built, how the exploration and design process is orchestrated with the involvement of all relevant stakeholders, and how the results and findings can be utilized in later system development phases.
... Beginning in the 1980s, project management began to extend beyond its traditional applications in engineering and technology, becoming a tool for organizational change and improvement. Another significant development during this decade was the introduction of iterative project management approaches, as opposed to traditional sequential methods, which eventually evolved into the agile methodologies we recognize today (Boehm, 1986). (Takeuchi and Nonaka, 1986) proposed an iterative approach to product development projects like rugby game as opposed to traditional sequential approach. ...
This study examines the impact of Industry 4.0 on the concept of leadership approaches. The research aims to compare leadership theories before and after Industry 4.0, determine how leadership roles have evolved in agile project management, and identify effective leadership styles. The study employs literature review and qualitative research methods, specifically using focus group studies. Two separate focus group studies were conducted through online meetings and face-to-face sessions to thoroughly examine the approaches of executives from companies who have mature project management offices in Turkey. Data were obtained by transcribing the audio recordings of discussions during focus group sessions and comparing them with researcher notes. The study extensively examines the impacts of identified leadership styles, determined through literature review, on the management of agile project teams. Findings indicate that leadership styles such as visionary, organizing, relational, and social leadership play significant roles in agile project management. Additionally, leadership personality traits observed in each of these styles have been identified. The results underscore the need to redefine leadership approaches and highlight the effects of Industry 4.0 on project management. By linking the characteristics of leadership styles and their impacts on agile teams with the literature, the study contributes to future leadership research and practices. In this context, it emphasizes the development of technological competencies for organizations to succeed and the need for flexible and innovative organizational structures. Furthermore, it suggests that leaders in the digital transformation processes brought by Industry 4.0 should possess skills to facilitate their employees' adaptation processes. This study contributes significantly to academic literature and business by exploring leadership evolution in Industry 4.0 and redefining roles in agile project management, emphasizing ongoing focus on development and innovation in leadership.
... These come in many flavors like the often mentioned waterfall methods in software engineering that follow a process outlined below ( (Boehm, 2000). The crucial assumption and philosophy is certainty in lock step within each key process node while going through the process. ...
Executive Summary Traditional and Modern methodologies for project management and team management has been touted to be very different based on assumptions, principles, practices, processes, and limitations. Further study of literature, research, and field experience portray a more dynamic story of interplay between the applicability and inappropriateness of various methodologies. This depends on the context within which different types of projects operate, strategic drivers that underpin it, economic fuel that constrains or liberates resource provisioning tactics, and people aspects of any social constructs that characterises projects, companies, and institutions more than processes, products, and technologies. The difficult decision points in pursuing profound and impactful human endeavors are rarely those that chooses between what is correct or wrong, nor whether it is truthful or false. What is profoundly difficult is the choice between two correct notions or different workable solutions; conversely, the same can be said between the discernment and choice between the lesser of two evils. What may break the stalemate is simple diligence and the wisdom to go beyond surface noise competing for attention and to understand the signal that beckons to be perceived by which directions and decisions must be made. Ultimately, the wisdom may prove to be a synthesis rather than a contrast of choices; whether that fusion of various lenses and thinking hats is an easy goal or a hard-fought win borne of experience and erudition is a different matter. But, persevere, we must, for so much is at stake. If history is any guide, the consequences of project failures impacts the project teams less but hurt the stakeholders that we frequently ignore more: the taxpayers for their sacrifices and our colleagues who stand to benefit less from projects individually but may helplessly lose livelihoods should those in charge neglect the significance of the responsibility they bear.
... Although concepts like iterative development had existed before (Boehm, 1988), it was the release of the "Manifesto for Agile Software Development" in 2001 (Manifesto for Agile Software Development, 2001) that brought about a radical shift in our understanding of project management, injecting a breath of fresh air into the discipline. However, several challenges still need to be addressed (Moreira, 2013;Pelrine, 2011): ...
Managing software development projects is a complex endeavor due to the constant emergence of unforeseen events that deviate from initial expectations. A competent project leader is not just someone who follows the planned course but also adept at handling and minimizing inconveniences, ultimately striving to achieve results that align as closely as possible with the desired outcome. However, individuals involved in technological development often cling to familiar tools that have previously yielded positive outcomes, even when those tools may not be the best fit for the current project context. The Agile Manifesto has significantly transformed project management, infusing the discipline with a fresh perspective. Nevertheless, there remain several challenges to overcome. In this article, we aim to provide a guide that addresses these difficulties and minimizes their impact. We explore the selection of key factors that adequately describe a project's complexity, which can subsequently be used in conjunction with the Cynefin framework to categorize management strategies, techniques, and tools based on their applicability to specific complexities. Additionally, we offer insights on adapting project management approaches throughout the project life cycle in response to changes in reality, utilizing the dynamics outlined by the Cynefin framework. Finally, we present suitable strategies, techniques, and tools for agile project management based on the complexity context assigned by the Cynefin framework.
... El ciclo de vida de desarrollo de software (SDLC) es un marco o metodología de trabajo utilizado para desarrollar, implementar y mantener software. [11][12][13] El SDLC formaliza las tareas o actividades en varias fases con el objetivo de mejorar la calidad del software centrándose en el proceso. La formalización de los pasos tiene como objetivo permitir la medición y el análisis para realizar mejoras mientras se monitorea el progreso y los costos. ...
Abordar la seguridad en etapas demasiado avanzadas del SDLC, después de haber completado las tareas más importantes de análisis, diseño y desarrollo, genera problemas de eficiencia y seguridad, ya que el costo de solucionar vulnerabilidades aumenta mientras más avanzada sea la fase del ciclo, y puede requerir que se vuelva a desarrollar y probar todo el software. Asumir en la empresa DATYS un SDLC tradicional ha impactado en que su proceso productivo, si bien es eficaz, no es del todo eficiente, ya queen general-las soluciones de software para ser certificadas y liberadas, deben pasar múltiples iteraciones incurriéndose en horas hombre extra plan, y dilatando en muchos casos su culminación. En este artículo se proyecta la transformación del SDLC de la empresa DATYS a un ciclo de vida de desarrollo seguro (SSDLC) a partir de integrar, de manera sistémica, los aspectos de seguridad en cada fase del ciclo de vida de desarrollo.
... It is estimated that 80% of software organizations use OOD in some form (OMG, 2018); this implies that much of the internet, search engines, smart phones, and mobile apps, the advancements of the last few decades, have been made using OOD. From a process perspective Waterfall was falling out of favor in the 80s due to its inflexible nature and replacements appeared, such as spiral which introduced iterative principles and allowed for flexibility and adaptation to changing requirements (Boehm, 1986). However, it was the 90s experimentation with agile methods and the 2001 publication of the Agile Manifesto (Beck et al., 2001) that would give rise to 71% of software projects today using agile methodologies such as Scrum, Extreme programming, and Lean (Statista, 2023). ...
Extending the work of Downing & Badar (2022), this paper presents the history of software, artificial intelligence, software quality assurance, and a software QA architecture called the Quality Assurance Machine (QAM). Using Design Science Research (DSR), the QAM was extended to support software containing ML models. Using descriptive statistics and hypothesis testing, this paper answers the research question: is QAM effective for assuring the quality of software containing ML? Future DSR efforts will add a Process Quality engine to the QAM to monitor and improve the processes used to create software and models.
... Many aspects of the Agile approach have been in use in systems development since the 1950s and increasingly applied in the 1990s [6]. For example, Spiral Development (1986), Rapid Application Development (1991), the Unified Process (UP) (1994), and Extreme Programming (XP) (1996), among others, all contained features or characteristics now attributed to Agile Development [7,8]. However, the writing and public release of the Agile Manifesto [4] has generally been regarded as the birth of Agile Development [9]. ...
Agile Development has been an integral part of project management and product development since its formal introduction by the Agile Manifesto in 2001. Subsequently, Agile has rapidly gained in popularity, leading to significant improvements in on-time delivery and managing costs, as well as successful delivery of the required scope for information systems (IS) projects. Agile has even moved beyond the IS domain into other business applications. This success may be tempered somewhat by the gaps in the Agile Development process that still exist, such as a lack of complete understanding of the process or the culture changes necessary to achieve larger benefits and the complexity of integrating Agile-developed products into existing IT infrastructure. However, there is also great promise in extending Agile by incorporating new tools and concepts and applying Agile development to novel and emerging problem domains. This paper proposes a Framework for Agile Development that can be used to explore existing results from Agile development, as well as to identify future possibilities and emphasize the importance of teaching Agile development in order for it to have further influence on practice.
... Such a view is a central idea for the systems engineering design process and the Human-Centered design process (HCD) [6]. Many popular system engineering design process models, such as the "Vee" model [7] and the spiral model [8], emphasize iterative approaches that involve various stakeholders in the design processes. The HCD approach guides designers to understand and respond to the needs of user(s), reframe problems, and iterate to develop their solutions. ...
... XP seeks to support timely and economical development of high-quality software that meets user requirements at the time of delivery. XP utilizes an iterative approach that is helpful in developing, modifying, and maintaining systems more quickly and more successfully [2,5]. It is these short iterations that provide the flexibility to accommodate the changes requested by the customers and allows the customer to increase competitiveness in the market [47]. ...
Background: Software Defect Prediction (SDP) is a vital step in software development. SDP aims to identify the most likely defect-prone modules before starting the testing phase, and it helps assign resources and reduces the cost of testing.
Aim: Although many machine learning algorithms have been used to classify software modules based on static code metrics, the k-Nearest Neighbors (kNN) method does not greatly improve defect prediction because it requires careful set-up of multiple configuration parameters before it can be used. To address this issue, we used the Non-dominated Sorting Genetic Algorithm (NSGA-II) to optimize the parameters in the kNN classifier with favor to improve SDP accuracy. We used NSGA-II because the existing accuracy metrics often behave differently, making an opposite judgment in evaluating SDP models. This means that changing one parameter might improve one accuracy measure while it decreases the others.
Method: The proposed NSGAII-kNN model was evaluated against the classical kNN model and state-of-the-art machine learning algorithms such as Support Vector Machine (SVM), Naïve Bayes (NB), and Random Forest (RF) classifiers.
Results: Results indicate that the GA-optimized kNN model yields a higher Matthews Coefficient Correlation and higher balanced accuracy based on ten datasets.
Conclusion: The paper concludes that integrating GA with kNN improved defect prediction when applied to large or small or large datasets.
... Product development management aims to optimize the implementation of functionalities (in the case of software development, programming, unit testing, QA, and product documentation) to ensure that the final product will achieve the highest possible product value with the lowest cost and the lowest risk [35]. The different management approaches aim to achieve this single goal, such as Agile [36], Incremental [37], Prototyping [38], Spiral [39], V model [40], and Waterfall [41]. However, an optimized end product can only be achieved if product management approaches receive an optimized set of functionalities as input. ...
Purpose: The gap between software development requirements and the available resources of software developers continues to widen. This requires changes in the development and organization of software development. Objectives: Presented is a model introducing a quantitative software development management methodology that estimates the relative importance and risk of functionality retention or abundance, which determines the final value of the software product. Method: The final value of the software product is interpreted as a function of the requirements and functionalities, represented as a computational graph (called a software product graph). The software product graph allows the relative importance of functionalities to be estimated by calculating the corresponding partial derivatives of the value function. The risk of not implementing the functionality is estimated by reducing the final value of a product. Validation: This model has been applied to two EU projects: CareHD and vINCI. In vINCI, the functionalities with the most significant added value to the application were developed based on the implemented model and those that brought the least value were abandoned. Optimization was not implemented in the CareHD project and proceeded as initially designed. Consequently, only 71% of the CareHD’s potential value has been realized. Conclusions: Presented model enables rational management and organization of software product development with real-time quantitative evaluation of functionalities impacts, assessment of the risks of omitting them without a significant impact. A quantitative evaluation of the impacts and risks of retention or abundance is possible based on the proposed algorithm, which is the core of the model. This model is a tool for rational organization and development of software products.
This chapter presents a broad overview of software engineering and discusses various software lifecycles and activities in software development. We discuss requirements such as gathering and specification, software design, implementation, testing, and maintenance. The lightweight Agile methodology is introduced, and it is mainstream in industry.
Negotiation emerges as an inevitable concept not only in design, but also in any
context including human relationships. However, the systematical integration and
awareness of successful negotiation into design processes is still considered a
new research area. The implementation of this systematical negotiation, increases
the efficiency of the design process as well as the design outcome. The design
negotiation enables the formation of a comprehensive understanding towards the
personal / corporate interests and values. This leads the stakeholders to generate
personal negotiation strategies within a framework of objective goals and unique
contexts. Therefore, this study primarily aims to unveil the designers’ individual
professional strategies through the design negotiation dynamics. In order to obtain
objective data on the research questions of this study, 10 in-depth interviews and
consulting sessions were made with Turkish expert, freelance industrial designers,
forming an independent sample from organizations’ internal dynamics. The
analysis and interpretation process was made through individual and collective
analysis, later to be comparatively discussed with literature. It was found that, the
sectoral survival and sustainability of a designer required the protection of
individual interests through developing specifically social common strategies,
individual tactics and social / designerly tools for design negotiation. As a result,
the strategy patterns found may be an outcome of the collective system
requirements of Turkey as a context. In addition, the tactical and instrumental
diversities may be a consequence of the sub-context requirements shaped by
scalar and sectoral variables.
Having a well-managed student information system is key to improving the way an education system functions, however having the traditional manual system most of the times lead to fragmented data, redundant process which wastes a lot of time. These make it hard to keep up with student records which also create inefficiencies for both the administration and also the teachers. As a result, it becomes difficult to manage tasks like student enrollment, grades, and attendance, ultimately affecting decision-making. To solve these issues, my project targets developing a more comprehensive Students Records System (SRS) that automates and centralizes the management of student records through digitizing data, this system aims to automate administrative tasks and improve communication between students, faculty, and staff. . This approach helps reduce the errors and cuts down on redundancy, and saves time for everyone involved in the safe guarding and storing the records. The system’s design will prioritize data accuracy, ease of use, and security. In this era schools and universities now rely more on technology to handle academic and administrative tasks, a well-designed Student Record System (SRS) helps streamline operations, making things more efficient for both students and the institution. The Students Records System (SRS) will be designed to revolutionize the way educational institutions manage and use student information by providing a centralized platform for storing, retrieving, and analyzing data. With the help of consultations with stakeholders and surveys and research, I was able to find the weaknesses of the existing manual systems, I there after developed a systematic approach to address these challenges. In conclusion, the SRS is a significant advancement in how student information is managed. It offers a solution tailored to the unique needs of educational institutions. By streamlining administrative processes, improving communication, and giving stakeholders access to actionable insights, the SRS lays the foundation for better performance and improved student outcomes.
El proceso de inscripción en la Coordinación de Lenguas Extranjeras (CLE) del Tecnológico Nacional de México (TECNM) campus Ciudad Juárez, solía realizarse manualmente, lo que generaba errores en los datos, largas filas y un tiempo prolongado de inscripción. Además, el pago debía realizarse en el banco y el alumno regresaba a la institución a presentar el comprobante, extendiendo el proceso hasta dos semanas. Para solucionar estas problemáticas, se adaptaron dos plataformas: El Sistema Integral de Servicios Administrativos y Estudiantiles (SIISAE) y el Sistema Integral de Lenguas Extranjeras (SIILE). El SIISAE gestiona un pre-registro, con la finalidad de contar con un estimado de los alumnos que ingresarán al CLE; también se genera su referencia bancaria para el pago de forma automática, permitiendo a los estudiantes obtener este documento automáticamente y realizar el pago por transferencia o en el banco; posteriormente, el alumno deberá cargar el comprobante de pago en la plataforma para su validación, eliminando con ello traslados a la institución y reduciendo tanto errores administrativos como tiempo. El nuevo sistema optimizó y automatizó el proceso de inscripción, reduciéndolo a solo dos días. Gracias a esta implementación, en el semestre febrero-junio 2025 inscribieron 635 alumnos de manera eficiente, logrando registrar 337 estudiantes en una hora aproximadamente. Además, los alumnos pueden acceder al SIILE para consultar horarios y docentes, facilitando la selección del grupo. Con estas mejoras tecnológicas, el CLE optimiza la experiencia estudiantil, disminuye la carga administrativa y garantiza un proceso de inscripción más ágil para todos.
This research explores the evolutionary pathway of agile frameworks within IT project management, focusing on enhancing product delivery outcomes. The introduction provides an overview of the Evolutionary Pathway concept, introduces agile frameworks, and emphasizes the importance of improved product delivery in IT projects. The evolution of Agile in IT project management is traced through historical context, key milestones, and widespread acceptance trends. Examining agile frameworks elucidates their principles, popular methodologies like Scrum and Kanban, and their application in IT project management contexts. Benefits of Agile methodologies include faster time-to-market, stakeholder engagement, adaptability, and product quality improvement, though challenges such as resistance to change and scaling issues persist. Strategies for successful agile adoption encompass leadership support, team training, customization, and feedback mechanisms. Case studies offer real-world insights and comparative analyses of agile approaches. Future directions discuss innovations, integration with other frameworks like DevOps, and the impact of emerging technologies on Agile practices. In conclusion, agile frameworks are deemed crucial for enhanced product delivery, with recommendations for organizations and suggestions for future research and practice provided.
The paper examines the impact of the war on the hospitality industry, which is facing an acute crisis. To overcome this challenge, businesses need a comprehensive transformation, including the introduction of innovations, improved service levels and the expansion of information campaigns, including in the digital environment. The post-war economic recovery is expected to be accompanied by a decline in wages and staff reductions, but the growing number of jobs will enable development in new areas such as automation and robotics. Automated management systems for the hotel business are becoming increasingly important as they help to reduce costs and increase productivity. In particular, the authors describe an algorithm for building enterprise management information systems (EMIS) that covers all stages from concept development to project support, emphasising the importance of security and flexibility in planning and implementing the system. The algorithm for implementing an IMS begins with a conceptual study, which involves a survey of the facility, formulation of goals and objectives, analysis of documents and identification of software tools. After that, a technical assignment is developed that outlines the basic requirements for the future system. The design stage includes choosing a structural concept, defining database parameters, and creating a set of project documentation. Implementation includes the creation of software and the development of a user interface. The final stages include testing, putting the system into operation, and staff training. The final stage of system maintenance involves warranty service and adjustments to ensure the system's reliable operation in the long term. Particular attention is paid to the creation of databases, which are the basis for the information system. Testing and experimental operation is the final step in the development process, ensuring the system's adaptation to real operating conditions. Implementation of an IMS at modern hotel enterprises allows achieving qualitative changes in management, contributing to safety, speed of operations, saving management resources and making timely management decisions. The article also discusses the conditions necessary for the successful implementation of an IMS: choosing a reliable manufacturer, checking compatibility with local standards, professional qualifications of the team and financial feasibility. A systematic approach to the development and integration of information technologies in the management of hospitality enterprises ensures the effectiveness of solutions, improving their quality and productivity.
При разработке сложной оптической техники трудоемкой задачей является выбор шагового двигателя. Разработана методика по оценке мощности шагового двигателя, основанная на использовании САПР SOLIDWORKS и Matlab/Simulink. Для механизма панкратического объектива разработана динамическая модель, позволяющая определить необходимый крутящий момент, развиваемый двигателем, с учетом воздействия пружин, сложного профиля и программного изменения угла поворота кулачкового механизма. Данная методика включает в себя несколько этапов. Сутью первого этапа является получение из 3D-модели САПР SolidWorks модели в среде MatLab. Сначала 3D-модель экспортируется в xml-файл данных с помощью транслятора Simscape Multibody Link. После того как произведен экспорт в xml-файл, модель импортируется непосредственно в Simscape Multibody Model. При трансляции, телам модели Simulink передаются соответствующие массо-инерционные характеристики компонентов сборки SolidWorks, а также сопряжения между телами 3D-модели SolidWorks, которые преобразуются в степени свободы динамических тел Simulink. Фактически при трансляции осуществляется построение динамической модели механизма. Для обеспечения визуализации модели Simulink геометрия элементов сборки SolidWorks передается с помощью транслируемых stl-файлов. Вторым этапом является доработка полученной динамической модели.
This paper presents a comparative study of the Waterfall model and sprint-based work tasks in project management. The Waterfall model, known for its linear and sequential approach, has been a cornerstone of software development since its inception in the 1970s. On the other hand, sprint-based work tasks, primarily used in Agile frameworks like Scrum, represent a flexible, iterative approach suited to modern, dynamic project requirements. This paper explores the key characteristics, advantages, and limitations of both models, as well as the contexts in which each is most effective ending with real time examples. Through a detailed analysis, this paper provides insights into selecting the optimal project management methodology based on project requirements, team dynamics, and organizational goals. Keywords Waterfall Model, Agile, Scrum, Sprint, Project Management, Software Development Life Cycle (SDLC), Iterative Development, Sequential Development
The choice of project management methodology is a critical factor in the success of public sector projects, which often operate under complex regulatory environments and serve a wide range of stakeholders. Agile and Waterfall methodologies represent two fundamentally different approaches to project management, each offering distinct benefits and challenges. In this paper, a detailed comparative analysis is presented, focusing on the use of Agile and Waterfall methodologies in public sector projects, particularly within the context of IT and non-IT projects. Drawing on real-world experiences from managing projects in the public health and government IT systems domains, this study examines the advantages and limitations of each methodology. Waterfall's linear, structured approach is well-suited for projects with clearly defined requirements and low tolerance for change. Its strengths lie in its predictability, detailed documentation, and ability to meet stringent regulatory compliance, making it a preferred choice for projects that demand precision and control, such as infrastructure developments or large-scale government procurement initiatives. However, the rigid nature of Waterfall can be a disadvantage in environments where flexibility and quick adaptation to change are necessary. On the other hand, Agile offers a flexible, iterative approach that emphasizes continuous stakeholder engagement, adaptability, and incremental delivery of value. This makes Agile particularly effective in government IT projects and public health initiatives, where evolving requirements and dynamic environments require the ability to pivot and adapt rapidly. However, Agile poses its challenges in public sector projects, especially when it comes to balancing flexibility with regulatory and compliance requirements, as well as navigating the traditionally bureaucratic structures of government organizations. This paper explores key considerations such as regulatory adherence, stakeholder involvement, risk management, and cultural adaptation within public sector projects. By analyzing the strengths and limitations of both methodologies through practical examples, the study concludes that while Waterfall provides stability and is suitable for projects with well-established scopes, Agile's adaptability makes it a better fit for projects that need iterative feedback and responsiveness to change. Agile methodologies may offer a more effective approach for public sector projects, especially in technology-driven fields like public health IT systems.
Development of complex systems through the application of Model‐Based Systems Engineering (MBSE) will require the creation and maintenance of multiple models, created using multiple languages. Hence, structuring the models such that there is efficient support for incremental development requires some foresight. Having models with multiple or unclear purposes may introduce situations where parts of the organisation will ask for modification for representing a desired future system state, whereas other parts of the organisation require it to remain unchanged in order to represent the present state. This paper introduces a structure with associated terms and characteristics of the different model types in order to provide guidance to an organisation. In particular, it extends previous work on model tenses, capturing different time perspectives/purposes on the models, to also include model usage for keeping track of the actual state of a realised system instance. For example, the concepts of Digital Twin and Digital Shadow are discussed and conceptualised. As such, the contributions made in the paper allows an organisation to reason about the completeness of their modelling methodology and its applicability to support incremental development. Above all, the paper spells out clearly that for a complex heterogeneous system, any request for an update to “the model” will prompt the response “Excuse me Sir/Madam, which model?”.
Este libro no proporciona planes de estudios específicos para cada disciplina de las CS y su relación con las matemáticas. En cambio, sugiere y ofrece muchas oportunidades, entre las que se incluyen actualizar el paradigma de la enseñanza y la educación con base en el aprendizaje basado en proyectos, pasar del conocimiento por competencias a los logros de aprendizaje e involucrar a los graduados para explotar los beneficios de las habilidades, destrezas y capacidades en el lugar de trabajo. El libro es el resultado de un esfuerzo cooperativo sin precedentes entre varias redes académico-científicas que abarcan diversos países. Como uno de los trabajos que buscan el objetivo mencionado, proporciona introspección y análisis de diversas disciplinas informáticas basadas en directrices curriculares actuales relacionadas con las matemáticas, y que son producto de muchos años de experimentación y refinamiento por actores de la industria, profesores, investigadores y facultades de otras disciplinas.
Bibliography: Petz, Andrea; Miesenberger, Klaus: Association ICCHP, Joh.-Wilh.-Klein-Strasse 3, 4040 Linz, Austria office@icchp-aaate.org / +43 664 60 2468 864 Aim and scope: To communicate and complete knowledge on ICT, AT and Accessibility for/with people with disabilities and older adults and connect research in these domains with the necessary practical background and user related aspects. Editorial Welcome to the 3rd edition of our Open Access Compendium! After an intense cooperation with AAATE in 2022, we represent again ICCHP and "Future Perspectives on AT, Accessibility and (e)Inclusion", published on the occasion of ICCHP 2024 at Linz University, Linz, Austria. After the Open Access Journal´s first two editions, the "Future Perspectives of AT, eAccessibility and eInclusion", ICCHP continues this publication covering a more practical view on AT, Accessibility, ICT with and for people with disabilities and older adults. These last 2 years were subject to significant changes in ICT and all connected areas-AI and Large Language Models revolutionize education and term paper writing. E.g. Chat GPT writes Program Code-and Graphical AI-like e.g. Midjourney draws the pictures to it. Data Scientists already talk about "intelligence" and the threat of Super-Villain AIs manipulating political systems and elections. AI also shows a merciless picture on how "society" or at least "the internet" sees and discusses "disability", "inclusion" and "Assistive Technology". In case you did not do so already, try it and ask e.g. Midjourney to draw a picture by just giving the terms Disability or Assistive Technology and see firsthand some main issues in the societal discourse that keeps us all from reaching our goals, accessibility and participation for "All". You will not see edge of tomorrow tech, nor laptops or tablets used by a person with a disability to take part in education or society-in most cases you see people in old, not fitting wheelchairs-and they are in most cases alone, standing in due distance from "where life is". Asking ChatGPT to "Write 200 words in editorial style elaborating the potential of artificial intelligence, large language models and pervasive computing in making IT, internet and life more accessible to people with disabilities in the future also mentioning privacy and data security issues" delivers the following: "Artificial intelligence (AI), large language models (LLMs), and pervasive computing hold tremendous promise in revolutionizing accessibility for individuals with disabilities. These technologies can transform how people interact with IT and the internet, fostering a more inclusive society. AI, with its capacity to learn and adapt, can be integrated into assistive devices to enhance their functionality. For instance, voice recognition and natural language processing (NLP) can empower those with mobility impairments to control computers and smart home devices through voice commands. Similarly, computer vision can aid visually impaired individuals by describing their surroundings or reading text aloud. LLMs like GPT-4 can significantly advance communication aids for individuals with speech or language disorders. By understanding context and generating human-like text, these models can assist in generating coherent, contextually appropriate responses, facilitating smoother communication for those who struggle with conventional methods. Pervasive computing, embedding computing power in everyday objects, ensures constant support and accessibility. Smart environments can adapt to users' needs in real-time, offering tailored assistance and reducing barriers to accessing information and services. However, these advancements also raise significant privacy and data security concerns. The reliance on vast amounts of personal data necessitates robust data protection frameworks to prevent misuse. Ensuring that AI systems are transparent, secure, and respect user privacy is crucial. As these technologies evolve, balancing innovation with ethical considerations will be vital to create a truly inclusive digital future." So then-let's create, use and work together and make the best of this potential to foster and promote our mission in the right direction! We hope that this third edition of our Open Access Compendium delivers memories, knowledge and also new aspects to you-and to come back in 2026; again renewed, bigger and even more relevant and exciting.
Purpose. To develop a method of updating the regression model for the normalization of specific energy consumption in the presence of frequent and significant changes in the energy efficiency of the production process. Methodology. Analysis of existing methods of updating regression models, comparison of their possibilities, and synthesis of the method of updating the model in conditions of frequent and significant changes in the energy efficiency of the production process. Findings. It was established that in the presence of a significant number of possible variants of structural and mode changes in the energy consumption of the control object, the introduction of associated variables into the regression model is problematic, as it requires an increase in the number of experimental data in conditions of their expected heterogeneity. The flaw of the well-known regression model for normalizing the power consumption of the object of control is revealed, which consists of the fact that the model does not take into account the last values in the sequence of their appearance of experimental data obtained in the process of energy efficiency control. This reduces the accuracy of predicted energy consumption values. It is proposed to update the regression model every time after performing the energy efficiency control and sample adjustment. Adjustments are implemented by checking the homogeneity of the obtained experimental data, followed by their addition to the elements of the existing sample and removal (if necessary) from the sample of outdated data. The defined sequence of adjustment of the initial data allows timely updating of the model and implementation of the forecast of specific energy consumption, entering data reflecting the latest changes that occurred in the facility's energy supply. The proposed method of updating the model implements the approximation in time of the moment of energy efficiency control to the moment of obtaining experimental data for building a regression dependence for normalizing energy consumption values. This helps to increase the accuracy of the forecast of normalized values. A significant change in the conditions of production of products with a violation of the homogeneity of data is accompanied by a transition to the transitional mode of adjustment, where it is proposed to reduce the number of elements of the existing sample, ensuring the sequential removal of the elements furthest from the next moment of control. Extraction continues until data homogeneity is achieved. During the daily control of the efficiency of electricity consumption, the change in the values of the regression model coefficients in the process of its renewal reflects the changes in the object's electricity consumption that occurred over the last day. This allows you to separate their impact from the impact of changes that occurred earlier and to assess the level of this impact. Originality. For the first time, the shortcomings of the existing methods of updating regression models in the conditions of frequent and significant changes in the energy efficiency of the production process were identified. A method of updating the model under these conditions has been developed, which involves adjusting the sample of experimental data by changing the number of its elements and checking the homogeneity of the data. Practical value is that the sequence of actions during the implementation of the developed method of updating the regression model is defined, which allows for an increase in the accuracy of calculating the normalized values of specific energy consumption.
En France, J.-L. Le Moigne a apporté une nouvelle perspective à l’ingénierie des systèmes d’information (SI), en promouvant l’analyse et la modélisation des systèmes. L’utilisation de modèles a apporté une contribution majeure à la conception des SI. Les méthodologies systémiques se sont multipliées à partir des années 1980, avant de céder la place aux approches agiles. Plusieurs facteurs ont contribué à repenser le rôle de la modélisation dans la conception des SI : la faible adoption des modèles par les utilisateurs, l’émergence d’une vision du développement des SI comme un processus social et la demande accrue d’innovation. Les approches récentes ont fait une place aux métaphores comme outil d’appréhension de la complexité des SI, à la fois dans les projets et dans la recherche. Nous présentons diverses utilisations d’une approche métaphorique dans la conception de SI. Nous décrivons ensuite comment nous avons utilisé des métaphores du pouvoir pour étudier les pratiques de leadership dans un projet de développement SI mené en mode agile.
This chapter discusses ethical software engineering and we discuss notable failures such as the space shuttle disaster and the defective Therac-25 radiotherapy machine. We discuss the extraordinary Volkswagen emissions scandal, where engineers designed a “defeat device” that would allow Volkswagen cars to pass emission tests in the United States.
In this chapter, a method is proposed for promoting ICT engineering safety learning from crisis management. In particular, ICT engineering arena human factors play a crucial role in promoting ICT system safety. The Tokyo stock exchange was crushed on the November 01, 2005, by an operation error, which had a severe impact on the global. The human factors (operator error, maintenance engineers’ error, etc.) cause severe impacts on not only ICT systems but also social systems (nuclear plant systems, transportation systems, etc.). In addition, the progress of ICT technologies (i.e., cloud, virtual, and network technology) inevitably shifts ICT systems into complexity interacting with tightly coupling domains. This trend places human factors above other elements to promote safety more than ever. The emergent property interaction between ICT and human conduct should be dealt with to promote system safety. Crisis management treats holistic property over partial components. The author introduces a human error framework to promote a holistic view to manage system failures. An application example of ICT human error exhibits the effectiveness of this methodology.
Designing software to be extensible and easily contracted is discussed as a special case of design for change. A number of ways that extension and contraction problems manifest themselves in current software are explained. Four steps in the design of software that is more flexible are then discussed. The most critical step is the design of a software structure called the " uses" relation. Some criteria for design decisions are given and illustrated using a small example. It is shown that the identification of minimal subsets and minimal extensions can lead to software that can be tailored to the needs of a broad variety of users.
This paper describes a methodology for the generation of software requirements for large, real-time unmanned weapons systems. It describes what needs to be done, how to evaluate the intermediate products, and how to use automated aids to improve the quality of the product. An example is provided to illustrate the methodology steps and their products and the benefits. The results of some experimental applications are summarized.
Software design - from 'topmost' specification down to final implementation - is viewed as a chain of uniform steps, each step being a transformation between two linguistic levels. A canonical form of the step is discussed and it is argued that all rational design activities are expressible as a combination of canonical steps. The role of backtracking in software design is explained and a mechanism for introducing changes, both indigeneous and exogeneous, is proposed, again entirely by a combination of canonical steps. The main tenet of the 'canonical step approach' is that a design step contains a degree of unconstrained, creative invention and a calculable part which is the actual transformation effected.
An abstract is not available.
Recognition that most software is domain dependent (DD) is extremely important because the most commonly used software life-cycle models are not adequate for DD software. The nature of DD software, and the need to manage its life cycle effectively, calls for a new approach to software design and the implementation of software development environments.
This paper provides a definition of the term "software engineering" and a survey of the current state of the art and likely future trends in the field. The survey covers the technology available in the various phases of the software life cycle—requirements engineering, design, coding, test, and maintenance—and in the overall area of software management and integrated technology-management approaches. It is oriented primarily toward discussing the domain of applicability of techniques (where and when they work), rather than how they work in detail. To cover the latter, an extensive set of 104 references is provided.
The primary thrust of this paper is to explore many of the problems currently plaguing software development activities and to propose how some of the recently developed management practices may be employed in dealing with them. The practices described range from people organizations (e.g., chief programmer teams) to fully automated engineering tools (e.g., software requirements engineering methodology). A number of techniques are presented. These include methods for coping with communications problems in the requirements definition activity, for evolving a facility which will help increase the productivity of software designers and proggammers, and for maintaining a high degree of visibility during the elusive unit design code and test phase of a project. A very practical view of the management problems and suggested approaches is presented. Key principles, potentials "pitfalls," and unresolved concerns are addressed from a viewpoint of where the state of the art is today and where the industry appears to be heading in the mid-1980's.
Applying the Spiral Model: Observations on Developing System Software in Ada
- F C Belz
Some further treatments of spiral model issues
and practices are:
Belz, F.C., " Applying the Spiral Model:
Observations on Developing System Software in Ada, " Proc. 1986 Annual Conf.
on Ada Technology, Atlanta, 1986, pp.
57-66.
Production of Large Computer Programs Advanced Programming Methods for DigitalComputers
- H D Benington
H.D. Benington, " Production of Large
Computer Programs, " Proc. ONR Symp.
Advanced Programming Methods for DigitalComputers, June 1956, pp. 15-27. Also
available in Annals of the History of Computing, Oct. 1983, pp. 350-361, and Proc.
Ninth Int'l Conf. Software Engineering,
Computer Society Press, 1987.
- C Potts
Potts, C., ed., Proc. Software Process
Workshop, IEEE Catalog No.
84CH2044-6, Feb. 1984.
Some similar cyclic spiral-type process models from other fields are described in: Carlsson
- P Keane
- J B Martin
Some similar cyclic spiral-type process models
from other fields are described in:
Carlsson, B., P. Keane, and J.B. Martin,
" R&D Organizations as Learning Systems, " SIoan Management Review, Spring
1976, pp. 1-15.
- M Dowson
Dowson, M., ed., Proc. Third Int'lSoftware Process Workshop, IEEE Catalog
NO. TH0184-2, NOV. 1986.
On Management and the Learning Process MIT Sloan School Working Article 652-73
- D A Kolb
Kolb, D.A., " On Management and the
Learning Process, " MIT Sloan School
Working Article 652-73, Cambridge,
Mass., 1973.
]. Boehm, B. W., "Software Design and Structuring," in Practical Strategies for Developing Large Software Systems, E. Horowitz (ed)
- Boehm
]. Mills, H. D., "Top-Down Programming in Large Systems," in Debugging Techniques in Large Systems, R. Raskin (ed)
- Mills