Software Development Life Cycle Process Research Articles

A Comparative Review of AI Techniques for Automated Code Generation in Software Development: Advancements, Challenges, and Future Directions

Artificial Intelligence (AI), as one of the most important fields of computer science, plays a significant role in the software development life cycle process, especially in the implementation phase, where developers require considerable effort to convert software requirements and design into code. Automated Code Generation (ACG) using AI can help in this phase. Automating the code generation process is becoming increasingly popular as a solution to address various software development challenges and increase productivity. In this work, we provide a comprehensive review and discussion of traditional and AI techniques used for ACG, their challenges, and limitations. By analysing a selection of related studies, we will identify all AI methods and algorithms used for ACG, extracting the evaluation metrics and criteria such as Accuracy, Efficiency, Scalability, Correctness, Generalization, and more. These criteria will be used to perform a comparative result for AI methods used for ACG, exploring their applications, strengths, weaknesses, performance, and future applications.

Design, Development and Validation of a Digital Performance Based Appraisal System: A Planned Approach in Change Management

Objectives: In India, the professional performance of the academic faculty is assessed annually using Academic Performance Indicator (API) as per the University Grants Commission (UGC), Government of India. This is a manual model is cumbersome in filling, and time-consuming. As a planned change and a measure to introduce technology-based platforms in JSS Academy of Higher Education & Research (JSSAHER), Mysuru, India, we have designed, developed, and validated digital platform technology to evaluate the annual performance of faculty working in medical, dental, pharmacy, life sciences fraternities. Methods: Academic Performance Indicator (API) guideline as per the University Grants Commission (UGC), Government of India, was used to design and develop the digital performance-based appraisal system (d-PBAS), and its performance was validated (20% random sampling) by comparing the manual and digital data entered by the faculty from different disciplines of JSSAHER. Findings: The present manuscript demonstrates the designing and validation methodology of d-PBAS. Software Development Life Cycle (SDLC) process and Waterfall model was adopted to develop d-PBAS. The digital platform was assessed for the performance and ranking of the faculty. More than 96% of the users expressed satisfaction and 4% expressed dissatisfaction in d-PBAS. Novelty: For the first of its kind in a university set up in India, JSSAHER designed and validated the digital performance-based appraisal system to evaluate academic performance. Since d-PBAS was developed using the SDLC process and Waterfall model it is easy and consumes less time to enter the data. The most important highlight is d-PBAS helps to rank the faculty performance automatically. The design and validation of d-PBAS described in the present manuscript are simple, robust, cost-effective, and have a go-green value. Keywords: Change Management, Higher Education Institutions, Performance­based, Appraisal System, academic Performance Indicator, digital technology

SOFTWARE DEVELOPMENT PROJECT MANAGEMENT BASED ON WORK BREAKDOWN STRUCTURE AND ODOO ERP

Software Development Project Management is the most important part of the Software Development Life Cycle process. The stages in project development include Initiating, Planning, Executing, Monitoring and Controlling, and Closing. This research uses the Work Breakdown Structure approach, which is a method used in project management to break down complex work into smaller and more manageable parts. Work Breakdown Structure helps in organizing, classifying, and describing the work to be done in a project. Odoo ERP is part of the tools that can be used for project management. Testing the project module using Blackbox Testing. The test scenario includes functional testing of the project management module. Application testing shows good results and is following existing needs. The results show that software project management using the Work Breakdown Structure approach can be implemented properly with Odoo ERP tools.

Software Development Life Cycle (SDLC) in Software Engineering – A Brief Review

The software development life cycle process is a crucial methodology that software developers use to create high-quality software products. In the requirements-gathering phase, the software development team works with stakeholders to define the project's objectives, scope, and requirements. The design phase involves creating the software architecture, which outlines the software's structure, components, and interactions. In the testing phase, the software is tested to ensure that it meets the requirements and functions correctly. The SDLC process plays a critical role in creating software that meets user requirements, is of high quality, and can be maintained and updated over time. By following a systematic approach, software development teams can ensure that the software they create is reliable, secure, and efficient. Overall, the SDLC process is a comprehensive methodology that software developers use to create high-quality software products. Software Development Life Cycle plays a major role in the life of a software engineer. Design thinking can be used to make the software development life cycle more powerful. This paper involves a discussion on how software development life cycle can be made powerful and used to satisfy the client's requirements.

