Learning about application software by studying processes

Predicting the number of bugs in any software application is an important but challenging task. The software manager by modelling the bug numbers, can take timely decisions in reducing the amount of effort investment and also the allocation of resources. The software developers can also take effective steps for reducing the number of bugs in the future version of the software application. The end users also can make a timely decision on adoption of a particular software application by knowing the growth pattern of bugs in advance. The challenges behind modeling the bug growth patterns are random causes behind a bug. A bug in any software may be caused during testing, development or application. Causal modelling of bug numbers is a complex and tedious task as they consider many internal characteristics to be modelled. In this paper, we have used we have used Long Short Term Memory (LSTM) [14] Network for temporal modelling the bug numbers of three different software applications. We have used both univariate and multivariate modelling approach to predict bug number in advance. The goal is to have an appropriate model for software bug growth pattern.

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.

Software application becomes critical tool in a business operation today. Generally there is no management staff in the business operation can tolerate the software application downtime beyond the Service Level Agreement (SLA). The time duration spent on root cause analysis activity of software application error carries crucial impact to the business transaction. This is because business operation cannot afford if the software application downtime gets prolonged. Especially an enterprise level of software application is involving multiple tiers. There will be at least one or even more log files at each tier. Of course the root cause analysis activity will easily get prolonged as more than one log file are required for analysis activity. The research is not only to mitigate the time duration prolonging on root cause analysis activity. It is also to increase the accuracy of identifying the actual root cause during analysis activity. This is a necessity to have a proposed logic model sitting at the logic tier. The logic model can analyze the required log files, and then identify the root cause without creating any interruption to the existing software application executing in the production environment. Therefore, this is the strong reason for a Prescriptive Analytical Logic Model (PAL) incorporated with Analytic Hierarchy Process (AHP) proposed. The proposed logic model will contribute a new knowledge in the area of log file analysis. It aligns with the two research objectives, (1) to shorten the total time spent on root cause analysis activity by adopting the decision making process and technique of AHP, (2) to reduce the frequency of attempt by increasing the accuracy of identifying the actual root cause. Furthermore, this proposed logic model contributes the new knowledge to close the existing knowledge gap of software application root cause analysis using AHP.

One promising approach to more effective software development is the concept of product platform originated from mechanical engineering, aiming at architectural product families instead of a portfolio of separate products. The concept was also offered for the development of software applications. Based on our literature review we argue that the presented sofware platforms intermixed the product and process platform approaches, leaving the borderline to re-use and component oriented software engineering methods unclear. We propose a new application frame concept that conserves the original objective of the product platform. To manage the complex interaction with the software process we propose that the software application frame should be taken as a strategic issue, where three software application sub-strategies are aligned (integrated). These are the structural (application architecture), the process (underlying technology), and the software application leverage. We propose effectiveness criteria and generic alignment processes for the frame strategy and discuss implications of the new framework for software development practices.

Mobile software application development process must be matured enough to handle the challenges (especially market related) associated with the development of high quality mobile software development. Ever increasing number of both mobile users and mobile applications had presented software engineers with the challenge of satisfying billions of users with high quality software applications to be delivered within deadline and budgets. Always there had been a lot of pressure to develop complex software categorized by thousands of requirements, under resource constrained environment. Requirement prioritization is one of the activities undertaken by software engineer to deliver partial software product to its customers such that most important requirements are implemented in the earliest releases. During next releases some changed and pending requirements are implemented, an activity that generates ripple effects. Such ripple effects need to be tested by executing modified source code against test cases of previous releases (regression testing). Regression testing is a very effortful activity that requires a software tester to select test cases that have high fault detection capability, execute the modified code against selected test cases and performing debugging. This regression testing activity can be lowered to the maximum extend by considering dependencies between requirements during the time of requirement prioritization. Thus requirement prioritization will be carried out not only against aspects like cost, time, risks, business values etc but against dependencies also. The aim is to implement almost all dependent highest priority requirements in current release so that implementation of new requirements is unlikely to have ripple effects. Changes in requirements might not be related to variable usage and definition and might not involve a change in functionality. In such cases there is no need to select already executed test cases of previous versions. Module dependencies can lead to test case selections of previous versions if changes of requirement lead to ripple effects. This paper aims to implement highest priority requirements such that regression testing is performed to minimum thereby improving development process of mobile applications. The proposed technique had been successfully evaluated on Android based notification software application that meets the specification of Aakash tablets.

