Software Development Approach Research Articles

Implementation of the perfect plasticity approximation with biogeochemical compartments in R

Modeling forest ecosystems is a landmark challenge in science, due to the complexity of the processes involved and their importance in predicting future planetary conditions. While there are a number of open‐source forest biogeochemistry models, few papers exist detailing the software development approach used to develop these models. This has left many forest biogeochemistry models large, opaque and/or difficult to use, typically implemented in compiled languages for speed. Here, we present a forest biogeochemistry model from the SORTIE‐PPA class of models, PPA‐SiBGC. Our model is based on the perfect plasticity approximation with simple biogeochemistry compartments and uses empirical vegetation dynamics rather than detailed prognostic processes to drive the estimation of carbon and nitrogen fluxes. This allows our model to be used with traditional forest inventory data, making it widely applicable and simple to parameterize. We detail the conceptual design of the model as well as the software implementation in the R language for statistical computing. Our aim is to provide a useful tool for the biogeochemistry modeling community that demonstrates the importance of vegetation dynamics in biogeochemical models.

Integrating security and privacy in software development

As a consequence to factors such as progress made by the attackers, release of new technologies and use of increasingly complex systems, and threats to applications security have been continuously evolving. Security of code and privacy of data must be implemented in both design and programming practice to face such scenarios. In such a context, this paper proposes a software development approach, Privacy Oriented Software Development (POSD), that complements traditional development processes by integrating the activities needed for addressing security and privacy management in software systems. The approach is based on 5 key elements (Privacy by Design, Privacy Design Strategies, Privacy Pattern, Vulnerabilities, Context). The approach can be applied in two directions forward and backward, for developing new software systems or re-engineering an existing one. This paper presents the POSD approach in the backward mode together with an application in the context of an industrial project. Results show that POSD is able to discover software vulnerabilities, identify the remediation patterns needed for addressing them in the source code, and design the target architecture to be used for guiding privacy-oriented system re-engineering.

EARL—Embodied Agent-Based Robot Control Systems Modelling Language

The paper presents the Embodied Agent-based Robot control system modelling Language (EARL). EARL follows a Model-Driven Software Development approach (MDSD), which facilitates robot control system development. It is based on a mathematical method of robot controller specification, employing the concept of an Embodied Agent, and a graphical modelling language: System Modelling Language (SysML). It combines the ease of use of SysML with the precision of mathematical specification of certain aspects of the designed system. It makes the whole system specification effective, from the point of view of the time needed to create it, conciseness of the specification and the possibility of its analysis. By using EARL it is possible to specify systems both with fixed and variable structure. This was achieved by introducing a generalised system model and presenting particular structures of the system in terms of modelling block configurations adapted by using instances. FABRIC framework was created to support the implementation of EARL-based controllers. EARL is compatible with component based robotic middlewares (e.g., ROS and Orocos).

An Integrated Software Development Method with built-in Software Process Improvement Framework

The concept of a startup is growing around the world where innovation is the major driving force. Managing such a small startup company from both technical and administrative perspective is a challenging issue. Though several approaches for software development, like the waterfall model, agile model, SCRUM model are available, it is difficult to implement such a model with full features due to limited number of resources, lack of experienced resources and lack of enough financial capability. The scopes of software process improvement are even narrower in a situation where they hardly manage or adapt a methodology. As a result, small companies suffer and work without a good quality framework model. Companies struggle to produce quality software. In this work, we have suggested an integrated software engineering methodology, in which, the process improvement framework is a built-in phenomenon. Our system is dubbed as 3D model, where the Ds stand for Design, Develop and Deploy. Design indicates the design of the product making as well as the process design. Develop and Deploy is also hinting to the product and process. The process improvement is managed through observation and management, which are fed back into the system through proper documentation. We did some client surveys, organization surveys, and observed work patterns of a group of human resources for a period. We measured some of the parameters before and after the implementation of 3D model. We found that implementation of 3D model gives an improved process and product development environment with no extra manpower or extra costing.

A proposed framework for improved software requirements elicitation process in SCRUM: Implementation by a real‐life Norway‐based IT project

