Testing

In particular, an early integration of performance specifications in the SDP has been recognized during the last few years as an effective approach to improve the overall quality of a software. Performance related problems are becoming more and more strategic in the software development, especially recently with the advent of Web Services and related business-oriented composition techniques (software as a service, Web 2.0, orchestration, choreography, etc.). The goal of our work is the definition of a software development process that integrates performance evaluation and prediction. The software performance engineering development process (SPEDP) we specify is focused on performance, which plays a key role driving the software development process, thus implementing a performance/QoS-driven (software) development process. More specifically, in this paper our aim is to formally define the SPEDP design process, posing particular interest on the basis, on the first step of SPEDP, the software/system architecture design, modeling and/or representation. We define both the diagrams to use and show how to model the structure of the software architecture, its behavior and performance requirements. This is the first mandatory step for the automation of the SPEDP into a specific tool.

Performance related problems are becoming more and more strategic in the software development, especially recently with the advent of Web Services and related business-oriented composition techniques (software as a service, Web 2.0, orchestration, choreography, etc.). In particular, an early integration of performance specifications in the SDP has been recognized during the last few years as an effective approach to improve the overall quality of a software. The goal of our work is the definition of a software development process that integrates performance evaluation and prediction. The software performance engineering development process (SPEDP) we specify is focused on performance, which plays a key role driving the software development process, thus implementing a performance/QoS-driven (software) development process. More specifically, in this paper our aim is to formally define the SPEDP design process, posing particular interest on the basis, on the first step of SPEDP, the software/system architecture design, modeling and/or representation. We define both the diagrams to use and show how to model the structure of the software architecture, its behavior and performance requirements. This is the first mandatory step for the automation of the SPEDP into a specific tool, which we have partially implemented as a performance plug-in for ArgoUML, ArgoPerformance.

The low-code approach is an important area of research being developed to improve the rapid creation and performance of software applications. This approach allows developers and users to easily create software applications through an interactive interface. Existing research shows that the low-code approach accelerates the development process in innovative ways, saves effort and time, and reduces code complexity. This study analyses and compares automatic code generation and transformation techniques in low-code platforms. The study analyses the contributions of automatic code generation and transformation to software engineering processes and evaluates the impact of these techniques on software product quality and development speed. The importance of the Model-Based Development (MBD) approach in automated code generation processes is highlighted. It is stated that MBD provides benefits such as speeding up the software development process and reducing errors by enabling automatic code generation from high-level abstract models. In the study, various literature studies were evaluated to examine the impact of automatic code generation and transformation techniques on the application development process. These studies have shown how automatic code generation and transformation techniques are applied, what results are achieved and what contributions these techniques make to the software development process. The results of the study show that automatic code generation and transformation techniques have a great impact on the application development process. In particular, the acceleration of the software development process, the reduction of errors and the ability to produce more effective and efficient software products are important benefits of these techniques. In addition, it has been found that this approach increases the success of software projects by enabling software developers to produce fast and accurate solutions in complex systems. In this context, the importance of automatic code generation and transformation techniques plays an important role in software development processes.

This scientific article presents the results of a study focused on the current practices and future prospects of AI-tools usage, specifically large language models (LLMs), in software development (SD) processes within European IT companies. The Pan-European study covers 35 SD teams from all regions of Europe and consists of three sections: the first section explores the current adoption of AI-tools in software production, the second section addresses common challenges in LLMs implementation, and the third section provides a forecast of the tech future in AI-tools development for SD. The study reveals that AI-tools, particularly LLMs, have gained popularity and approbation in European IT companies for tasks related to software design and construction, coding, and software documentation. However, their usage for business and system analysis remains limited. Nevertheless, challenges such as resource constraints and organizational resistance are evident. The article also highlights the potential of AI-tools in the software development process, such as automating routine operations, speeding up work processes, and enhancing software product excellence. Moreover, the research examines the transformation of IT paradigms driven by AI-tools, leading to changes in the skill sets of software developers. Although the impact of LLMs on the software development industry is perceived as modest, experts anticipate significant changes in the next 10 years, including AI-tools integration into advanced IDEs, software project management systems, and product management tools. Ethical concerns about data ownership, information security and legal aspects of AI-tools usage are also discussed, with experts emphasizing the need for legal formalization and regulation in the AI domain. Overall, the study highlights the growing importance and potential of AI-tools in software development, as well as the need for careful consideration of challenges and ethical implications to fully leverage their benefits.

