Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 5,210 papers for “software development lifecycle”

Global-software development lifecycle

Alvin W. Yeo · 2001

This study was conducted to explore the efficacy of the global-software development lifecycle (global-SDLC), which comprises design, implementation and usability evaluation phase. A spreadsheet was adapted using the global-SDLC process to accommodate a number of cultures. The design and implementation phases were efficacious. However, in the usability evaluation phase, the usability evaluation techniques were only efficacious when participants, who were experienced computer users and participants who were familiar with the experimenter, were employed. Explanations, from cultural literature such as Hofstede, are presented and implications of these findings on the usability evaluation phase and the global-SDLC are also described.

Cited by 81

Software development lifecycle models

Nayan B. Ruparelia · ACM SIGSOFT Software Engineering Notes · 2010

This history column article provides a tour of the main software development life cycle (SDLC) models. (A lifecycle covers all the stages of software from its inception with requirements definition through to fielding and maintenance.) System development lifecycle models have drawn heavily on software and so the two terms can be used interchangeably in terms of SDLC, especially since software development in this respect encompasses software systems development. Because the merits of selecting and using an SDLC vary according to the environment in which software is developed as well as its application, I discuss three broad categories for consideration when analyzing the relative merits of SDLC models. I consider the waterfall model before the other models because it has had a profound effect on software development, and has additionally influenced many SDLC models prevalent today. Thereafter, I consider some of the mainstream models and finish with a discussion of what the future could hold for SDLC models.

Cited by 403

A progressive software development lifecycle

R. Turpin · 2002

Traditional software lifecycles put significant effort in analysis, design, and implementation before their results can be tested. The start of testing late in the lifecycle often uncovers flaws from these early phases that require significant rework of analysis and design, causing cost overruns and schedule slippages. We describe a software lifecycle where each phase of development is followed by an execution test of the results of that phase. This lifecycle is progressive in the sense that it does not require significant "backing up" to earlier phases of development. The use of this lifecycle requires tool support that is just now becoming available. We examine this lifecycle and its implications for embedded software development. Section I examines traditional lifecycles. Section 2 describes the progressive lifecycle, explains its benefits and requirements, and briefly relates it to other software development paradigms. In conclusion, we relate development lifecycles to process maturity.

Cited by 4

A Progressive Software Development Lifecycle

Russell Twin · 1996

Traditional software lifecycles put sign$canr effort in analysis, design, and implementation b@ore their results can be tested. The start of testing late in the Ei$ecycle @en uncoverswcant “backing up” to earlierphmes of development. The use of this lifecycle requires tool support that is just now becoming available. We examine this lifecycle and its implicationsfor embedded sofrware development. Section 1 examines traditional kifecycles. Section 2 describes the progressive lifecycle, explains its benefits and requirements, and brie$y relates it to other sofhlrnre development paradigms. In conclusion, we relate development lifecycles to process ma~~rizy.

Cited by 0

IMPROVING THE SOFTWARE DEVELOPMENT LIFECYCLE

Denis Kokorev, V. G. Sidorenko · 2023

This article deals with the methodology for developing a software development process. The method for generating a list of practices for evaluation based on the development option and distribution of the evaluation of the development process is described.

Cited by 0

Secure Software Development Lifecycle (SSDLC)

Scott Norberg · Apress eBooks · 2024

I’ve spent pretty much the entire book up to this point talking about specific programming and configuration techniques you can use to help make your applications secure. Now it’s time to talk about how to verify that your applications are, in fact, secure. Let’s start by getting one thing out of the way: adding security after the fact never works well. Starting your security checks right before you go live “just to be sure” ensures that you won’t have enough time to fix more than the most egregious problems, and going live before doing any research means your customers’ information is at risk. As one example, Disney+ was hacked hours after going live.

Cited by 0

DSP Software Development Lifecycle Issues

Robert Oshana Raytheon, Robert Oshana · 2007

This memory is used to store intermediate variables and is much faster to access than external memory. Effective management and use of on-chip memory may result in significant performance improvements.

Cited by 0

Enhanced Software Risk Assessment in Software Development Lifecycle

Kuma Yadi · Multimedia Research · 2022

Risk is a destructive and serious problem that may happen in the future of the software project.The definition of risk is an indicated negative thing.However, in software project development risk has two meanings.One is the opportunity for the developer and customer if it gives motivational consequence on the project objectives and the other one is a negative risk that affects the project objectives and may lead to the failure of the project.Improper assessment of negative risk is the main reason for the failure of SP.

Cited by 0Open access

Security in the Software Development Lifecycle

Díaz López, Daniel Orlando · Repositorio Institucional E-DocUR (Universidad Del Rosario) · 2021

Esta presentación realiza una introducción a la seguridad en aplicaciones, primero indicando su importancia y luego presentando el concepto de "seguridad holística" el cual incluye a la seguridad de aplicaciones como un elemento fundamental. Esta presentación también habla de la triple restricción en la gerencia de proyectos de software. Adicionalmente se explican los conceptos de diseño de software seguro y los tipos de requerimientos de seguridad. Finalmente, esta presentación explica algunas de las principales metodologías de desarrollo de software que existen, haciendo un recorrido desde las mas tradicionales hasta SCRUM. Sobre SCRUM se explican los principios del desarrollo de software agil, los roles y el flujo de trabajo, indicando siempre en que parte de la metodología deberían incluirse los requerimientos de seguridad. La presentación también incluye un conjunto de preguntas de selección mútiple que sirven para validar y consolidar el conocimiento.