AbstractSoftware requirement engineering (SRE) is the initial stage of the software engineering process and entails several challenges relating to the identification, implementation, evolution, and management of requirements for the development of software systems that meet the desired functionality quality standards. Agile software development (ASD) is a well‐known software development process that follows a lightweight and adaptive methodology to support the incremental development of software systems. Since the ASD follows an adaptive procedure (ie, a flexible, nanostructured, and dynamic approach) of software development, it becomes challenging to perform SRE that follows a structured approach for managing software requirements throughout the life cycle of software development. The primary challenges for SRE, while pursuing an ASD, include, but are not limited to, identification of incomplete requirements, implementation of vague requirements, prioritization of secondary functional requirements, and compromise on users' involvement that negatively impacts the software system's functionality and quality. To overcome these challenges, some of the recent research efforts have focused on managing different phases of SRE during software development using the ASD. However, there is a lack of solutions that provide software engineers/practitioners with a solution. Besides, frameworks to effectively manage all the phases of SRE as per the needs of the ASD are needed. We propose a framework that unifies joint requirements document (JRD) and SCRUM to incrementally (a) identify, (b) implement, (c) evolve, and (d) manage system requirements throughout the software development cycle. We have used the action research method to qualitatively validate the proposed framework based on data and user requirements collected from a product‐focused (multinational) Norway‐based software company. The results of the validation are based on statistical analysis that reflects the usefulness of the proposed framework for SRE in ASD‐based software engineering and development. Future research is the possible application of a machine learning approach (es) in the intended context for agile requirements elicitations.

Scrum: An Agile Process Reengineering In Software Engineering

BPR (Business Process Re-engineering) is an organizational mechanism leading organization towards change management as and when it is required. In the form BPR, Agile practices have had a remarkable impact on Software Engineering Management (SEM) in software development organizations across the world. It has enhanced collaboration and productivity of Software Engineering (SE) teams and improved the level of quality of software products. Nowadays Scrum has been trending into software development organizations as a standard SDLC approach. Scrum is the framework of the Agile methodology, built on empiricism control theory, asserts that experience brings knowledge and increases decision making capabilities. The empiricism control theory is built on three pillars: Adaptation, Inspection and Transparency. This research study presents Scrum as a trending SDLC framework using empirical analysis. We have analyzed literature reviews, case studies, and research surveys; and implemented Scrum in our software development unit and carried out the reasons, why Scrum is trending in software development organizations. How the scrum artifacts, events and values play a vital role in upholding the Scrum pillars and strengthen the capabilities of Scrum team members to address the software engineering management challenges; compared to traditional software development approaches.

Parallel multi-objective artificial bee colony algorithm for software requirement optimization

In incremental software development approaches, the product is developed in various releases. In each release, a set of requirements is proposed for the development. Usually, due to lack of funds, lack of time and dependency between requirements, there is no possibility to develop all the required requirements. There are two conflicting objectives for choosing an optimal subset of the requirements: increasing customer satisfaction and reducing development costs. This problem is known as the next release problem (NRP) and is categorized as an NP-hard problem. Unlike the standard version of the NRP, we formulate this problem as a restricted multi-objective optimization problem. There exist metaheuristic algorithms for solving this problem performed as serials. In this paper, we introduce a parallel algorithm based on the master–slave model in order to improve the quality of the solutions. Based on the criteria of multi-objective problems, the quality of the obtained solution is compared with several metaheuristic algorithms. Two scenarios and two different datasets are used for experiments. Results indicate that the proposed method in the first scenario would highly improve the quality of solutions. Moreover, the method reduces execution time significantly through improvement in the quality of the solution in the second scenario.

Ontology driven software development for automatic detection and updation of software requirement specifications

Recent studies have shown that due to tight schedule or cost/resource constraint, development or maintenance team generally develops or updates the software system without maintaining the proper Software Requirement Specification documentation. In the above scenario, the situation becomes troublesome to maintain the software system once it goes into the maintenance phase. Therefore, there is a need to develop a mechanism that automatically detects and updates the Software Requirement Specification documentation immediately after any update takes place in the concerned software system. Hence, in this research article, we provide ontology driven software development approach for automatic detection and updation of Software Requirement Specifications. To implement and evaluate the proposed approach, we picked a case study, which clearly shows that it automatically detects the outdated requirements. Also, as a result of our work, we automatically find the requirements that have been added, deleted, or modified to the existing Software Requirements Specification. Moreover, to reflect the updated requirement specification documentation, we provide a mechanism that automatically generates it. Further, the generated documentation is available in the machine as well as in human-readable form along with free of inconsistencies.

REQUIREMENTS GATHERINGS AND IMPLEMENT ISSUES

