NMorph Framework: An Innovative Approach to Transpiler-Based Multi-Language Software Development

Target language extraction (TLE) is a novel task in the field of selective auditory attention, which seeks to extract all speech signals that are spoken in a target language from other sources in a multilingual cocktail party. In our prior studies, a TLE model was trained to extract a predefined, single target language, referred to as Single-TLE. In this paper, we extend the Single-TLE framework to Multi-TLE. Multi-TLE models can also extract all speech signals of one specific target language, but they are optimized on a set of multiple target languages during training. As such, they learn the characteristics of several target languages and can replace multiple Single-TLE models without retraining. We perform experiments on the GlobalPhoneMCP database and incorporate a dynamic language mixing scheme for training. The Multi-TLE model does not only outperform Single-TLE models, but when given a language ID as additional input, it is also able to extract the speech of a specific target language from a mixture which contains multiple learned target languages.

Software Requirements Changes is a typical phenomenon in any software development project. Restricting incoming changes might cause user dissatisfaction and allowing too many changes might cause delay in project delivery. Moreover, the acceptance or rejection of the change requests become challenging for software project managers when these changes are occurred in Software Development Phase. Where in Software Development Phase software artifacts are not in consistent state such as: some of the class artifacts are Fully Developed, some are Half Developed, some are Major Developed, some are Minor Developed and some are Not Developed yet. However, software effort estimation and change impact analysis are the two most common techniques which might help software project managers in accepting or rejecting change requests during Software Development Phase. The aim of this research is to develop a new software change effort estimation model which helps software project manager in estimating the effort for software Requirement Changes during Software Development Phase. Thus, this research has analyzed the existing effort estimation models and change impact analysis techniques for Softwrae Development Phase from the literature and proposed a new software change effort estimation model by combining change impact analysis technique with effort estimation model. Later, the new proposed model has been evaluated by selecting four small size software projects as case selections in applying experimental approch. The experiment results show that the overall Mean Magnitude Relative Error value produced by the new proposed model is under 25%. Hence it is concluded that the new proposed model is applicable in estimating the amount of effort for requirement changes during SDP.

The focus of this research paper is on the analysis of factors which affect software testing techniques in Object Oriented Software with the opinion of people who are engage in software development phases. The study uses a survey instrument to analyze the factors and identify factors that have significant impact on software testing techniques. The research focuses on the perspective of the primary participants, managers, programmers, testers and other people involved in software research or development teams. The original contribution of this research is to provide a general guide to the important aspects to consider in the whole software development process.

The variety and complexity of processes required to be controlled in modern manufacturing places heavy demands on PLCs. To meet these demands PLC manufacturers are producing increasingly more powerful PLCs which require more complex programming languages. These complex programming languages result in longer specialised training and familiarisation times. To overcome these problems, the PLC programming language standard IEC 1131-3 was created. The standard details the workings of languages which provide PLC users with a set of programming languages based around familiar PLC concepts, but with language constructs similar to those of current generation PC programming languages. This paper describes the work done in a TCS partnership between Elite Control Systems Ltd. and Napier University to examine the viability of using structured methods for developing PLC software. Object oriented methods have established themselves as the future of software development for high level language users. We discuss how the object modelling technique of Rumbaugh et al. (1991) [one of the principal object oriented methods used in the UK] can be adapted for the creation of PLC software, and how the resulting practices differ from traditional PLC software development. We then describe the improvements in terms of software quality, development time, development costs, and maintainability that we have observed by adopting these techniques.

As interests in security increases, several software development lifecycle considering security have been proposed. Actual results of applying software development lifecycle considering security reduced threats have been reported. But to apply software development lifecycle considering security, requires expertise and experiences. In this paper a secure software development lifecycle applying integrated secure guide is proposed. Secure Guides such as Misuse Case, Security Patterns and Secure Coding are integrated in the proposed method. And then, by applying integrated Secure Guide in each software development phase, the security becomes available in every phase of software development. Since, proposed secure guide provides more security information than available secure guides, software developer can use more security information while they are developing software. As a result, it is expected that developers could consider security more easily when developing software even though developers lacks expertise in security or experience.

A lot of research on software project risk associated with the software development lifecycle. To accommodate the many risk factors in software development, the Software Engineering Institute (SEI) then launched a risk taxonomy model that consist of 3 classes, 13 elements, and 63 attributes. This study aims to map the risk factors obtained from the results of a systematic literature review, then adjust the risk weights for 12 software development activities. Of the 197 risk factors that have been mapped into 12 activities, then adjusted weight for each activity is calculated next. The results of this study indicate that the Implementation activity in the software development phase is the activity with the greatest potential risk, which is 9.57 percent. Meanwhile, in the on-going lifecycle phase, the greatest potential risk is Project Management activity as much as 19.14 percent. That's why an experienced project manager can reduce impact of software development project risk failure.

