7th international workshop on economics-driven software engineering research

The paper examined the problem of modeling and design of software computer systems. The article briefly describes the content aspects of the various stages of the implementation of software complexes and systems. The methodology of research and analysis of systems, which uses the method of computer simulation modeling, is given. The aim of the work is to create a new universal approach to the design and implementation of software systems of various levels of complexity. During the study, the following general scientific methods were used: system analysis, synthesis, formalization, modeling, decomposition, structuring, description, comparison. The materials used in the study were: computers and software development tools. As a result of the study proposed a universal agent-module approach to the design and implementation of software systems based on simulation agent-based modeling. The study presents the processes of modeling and designing software systems, their stages, and the possibility of their integration within the described approach. Examples of formal model and structure of the software system under design based on the agent-module approach are presented. The proposed approach can be used in the process of software development at the initial stages related to modeling and designing of software systems. Integration of modeling and design stages in the proposed approach will significantly reduce software development time and simplify the design process by making it clearer and more formalized. Materials of the article are of scientific and practical value for a wide range of specialists interested in system analysis, modeling, design and implementation of software systems.

Design management systems have been developed and researched for traditional product and service industries. For interaction design little research has been performed on design management. The objective of this paper is to describe aspects of and provisions for industrial interaction design that influence approaches to design management within system and software development. We discuss whether there are specific conditions for design management of interaction design within the software and system development industries. The research is based on three short case studies from industrial software development. We identify some of these specific conditions; the difference between a usage and a product perspective, the design tools and practices, and the modularized and distributed processes. These issues point towards challenges facing design management within the software and system development context, as well as the need for interaction design to clarify its position as a strategic resource in software companies. The conclusions point towards the need for continued research on strategic possibilities and alternatives to organize and manage design work in software and system development.

The capability of an enterprise to innovate and promptly and effectively respond to change requests coming from both internal and external drivers has nowadays become a measure of the competitiveness of the enterprise in all business sectors. Innovation often implies modifying the enterprise business processes and, as a consequence, requires the evolution of the enterprise software systems. In this context, the workshop on Evolution of Software Systems in a Business Context (ESSBC), held in Budapest, Hungary, as part of the IEEE Software Technology and Engineering Practice workshop series (STEP 2005), aimed at discussing experiences and research outcomes and identifying research issues in supporting the evolution of enterprise software systems to reach innovation goals

The most current trends in the evolution of software development process are closely related with the increasing complexity of software systems. This motivates software engineers and system developers to find an alternative solution for software system design and development. In this case, the manner offered by OMG’s initiative, the Model Driven Architecture namely, represents a model-driven approach to software development. It also considers the further evolution of CASE tools, bringing their functionality to the next level. This paper investigates the variety of the CASE tools developed under an impact of MDA growing progress. The differences between Model Driven Architecture and Model Driven Development in the context of automatic capabilities for software development are also discussed in the paper. The example of possibility to define a set of tools proposed as a tool chain for development of software systems under the framework of MDA, the projection of two-hemisphere approach for object-oriented software development into authors’ developed component model of MDA is offered in the paper.

Software systems need constantly maintaining or adapting to continuously meet the changing business requirements. The process of maintenance or adaptation is software evolution. In general, people hope to evaluate software evolution for guiding software maintenances. By evaluating how well software maintenances follow the positive evolutionary trends, developers can assert whether it is necessary to redevelop or even refactor newly released or maintained versions of software to enforce the software evolution back on track. In this paper, we propose an approach to evaluating software evolution based on API usage patterns, which are the accumulations and summarizations of people's software design and development experience. In the approach, better software evolution is considered as the process of reusing more usage patterns, and software evolution is evaluated based on how well software reuses usage patterns in the process of evolution. Our work consists of three parts. First, we use a graph-based algorithm to mine usage patterns from different open-source software. Second, we use the patterns to evaluate the evolutions of software systems and accordingly analyze the important changes during software evolution. Third, we compare different approaches and analyze which approach can reflect the process of software evolution accurately. Our experiments on several open source programs show that our approach is more effective than other approaches on identifying the great change events during software evolution.