Summary of the Research Research goal is better understanding and learning by using old and new techniques for resolve problems and empty blank spaces which are mostly facing during requirement gathering phase to development phase. This paper mainly purpose gathering research on Software requirements gathering and their effect on all incoming challenges and cost, benefits. Requirements is one in technology application style and development. . Most of the projects are fail due to gathering the poor requirement gathering. Many of the software based projects acquired by one to one the interview for requirement gathering. During last few years new software development approaches were introduced for increase software product which are helpful for reduce cost, time, and effort. For all procedure Software Requirement gathering is the one of the special key. Requirement gathering is the most important area in Software Engineering and project management.

IoT methodologies: comparative study

Abstract The Internet of Things or the Internet of Everything is a new and a potentially disruptive technology paradigm. It describes several technologies such as RFID, short range wireless communications, and research disciplines that can connect physical objects from the real world to the internet. To implement IoT solutions, they exist software development approaches like Scrum and Kanban, also, others are adapted viz; Large-Scale Scrum, Scaled Agile Framework and so on., and many methods have proposed such as Ignite | IoT Methodology and IoT Methodology. Most of them have taken agile thinking as a strategy. However, they are monolithic, which are not easy to adopt. Then, a new method is needed to handle the real nature of IoT, particularity, to handle distributed, mobile and human out-of-the-loop concerns, and that can grow as new product evolve and new problems emerge. This research studies and analyses some of the existing IOT methodologies. Particularly, it focuses on these methodologies Scrum, Kanban, Scaled Agile Framework, Ignite | IoT Methodology and IoT Methodology. Our study evaluates their capabilities and compares their main characteristics and behaviors in terms of various methodologies of IoT. The comparison presented in this paper would benefit in selecting an appropriate methodology for the IoT projects. In addition, it identifies their advantages and limits in order to suggest a new approved IoT methodology.

Security patterns: A systematic mapping study

Security patterns are a well-established means to encapsulate and communicate proven security solutions and introduce security into the development process. Our objective is to explore the research efforts on security patterns and discuss the current state of the art, which will serve as a guideline for interested researchers, practitioners, and teachers. We have conducted a systematic mapping study of relevant literature from 1997 until the end of 2017 and identified 403 relevant papers, 274 of which were selected for analysis based on quality criteria. This study derives a customized research strategy from established systematic approaches in the literature. The first 3 research questions address the demographics of security pattern research such as topic classification, trends, and distribution between academia and industry, along with prominent researchers and venues. The next 9 research questions focus on more in-depth analyses such as pattern presentation notations and classification criteria, pattern evaluation techniques, and pattern usage environments. We observe that security pattern research is an active and growing field and the patterns are increasingly being used to improve software development approaches. Pattern evaluation is currently the least explored topic by researchers and there is a lack of empirical studies in the field.

Програмний комплекс створення та проведення числових симуляцій

Business-simulations gained popularity and relevance in the modern world. Business simulations are the interactive systems allowing to organize, create and conduct simulations of economic and socio-economic processes with satisfactory realism. At the same time, study conducted among students of higher education establishments revealed lack of knowledge and technical skills in the area of business-simulations development using modern software development approaches and technologies. Objective of the paper is to present results of logical and technical design of the system that allows teachers and students organize and conduct business-simulations in the educational process. The general scientific methods were used to define the problem, analyze the need and idealize the solution. The methods of complex software systems design and development were used on the stage of architecture, programming interfaces creation and implementation. The paper describes design and development of the software system for creation and conducting quantitative simulations. The next requirements to the software system were defined: the system has to be web-based; the system has to be neutral to the type of the device and operating environment; the system has to have adaptive interface; the system has to be scalable towards adding third-party simulations, supporting defined API; the system has to have user-friendly interface, minimizing time overhead for the teacher and students during preparation, conducting and analyzing simulation. The cloud architecture has been chosen on the design stage of the research. It allows managing simulations using centralized resource. Developed software system for creation and conducting software simulations consist of the next components: SimulationLab.Admin, SimulationLab.Api.Models, SimulationLab.Engine, SimulationLab.Core, SimulationLab.Web. The augmentation of the cognitive experience of the students was proved during conducting the research. Augmentation was resulting in the practical skills development. Ease of implementation of the business-simulations into educational process is crucial to ability to augment cognitive experience. This resulted in the special attention to the efficient user experience for the teacher and the students during lectures and practical classes. The system is designed and developed using modern software development approaches and tools. Developed system implementation making augmenting theoretical material by practical and research-based type of activities significantly easier and more productive. The courses of mathematical and socio-economic blocks of disciplines of the higher education establishments, schools, corporate trainings and informal education events and materials are the targets to be effectively augmented by the designed and developed system.

