Software Life Cycle Processes Research Articles

Guideline for software life cycle in health informatics.

The long-lasting trend of medical informatics is to adapt novel technologies in the medical context. In particular, incorporating artificial intelligence to support clinical decision-making can significantly improve monitoring, diagnostics, and prognostics for the patient's and medic's sake. However, obstacles hinder a timely technology transfer from research to the clinic. Due to the pressure for novelty in the research context, projects rarely implement quality standards. Here, we propose a guideline for academic software life cycle processes tailored to the needs and capabilities of research organizations. While the complete implementation of a software life cycle according to commercial standards is not feasible in scientific work, we propose a subset of elements that we are convinced will provide a significant benefit while keeping the effort within a feasible range. Ultimately, the emerging quality checks for academic software development can pave the way for an accelerated deployment of academic advances in clinical practice.

Software Enterprise Risk Detection Model Based on BP Neural Network

With the rapid development of software industry, software enterprises have many problems in risk management, and enterprises are facing a huge crisis. In order to detect the risk of software enterprise, a risk detection model based on BP neural network is proposed in this paper. Firstly, risk analysis and modeling are carried out for the software life cycle process of the enterprise. Then, BP neural network is combined with common software risk items to realize supervised deep learning based on label information in data set. Using the advantage of neural network in automatic selection of original data features, the relationship between these risk items is extracted. Meanwhile, the network model in this paper learns the complex relational rules of the input risk features, to classify the risks. Finally, the proposed combined prediction model is compared with other prediction models. The experimental results show that the risk prediction effect of the proposed algorithm is better, to avoid the loss caused by the risk of software enterprises.

Quantum software testing: State of the art

AbstractQuantum computing is expected to exponentially outperform classic computing on a broad set of problems, including encryption, machine learning, and simulations. It has an impact yet to explore on all software lifecycle's processes and techniques. Testing quantum software raises a significant number of challenges due to the unique properties of quantum physics—such as superposition and entanglementand the stochastic behavior of quantum systems. It is, therefore, an open research issue. In this work, we offer a systematic mapping study of quantum software testing engineering, presenting a comprehensive view of the current state of the art. The main identified trends in testing techniques are (1) the statistic approaches based on repeated measurements and (2) the use of Hoare‐like logics to reason about software correctness. Another relevant line of research is reversible circuit testing, which is partially applicable to quantum software unitary testing. Finally, we have observed a flourishing of secondary studies and frameworks supporting testing processes from 2018 onwards.

A cloud software life cycle process (CSLCP) model

Small to medium-sized enterprises take advantage of the strengths and opportunities of cloud computing. These enterprises require a well-defined software process model to produce reliable and quality cloud software, given their limited resources. Existing related work is surveyed, and the needed missing features are determined. A cloud software life cycle process model is proposed, validated, and verified to handle the shortcomings of existing cloud software process models. A case study is used to illustrate all the activities required throughout the software life cycle of the proposed model. The proposed cloud software life cycle process model is a cyclic iterative prototyping model. It is compatible with levels two and three of the capability maturity model integration and extends the Egyptian software process improvement model to fit the cloud environment. The model helps small enterprises develop quality, maintainable, and sustainable cloud software at a reasonable cost.

Developing a Model for Measuring Project Performance with Software Life Cycle Process Metrics and Calculating Project Success Score

Despite the developments in the process and tool infrastructure in the software world, project success has not significantly improved. In software projects, the definition of project success means to produce products that the customer desires in the planned effort, time and budget. To achieve this goal, planning, analysis, design, coding, integration, testing and delivery processes are operated interactively from the beginning to the end of a software project. Metrics of these processes are used to measure the performance of software projects. Since the literature review shows that project management process metrics such as budget, effort, schedule, customer satisfaction, product quality are used in measuring project performance, more comprehensive and effective criteria are needed to be defined and applied in measuring project performances. Due to the importance of the project performance evaluation, a general evaluation model was created in this study. The proposed model is designed for use in the software industry. In terms of project performance, a model has been developed that focuses on management of project, requirement, risk, quality and configuration, development, verification and validation processes. The purpose of this article is to present a model that evaluates the performance of software projects and expresses project success with a numerical value. Analytical hierarchy process (AHP) was used to calculate the relative importance of each process metric criterion and sub-criteria that provide input to the performance evaluation. Statistical process control method was used in the evaluation of project performance and calculation of the project success score. It was operated in an R&D organization to verify the proposed model and the performance of a project in delivery phase to the customer was measured. It is thought that the model presented in this study will help the managers, who monitor the project status, to evaluate project performance, as well as provide the numerical comparison of performance between projects.

