Aspects Of Software Development Research Articles

Africa Centre of Excellence for Innovative and STEM Education Lagos State University, Ojo E-mail: mikeade3000@yahoo.com 0000-0002-8003-6761; 0000-0002-9973-6741 ; 0000-0002-7096-0352

Examination of data from a variety of sources could be a very effective tool for needs elicitation and management (Franch, 2020) and an indigenously developed platform for learning purposes should not be excluded or ignored (Adewusi, Egbowon & Akindoju, 2021). With the use of natural language processing or machine learning in analysing, data are tough to grasp since they necessitate high-quality data and specialised knowledge from several domains, and more importantly, their generalisation remains a difficult task (Franch, 2020). Although data-driven approaches are becoming more prevalent in practically every aspect of software development and or engineering, the issue of requirement engineering is still not being addressed to ensure that designed software, particularly indigenous applications, is appropriate to the end-users such as parents, government and stakeholders in all educational sector all over the world. However many countries shut down their schools in a bid to avoid the spread of COVID-19. This Chapter examines Requirement Engineering in Learning Analytics (Machine Learning) in an Indigenously Designed Learning Platform using a Case Study Keywords: Requirement Engineering, Learning Analytics, Machine Learning

Placing Trust in Automated Software Development Processes

Automation of certain aspects of software development and maintenance help us achieve our software-productivity goals, but we need to consider the trust we can place in that automation.

Complexity in the adaptation of aspect-oriented software Development

The software products are an integral part of the modern era and this encourages the developers to explore new techniques for the development. As the software products are becoming more complex, this demands a new technique to deal with the complexity. Aspect-Oriented Software Development is an example of a technique that deals with modern complex systems. As the structure of the new technique is also complex for the new developers, they want to change their way of development according to the new demands and there is no model for the new developers. This paper purposed a model using the basic phases of software development. This model educates and encourages the new developers to adopt the new software development technique. The Paper also discusses the common tools and techniques regarding the different phases of aspect-oriented software development (AOSD) to deal with the complexity of the system more efficiently.

Operationalizing Human Values in Software Engineering: A Survey

Human values (e.g., pleasure, privacy, and social justice) are what a person or a society considers important. The inability to address them in software-intensive systems can result in numerous undesired consequences (e.g., financial losses) for individuals and communities. Various solutions (e.g., methodologies, techniques) are developed to help "operationalize values in software". The ultimate goal is to ensure building software (better) reflects and respects human values. In this survey, "operationalizing values" is referred to as the process of identifying human values and translating them to accessible and concrete concepts so that they can be implemented, validated, verified, and measured in software. This paper provides a deep understanding of the research landscape on operationalizing values in software engineering, covering 51 primary studies. It also presents an analysis and taxonomy of 51 solutions for operationalizing values in software engineering. Our survey reveals that most solutions attempt to help operationalize values in the early phases (requirements and design) of the software development life cycle. However, the later phases (implementation and testing) and other aspects of software development (e.g., "team organization") still need adequate consideration. We outline implications for research and practice and identify open issues and future research directions to advance this area.

ANALYSIS OF FLEXIBLE METHODOLOGIES OF SOFTWARE DEVELOPMENT FOR IMPLEMENTATION IN TEAM PROJECTS