MoFQA: A TDD Process and Tool for Automatic Test Case Generation from MDD Models

Techniques for quality assurance have to deal with the complexity of software systems and the high probabilities of new errors appearing in any stage of the software life cycle. Software testing is a widely used approach but, due to the costs involved in this process, development teams often debate its applicability in their projects. In the endeavor to reduce the complexity of this process, this study presents an approach for software development based in Test-Driven Development (TDD) supported by Model-Based Testing (MBT) tools to allow automatic test-case generation. The approach, called MoFQA (Model-First Quality Assurance), consists of two main aspects: i) a method to drive software development based on testing techniques which defines steps and recom-mended practices; and, ii) a tool-set to allow clients and stakeholders to model system requirements, testers to create models that represent unit and abstract tests, and transformation tools used to generate executable tests. The tools that MoFQA provides are focusing on web applications. In order to validate the MoFQA tools, two validation experiences are presented.

A Comparative Analysis on Effort Estimation for Agile and Non-agile Software Projects Using DBN-ALO

At present, in the software industry, agile and non-agile software development approaches are followed and effort estimation is an intrinsic part of both the approaches. This work investigates the application of deep belief network (DBN) along with antlion optimization (ALO) technique for effort prediction in both agile as well as non-agile software development environment. The study also provides a prediction interval of effort to handle uncertainty in estimation. This will help the project managers to estimate the effort in ranges instead of a crisp value. The proposed DBN-ALO approach is applied on four promise repository datasets for traditional software development (non-agile), and on three agile datasets. It provides the best results in all the evaluation criteria used. The proposed approach is also statistically validated using nonparametric tests, and it is found that DBN-ALO worked best for both agile and non-agile development approaches.

Management of quality requirements in agile and rapid software development: A systematic mapping study

Context:Quality requirements (QRs) describe the desired quality of software, and they play an important role in the success of software projects. In agile software development (ASD), QRs are often ill-defined and not well addressed due to the focus on quickly delivering functionality. Rapid software development (RSD) approaches (e.g., continuous delivery and continuous deployment), which shorten delivery times, are more prone to neglect QRs. Despite the significance of QRs in both ASD and RSD, there is limited synthesized knowledge on their management in those approaches. Objective:This study aims to synthesize state-of-the-art knowledge about QR management in ASD and RSD, focusing on three aspects: bibliometric, strategies, and challenges. Research method:Using a systematic mapping study with a snowballing search strategy, we identified and structured the literature on QR management in ASD and RSD. Check the PDF file to see the full abstract and document.

Empirical evaluation of metrics on aspect-oriented programs


 The quality evaluation of software metrics measurement is considered as the primary indicator of imperfection prediction and software maintenance in various empirical studies of software products. However, there is no agreement on which metrics are compelling quality pointers for new software development approaches such as aspect-oriented programming (AOP) techniques. AOP intends to enhance programming quality by providing fundamentally different parts of the systems, for example, pointcuts, advice, and intertype relationships. Hence, it is not evident if quality characteristics for AOP could be extracted from direct expansions of traditional object-oriented programming (OOP) measurements. Then again, investigations of AOP do regularly depend on established static and dynamic metrics measurement; notwithstanding the late research of AOP in empirical studies, few analyses been adopted using the International Organization for Standardization 9126 quality model as useful markers of flaw inclination in this context. This paper examination we have considered different programming quality models given by various authors every once in a while and distinguished that adaptability was deficient in the current model. We have testing 10 projects developed by AOP. We have used many applications to extract the metrics, but none of them could extract all AOP Metrics. It only can measure some of AOP Metrics, not all of them. This study investigates the suitable framework for extract AOP Metrics, for instance, static and dynamic metrics measurement for hybrid application systems (AOP and OOP) or only AOP application.

Multidisciplinary Software Design for the Routine Monitoring and Assessment of Pain in Palliative Care Services: The Development of PainCheck