A systematic review of non-functional requirements mapping into architectural styles

Fortunately, the software attracted enough businesses to the market, allowing them to earn money in less time with less work and more accurate results. Software development life cycle (SDLC) is used for software development as it is responsible for system functionality, efficiency, maintainability, and any other non-functional system requirements. Each stage of the SDLC process is critical. However, software requirements and software architecture are both fundamental activities that play a vital role in all other SDLC stages. Non-functional requirements are critical to the success of any software because they explain all system quality attributes such as complexity, reliability, security, and maintainability, among others. The architectural styles assist you in determining which architecture may be best for your project requirements. This paper discusses several of the most important architectural styles that are best suited for mapping desired non-functional requirements for software development, as well as their comparison based on various quality attributes (non-functional requirements).

Threat modeling in application security planning citizen service complaints

The mobile-based service complaint application is one way to implement good governance today. Public facilitated to make complaints without going through a complicated process. Security aspects must be considered to protect user privacy. The security design must be considered so that no one is harmed by the application's users damaged in the application's use. This study used threat modeling during the planning stage of developing a citizen service complaint application to obtain information about vulnerabilities. The researcher uses the threat modeling process that the open web application security project (OWASP) organization has formulated as a framework. The researchers took steps to describe application information, determine and rank threats, countermeasures, and mitigation. In the final stage, the spoofing, tampering, repudiation, information disclosure, denial of service and elevation of privilege (STRIDE) threat modeling methodology is used to analyze and assess mitigation actions against threats in the application. The researcher gets a defense strategy to reduce the danger based on the threat analysis results. Threat modeling in the early phase software development life cycle process is constructive in ensuring that software is developed with adequate security based on threat mitigation from the beginning.

Automatic model transformation on multi-platform system development with model driven architecture approach

Several difficulties commonly arise during the software development process. Among them are the lengthy technical process of developing a system, the limited number and technical capabilities of human resources, the possibility of bugs and errors during the testing and implementation phase, dynamic and frequently changing user requirements, and the need for a system that supports multi-platforms. Rapid application development (RAD) is the software development life cycle (SDLC) that emphasizes the production of a prototype in a short amount of time (30-90 days). This study discovered that implementing a model-driven architecture (MDA) approach into the RAD method can accelerate the model design and prototyping stages. The goal is to accelerate the SDLC process. It took roughly five weeks to construct the system by applying all of the RAD stages. This time frame does not include iteration and the cutover procedure. During the prototype test, there were no errors with the create, read, update, and delete (CRUD) procedure. It was demonstrated that automatic transformation in MDA can shorten the RAD phases for designing the model and developing an early prototype, reduce code errors in standard processes like CRUD, and construct a system that supports multi-platform.

Automatic model transformation on multi-platform system development with model driven architecture approach

Several difficulties commonly arise during the software development process. Among them are the lengthy technical process of developing a system, the limited number and technical capabilities of human resources, the possibility of bugs and errors during the testing and implementation phase, dynamic and frequently changing user requirements, and the need for a system that supports multi-platforms. Rapid application development (RAD) is the software development life cycle (SDLC) that emphasizes the production of a prototype in a short amount of time (30-90 days). This study discovered that implementing a model-driven architecture (MDA) approach into the RAD method can accelerate the model design and prototyping stages. The goal is to accelerate the SDLC process. It took roughly five weeks to construct the system by applying all of the RAD stages. This time frame does not include iteration and the cutover procedure. During the prototype test, there were no errors with the create, read, update, and delete (CRUD) procedure. It was demonstrated that automatic transformation in MDA can shorten the RAD phases for designing the model and developing an early prototype, reduce code errors in standard processes like CRUD, and construct a system that supports multi-platform.

Lean IT With Value Stream Mapping Analysis

