Aspects Of Software Development Research Articles

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.

Teaching Computer Programming to Medical Doctors, Nurses and Hospital Staff: A Pilot Study

There is plenty of opportunity where the medical world can benefit from caregivers who can translate point-of-care challenges into digital solutions using coding skills. The objective of this pilot study is to evaluate the feasibility of teaching computer programming to hospital staff with no or limited programming experience. In October 2015 during the EU Code Week 2015 we organized a 2-day introductory workshop Building Medical Apps for hospital staff (n=14) using Apple's XCode integrated development environment with the Swift programming language. The first day focused on basic programming fundamentals, whereas the second day focused on building a graphical user interface and adding interactivity with code. General programming knowledge improved with a mean of 1.4±0.5 and a median of 1.0 (IQR 1.0) points. App building skills improved with a median of 0.9±0.5 and a median of 1.0 (IQR 0.0) points. The degree to which participants considered having programming skills to be important increased with a mean of 1.2±0.9 and a median of 1.0 (IQR 2.0) points. The willingness to develop apps if participants were to be supported in legal aspects of software development increased with 1.0±0.7 and a median of 1.0 (IQR 0.0) points. In conclusion, this pilot demonstrates feasibility of teaching computer programming to an audience of medical doctors, nurses and hospital staff. Two days of training was sufficient to get a basic level of skills to build a simple mobile app. Participants expressed a desire to continue using these skills, provided they would get support from the hospital such as a helpdesk for questions and regulatory affairs.

Extending Unified Modeling Language to Support Aspect-Oriented Software Development

Aspect-Oriented Software Development (AOSD) is continuously gaining more importance as the complexity of software systems increases and requirement changes are high- rated. A smart way for making reuse of functionality without additional effort is separating the functional and non functional requirements. Aspect-oriented software development supports the capability of separating requirements based on concerns. AspectJ is one of the aspect-oriented implementations of Java. Using Model Driven Architecture (MDA) specifications, an AspectJ model representing AspectJ elements can be created in an abstract way with the ability to be applied in UML, Java or XML. One of the open source tools which support MDA and follows the standards of the Object Management Group (OMG) for both UML and MDA is Eclipse providing an implementation of MDA through Eclipse Modeling Framework (EMF). This paper focuses on creating a UML profile; a UML extension which supports language specifications for AspectJ using EMF. Our work is based on the latest UML specification (UML 2.5) and uses MDA to enable the inclusion of aspect-oriented concepts in the design process.

Preserving use case flows in source code: Approach, context, and challenges

Being able to see use case steps directly in code would make the intent expressed by the code more comprehensible and easier to maintain. In this paper, an approach to preserving use case flows (of events) in source code called InFlow is presented within a broader context of its application in the software development process along with the issues that remain as challenges. The approach preserves individual steps of use case flows in the form of their counterpart statements, as well as their ordering. This is achieved by mimicking each use case flow by a sequence of method implementations with each step of the use case flow corresponding to one statement in one of these methods, enabled by the annotation named InFlow. A study of implementing an audio streaming service using InFlow, DCI, and aspect-oriented software development with use cases has been performed and assessed using several metrics in order to determine the level of preserving use case flows in source code. Although InFlow introduces a lot of indirect references to code, the overall results speak in favor of InFlow. DCI adds more complexity to following a use case flow in code than other two approaches. Complexity of making a change to a use case flow ended up with closely matching results. But InFlow guarantees traceability of use case implementation from the domain model implementation.

Systematic review of aspect-oriented formal method

Aspect-oriented modelling is used in a growing number of business and software development projects. However, the plethora of unstandardised aspect-oriented approaches is preventing companies from adapting aspect-oriented software development methods into a formal method. Both aspect-orientation and formal methods have evolved separately and little has been done to investigate the benefits of the possible integration of these two fields. Therefore, in this paper we aim to present a survey of the approaches used to date in the application of the aspect-oriented paradigm to formal methods of specification. We also systematically review some of the techniques and approaches that combine both concepts together and discuss the problems and issues that arise in relation to the combination of formal methods and aspect orientation. In addition, we identify the open research questions to highlight potential areas of future research.

Systematic review of aspect-oriented formal method