In the process of software development, the allocation of resources is a very challenging task so as to minimize cost and at the same time, to deliver software to the client on time. Apart from cost and time concerns, quality characteristics of software also need to be taken into consideration to determine the distribution of available resources among various modules in an application. In the present study, one of the multi-criteria decision making technique (MCDM), Fuzzy analytical hierarchy process (FAHP) is used for pair-wise comparison of criteria and sub-criteria of quality attributes. It is further used for ranking various modules based on conflicting nature of criteria in order to allocate the resources in an efficient way. Later, a numerical is presented to show how the fixed amount of resources is allocated to various modules in a software application in proportion to weights as obtained using Fuzzy AHP.KeywordsResource allocationMulti criteria decision makingFuzzy analytic hierarchy process

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.

SUMMARYSoftware process engineering is a discipline, which aims to study and improve software development and maintenance processes. The explicit definition of software processes is essential. To this end, the Object Management Group consortium proposed the Software & Systems Process Engineering Meta‐Model (SPEM) that exploits the benefits of the Model Driven Architecture paradigm applied to software process models, instead of software specification models. The aim of this study is to discover evidence clusters and evidence deserts in the use and application of SPEM from a business process management point of view. To reach the proposed objective, we have undertaken a systematic mapping study of the existing scientific literature.The reviewed literature deals mainly with process modeling and, to a lesser extent, with process adaptability, verification, and validation, enactment and evaluation. Wide agreement exists in using the SPEM meta‐model to develop different types of methods and processes. Further research efforts are needed in areas related to enactment and evaluation of software processes. There is a need to evolve to a new version of the meta‐model that incorporates the improvements proposed by different authors. Copyright © 2013 John Wiley & Sons, Ltd.

This article analyzes the basic concepts, development process, and application advantages of computer music. The author studies the specific application of computer music production software in modern music works, film and television music works, electronic music works, dance music works, classical music works, ethnic music works, and symphony works. The purpose of this paper is to improve the level of music creation and increase the attractiveness of music creation results by studying the relevant content of the mainstream music production in the future.

Abstract: The term "drought" is multifaceted, with varying interpretations based on personal experiences. It is a natural disaster that is distinguished by a severe and ongoing precipitation deficit. The planning and management of freshwater resources as well as the forecasting of the arrival and intensity of droughts depend heavily on drought monitoring. A number of indices have been put forth over time to track and measure data related to droughts. The Standardized Precipitation index (SPI), which is based on the idea of probability, is the most commonly used index. The current study examines the possibility of analysing the temporal pattern and severity of drought in the Kashmir Valley (Jammu and Kashmir) using precipitation-based SPI. Utilizing the "DrinC" software application, the Indices were calculated. SPI values were calculated using monthly precipitation data for the IMD Srinagar 2003 to 2022. SPI series computations were carried out for short, moderate, and long time scales. Based on the data, the Kashmir region experienced four periods of moderate drought in the years 2007, 2009, 2012, and 2016. Additionally, there was no significant drought from 2003 to 2022. 2007 had the maximum intensity with an SPI value of -1.37 for a moderate drought.

Due to the increase in collaborative work and the decentralization of processes in many domains, there is an expanding demand for large-scale, flexible and adaptive software systems to support the interactions of people and institutions distributed in heterogeneous environments. Commonly, these software applications should follow specific regulations meaning the actors using them are bound by rights, duties and restrictions. Since this normative environment determines the final design of the software system, it should be considered as an important issue during the design of the system. Some agent-oriented software engineering methodologies deal with the development of normative systems (systems that have a normative environment) by integrating the analysis of the normative environment of a system in the development process. This paper analyses to what extent these methodologies support the analysis and formalisation of the normative environment and highlights some open issues of the topic.