PURPOSEThe use of health information technology (HIT) to support patient and health professional communication is emerging as a core component of modern cancer care. Approaches to HIT development for cancer care are often underreported, despite their implementation in complex, multidisciplinary environments, typically supporting patients with multifaceted needs. We describe the development and evaluation of an e-health tool for pain management in patients with advanced cancer, arising from collaboration between health researchers and a commercial software development company.METHODSWe adopted a research-led development process, involving patients with advanced cancer and their health professionals, focusing on use within real clinical settings. A software development approach (disciplined agile delivery) was combined with health science research methods (ie, diary studies, face-to-face interviews, questionnaires, prototyping, think aloud, process reviews, and pilots). Three software iterations were managed through three disciplined agile delivery phases to develop PainCheck and prepare it for use in a clinical trial.RESULTSFindings from development phases (inception, elaboration, and construction) informed the design and implementation of PainCheck. During the transition phase, where PainCheck was evaluated in a randomized clinical trial, there was variation in the extent of engagement by patients and health professionals. Prior personal experience and confidence with HIT led to a gatekeeping effect among health professionals, who were reluctant to introduce PainCheck to patients. Patients who did use PainCheck seemed to benefit, and no usability issues were reported.CONCLUSIONHealth science research methods seemed to help in the development of PainCheck, although a more rigorous application of implementation science methodologies might help to elucidate further the barriers and facilitators to adoption and inform an evidence-based plan for future implementation.

Application of Fuzzy DEMATEL Approach in Analyzing Mobile App Issues

In the current scenario, the popularity of smartphones has led to the emergence of an ample collection of mobile applications (apps). Mobile apps are dynamic in nature; therefore, classical software development approaches are not suitable. Individual needs of the customer, new technology, battery consumption, and many more issues force app developers regularly introduce new apps to the market. But due to the unavailability of any formal and customized practices of app development, various issues occur in mobile apps. These issues may adversely affect the application and user acceptance of the end product. In this paper, fifteen issues in mobile apps have been identified. Then we applied Fuzzy-DEMATEL (Decision Making Trial and Evaluation Laboratory) method to analyze the critical mobile issues (CMIs) and divide these issues into cause and effect groups. Firstly, multiple experts evaluate the direct relations of influential issues in mobile apps. The evaluation results are presented in triangular fuzzy numbers (TFN). Secondly, convert the linguistic terms into TFN. Thirdly, based on DEMATEL, the cause-effect classifications of issues are obtained. Finally, the issues in the cause category are identified as CMIs in mobile apps. The outcome of the research is compared with the other variants of DEMATEL like G-DEMATEL and E-DEMATEL and the comparative results suggest that fuzzy-DEMATEL is the most fitting method to analyze the interrelationship of different issues in mobile apps development. The outcome of this work definitely assists the mobile apps development industry to successful identification of the serious issues where professionals and project managers could really focus on.

Challenges Faced in the Enterprise Resource Planning Material Management Section when Transitioning Towards Agile Software Development

Agile Software Development Approach is the buzzword for the Organizations working with Traditional Software Development Approach. Scrum is one of the most vital frameworks used when working towards Agile Software Development projects. Material Management is one of the salient processes of the Supply Chain Management in transforming inputs into outputs. Extreme Programming is more technical in nature and Scrum is a People focused Management approach. This scrum framework is customizable according to the project teams and it is adopted widely to effectively manage software projects. Scrum framework fits into the groove for delivering quality product at a faster pace with minimal continuous feature delivery at frequent intervals. The minimal Marketable feature is delivered at the end of each Sprint. A Sprint is an iterative activity which ends up at regular intervals. But, the way of customizing the process and giving a minimal feature delivery at the end of each Sprint in the projects act as a major challenge. Other challenges resulted in the team collaboration and the involvement of the team members in the project and in integrating the minimal marketable feature. Syncing with the product owner and the other stake holders, and participation in the sprint planning were some of the issues that the team faced. The success of the entire team in implementing the Agile Software Development approach in the Enterprise Resource Planning Material Management Section is discussed.

Breast Cancer Dataset Classification using Neural Network

Agile Software Development Approach is the buzzword for the Organizations working with Traditional Software Development Approach. Scrum is one of the most vital frameworks used when working towards Agile Software Development projects. Material Management is one of the salient processes of the Supply Chain Management in transforming inputs into outputs. Extreme Programming is more technical in nature and Scrum is a People focused Management approach. This scrum framework is customizable according to the project teams and it is adopted widely to effectively manage software projects. Scrum framework fits into the groove for delivering quality product at a faster pace with minimal continuous feature delivery at frequent intervals. The minimal Marketable feature is delivered at the end of each Sprint. A Sprint is an iterative activity which ends up at regular intervals. But, the way of customizing the process and giving a minimal feature delivery at the end of each Sprint in the projects act as a major challenge. Other challenges resulted in the team collaboration and the involvement of the team members in the project and in integrating the minimal marketable feature. Syncing with the product owner and the other stake holders, and participation in the sprint planning were some of the issues that the team faced. The success of the entire team in implementing the Agile Software Development approach in the Enterprise Resource Planning Material Management Section is discussed.