Aspect-oriented modelling is used in a growing number of business and software development projects. However, the plethora of unstandardised aspect-oriented approaches is preventing companies from adapting aspect-oriented software development methods into a formal method. Both aspect-orientation and formal methods have evolved separately and little has been done to investigate the benefits of the possible integration of these two fields. Therefore, in this paper we aim to present a survey of the approaches used to date in the application of the aspect-oriented paradigm to formal methods of specification. We also systematically review some of the techniques and approaches that combine both concepts together and discuss the problems and issues that arise in relation to the combination of formal methods and aspect orientation. In addition, we identify the open research questions to highlight potential areas of future research.

An Approach for Detecting Unnecessary Cyclomatic Complexity on Source Code

Seeking product's quality is essential nowadays. One of the many quality aspects in software development is the source code complexity. Not paying attention to the complexity during the development can result in unexpected cost, caused by the difficulty on the source code understanding. The goal of this paper is to introduce an initial approach to identify unnecessary complexity in source code. Besides identifying, the approach can also show to its user how to properly rewrite the source code without the unnecessary complexity. The approach is based on the static analysis of the source code control flow graph. Once the unnecessary complexity is identified, the graph is refactored in order to allow the user to understand the improvement on the source code. The approach was included in a software tool in order to prove its concept. A performance evaluation of the approach was performed, resulting in a high accuracy. Two experimental studies were also performed to assess the viability of the approach when used by real users. The evidences provided by these studies suggests that the approach support the unnecessary complexity removal.

An approach based on runtime models for developing dynamically adaptive systems

We propose an approach based on runtime models and Aspect Oriented Software Development for modeling and implementing dynamically adaptive systems. Such system requires specific modeling formalisms to support the definition of the monitoring and reconfiguration modules at an abstract level. The verification of the consistency during the reconfiguration is also an essential and primordial task in the development process of dynamically adaptive systems. In addition, a middleware that enables to perform the dynamic reconfiguration during execution should be implemented.Our proposed approach addresses these requirements: It enables specifying dynamically adaptive systems using AADL and AO4AADL and verifying the integrity of the system at any time of its life cycle even at runtime based on a set of architectural patterns. Our approach uses the Aspect Oriented Software Development to ensure the monitoring of the system and perform the reconfiguration through a set of routines developed in our middleware.

Security Injections@Towson

Despite the critical societal importance of computer security, security is not well integrated into the undergraduate computing curriculum. Security classes and tracks treat security issues as separable topics as opposed to fundamental issues that pervade all aspects of software development. Recently, there has been an increasing focus on security as a cross-cutting concern across the computer science curriculum. The Security Injections@Towson project provides resources and effective strategies to incorporate secure coding in the early programming classes. We describe the development, assessment, and dissemination of more than 40 lab-based security injection modules designed to be injected into courses with minimal impact on the curriculum. We include assessment results from 1,135 students across five diverse institutions demonstrating that the security injections help students retain, comprehend, and apply secure coding concepts in the introductory programming courses.

Aspect-oriented middleware framework for resolving service discovery issues in Internet of Things

Internet of Things IoT is a model of future internet and pervasive computing which have its own challenges derived from the internet in terms of scalability, undefined topology and so on. The proposed work aims to resolve the challenges posed by IoT in service discovery functionality. Considering the pervasive and context dependent nature of IoT the planned work bases its development strategy using an aspect oriented software development methodology. The novelty lies in achieving high degree configuration and customisability by selecting subset of middleware functionality depending on the need. The performance is compared with MUSIC pervasive computing middleware and Android built-in configuration. The result reveals 6.5% decrease on average boot up and reconfiguration time for smart phones and 11.6% percentage decrease in Android tablets. In the context of boot up and reconfiguration time the middleware brings out 5% decrease for smart phones and 3% for Android tablets when compared with MUSIC middleware. The middleware shows 6.3% and 4% reduction in execution time of applications on smart phones and tablets when assessed with MUSIC middleware.

Pareto Analysis of Critical Success Factors for Total Quality Management Targeting the Service Industry

Quality is an important aspect of software development. This is the reason some researchers and practitioners have attempted to integrate TQM concepts into software engineering. Total Data Quality Management (TDQM) methodology claims that we should manage data as we manage products, but principles, guidelines, and techniques of Total Quality Management for physical products have limitations in TDQM practices because of the nature of data. In our research we have studied about 22 research papers in which different strategies, issues of TQM challenges and how to overcome these challenges are discussed.