Value Stream Mapping (VSM) is a useful tool for depicting the flow of materials and information in manufacturing and service processes. It is known as one of the most popular lean methods to identify bottlenecks, reduce cycle time, and improve current processes. Although VSM has been extensively used in manufacturing, there are limited studies that applied VSM in non-manufacturing environments. In this study, we present an application of VSM to improve Software Development Life Cycle (SDLC) process in an IT firm. The current process flows (as-is) are mapped to identify non-value-added activities as well as areas for improvement. Based on the analysis of the current state map, we propose recommendations, action plans, and a future state map (to-be-process). We estimate that, with the new process changes, IT project delivery time can be reduced from 210.5 days to 137.5 days – a 34.7% reduction in the software development life cycle process. This provides a powerful base for IT project management and enables the IT department to meet its expected project turnaround time.

Synthesizing secure software development activities for linear and agile lifecycle models

AbstractApplication security is an important concern, and security activities to support software development lifecycle processes, such as specification, design, implementation, and testing are increasingly in need. Despite the plethora of knowledge available for secure software development in online and books, software systems are seldom secure as developers lack security knowledge. The primary reason for this paradox is the diversity and overwhelming nature of the available security knowledge. In this article, we propose to synthesize the well‐known secure software development practices for both linear and agile lifecycle models. Using the MediaWiki platform, we make this knowledge available to software developers and designers from a single source.

Reliability Analysis and Modeling of Green Computing Based Software Systems

Background: Software industries are growing very fast to develop new solutions and ease people’s life. Software reliability has been considered as a critical factor in today’s growing digital world. Software reliability models are one of the most generally used mathematical tools for estimation of software reliability. These reliability models can be applied on the development of sustainable and green computing-based software’s having their constrained development environments. Objective: This paper proposes a new reliability estimation model for green IT environment based software systems. Methods: In this paper, a new failure rate behavior-based model centered on green software development life cycle process has been developed. This model integrates a new modulation factor for incorporating changing needs in each phase of green software development methodology. Parameter estimation for proposed model has been done using hybrid Particle Swarm Optimization and Gravitational Search Algorithm. The proposed model has been tested on real-world datasets. Results: Experimental results are showing the enhanced capability of proposed model in simulating real green software development environment. Using GC-1 and GC-2 dataset, the proposed model is about 60.05% which is more significant than other models. Conclusion: This paper proposed a new failure rate model for softwares that have been developed under green IT environment.

New failure rate model for iterative software development life cycle process

Software reliability models are one of the most generally used mathematical tool for estimation of reliability, failure rate and number of remaining faults in the software. Existing software reliability models are designed to follow waterfall software development life cycle process. These existing models do not take advantage of iterative software development process. In this paper, a new failure rate model centered on iterative software development life cycle process has been developed. It aims to integrate a new modulation factor for incorporating varying needs in each phase of iterative software development process. It comprises imperfect debugging with the possibility of fault introduction and removal of multiple faults in an interval as iterative development of the software proceeds. The proposed model has been validated on twelve iterations of Eclipse software failure dataset and nine iterations of Java Development toolkit (JDT) software failure dataset. Parameter estimation for the proposed model has been done by hybrid particle swarm optimization and gravitational search algorithm. Experimental results in-terms of goodness-of-fit shows that proposed model has outperformed Jelinski Moranda, Shick Wolverton, Goel Okummotto Imperfect debugging, GS Mahapatra, Modified Shick Wolverton in 83.33% of iterations for eclipse dataset and 77.77% of iterations for JDT dataset.

Novel Triplex Procedure for Ranking the Ability of Software Engineering Students Based on Two levels of AHP and Group TOPSIS Techniques