By now, one can point to many instances where measurement has been used effectively to inform management and technical decisions in support of the development and maintenance of software and software intensive systems. Yet, measurement is not very well integrated into software or systems engineering education or practice, and measurement remains challenging for all too many organizations. For this paper, we have analyzed 1350 findings drawn from 663 Software CMM/spl reg/ appraisals that were conducted between 1987 and 2002 inclusive. The results are augmented by questions from a survey of CIO's from state and local governments and the private sector. Our analyses suggest several areas where both managers and engineers would benefit from better guidance about the proper use of measurement and analysis. Future work may include lexical analyses based on natural language processing as well as studies of appraiser understanding of the measurement content in CMMI/spl reg/ models.

Many regular business operations are transforming into digital services, increasing advanced multi-platforms, rapid operational alignment, flexibility, and environmental impact through energy consumption, hardware waste, and technology investments. Flexible and sustainable system development models emphasizing energy efficiency can help innovate software development as digital servicing applications shift. This research is motivated by the need to improve energy consumption in early software design and development due to rising technological efficiency and sustainability demands. Although effective in iterative development and stakeholder engagement, traditional Agile methodologies often struggle with long-term sustainability and energy efficiency. Extended Agile, combining Agile, layered architecture, and aspect-oriented frameworks (ALAI), promises to improve system modularity, flexibility, maintainability, and sustainability. This study’s findings are not just theoretical, but also practically relevant, as they explore the energy efficiency of ALAI software development methodologies, using graduate admission information system services (GAISS) as an example. GAISS is a complex system that handles the entire process of graduate admissions, from application submission to final decision. The study quantifies the energy usage of a student-list webpage by analyzing Microsoft IIS server logs from February 2022 to May 2024. Directly applicable findings show that the GAISS based on the ALAI framework reduces energy consumption by 10.7914% compared to traditional Agile software developments. ALAI used 892.80 kWh versus Agile’s 1000.80 kWh during operations, saving energy. These findings demonstrate the benefits of integrating aspect-oriented frameworks and layering approaches into Agile methodologies, contributing to sustainable software development discourse. The study emphasizes the importance of energy-efficient frameworks such as ALAI to reduce software systems’ environmental impact and promote software development sustainability. The findings of this study, with their practical relevance, assist software developers and organizations in choosing software design and development methods that maximize operational efficiency and environmental sustainability.

Component based software development (CBSD) endeavors to deliver cost-effective and quality software systems through the selection and integration of commercially available software components. CBSD emphasizes the design and development of software systems using preexisting components. Software component reusability is an indispensable part of component based software development life cycle (CBSDLC), which consumes a significant amount of organization’s resources, that is, time and effort. It is convenient in component based software system (CBSS) to select the most suitable and appropriate software components that provide all the required functionalities. Selecting the most appropriate components is crucial for the success of the entire system. However, decisions regarding software component reusability are often made in an ad hoc manner, which ultimately results in schedule delay and lowers the entire quality system. In this paper, we have discussed the analytic network process (ANP) method for software component selection. The methodology is explained and assessed using a real life case study.

The various software systems developed for the DIII-D tokamak have played a highly visible and important role in tokamak operations and fusion research. Because of the heavy reliance on in-house developed software encompassing all aspects of operating the tokamak, much attention has been given to the careful design, development and maintenance of these software systems. Software systems responsible for tokamak control and monitoring, neutral beam injection, and data acquisition demand the highest level of reliability during plasma operations. These systems made up of hundreds of programs totaling thousands of lines of code have presented a wide variety of software design and development issues ranging from low level hardware communications, database management, and distributed process control, to man machine interfaces. The focus of this paper will be to describe how software is developed and managed for the DIII-D control and data acquisition computers. It will include an overview and status of software systems implemented for tokamak control, neutral beam control, and data acquisition. The issues and challenges faced developing and managing the large amounts of software in support of the dynamic and everchanging needs of the DIII-D experimental program will be addressed.