Cited by 0

Software Development Lifecycle for Energy Efficiency

Stefanos Georgiou, Stamatia Rizou, Diomidis Spinellis · ACM Computing Surveys · 2019

Motivation: In modern it systems, the increasing demand for computational power is tightly coupled with ever higher energy consumption. Traditionally, energy efficiency research has focused on reducing energy consumption at the hardware level. Nevertheless, the software itself provides numerous opportunities for improving energy efficiency. Goal: Given that energy efficiency for it systems is a rising concern, we investigate existing work in the area of energy-aware software development and identify open research challenges. Our goal is to reveal limitations, features, and tradeoffs regarding energy-performance for software development and provide insights on existing approaches, tools, and techniques for energy-efficient programming. Method: We analyze and categorize research work mostly extracted from top-tier conferences and journals concerning energy efficiency across the software development lifecycle phases. Results: Our analysis shows that related work in this area has focused mainly on the implementation and verification phases of the software development lifecycle. Existing work shows that the use of parallel and approximate programming, source code analyzers, efficient data structures, coding practices, and specific programming languages can significantly increase energy efficiency. Moreover, the utilization of energy monitoring tools and benchmarks can provide insights for the software practitioners and raise energy-awareness during the development phase.

Cited by 55

AI-Driven Software Development Lifecycle Optimization

Pawan Kumar Goel, Km Komal, Nitish Vashishth · Advances in systems analysis, software engineering, and high performance computing book series · 2024

This research explores the integration of artificial intelligence (AI) into the software development lifecycle (SDLC) to optimize processes and address evolving industry demands. Against a backdrop of increased complexity in software projects, the study investigates historical context, emphasizing the imperative for AI infusion in SDLC. The primary objective is to illuminate how AI strategically enhances various SDLC stages, elucidating specific challenges it addresses. Employing a multifaceted approach, including literature reviews, case studies, and empirical analyses, the research showcases AI's role in automated code generation, intelligent code reviews, predictive maintenance, AI-powered testing, and dynamic resource allocation. Results demonstrate increased development speed, improved code quality, proactive issue identification, and efficient resource utilization. The chapter synthesizes key insights, underscoring AI's transformative impact on software development efficiency and product quality.

Cited by 9

DevOps phases across Software Development Lifecycle

Mayank Gokarna · 2020

DevOps is the combination of cultural mindset, practices, and tools that increases a team's ability to release applications and services at high velocity. Transitioning to DevOps requires a change in culture and mindset first. DevOps is about removing the barriers between two traditionally delimited teams, development and operations. With DevOps, these two teams work together to optimize both the productivity of developers and the reliability of operations. They strive to communicate frequently, increase efficiencies, and improve the quality of services they provide. They take full ownership for their services, often beyond where their stated roles or titles have traditionally been scoped. This paper aims to bring different phases of software development lifecycle into DevOps implementation strategy.This paper highlights on DevOps practices which span across different phases of the Software Development Lifecycle (SDLC).

Cited by 5Open access

FUNDAMENTAL CONCEPTS OF SOFTWARE DEVELOPMENT LIFECYCLE EXPLAINED

Iqbal, Farhan Nadim · Zenodo (CERN European Organization for Nuclear Research) · 2023

Software Development Lifecycle, or SDLC, is a project management process for the software industry with various approaches and methodologies during the lifetime of a software system, from its inception to the end-of-life date. If it is appropriately utilized during the lifecycle of a software or program, it can cause minimum backlashes for stakeholders, developers, and customers involved by managing resources and functioning efficiently. This paper delves deeper and tries to explain their concepts briefly.

Cited by 0Open access

Legal Risks in the Software Development Lifecycle

Oana GHERGHINA · 2026

Legal Risks in the Software Development Lifecycle addresses the growing complexity of software development as both a technical and legal discipline. As the digital economy expands, software has become a core infrastructure asset whose lifecycle demands rigorous and enforceable contractual governance. This book analyses how legal risks arise and evolve across the Software Development Lifecycle (SDLC), providing a systematic account of the planning, delivery, and long-term maintenance of software projects. The book takes readers through the entire SDLC, explaining each phase’s technical purpose, the role and obligations of the parties involved, and the contractual documentation required to secure compliance and accountability. At every stage, it identifies the principal legal risks and demonstrates how they can be prevented through careful planning, well-defined deliverables, and tailored contractual provisions. Rather than focusing on litigation outcomes, the book emphasizes preventive strategies, providing readers with a structured roadmap to anticipate disputes before they arise. Sample clauses and checklists are included to highlight practical solutions, but the core value lies in its systematic explanation of processes, responsibilities, and risk-management mechanisms. Covering major contractual models such as Fixed-Price, Time & Material, Agile, Hybrid, and Milestone-based agreements, it highlights their advantages, limitations, and common points of dispute, while offering strategies to structure payments, allocate intellectual property rights, and manage scope changes effectively. The book’s approach is multidisciplinary. It is written for lawyers and legal advisors seeking to understand technical processes and draft precise, enforceable agreements; for project managers and clients who need to anticipate and manage contractual obligations; for software developers and vendors who want to align deliverables with contract terms and regulatory requirements; for judges, arbitrators, and mediators resolving IT-related disputes; and for students and researchers in law, technology and business, seeking a bridge between theory and practice.

Cited by 0