Ranking the strengths and weaknesses of software engineering students in software development life cycle (SDLC) process level is a challenging task owing to (1) data variation, (2) multievaluation criteria, (3) criterion importance and (4) alternative member importance. According to the existing literature, no specified procedure can rank the ability of software engineering students based on SDLC process levels to figure out the strengths and weaknesses of each student. This study aims to present a novel triplex procedure for ranking the ability of software engineering students to address the literature gap. The methodology of the proposed work is presented on the basis of three phases. In the identification phase, four steps are implemented, namely, processing dataset, identifying the criteria, distributing the courses to the software engineering body of knowledge and proposing the pre-decision matrix (DM). The data comprise the GPA and soft skills from 60 software engineering students who graduated from Universiti Pendidikan Sultan Idris in 2016. In the pre-processing phase, three steps are involved as follows. Analytic hierarchy process (AHP) is first used to assign weights to the courses and then multiply the assigned weight by courses, which is the first procedure in the proposed work. In this phase, the construction of DM is presented based on multimeasurement criteria (GPA and soft skills), with SDLC process levels as alternatives. In the development phase, AHP is used again to weight the multimeasurement criteria, and this is the second procedure. In such case, the coordinator and head of the software engineering department are consulted to obtain subjective judgments for each criterion. Technique for order performance by similarity to ideal solution (TOPSIS) is then used to rank the students, which is the third procedure. In the validation, statistical analysis is performed to validate the results by checking the accuracy of the systematic ranking. Results show that (1) integrating AHP and group TOPSIS is suitable for ranking the ability of students. (2) The 60 students are categorized into five ranking groups based on their strength level: 14 collector requirements, 13 designers, 5 programmers, 13 testers and 15 maintenances. (3) Significant differences are observed between the groups’ scores for each level of SDLC, indicating that the ranking results are identical for all levels.

Quantitative software reliability assessment methodology based on Bayesian belief networks and statistical testing for safety-critical software

This study proposes an overall methodology that provides in-depth evidence on software reliability. It is used to quantitatively assess the reliability of nuclear power plant (NPP) safety-critical software for the incorporation of digital instrumentation and control systems into NPP probabilistic risk assessment (PRA). The methodology consists of three parts: (1) the relationships among the software development life cycle (SDLC) phases, the number of remaining faults in the software, and the probability of failure on demand (PFD) are modeled by a Bayesian belief network, which can provide a prior distribution of the software PFD; (2) a reliability model for the PFD is used to calculate the number of no-failure tests needed to meet the expected reliability target according to the prior distribution; (3) the software statistical testing (SST) based on PRA is used as a reliability validation test method to assess reliability, when the required no-failure tests are completed, it is considered that the software meets the expected reliability target. The main contribution of this methodology is that it fully considers the factors that affect software reliability, i.e. the quality of development activities and verification & validation (V&V) activities of the SDLC processes, software operational profile and software operational environment when assessing software reliability. This is done such that the methodology overcomes the subjectivity of separate quality assessments of the SDLC processes. It also solves the problem that occurs because an individual SST using an uninformative prior distribution is conservative.

Building Blocks of Software Design

Software design involves the process of understanding the requirements and creating the artifacts that specify these requirements as the product to be built. The specification of the requirements ultimately happens in code. Intermediate abstraction mechanisms, such as domain modeling languages, software design and architecture patterns, programming paradigms, and design fragments, assist software engineers to specify requirements further into the final designs as implementations. However, in the absence of commonly agreed-upon building blocks that assist software engineers in tracing the design specification across software elements, these abstraction mechanisms become sources of unintended errors. Consequently, despite the availability of many software development lifecycle processes and implementation tool support, designs erode and drift from their intent quicker than anticipated.

A new software development paradigm for intelligent information systems

The continuous growth in software management cost requires the development of self-managed software systems. Using self-managed property, a system will take intelligent decisions to make a system work properly. Autonomic computing is the technique, which is used to develop such systems. Autonomic computing systems are highly reliable software systems. To enhance the quality of software systems, implementation of autonomic computing-based software development life cycle process may be a novel idea. It involves autonomous decision making by the autonomic component during the development of software. This approach reduces the complexity of the software development process. In addition, it resolves the purpose of autonomic computing to reduce software complexity and do real-time exception handling. In this paper, the implementation of the autonomic advisor-based software development process is proposed using the cloud computing technique. Cloud computing helps the developers to develop software, applications using deliverable services such as platform, infrastructure, and software. During the implementation and usage of autonomic advisor, the database becomes heavier. Therefore, to resolve such issues, cloud computing will be a beneficiary step. Other benefits of such an autonomous software development life cycle process are discussed further in this paper.

A Comparative Study of Static Code Analysis tools for Vulnerability Detection in C/C++ and JAVA Source Code