Start to Finish Automation Achieve on Cloud with Build Channel: By DevOps Method

Abstract Innovations through IoTs urge software developing industry need to come up with new life cycle model instead than usual. Process of software developments should be go along with advancements life cycle. This brings the attention for native and adoptable software life cycle process that is required for current industry standards. Manufactures are integrating the methodologies of software development process in a single bundle as automation with support of cloud with DevOps. The operation engineers, development engineers and QAs participate together for building the software applications will spin into minutes instead of days. Automation is the ultimate demand for DevOps approach. This approach advents continual automation to the software life cycle is known as delivery. This continually performs the tests and analysis of code. The developers provision and build the software into their cloud environment. Every step in the continuous delivery can be repeated in a several time a day depending on how much new applications need to release. Automation in DevOps improving speed of development, precision, consistency and increases the number of delivery.

Experiences on the use of a game for improving learning and assessing knowledge

AbstractThe combination of traditional teaching methods with innovative learning tools generates a positive effect on the learning. MiProJOC is a web‐based question and answer game developed to support the delivery of interactive lessons and the assessment of the students’ learning, both as in‐class and distance education activities. MiProJOC was designed to maintain a repository of questions from different knowledge areas, to define and set different game modes, and to present the statistical results from the use of the tool. MiProJOC has been used to facilitate the learning of the software life cycle processes of the ISO/IEC/IEEE 12207 International Standard within a Software Quality course. This tool has been tested and validated by three different groups of users: students, teachers, and experts from an Information Technology center. The use of MiProJOC to consolidate theoretical concepts is quite profitable, instructive, and beneficial. The tool has achieved an increase in the student interest toward the topics studied. Students are more motivated when innovative techniques are used for the acquisition and consolidation of knowledge.

Software engineering ontologies categorization

Software engineering is an own scientific and practice aria with an own structure, terminology, products, pro-cesses and resources. The software product is a knowledge-based product and it is the result of the knowledge-based actions. In this research, categorization of ontologies in software engineering are presented. The known criterion (process, domain, structure) are used for the categorization of ontologies but two criterion (process and domain) was modified. The process criterions is looked in the connection whit time period and the prede-velopment time added to time period. The domain criterions is making whit help of the representation of soft-ware engineering world in the form of domains. The ontologies are involved in representing knowledge of three types of the software engineering domains. In the first, the application domain, the focus is on under-standing the customer needs and what the software product must do. In the second, the implementation do-main, the focus is on understanding how the software product must behave and respond to the customer needs. In the third, the problem domain, the focus is on understanding the software engineering problems, which can be during software life cycle processes of the software product. Our research goal is to develop categorization of the software engineering ontologies on the base of adding known criterion. Ontological representation of software engineering knowledge; categorization; domain analysis; object-oriented programming; ontology-driven utilizing of programming styles. Categorization of the software engineering ontologies. The results of case study, using ontologies by categorization are presented. Had developed categorization of ontologies, it is possible exactly to define types of software engineering ontologies and its places into software processes. This is demonstrating on the examples of the case studies. Problems in programming 2018; 1: 55-64

On the Design of Effective E-Commerce Applications: An ISO-Based Lifecycle Model

The provision of services as e-commodities and the wide use of networked business models have driven buyer experience to new heights. Innovation, coupled with quality is the competitive advantage e-commerce vendors strive to achieve when designing or re-designing their software. In terms of quality, evaluation stood in the spotlight for many years. However, software analysis and design based on quality models have been used mostly for understanding, rather than improving. In this work, we present a new model for the analysis and design of e-commerce software systems mapped to the software life-cycle process. Quality control procedures are mapped to every phase, from initiation and design to delivery. Based on current ISO standards such as ISO25000 series, this work discusses technical and managerial principles that need to be applied in order to obtain quality e-commerce software.