Moscow Institute of Physics and Technology (National Research University) The paper advocates the need to move from separate stages of the product life cycle (LC; R&D, production, operation) to a single project implemented in a new paradigm of system design based on software and methodological tools of model-based systems engineering (MBSE). Currently available in Russia foreign software (SW) and methodological MBSE tools for the design and development (D&D) of systems (including space instruments) are expensive and complex. This paper formulates and considers the question: «Is it possible to reduce the cost and simplify the use of software and methodological MBSE tools by means that are available to a wide audience of users?». To answer this question, the authors analyzed SysML, QFD method, HoQ method, and the SW for their application. As the result of literature review, it is shown that in the leading countries, the relevance of implementing these tools in the design and development of hardware and software systems is increasing. For the use of SysML, QFD, HoQ by a wide audience of potential users from Russian Federation were defined software tools. 13 disadvantages that prevent the application of SysML, QFD and HoQ, as well as SW for their use were identified. In order to overcome the identified disadvantages, was developed SW and methodological MBSE tool based on modernization, specification and synthesis of SysML, QFD, HoQ and SW for their application. The developed MBSE SW and methodological tool allows for a wide audience of users to D&D systems in accordance with MBSE approach (QFD, HoQ, SysML), to identify critical requirements of different development elements, to develop automatically (in a few hours instead of several days) and update SysML models of requirements, to reduce labor costs for the implementation of the D&D LC stages of future analog products by 5-10%. As a result of validation of SysML models, it is proved that their repeated use reduces the planning time of the LC stages of analog products by up to 60%, increases the compliance of the reporting documentation of the LC stages with the requirements of regulatory and technical documents by 10%.

The management of software development for single and dual processor system designs is making progress towards becoming a mature discipline. A good part of the progress can be attributed to the development and use of standard system and software engineering methods and design principles.However, new computer system designs (networking, distributed systems, embedded systems, multi- and coprocessors, fault tolerant systems, etc.) will create new challenges for managers of software development. The reason for this effect on management is that some of the system and software engineering methods and design principles developed for single and dual processor system designs are not valid for these newer designs.Some of the issues that software development project managers will need to cope with are:1. Life cycle model adjustments2. Rapid prototyping activities3. Different hardware and software phasing4. Increased tool development5. New trade-offs and hybrid developments of off-the-shelf software and newly developed software6. Development of concurrent design principles7. New software design principles to support fault tolerance and the use of new memory technologiesThe above items are just now being recognized as problems, and solutions for them either do not exist, or are not widely known.These problems create a series of new challenges that managers must deal with for software development based on the new architectures and requirements. The purposes of this paper are to discuss these issues and to identify some solutions that can serve in the interim as the technology changes to meet these new challenges.

Welcome to the International Conference on Software and Systems Process (ICSSP) held in Zurich, Switzerland, on June 2nd and 3rd, 2012. Having grown from a Software Process Workshop in 2005 to the International Conference on Software Process (ICSP) in 2007, and finally to the International Conference on Software and Systems Process (ICSSP) in 2011, this conference series has established its place in the software engineering community as a respected conference focusing on research and practice related to software and systems development process. Software and software systems development use processes as one major means for achieving and ensuring the quality of the final product. This leads to specific challenges regarding software processes such as simplicity, adaptability, standard conformance, the coordination of multiple domains and lifecycles, etc. Processes from other domains (e.g., health care, manufacturing, business, aerospace, automotive systems, and others) face similar challenges. Yet, they share interesting similarities with and differences to software processes. The question is: How can we in the software domain learn from other domains to meet our software process engineering challenges? The ICSSP conferences hence connect the traditional software and systems process community with outside views and insights, broadening its scope of software development processes to system development and explicitly including processes of other domains such as health care, business, and manufacturing. By sharing process development theories and practices from such domains, ICSSP 2012 is investigating novel solutions to today's process challenges. Correspondingly, the main theme of ICSSP 2012 is Beyond Software and Software Systems Processes, signaling our goal of learning from domains other than the traditional software process community.