Abstract Software security has become an essential component of software development process. It is necessary for an organisation to maintain software security in order to ensure integrity, authenticity and availability of the software product. To ensure software security, one of the major task is to identify vulnerabilities present in the source code before the software is being deployed. Detecting vulnerabilities in early phases of software development cycle, makes the process of fixing those vulnerabilities much easier for software developers. The vulnerability detection can be done either at the production phase, this means when the software is still being developed by statically auditing the source code, or dynamically at run time. In this study, vulnerability detection was done through Static code analysis process. Static code analysis can be done either manually or through automated tools. This paper focuses on using automated source code scanning tools for vulnerabilities detection in a software. Automated static Code Analysis tools audits the entire source code for its quality and identify any potential security vulnerability, if present. Unlike dynamic source code analysis that evaluates the source code behaviour during code execution, which is done quite late in the software development life cycle, Static Code Analysis leads to detection of security vulnerabilities in a source code in early stages of software development process, when the software is still in production phase because it does not require code to be in execution state. This paper firstly explains the importance of incorporating static code analysis in software development life cycle process so as to facilitate early detection of vulnerabilities in software product, and then present a comparative study of various static code analysis tools available for vulnerability detection in C/C++ and JAVA source code. The comparative study of three C/C++ static code analysis tools (flawfinder, RATS and CPPCheck) and two JAVA static code analysis tools (spotbugs and PMD) is done using Juliet (version1.3) test suite and APACHE tomcat dataset respectively, on the basis of category of vulnerability detected by each of the selected tool and the likelihood of false positive reported by each tool. Results showed that Flawfinder detected maximum categories of vulnerabilities and RATS and CPPCheck were almost similar in types of vulnerabilities detected. Also, it was observed that CPPCheck reported maximum number of false positives as compared to other two tools. Java static code analysis tools Spot bugs was able to detect more number of vulnerabilities than PMD.

Optimization of software development life cycle process to minimize the delivered defect density

Many organizations utilize information technology to gain competitive advantage. As the need for software increased, the number of software companies and the competition among them also increased. The software organizations in countries like India can no longer survive based on cost advantage alone. The companies need to deliver defect-free software on time within the budgeted cost. This paper is a case study on minimizing the delivered defect density by optimally executing the various phases in software development life cycle process. The implementation of the study on four projects has shown that the delivered defect density can be minimized by executing the software development process with optimum settings suggested by the methodology. The project managers can also utilize the approach to achieve the goals set on other important output characteristics like productivity, schedule, etc.

Autonomic Provisioning in Software Development Life Cycle Process

Advancement in software technologies has helped IT developers to work efficiently and enhance quality of the products but simultaneously; it has also presented the problem of increasing complexity in terms of software architectures, programming code and software management task. These issues raise chances of vulnerabilities in the software system. Run-time solution to the faults and failures of software need to be done. One such solution for handling run-time management tasks is Autonomic Computing. Autonomic computing technique, automate the management task to prevent the occurrence of vulnerability based issues. Further, to reduce the occurrence of system failures, an idea to provide an autonomic advisor to the Software Development Life Cycle process has been proposed in this paper. The autonomic advisor gives autonomic features based required suggestions to the developers during the software development process. It will also help to perform risk analysis during development. This will lead to the development of quality and efficient software systems. This paper also provides a review of the existing work of the autonomic computing including its challenges and their effects on management process of the system.

Comparison of Agile Method and Scrum Method with Software Quality Affecting Factors

The software industry used software development lifecycle (SDLC) to design, develop, produce high quality, reliable and cost-effective software products. To develop an application, project team used some methodology which may include artifacts and pre-defining specific deliverables. There are different SDLC process models such as waterfall, iterative, spiral and agile model available to develop a quality product. In this paper we focus only on agile software development model, and Scrum model and their techniques. There are many papers and books written on agile methodologies. We will also use their knowledge in this paper. To collect data for comparison of agile method with software quality affecting factors, an online questionnaire survey was conducted. The survey sample consisted of software developers with several years of industry experience using agile methodologies. The main purpose of this study is to compare soft-ware quality affecting factors with agile and scrum model.