HIPAA Security and Privacy Rules Auditing in Extreme Programming Environments

Healthcare business is responsible of keeping patient data safe and secure by following the rules of the federal Health Insurance Portability and Accountability Act of 1996, (HIPAA). Agile software organizations that deal with healthcare software system face a number of challenges to demonstrate that their process activities conform to the rules of HIPAA. Such organizations must establish a software process life cycle and develop procedures, tools, and methodologies that can manage the HIPAA requirements during the different stages of system development, and also must provide evidences of HIPAA conformity. This paper proposes an auditing model for HIPAA security and privacy rules in XP environments. The design of the proposed model is based on an evaluation theory which takes as its input the work of Lopez ATAM, and the standards of common criteria (CC) concepts. The proposed auditing model has been assessed based on four case studies. The auditing result shows that the proposed model is capable of capturing the auditing evidences in most of the selected case studies.

Teaching ISO/IEC 12207 software lifecycle processes: A serious game approach

Serious games involve applying game design techniques to tasks of a serious nature. In particular, serious games can be used as informative tools and can be embedded in formal education. Although there are some studies related to the application of serious games for the software development process, there is no serious game that teaches the fundamentals of the ISO/IEC 12207:1995 Systems and software engineering – Software life cycle processes, which is an international standard for software lifecycle processes that aims to be ‘the’ standard that defines all the tasks required for developing and maintaining software. “Floors” is a serious game that proposes an interactive learning experience to introduce ISO/IEC 12207:1995 by creating different floors of a virtual environment where various processes of the standard are discussed and implemented. Inherently, it follows an iterative process based on interactive technical dialogues in a 3D computer simulated office. The tool is designed to assess the novice engineering practitioners knowledge and provide preliminary training for ISO/IEC 12207:1995 processes. By playing such a game, participants are able to learn about the details of this standard. The present study provides a framework for the exploration of research data obtained from computer engineering students. Results suggest that there is a significant difference between the knowledge gained among the students who have played Floors and those who have only participated in paper-based learning sessions. Our findings indicate that participants who played Floors tend to have greater knowledge of the ISO/IEC 12207:1995 standard, and as a result, we recommend the use of serious games that seem to be superior to traditional paper based approach.

A standard-based framework to integrate software work in small settings

Small software companies have to work hard in order to survive. They usually find it challenging to spend time and effort on improving their operations and processes. Therefore, it is important to address such needs by the introduction of a proposed framework that specifies ways of getting things done while consciously encourage them to enhance their ability to improve. Although there are many software process improvement approaches, none of them address the human factors of small companies in a comprehensive and holistic way. Samay is a proposed framework to integrate human factors in the daily work as a way to deal with that challenge. This study suggests managing human factors but pointing out the software process life cycle. The purpose is to converge toward a continuous improvement by means of alternative mechanisms that impact on people. This framework was developed based upon reviews of relevant standards (such as ISO/IEC 29110, ISO 10018, OMG Essence and ISO/IEC 33014) and previously published studies in this field. Moreover, an expert review and validation findings supported the view that Samay could support practitioners when small software companies want to start improving their ways of work.

Software project management tools in global software development: a systematic mapping study.

Global software development (GSD) which is a growing trend in the software industry is characterized by a highly distributed environment. Performing software project management (SPM) in such conditions implies the need to overcome new limitations resulting from cultural, temporal and geographic separation. The aim of this research is to discover and classify the various tools mentioned in literature that provide GSD project managers with support and to identify in what way they support group interaction. A systematic mapping study has been performed by means of automatic searches in five sources. We have then synthesized the data extracted and presented the results of this study. A total of 102 tools were identified as being used in SPM activities in GSD. We have classified these tools, according to the software life cycle process on which they focus and how they support the 3C collaboration model (communication, coordination and cooperation). The majority of the tools found are standalone tools (77%). A small number of platforms (8%) also offer a set of interacting tools that cover the software development lifecycle. Results also indicate that SPM areas in GSD are not adequately supported by corresponding tools and deserve more attention from tool builders.

