software lifecycle
SpringerReference · 2011
Cited by 0
Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.
About 8,756 papers for “software lifecycle”
SpringerReference · 2011
Cited by 0
Guy Courbebaisse, Bernd Flemisch, K. Graf et al. · SPIRE - Sciences Po Institutional REpository · 2023
Software developed in the process of doing research is receiving increased attention. It is now more and more often considered a genuine research output next to scientific articles and research data publications. Based on representative user stories we identify and characterize the different phases and stages that the research software development process can go through thereby defining the “Research Software Lifecycle”. Different approaches to software development such as product-, project- or platform-orientation are also outlined. We close with recommendations on EOSC infrastructure components needed to support the identified processes and platforms.
Cited by 1Open access
Susan M. Houston · 2017
Cited by 7
Susan M. Houston · Productivity Press eBooks · 2021
Cited by 0
Courbebaisse, Guy, Flemisch, Bernd, Graf, Kay et al. · Zenodo (CERN European Organization for Nuclear Research) · 2023
Software developed in the process of doing research is receiving increased attention. It is now more and more often considered a genuine research output next to scientific articles and research data publications. Based on representative user stories we identify and characterize the different phases and stages that the research software development process can go through thereby defining the “Research Software Lifecycle”. Different approaches to software development such as product-, project- or platform-orientation are also outlined. We close with recommendations on EOSC infrastructure components needed to support the identified processes and platforms.
Cited by 0Open access
Казакова, Н.Ф., Казакова, Н.Ф., Kazakova, N. · Electronic Odessa National Economic University Institutional Repository (Odessa National Economic University) · 2013
Розглядаються загальні принципи стандартизації життєвого циклу програмних засобів, які є одним з дієвих інструментів при вирішенні питань їх замовлення, придбання, розробки, експлуатації та супроводу. Аналізується використання уніфікованих підходів, закріплених в сучасних міжнародних і вітчизняних стандартах, включаючи діючі стандарти СРСР.
Cited by 0Open access
Benjamin Weder, Johanna Barzen, Frank Leymann et al. · 2020
Quantum computing is an emerging paradigm that enables to solve a variety of problems more efficiently than it is possible on classical computers. As the first quantum computers are available, quantum algorithms can be implemented and executed on real quantum hardware. However, the capabilities of today’s quantum computers are very limited and quantum computations are always disturbed by some error. Thus, further research is needed to develop or improve quantum algorithms, quantum computers, or required software tooling support. Due to the interdisciplinary nature of quantum computing, a common understanding of how to develop and execute a quantum software application is needed. However, there is currently no methodology or lifecycle comprising all relevant phases that can occur during the development and execution process. Hence, in this paper, we introduce the quantum software lifecycle consisting of ten phases a gate-based quantum software application should go through. We analyze the purpose of each phase, the available methods and tools that can be applied, and the open problems or research questions. Therefore, the lifecycle can be used as a baseline for discussions and future research.
Cited by 58
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
Wade, Stan, Wade, Stan · Spiral (Imperial College London) · 2006
Cited by 0
Oana GHERGHINA · 2026
Cited by 0
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
MATHEU GARCIA, SARA NIEVES · Zenodo (CERN European Organization for Nuclear Research) · 2025
Teaching material abut secure software development methodologies, with special emphasis on DevSecOps, cybersecurity certification and regulation.
Cited by 0Open access
Frank John Hodum · Journal of International Crisis and Risk Communication Research · 1999
Cited by 0Open access
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
Martin Reinhardt · Zenodo (CERN European Organization for Nuclear Research) · 2026
This workshop is designed for Users of the DAPHNE community. Key facts are: general knowledge of git is known no Professional knowledge of git no knowledge about Zenodo Github integration no Docker knowledge intermediate coding skills It is designed for working on hands for 35 minutes. It will be close to a demo which can be repeated at own pace.
Cited by 0Open access
Michael A. Heroux, Ross Bartlett, James Willenbring · Figshare · 2014
This presentation is about software lifecycle models for scientific computing projects. In particular, we highlight the experiences of the Trilinos project, which develops modular, reusable components for scientific and engineering applications.
Cited by 0Open access
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
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
Martin Reinhardt · Zenodo (CERN European Organization for Nuclear Research) · 2026
Full Changelog: https://github.com/Sonicious/DaphneSoftwareWorkshop/compare/0.5...0.6 More text here
Cited by 0Open access
Heroux Michael, Bartlett Ross, Willenbring James · Figshare · 2014
This presentation is about software lifecycle models for scientific computing projects. In particular, we highlight the experiences of the Trilinos project, which develops modular, reusable components for scientific and engineering applications.
Cited by 0Open access