Standard workday today includes use of software applications that enable faster task processing and can do so for several tasks in parallel for us. Still, also the best applications can stop working or may not work correctly. For investigating such unintended malfunctioning of a software application, logging is very important. By examining application logs, software developers can find the cause and provide an update or patch with fixed bugs. On the other hand, logging can provide enormous amount of data that can flood the memory. That is why it is important not to log everything. The decision about logging (how to do logging of what data) is done during the software development phase. This paper describes research that has been focused on logging strategies in form of case studies of software development projects and in conclusion we give some guidelines for future decisions on logging for software development teams that may lead to logging improvement.

Software development is a highly knowledge intensive activity. During the software life cycle, knowledge and experiences are accumulated over time. One of the main knowledge sources in software development is lessons learned. Even though lessons learned have been a common practice for process improvement, however, there are arguments that lessons learned are not used effectively and organizations continuously fail to learn from past projects. In this paper, we propose utilizing lessons learned by transforming it into an experience base incorporated with software engineering life cycle for the purpose of sharing and future reuse. An initial model is formulated based on literature analysis and a preliminary study. The goal of the study is to assess the experts' perception on the model formulation in terms of its importance in each software development phase, and which knowledge element is more valuable as future reuse. Additionally, results from the study show that such model can bring positive impact to individuals as well as organizations.

Building secure software is about taking security into account during all phases of software development. This practice is missing in, widely used, traditional developments due to domain immaturity, newness of the field and process complexity. Software development includes two views, a product view and a process view. Product view defines what the product is, whereas process view describes how the product is developed. Here we are concerned with the process view. Modelling the process allows simulate and analyze a software development process, which can help developers better understand, manage and optimize the software development process. In this paper we present our approach S2D-ProM, for Secure Software Development Process Model, which is a strategy oriented process model. This latter, capture steps and strategies that are required for the development of secure software and provide a two level guidance. The first level guidance is strategic helping developers choosing one among several strategies. The second level guidance is tactical helping developers achieving their selection for producing secure software. The proposed process model is easily extensible and allows building customized processes adapted to context, developer's finalities and product state. This flexibility allows the environment evolving through time to support new securing strategies.

Software Testing from an Agile and Traditional view

The principles of ethics are not a new topic in the area of Software Engineering; this term emerged in the 90s after the rise of computers due to incorrect practices in software development. This research aims to classify the ethical problems arising in the software development life cycle, for which a preliminary secondary study (PSS) was conducted. As a result of the PSS, 27 primary studies were obtained. These studies propose methodologies and solutions for some ethical issues in a specific phase. Therefore, we classified the ethical issues, but not all adversities can be included due to the variety of problems. We conclude that no research papers classify ethical issues arising in the phases of software development.

In this paper, we identify a set of factors that may be used to forecast software productivity and software development time. Software productivity was measured in function points per person hours, and software development time was measured in number of elapsed days. Using field data on over 130 field software projects from various industries, we empirically test the impact of team size, integrated computer aided software engineering (ICASE) tools, software development type, software development platform, and programming language type on the software development productivity and development time. Our results indicate that team size, software development type, software development platform, and programming language type significantly impact software development productivity. However, only team size significantly impacts software development time. Our results indicate that effective management of software development teams, and using different management strategies for different software development type environments may improve software development productivity.

Software developers need to cope with a massive amount of knowledge throughout the typical life cycle of modern projects. This knowledge includes expertise related to the software development phases (e.g., programming, testing) using a wide variety of methods and tools, including development methodologies (e.g., waterfall, agile), software tools (e.g., Eclipse), programming languages (e.g., Java, SQL), and deployment strategies (e.g., Docker, Jenkins). However, there is no explicit integration of these various types of knowledge with software development projects so that developers can avoid having to search over and over for similar and recurrent solutions to tasks and reuse this knowledge. Specifically, Q&A sites such as Stack Overflow are used by developers to share software development knowledge through posts published in several categories, but there is no link between these posts and the tasks developers perform. In this paper, we present an approach that (i) allows developers to associate project tasks with Stack Overflow posts, and (ii) recommends which Stack Overflow posts might be reused based on task similarity. We analyze an industry dataset, which contains project tasks associated with Stack Overflow posts, looking for the similarity of project tasks that reuse a Stack Overflow post. The approach indicates that when a software developer is performing a task, and this task is similar to another task that has been associated with a post, the same post can be recommended to the developer and possibly reused. We believe that this approach can significantly advance the state of the art of software knowledge reuse by supporting novel knowledge-project associations.

Structural analysis software and the C programming language

Parallel architecture for functional programming