Many papers proposed in the software engineering and information systems literature are dedicated to analysis of software projects missing their schedules, exceeding their budgets, delivering software products with poor quality and in some cases even wrong functionality. The expression “software crisis“ has been coined since the late 60's to illustrate this phenomenon. Various solutions has been proposed by academics and practitioners in order to deal with the software crisis, counter these trends and improve productivity and software quality. Such solutions recommend software process improvement as the best way to build software products needed by modern organizations. Among the well-known solutions, many are based either on software development tools or on software development approaches, methods, processes, and notations. Nevertheless, the scope of these solutions seems to be limited and the improvements they provide are often not significant. We think that since software artifacts are accumulation of knowledge owned by organizational stakeholders, the software crisis is due to a knowledge gap resulting from the discrepancy between the knowledge integrated in software systems and the knowledge owned by organizational actors. In particular, integrating knowledge management in software development process permits reducing the knowledge gap through building software products which reflect at least partly the organization's know-how. In this paper, we propose a framework which provides a definition of knowledge based on information systems architecture and describes a knowledge-oriented software development process to help organizations in reducing the software crisis impacts.

The software development process (SDP) contains many variables depending on the methodology chosen. Software development methodologies such as Agile or Waterfall can specify how and in what sequence software is developed. However, the SDP remains a hot topic among practitioners and academics, who seek to clarify the key aspects that influence the successful implementation of the SDP. As the SDP is a dynamic and knowledge-intensive business process (BP), one of its most impact components is the human factor (HF). It is difficult to predict how the HF impacts the sequence and results of SDP implementation. This paper proposes a new approach to investigate the impact of the HF on the SDP through the perspectives of different software development methodologies. The advantages and novelties of this approach include modelling HF uncertainties through their fuzzification in SDP activities, modelling different SDP methodologies using a case-handling approach, and simulating a dynamic, case-based SDP with real HF-related data collected from several IT organizations. The results show that the impact of the HF on SDP performance differs across the Waterfall and Agile methodologies. The results also allow researchers and practitioners working on software development projects to familiarize themselves with the impact of the HF on different SDPs, and to assess the degree of development risk associated with the SDP depending on the methodology chosen.

This IIA assessed the flow down of institutional 830 Software Quality Assurance requirements through three required document templates to the CASTLE-PX software effort and the implementation of those SQA requirements. The templates flow down the DOE O 414.1D consensus standard requirements for Safety Software. This assessment did not include the flow down of NAP-24, Weapon Quality Policy, requirements. The assessment focused on the CASTLE-PX project’s software development and release processes. It did not assess Pantex’s acceptance or usage of the software. The assessment resulted in 3 Deficiencies, 5 Observations, 1 Recommendation, and 3 Strengths. Overall the CASTLE-PX team demonstrated it values quality and has worked to integrate quality practices into its software development processes. Improvement in documentation will enhance their SQA implementation.

CloudTeams: Bridging the Gap Between Developers and Customers During Software Development Processes

Abstract. The increasing demand for software has generated greater need for software de-velopment processes. The literature, on the other hand, does not present processes for the development of scientific software, and, in this way, in previous studies, a Specific Process for Scientific Software (SPSS) was proposed. It was conceived based on the Humphrey’s Meth-odology, which defines that for the acquisition of a process it is necessary the execution of eight steps. Having in mind that the six first steps have already been concluded, the current work considers the execution of the seventh and eighth steps of the Methodology, which are the validation of the initial process and its later improvement. It is important to highlight the significance of these steps because, for a process to ensure its efficiency, it must be tested and validated. So, firstly, a webapp to automate and model the SPSS was developed, in order to help in its implementation. In the continuation of the study, SPSS was applied in real envi-ronments of scientific software development, to obtain results which allow them to be ana-lyzed through a validation technique, by inspection, named VProcInsp. At the end, in spite of some inconsistencies, it was concluded that the SPSS had indicated that it can really contrib-ute in the development of academic scientific software. The results are shown and discussed in this the article.