Creation of an IEC 62304 compliant software development plan

AbstractOrganizations engaged in medical device software development are required to demonstrate compliance with a set of medical device standards and regulations before the device can be marketed. One such standard IEC 62304, Medical Device Software—Software Life Cycle Processes, defines the processes that are required in order to develop safe software. Demonstrating compliance with IEC 62304 can be problematic for organizations that are new to or have limited experience in the domain. The standard defines what processes must be carried out but does not state how. In a review of a number of such organizations, it was found that the development of a software development plan proved to be a difficult task. In this work we have created a software development plan template to assist organizations with this arduous task. The software development plan template will be validated with these organizations as part of the future work.

Functional change impact analysis in use cases: An approach based on COSMIC functional size measurement

Context: Because functional changes are inevitable throughout the software life-cycle, it is essential to assess and evaluate whether a Functional Change (FC) can be handled within the estimated project budget and time. Thus, a well-defined change measure and control process is vital for the success of the development project. In fact, the size measurement is widely used for effort and cost estimation. This paper explores the COSMIC Functional Size Measurement (FSM) method to evaluate a FC. Objective: The objective of this paper is to assess a FC in terms of COSMIC Function Point units in order to identify changes incurring potential impact on the software development progress. Thus, we suppose that the functional size of a FC is one of the factors that must be taken into consideration to analyze the impact of changes on the development progress. This helps managers in making decisions to answer a FC request. Method: The method proposed in this paper analyzes the FC impact in use case diagrams, the de-facto standard for modeling the Functional User Requirements (FUR). It distinguishes between internal and external FC to a use case. It proposes to quantify the FC impact on the functional size of a use case diagram in terms of COSMIC Function Point (CFP) units. In addition, it evaluates the status of a FC according to its functional size. Furthermore, we propose an algorithm for prioritizing changes in the case where more than one functional change is proposed. The algorithm is based on a set of heuristics where the objective is to minimize the effort required to answer the changes. It accounts for the most important factors when prioritizing changes (the functional size of the FC, and the preference of the change requester). These two factors are identified based on an investigation with the international COSMIC community. Originality: Several techniques have been used to identify and analyze the impact of a FC during various phases of the software life-cycle. For example, some researches used the colored commit graphs (at the implementation phase), other studies used the consistency rules between UML diagrams (at the design phase), etc. Compared to other approaches focused on impact change analysis, our proposed approach uses the COSMIC-FSM method. Quantifying the functional size of a FC in terms of CFP units allows us to evaluate more realistically the impact of a FC on the software development progress. Results: We propose six categories of FC status according to their sizes. Based on the FC status, it is possible to identify the FC impact on the software development progress. The FC status will help not only designers/developers in analyzing the impact of FC on the size of their work products but also managers to decide to accept or forgo a FC and maintain the development schedule. Moreover, the experiment conducted with 30 computer engineering students showed that students' ratings can be approximately evaluated when measuring FUR in terms of CFP units based on the FC status. Conclusion: Based on the finding of this study, it is now feasible to identify FC leading to potential impact on the software development progress. More specifically, evaluating FC in the use case diagrams will help in making quick decisions about accepting or rejecting a FC. Regardless of the used software life-cycle process, use cases are popular for specifying the software functionality. In practice, our proposed approach is applicable not only in the software development industry but also in academia. • Evaluate a functional change using COSMIC-FSM method to identify if it can be handled within the estimated budget and time. • A functional change impact analysis on the UML use case diagram approach is proposed. • The approach quantify a change in terms of CFP units and its impact on the functional size of the use case diagram. • Functional change status is identified based on its size. Six categories have been proposed to identify potential changes.

Prototype dependability model in software: an application using BOCR models