Based on the scientific design, development, application, evaluation and management of study processes and teaching resources in PE teaching in higher education, centered by the educational ideas of human centered and health first, this study explored the development and application of computer supplementary software of CAI, CAT, CMI in PE teaching, widened the new study channel of students! development and research study mode, cultivate students! Creativity and practical ability, improve thoroughly students basic sport knowledge, basic techniques, physical fitness and the level of health, therefore enhance the modernization of PE teaching, measurement, educational management methods in PE teaching of higher education.

Insights and assessments about the quality, reliability, or trustworthiness of software systems is important for many software applications. Especially for large or mission-critical software systems, reliable measures and assertions are crucial. Since software repositories contain information about source code, software development processes, and team interactions, we extract the provenance of software artifacts from those repositories and store the provenance according to a provenance model defined using W3C PROV data model. We use the recorded provenance to discover insights about the software and its development process, which we apply and evaluate for a large aerospace software system.

In the current digital era, the security of information has become a fundamental aspect of system development. Cryptography, especially symmetric key algorithms, plays a key role in protecting data confidentiality. This research presents the development of a modern cryptographic application based on the Data Encryption Standard (DES), implemented using the Python programming language. The system is equipped with a graphical user interface (GUI) developed using Tkinter, allowing users to easily encrypt and decrypt text data. In addition to DES, the application also includes educational features such as RSA encryption and SHA-256 hashing to enhance users' understanding of various cryptographic techniques. The development process follows a prototyping method, from initial analysis to implementation and testing. Several functional tests were conducted using various text inputs, and results showed that the application successfully performed accurate encryption and decryption. Furthermore, the GUI interface provides an intuitive user experience, making it suitable as a learning tool in educational environments. This research contributes to the field of computer security by offering an open, accessible tool for understanding classical encryption methods and promoting awareness of basic data protection strategies in software applications.

The Wright brothers' first flight took place in 1903, and for the next 60 years flight was purely a mechanical activity. This all changed in the early 1960s, when computers first began to find their way onto airplanes. The first onboard computers were hybrid electromechanical devices and made use of very specialized and limited instruction sets. There was a substantial lag between the appearance of digital technology in military aircraft and those flown in civilian applications. Although many people view aviation as an extremely high technology field, there is often a lag in technology adoption, particularly in the airborne segment of civil aviation. This lag is the result of conservatism due to safety concerns as well as a need to constrain both the weight and the cost of onboard systems. While slow to embrace the digital age, aviation‐related applications of software engineering are now at the forefront of this new science. Software applications are now found in all phased of aviation and include among the many, aircraft design, flight safety, air traffic control, maintenance, etc. Ever greater levels of automation onboard aircraft and in ATC systems require highly complex designs while demanding the utmost reliability and dependability of the software and the hosting hardware. Time and experience has shown that such reliability is the result of disciplined, well‐planned, thorough development processes. Current regulatory guidance for airborne systems containing software invokes DO‐178B/ED‐12B as the design assurance standard of choice to ensure safe software. Where software blends with hardware to produce firmware in the form of application‐specific integrated circuits and programmable logic devices, a new standard, DO‐254/ED‐80, has been introduced to extend design assurance to this area of software engineering for airborne systems. The software engineering approaches and techniques discussed here are a result of ongoing debate and consensus among the industry, regulators, and researchers. There is much engineering judgment in the techniques described, although there is no empirical basis or measurement of how best these techniques can eliminate safety‐related problems. Models have been developed to predict the latent fault density by correlating the maturity of the development process. Such models have not yet been applied and tested in the aviation industry. It should be noted that as the amount of software has steadily risen in commercial aircraft, the fatal accident rate has steadily fallen over the same time period. While a direct cause–effect relationship has yet to be established between the design assurance approaches discussed in this article and overall system safety, the trends provide significant confidence in our modern aerospace infrastructure.