The materials of the article analyze the main models of the software life cycle, which underlie the flexible methodologies of software development to identify the features of its application during the implementation of team projects. It was found that the use of classical life cycle models, in particular, cascade, spiral, incremental, V-shaped and iterative, is not effective in implementing all modern aspects of software development based on the use of new information technologies. It was conducted the comparative analysis of the most popular flexible methodologies of software development Agile, Scrum, Kanban, RUP, DSDM, RAD on such indicators as life cycle model, number of iterations, purpose of project creation and types of projects for implementation, priorities, possibility of interaction with the customer, adaptation to change. The advantages and disadvantages of flexible software development methodologies made it possible to single out the MSF methodology, which is based on the harmonization of cascading, spiral and iterative models of the software development lifecycle and allows you to choose the Scrum template as the most successful for implementing and demonstrating work in team development projects. MSF uses an approach that involves the gradual creation of a working product with some functionality that reflects the requirements for the final product at this stage. It is proposed to use Microsoft solutions based on Visual Studio and Team Foundation Server for centralized management of team project elements, use of visual architecture modeling tools, code quality management capabilities and obtaining all project team members up-to-date information on project status. This is because the MSF model combines five following main models: team model; process model (sequence of actions required to build a team project); discipline of project management (provides comprehensive planning of all stages of the team project, budget management, resources, costs, scheduling); risk management disciplines and readiness management disciplines (assessment of team project members' knowledge for further distribution of team roles). The article demonstrates an example of creating a training team project based on the use of the Scrum flexible methodology template in Visual Studio based on Team Foundation Server.

XPro: A Model to Explain the Limited Adoption and Implementation of Experimentation in Software Startups

Software startups develop innovative, software-intensive products or services. Such innovativeness translates into uncertainty regarding a matching need for a product from potential customers, representing a possible determinant reason for startup failure. Research has shown that experimentation, an approach based on the use of experiments to guide several aspects of software development, could improve these companies’ success rate by fostering the evaluation of assumptions about customers’ needs before developing a full-fledged product. Nevertheless, software startups are not using experimentation as expected. In this study, we investigated the reasons behind such a mismatch between theory and practice. To achieve it, we performed a qualitative survey study of 106 failed software startups. We built the eXperimentation Progression model (XPro), demonstrating that the effective adoption and implementation of experimentation is a staged process: first, teams should be aware of experimentation, then they need to develop an intention to experiment, perform the experiments, analyze the results, and finally act based on the obtained learning. Based on the XPro model, we further identified 25 inhibitors that prevent a team from progressing along the stages properly. Our findings inform researchers of how to develop practices and techniques to improve experimentation adoption in software startups. Practitioners could learn various factors that could lead to their startup failure so they could take action to avoid them.

Experiments on Model-Based Software Energy Consumption Analysis Involving Sorting Algorithms

Although energy has become an important aspect in software development, little support exists for creating energy-efficient programs. One reason for that is the lack of abstractions and tools to enable the analysis of relevant properties involving energy consumption. This paper presents the results of some experiments involving the gathering, modelling, and analysis of energy-related information, in particular, the costs of executing certain parts of a software. We combine some existing free and open-source tools to carry out the experiments, extending one of them to handle energy information. Our experiments consider a comparison of energy consumption of Java implementations of the Bubble Sort, Insertion Sort and Selection Sort algorithms using different data structures. We show how to combine an energy measurement tool and a model analysis tool to carry such a comparison. Based on this support and on our experiments, we believe this is a first step to allow developers to start creating more energy-efficient software.

Managing the social aspects of software development ecosystems: An industrial case study on personality

AbstractThe social aspects of software development encompass concerns such as motivating practitioners, building effective teams, and developing personal relations. Not surprisingly, perhaps, many software projects fail due to personality conflicts within team members. This study investigates the personality traits of 132 software practitioners by employing a tailored interactive assessment that was specifically developed for software development organizations. To assess the personality characteristics of the software teams as a whole, the results of 20 project teams were visualized by using personality–team radar charts. The validity part of the study was performed through validation interviews with experts from the field, discussing their experiences using the interactive assessment. The findings of this investigation complement those of earlier studies that suggest that productive team members who were working on social isolation showed higher introversion. In particular, this study strengthens the idea that agreeableness was observed in agile teams. Ultimately, the present data also highlight the existence of conscientiousness personalities in agile software development.

How do you Propose Your Code Changes? Empirical Analysis of Affect Metrics of Pull Requests on GitHub

Software engineering methodologies rely on version control systems such as git to store source code artifacts and manage changes to the codebase. Pull requests include chunks of source code, history of changes, log messages around a proposed change of the mainstream codebase, and much discussion on whether to integrate such changes or not. A better understanding of what contributes to a pull request fate and latency will allow us to build predictive models of what is going to happen and when. Several factors can influence the acceptance of pull requests, many of which are related to the individual aspects of software developers. In this study, we aim to understand how the affect (e.g., sentiment, discrete emotions, and valence-arousal-dominance dimensions) expressed in the discussion of pull request issues influence the acceptance of pull requests. We conducted a mining study of large git software repositories and analyzed more than 150,000 issues with more than 1,000,000 comments in them. We built a model to understand whether the affect and the politeness have an impact on the chance of issues and pull requests to be merged-i.e., the code which fixes the issue is integrated in the codebase. We built two logistic classifiers, one without affect metrics and one with them. By comparing the two classifiers, we show that the affect metrics improve the prediction performance. Our results show that valence (expressed in comments received and posted by a reporter) and joy expressed in the comments written by a reporter are linked to a higher likelihood of issues to be merged. On the contrary, sadness, anger, and arousal expressed in the comments written by a reporter, and anger, arousal, and dominance expressed in the comments received by a reporter, are linked to a lower likelihood of a pull request to be merged.

JPIAspectZ: A Formal Requirement Specification Language for Joint Point Interface AOP Applications

Aspect-oriented software development (AOSD) solves a few issues of the object-oriented software development (OOSD) approach and adds a few more concerning modules and their relationships. Join point interface (JPI) is an AOSD methodology that by the definition of the interface between advised artifacts and aspects solves associated AOSD issues to get software with a high modularity level. Looking for a JPI software development approach, this article proposes and exemplifies the use of JPIAspectZ, an extension of the formal aspect-oriented language AspectZ for the software JPI requirement specifications. Mainly, JPIAspectZ looks for a concept and model consistency in a JPI software development process. Since the main JPI characteristics are the joining point interfaces definitions, i. e. explicit associations definition between aspects and advised modules, thus, by JPI, classes are no longer oblivious of possible interaction with aspects, and aspects, for their action effectiveness, do not depend anymore on signatures of advisable module components. JPIAspectZ fully supports these JPI principles. As JPI application examples, this article shows the formal requirements specification for classic aspect-oriented and JPI examples, along with describing the advantages and disadvantages of this language.

Exploring the Quality Improvement in Small Scale Project Using Aspect-Oriented Design

Aspect-oriented software development (AOSD) seeks to renovate the software quality by use of alteration to the design in object-oriented based systems. Each system component has been divided into numbers of modules and arranges a design in a way that the module has not crosscut to each other. A module is a collection of block of codes, whose role is to restrict and conceal the design definition. This type of behavior is known as the Separation of Concerns (SoC). AOP helps programmers for separating crosscutting concerns. It can be helpful at better modularizing system, the problem with complex system is that the component require different, crosscutting descriptions at different levels and need maintenance too. In this paper, a study was conducted to analyses quality in aspect-oriented software design. This paper also explores varieties of existing metrics related to AOP also and will discuss in detail with comparison of OOPs using small scale projects that how the new programming paradigm design effects on quality of the software.

Disaster responsive planning: the role of societal forces in implementing software applications

Open source software development is frequently used to serve human society, especially in finding solutions for managing and planning disaster situations such as floods, droughts and tsunami incidents. Careful consideration of the technical accuracy as well as social acceptance is essential to guarantee the sustainability of software development. Understanding the interaction between technology and human behaviour is vital in open source software development in terms of minimizing the negativities after the implementation. The social aspects of software development often being neglected or not being considered well enough in practical filed. The paper discusses the societal factors that can attribute when implementing open source disaster relief management platforms. Humanitarian disaster relief coordination involves some actors with different levels of power and authority. By using theories of multilevel governance and power relations, this paper focuses on understanding the consequences that may arise when implementing common open source platforms, especially in disaster management sector in developing counties. Finally, the article provides recommendations to minimize such obstacles for better functionality and the sustainability of the platform.

Toward the Design and Implementation of Traceability Engineering Tool Support

Requirements of a system keep on changing based on the need of stakeholders or the system developers, making requirement engineering an important aspect in software development. This develops a need for appropriate requirement change management. The importance of requirements traceability is defining relationships between the requirements and artefacts extracted by the stakeholder during the software development life-cycle and gives vital information to encourage software understanding. In this paper, we have concentrated on developing a tool for requirement traceability that can be used to extend the requirement elicitation and identification of system-wide qualities using the notion of quality attribute scenarios to capture the non-functional requirements. It allows us to link the functional and non-functional requirements of the system based on the quality attribute scenarios template proposed by the Carnegie Mellon Software Engineering Institute (SEI). Apart from this, the paper focuses on tracing the functional and non-functional requirements of the system using the concept of requirement traceability matrix.

Modelo de requerimientos y de funcionalidad de software basado en MDA y UML para la gestión de proyectos y convenios globales

Modelo de requerimientos y de funcionalidad de software basado en MDA y UML para la gestión de proyectos y convenios globales Luis Alberto Lujan Campos Escuela de Post Grado, Universidad Nacional Federico Villarreal, Jr. Camana 1014, Lima, Perú Recibido el 01 de junio del 2017. Aceptado el 1 de julio del 2017 DOI: https://doi.org/10.33017/RevECIPeru2017.0002/ Resumen El propósito es elaborar modelos de la arquitectura que son independientes de la plataforma de software para la gestión de información de proyectos y convenios globales. Que sean orientados por el enfoque Model Driven Architecture (MDA, Arquitectura Dirigida por Modelos) que puede ayudar a resolver al mismo tiempo tanto los problemas de la industrialización y las infraestructuras de software en constante cambio [1]. Este enfoque de arquitectura de software promueve la separación de la especificación de la funcionalidad de la implementación de esta funcionalidad en plataformas específicas. En la arquitectura del sistema de software para la gestión de proyectos y convenios globales se determinó los módulos principales: módulo de cooperantes, módulo de datos del proyecto o convenio, módulo de presupuesto, módulo de finanzas y módulo de seguimiento de actividades y se logró elaborar los siguientes modelos: requisitos, estructura de clases de objetos y de secuencia. Estos modelos son los conductores primarios en todos los aspectos del desarrollo de software. Los modelos tienen diversas vistas como: Modelo de la estructura del sistema y de la funcionalidad de los módulos. Para la elaboración de los modelos se ha utilizado el Unified Modeling Language (UML, Lenguaje Unificado de Modelado). UML es un lenguaje de modelado y no un método, es la notación (principalmente gráfica) del que se valen los métodos para expresar los diseños y que en el proceso de software es la orientación que nos dan sobre los pasos a seguir para hacer el diseño [2]. Descriptores: Arquitectura Dirigida por Modelos, Lenguaje Unificado de Modelado, Diseño de software Abstract The purpose is to develop architecture models that are independent of the software platform for the management of information of global projects and agreements. That is guided by the Model Driven Architecture (MDA) approach that may help solving at the same time both problems of industrialization and ever-changing software infrastructures [1]. This software architecture approach promotes the separation of the specification from the functionality of the implementation of this functionality into specific platforms. In the architecture of the software system for the management of global projects and conventions, the main modules were determined: cooperators module, data module of the project or agreement, budget module, finance module and activity tracking module and elaboration The following models: requirements, structure of object classes and sequence. These models are the primary drivers in all aspects of software development. The models have different views such as: Model of the structure of the system and the functionality of the modules. For the elaboration of the models the Unified Modeling Language (UML) has been used. UML is a modeling language and not a method, it is in the notation (mainly graph) of which the methods are used to express the designs and that in the software process is the orientation that they do not give on the steps to follow to do the design [2]. Keywords: Model Driven Architecture (MDA), Unified Modeling Language (UML), Software Design

Gendered work culture in free/libre open source software development

This article adopts a feminist perspective to examine masculine work culture in the development of free/libre open source software. The authors draw on a case study of the ‘Heidi bug’ discovered during the development of the Mozilla Firefox web browser to examine how ‘gendered talk’ was (en)‐acted to facilitate ‘bricolage’ in an online work environment. Such gendered talks contain cultural references familiar to male developers. Though seemingly innocuous, such acts could be seen as a performance of gender that simply reflects the hegemonic heterosexual masculine culture manifested in an online virtual work space. The virtual work space therefore can be exclusive to those who shared the cultural references. Although it may not necessarily be ignorance or insensitivity of male developers, a more gender‐balanced, women‐friendly and inclusive workplace certainly would benefit from a more diverse environment. This article highlights the gendered aspect of software development through examining the language use and mainstream ‘bricolage’ practice, and establishes a compelling ground for enlarging the talent pool to include more women and integrating gender ethics (e.g., raising awareness of sensitive language and design approaches) into computer ethics education.

ASPECT-ORIENTED SOFTWARE TESTING TECHNIQUES: A REVIEW

- Software testing is a prominent area of research as it ensures the quality and reliability of the software. Testing an aspect-oriented software is also the latest area of research. Although, research in aspect-oriented software testing has reported a couple of new testing techniques. But, there is no work yet indicated in the literature to focus on the basic fundamentals of the aspect-oriented software testing and relationship with traditional software testing techniques. Therefore, this position paper handles this shortcoming and presents the basic concepts of aspect-oriented programming, phases of aspect-oriented software development life cycle and testing phases for new researchers to gather the information on the subject. This paper also presents a comprehensive detail about the relationship of aspect-oriented software testing techniques with other traditional testing techniques.

Towards an affordable brain computer interface for the assessment of programmers’ mental workload

Abstract This paper provides a proof of concept for the use of wearable technology, and specifically wearable Electroencephalography (EEG), in the field of Empirical Software Engineering. Particularly, we investigated the brain activity of Software Engineers (SEngs) while performing two distinct but related mental tasks: understanding and inspecting code for syntax errors. By comparing the emerging EEG patterns of activity and neural synchrony, we identified brain signatures that are specific to code comprehension. Moreover, using the programmer's rating about the difficulty of each code snippet shown, we identified neural correlates of subjective difficulty during code comprehension. Finally, we attempted to build a model of subjective difficulty based on the recorded brainwave patterns. The reported results show promise towards novel alternatives to programmers’ training and education. Findings of this kind may eventually lead to various technical and methodological improvements in various aspects of software development like programming languages, building platforms for teams, and team working schemes.

The Adoption of Agile Software Methodology with Team Software Process (TSPI) Practices in the Software Engineering Undergraduate Course


 
 
 In computer science, software engineering courses expose the undergraduate students to both the technical and methodological aspects of software development. The traditional software development methods and techniques represent a huge proportion of the courses and hence contribute an essential part of software engineering students’ development process. This plan-driven development is dependent on a set of predefined phases and ongoing documentation which found to be problematic; such as time-consuming, slipped requirements and complicated processes. The main aim of this paper is to study and review the adoption of Agile Software Methodology and Team Software Process (TSPi) practices in the undergraduate course focus on software development. The framework and course plan will be designed to apply and observe the implementation. Furthermore, this study will help to gather the teams’ viewpoint regarding the importance of Agile and TSPi practices in handling small projects with real clients.
 
 

An Efficient Software Defect Analysis Using Correlation-Based Oversampling

In software industry, probability of risks in large project is increasing due to the presence of defective modules which leads to failure in software execution. Quality assurance is one of the important aspects of software development. The extracted information from software repositories about defective modules can help project managers a lot for completion of projects on time with reliable quality. There are many existing knowledge extracting techniques for software defect analysis and prediction, but they have considered this problem in a general framework. Class imbalance is one of the major problems for constructing efficient decision trees for extracting knowledge from software defect datasets. To overcome this problem, a novel approach called as ICOS (Improved Correlation over Sampling) is proposed for handling class imbalance software defect datasets. This proposed approach uses oversampling strategy to generate new instances using synthetic and hybrid category approaches. The experimental results confirm that the proposed approach can efficiently identify the modules which are error-prone using simple rules.

Conceptual Framework for Knowledge Flow in Software Development Process

The main aim of this study to merge knowledge flow activities with software development process Past models of flow of knowledge lacked in terms of software development and lacked on sharing right knowledge and lacked in-depth exploration of context modeling, which made those models less applicable. In addition now it attracts much consideration, attention in the knowledge management field. In a knowledge-based organization, knowledge workers need to acquire a variety of knowledge (information) about their tasks. Therefore; many organizations have built knowledge support plat forms to assist workers in meeting their knowledge-needs. These platforms help workers to identify and share knowledge in order to speed up organization innovation and improve employee Productivity. This research proposes a conceptual framework of context oriented flow of knowledge in software development aspects. In this framework, the context is seen as an inseparable element of flow of knowledge, which is regarding the creation, transformation as well as application of knowledge items. One of the main challenges is how to exploring knowledge flow, sharing knowledge in software development process. The main goal for this research to provide a framework to solve this challenge. In this research used questionnaire instrument with 21 people as they are from software development process environment, also in this study want to improve all factors, task, type of knowledge, nature of knowledge used in software development process during the flow of knowledge. Finally in this study validate the framework using experts review, 4 experts from academic and industrial result was great shows all phases in software development process and factors when active, moreover in this research verified the component by using cronpach alpha methods the result was good in acceptable rang 0.711.