Actual software project feasibility assessment is one of the foremost challenging and vital activities in estimating economics of software before its actual development. Therefore, prototyping in recent years, gradually become an approach to decide various options and possible outcomes before its real implementation and success of the projects. Most of the prototype studies in software engineering acts as a good pointer to envision and reflect upon the final product prediction. However, there has been dearth so far for a detailed economic analysis accountable for benefits, opportunities, risks and costs (BOCR) merits arising from various influencing factors (criteria and sub-criteria…). Further to determine the final possible outcomes (alternatives) through the trade-offs between the BOCR models. The present work attempts to close this gap. The modeling is performed in association with two types of models: analytic network process (ANP) and analytic hierarchy process (AHP) with complex relations between influencing factors. The former is illustrated as BOCR-ANP in the form of a control network and analysed through questionnaire based on expert judgement and historic data. The latter BOCR-AHP as a strategic hierarchy via real time data collected from the defect consolidation log data sets through linguistic variables proposed by same authors in our previous work. Thus we propose to investigate prototype dependability model through the inputs arising from expert judgement and real time data. More importantly our proposed model is realized without constructing actual working model. It is an analytical model based on inputs from past experience. The model can be a replacement for a working model for smaller/medium projects or additional inputs to strengthen working model for larger complex software systems. Thus our paper proposes a holistic model to assess the prototype dependability in software at prototype level in early in the software life cycle process. We carried over a case study to examine the proposed approach and to evaluate the economic feasibility of projects in I.T. industry.

ELEMENTS OF LEGACY PROGRAM COMPLEXITY

Researchers in the field of software engineering, business process improvement and information engineering all want to drastically modernize software life-cycle processes and technologies to correct the problems and to improve the quality of software. Research goals have included ancillary issues, such as improving user services through conversion to new platforms and facilitating software processes by adopting automated tools. Automated tools for software development, understanding, maintenance, and documentation add to process maturity, leading to better quality and reliability of computer services and greater customer satisfaction. This paper focuses on critical issues of legacy program improvement. The program improvement needs the estimation of program from various perspectives. The paper highlights various elements of legacy program complexity which further can be taken in account for further program development.

Rate-Based Queueing Simulation Model of Open Source Software Debugging Activities

Open source software (OSS) approach has become increasingly prevalent for software development. As the widespread utilization of OSS, the reliability of OSS products becomes an important issue. By simulating the testing and debugging processes of software life cycle, the rate-based queueing simulation model has shown its feasibility for closed source software (CSS) reliability assessment. However, the debugging activities of OSS projects are different in many ways from those of CSS projects and thus the simulation approach needs to be calibrated for OSS projects. In this paper, we first characterize the debugging activities of OSS projects. Based on this, we propose a new rate-based queueing simulation framework for OSS reliability assessment including the model and the procedures. Then a decision model is developed to determine the optimal version-updating time with respect to two objectives: minimizing the time for version update, and maximizing OSS reliability. To illustrate the proposed framework, three real datasets from Apache and GNOME projects are used. The empirical results indicate that our framework is able to effectively approximate the real scenarios. Moreover, the influences of the core contributor staffing levels are analyzed and the optimal version-updating times are obtained.

Implementing information security best practices on software lifecycle processes: The ISO/IEC 15504 Security Extension

The ISO/IEC 15504 international standard can be aligned with the ISO/IEC 27000 information security management framework. During the research conducted all the existing relations between ISO/IEC 15504-5 software development base practices and ISO/IEC 27002 security controls have been analysed and the ISO/IEC 15504 Security Extension has been developed. This extension details the changes that software companies should make in the software lifecycle processes for the successful implementation of the related security controls. To attain our research objectives, we evaluate the ISO/IEC 15504 Security Extension through case studies in a sample of software development organizations. This study follows the design science research paradigm that is based on constructive research.

A Knowledge Integration Approach of Safety-critical Software Development and Operation based on the Method Architecture

It is necessary to integrate practical software development and operation body of knowledge to deploy development and operation methods for assuring safety. In this paper, an approach based on the method architecture is proposed to develop an integrated method for describing various software related bodies of knowledge and the safety case for assured software life cycle processes.