It is our great pleasure to welcome you to Modularity: aosd.12, the premiere international research conference on modularity in software and software-intensive systems. Modularity: aosd.12 is the 11th annual international conference on Aspect Oriented Software Development (AOSD), and the first in which the conference committee will give an award for the most influential paper published in the Proceedings of the conference 10 years ago: in 2002. This year's conference continues to broaden of the scope of the field to address all aspects of modularity, abstraction, and separation of concerns as they pertain to software, including new forms, uses, and analysis of modularity, along with the costs and benefits, and tradeoffs involved in their application. Modularity provides the international computer science research community and its many sub-disciplines (including software engineering, languages, and computer systems) with unique opportunities to come together to share and discuss perspectives, results, and visions with others interested in modularity as well as in the languages, development methods, architectures, algorithms, and other technologies organized around this fundamental concept. The Modularity: aosd.12 conference comprises two main events: Research Results and Modularity Visions. Both events invited full, scholarly papers of the highest quality on results and new ideas in areas that include but are not limited to complex systems, software design and engineering, programming languages, cyber-physical systems, and other areas across the whole system life cycle. Papers submitted to the Research Results track were reviewed in accordance with the highest established standards of scientific rigor applied in peer review of putative research results. Reviewers assessed works in terms of research problem formulations, novelty and sophistication of proposed solutions, clarity and significance of hypotheses, proper design and execution of experimental or analytical assessments, sound interpretation of data, and correct characterization of work in relation to existing knowledge. Papers submitted to the Modularity Visions track were reviewed in accordance with the highest established standards of scientific rigor applied in peer review of scientific research proposals. Reviewers assessed works in terms of research problem formulations, novelty and sophistication of proposed solutions, clarity and significance of hypotheses, compelling preliminary results, proposals for sound future experimental or analytical assessments and interpretation of data, and correct characterization of work in relation to existing knowledge. The Results track attracted 79 submissions from across the world. Of these, 20 papers were accepted for publication, for a 25% acceptance rate. The program committee accepted papers in three rounds. In each round papers each paper was accepted, rejected, or (except in the last round) invited for revision and a second review. Five (5) papers were invited for revision and a second review, all of which were ultimately accepted. The Visions track reviewed 10 papers, one of which was referred from the Results track. Of these, three papers were accepted for publication for a 30% acceptance rate. Our keynote and heart of technology speakers are Lars Bak, James O. Coplien, and Martin C. Rinard. Lars will report on implementing language-based virtual machines; Jim will talk about objects of the people, for the people, and by the people; and Martin will tell us what to do when things go wrong and how to recover in complex systems.

This paper outlines perspectives on the teaching and learning of software systems development in large groups based on the designed, final year, software systems analysis (SSA) and software systems design (SSD) subjects within the undergraduate Software Engineering Program at the Faculty of Engineering, University of Technology Sydney (UTS). Topics described by this paper include shared experiences in implementing these subjects over the last two years and discusses their successes, as well as common problems both experienced and anticipated. While the SSA and SSD subjects are practice based, its content is the synthesis of all subjects taught in the Software Engineering Program and practiced in industrial internships. The object of these two subjects is to bridge the gap between the students' individualistic, often unplanned, unbudgeted and uncoordinated efforts, that dominate the traditional approach to teaching and learning software subjects; and the demands of planned, process driven, well coordinated and budgeted - modern, large team based development of complex software systems, demanded by industry. The subjects are evolutionary in nature, but the most critical aspect and challenge is to maintain a careful balance of academic and pedagogical interests with ever changing industry demands and practices.

\n Contains fulltext :\n 158152.pdf (Publisher’s version ) (Open Access)\n