Sustainability incorporation within the field of Software Engineering is an emerging research area. Sustainability, from an academic perspective, has been addressed to a large extent. However, when it comes to the software industry, the topic has not received much-needed attention. Software, being designed and developed in the industry, can benefit society at large, if sustainability is taken into account by the software professionals during the software design and development process. To develop a sustainable software application, knowledge and awareness about sustainability by professional software developers is one of the key elements. This study is an attempt to examine sustainability knowledge, importance, and support from the perspective of South Asian software professionals. Additionally, this study also proposes sustainability guidelines for certain software applications and also a catalog for the identification of sustainability requirements for different software applications. The queries such as ‘What does sustainability mean to a professional software developer?’, ‘How does the software industry identify sustainability requirements?’, ‘How do software developers incorporate the sustainability parameters within software during software development?’, and many other such queries are addressed in this study. To achieve this goal, a survey was carried out among 221 industry practitioners involved in software projects in various application domains such as banking, finance, and management applications. The results pinpoint that even though sustainability is deemed important by 91% of practitioners, still there is a lack of understanding regarding sustainability incorporation in software development. A total of 48% of professionals often misunderstand “Green software” as “sustainable software”. The technical aspect of sustainability is considered most important by professionals (67%) as well as companies (77%). One of the key findings of this study is that 92% of software practitioners are not able to identify sustainability requirements for software applications. The outcomes of the study may be regarded as an initial attempt towards how sustainability is comprehended in software by the South Asian software industry.

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.

Behavior Driven Development (BDD) is a widely adopted agile methodology for software development that emphasizes the behavior of an application as a series of test cases, using the keywords, which include "Given," "When," and "Then." It involves writing requirements in a structured and testable format that can be evaluated to ensure compliance with the expected behavior. Although a significant amount of research has been conducted to examine the impact of using BDD on software development process yet rare work is observed to synthesize these studies and identify areas for future exploration. This study presents a review of the state-of-the-art BDD by synthesizing the recent advancements in its uses and applications. It aims to systematically investigate the impact of BDD on software development process as well as on product quality by aiding to bridge the communication gap between the stakeholders. The results reveal that BDD is an effective technique to clarify requirements during the software development process as it helps minimizing the intrinsic ambiguities. This work proposes a taxonomy based on the role and applications of BDD in various contexts. It suggests a framework for applying BDD in software development and defines a workflow for its application in software development. Finally, this work highlights some pertinent future directions for the use of BDD in software development.

The main objective of the paper is to create context sensitive decision support services within flexible Quality Assurance (QA) of software development projects and their resulting products. The new QA process is supported by an Internet solution composed of several knowledge, context sensitive services based on open standards that is able to detect changes in the scope and requirements of an application (or changes in its development process) and provide the adequate set of assessments as a basis for an accurate measurement of the quality of the process and product at any time and allow for effective decision making within QA. The Internet Services monitor the different stages of the software development process, interoperating with the existing applications and systems to provide quantitative information about the quality of each phase (i.e. project management, requirements gathering, functional and technical design, development and testing), the project as a whole and the resulting product. They also monitor context under which the SW is developed and decisions on QA have to be made. Data obtained in real-time by the monitoring services are used in an indistinctive way by software engineers, designers, developers, testers and managers alike for different collaborative decision making. The paper is one of the first attempts to apply context sensitivity to support decision making in QA for SW development. The approach is assessed in 2 different business cases in order to validate the results under different conditions. The first business case belongs to a large software company developing large Internet projects based on Rational Unified Process methodology. The second business case belongs to a SME developing complex projects based on agile methodologies.

It is tempting just to develop software in the usual way and then try to assure that the finished product is safe. This approach is akin to relying on downstream protection systems-the cost can be exorbitant and the assurance limited. The most practical and effective way to enhance software system safety is to follow a complete safeware program that applies safety enhancing techniques throughout software development and maintenance. Verification testing verifies that requirements for a subsystem have been met. Validation tests a finished device to the original requirements to ensure they have been met. Appropriately applied V and V decreases the cost of software development. Verification and validation can make a significant contribution in making the final product safe and effective. Software changes can be more easily and safely made when the development process is controlled and documented. The template is already in place. Regression testing is easily identified and can reduce the time required to make and test changes. The FDA requires evidence that verification and validation is included in the product development process. The emphasis is on appropriately applied V and V. A software development process that produces, on time, bug free code, meeting all of its requirements, and has intrinsic verification and validation identifying defects as early as possible, is a very cost efficient process, regardless of industry. The earlier a defect is found in the development process, the lower the cost to correct it.

Despite the ever-growing demand for software development graduates, it is recognised that a significant barrier for increasing graduate numbers lies in the inherent difficulty in learning how to develop software. This paper presents a study that is part of a larger research project aimed at addressing the gap in the provision of educational software development processes for freshman, novice undergraduate learners, to improve proficiency levels. As a means of understanding how such learners problem solve in software development in the absence of a formal process, this study examines the experiences and depth of learning acquired by a sample set of novice, freshman university learners. The study finds that without the scaffolding of an appropriate structured development process tailored to novices, students are in danger of failing to engage with the problem solving skills necessary for software development, particularly the skill of designing solutions prior to coding.