Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.
About 1,109 papers for “Software versioning”
Klaus Marquardt · 2010
Software developers rightfully focus on the activities needed to polish the software for its first release. The management of future releases, version identification, compatibility checks, and update strategies are typically treated as an afterthought, but insufficiencies or inconsistencies here have all the potential to make your life miserable once the software has hit the market.
Cited by 3
Castes, Charly, Bugnion, Edouard · Infoscience (Ecole Polytechnique Fédérale de Lausanne) · 2022
Trusted execution environments enable the creation of confidential and attestable enclaves that exclude the platform and service providers from the trusted base. From its initial attestable state, a stateful enclave such as a confidential database can hold confidential information in memory or use an enclave-specific secret seed to encrypt it on disk. The attestation logic is bound to a unique software version, and does not provide a mechanism to upgrade software version. We propose attestable software versioning to ensure the trust-worthy software migration of stateful enclaves in the context of an untrusted service operator. Attestable software versioning relies on extended attestation, a two-steps hashing process for measurement validation of an enclave extended with its complete software lineage, which further restricts migration to white-listed software versions. Enclaves rely on mutual local or remote extended attestation during the software upgrade; client program use remote extended attestation to determine the software lineage decisions made by the untrusted service operator. The mechanism enables a full separation of roles and responsibilities between software editors, which cannot access data, and untrusted platform operators, who trigger attestable software upgrades.
Cited by 0Open access
FAIRsharing Team, · FAIRsharing.org · 2026
This FAIRsharing record describes: This indicator aims to determine if the version (or versions) of a software tool follows an established community convention like semantic versioning (SemVer) or calendar versioning (CalVer).
Cited by 0Open access
Stanko Tvrde · Repository of University Department of Professional Studies · 2021
Cilj ovog završnog rada je izrada web aplikacije za verzioniranje softvera, odnosno alata koji bi olakšao praćenje razvoja softvera u poduzećima. Osnovna ideja je bila pružiti proizvod poduzećima koja se bave proizvodnjom i razvojem softvera. Jedan od glavnih zadataka web aplikacije za verzioniranje je izraditi alat koji će olakšati proces prenošenja korisničkih zahtjeva do samih programera. Voditelji timova (engl. Team leaders) imaju uvid i mogućnost editiranja svih verzija softvera koje su proizveli do sada, popis svih funkcionalnosti po verzijama, te mogućinost uvida u popis korisničkih zahtjeva i prijavljene greške (engl. bug) na svaku pojedinu verziju. Web aplikacija je namijenjena za korištenje na svim uređajima koji podržavaju web preglednike. Aplikacija je stabilna i skalabilna pa je stoga lako nadograđivati. Za izradu web aplikacije je u najvećem dijelu je korišten razvojni okvir Django i programski jezik Python.
Cited by 0
Youakim Badr, Guy Caplat · HAL (Le Centre pour la Communication Scientifique Directe) · 2010
International audience
Cited by 0
Arne Lie, Reidar Conradi, Tor Didriksen et al. · 1989
We present the change oriented model of versioning, which focuses strongly on functional changes in a software product and therefore can be seen as an alternative to the traditional, “version oriented” models. The change oriented model is used as a basis for the versioning in the EPOS software engineering database, which features an integrated transaction and versioning mechanism.
Cited by 69
Anonymous · Zenodo (CERN European Organization for Nuclear Research) · 2026
Change Propagation in Software Versioning: Systematic Literature Review
Cited by 0Open access
Anonymous · Zenodo (CERN European Organization for Nuclear Research) · 2026
Change Propagation in Software Versioning: Systematic Literature Review
Cited by 0Open access
Pietsch, Pit, Kelter, Udo, Ringert, Jan Oliver · RWTH Publications (RWTH Aachen) · 2014
Cited by 0
Jaroslav Gergič · 2004
The world of software development has rapidly changed in the last few years due to the adoption of component-based technologies. The classical software configuration management, which deals with source code versioning, becomes insufficient in the world where most components are distributed in a binary form. This paper focuses on solving versioning issues in the SOFA/DCUP (software appliances/dynamic component updating) component environment. However, many ideas introduced in this paper are applicable in other component-based environments. The paper incorporates the following versioning issues: component and type identification, component and type evolution, component version description model and component retrieving based on the version description model. It also outlines a prototype repository designed as a proof of concept.
Cited by 15
Jens-otto Larsen, Bjørn P. Munch, Bjørn Gulla et al. · 2010
This paper discusses aspects of the Change Oriented Versioning (CoV) model, which provides a uniform version concept rather different from the more traditional models. Its main goal is to give users and administrators a more flexible, yet simpler, way to manage changes in large and complex sets of data. In addition to a description of our model, we here add some simple guidelines about how we think it will be used, and describe some of our recent work, not previously presented. We also discuss its use in our work on cooperating transactions. One recent breakthrough in CoV is that we have now designed and implemented a versioning “engine” which is independent of the data model being used. 1
Cited by 0
Richard Mordinyi, Estefanía Serral, Dietmar Winkler et al. · 2014
Cited by 0
Kirti Mathur, Amber Jain · Indian Journal Of Applied Research · 2011
IJAR - Indian Journal of Applied Research (IJAR) IJAR is a double reviewed monthly print journal that accepts research works from scholars, academicians, professors, doctorates, lecturers, and corporate in their respective expertise of studies.
Cited by 0
Sun, Yangyang, Dang, Chuangyin, Feng, Gengzhong · Figshare · 2020
Software-as-a-service (SaaS) is gaining tremendous popularity in the enterprise software releases, which has brought the growing challenge for the incumbent used to adopt the on-premise licensing model. In this paper, we focus on the optimal versioning strategy problem of the incumbent when he faces the competition from the entrant who releases the SaaS software. He can choose from providing the upgraded on-premise software, turning to offer the SaaS version of the software, and releasing both the versions. We indicate that releasing both versions won't be the optimal choice in the competitive environment. When the upgrade cost is above a certain value, and the gap of value is below a threshold positively linear correlated with the upgrade cost, the incumbent prefers the SaaS strategy. Otherwise, the on-premise strategy generates the highest profit. A special case is that in the medium switching cost environment, the SaaS strategy can be optimal for all possible values of upgrade cost. Finally, We consider the problem in the presence of network effect and in the uncovered market setting. The results provide effective managerial insights into the strategy selection for the incumbent.
Cited by 0Open access
Wenjun Shu, Zhongdong Xiao, Ruirui Zhang et al. · Journal of theoretical and applied electronic commerce research · 2023
This study investigates the optimal versioning problem when a monopoly software provider bears the deliberation cost to help reduce consumer uncertainty about SaaS customization. We develop stylized models based on different production strategies and deliberation support strategies. We consider customer deliberation behavior as a new perspective on the need for a free trial. Our results indicate that a short free trial leads to free riders while a long enough free trial eliminates free riders. This is because a long free trial means that consumers easily get accustomed to the product. We also find that the seller benefits from offering deliberation support. The optimal product strategy is dependent on the deliberation support cost. When the deliberation support cost is low, the seller should provide dual products; on the contrary, the single SaaS product strategy is better with a high deliberation cost.
Cited by 1Open access
Abderrahman Mokni, Marianne Huchard, Christelle Urtado et al. · SPIRE - Sciences Po Institutional REpository · 2016
International audience
Cited by 1
2009
Cited by 5
Waqar Mehmood, Nadir Shah, Ehsan Ullah Munir · Research Journal of Information Technology · 2013
In this study we present an approach to address the issues of synchronization, evolution control and version granularity in Software Configuration Management (SCM). Our approach is based on a unified model developed during software lifecycle. The unified model consists of a set of different kinds of model and the interlinks information between these models, such models includes Analysis and design model, Test models etc. These models may possibly be created using different development tools in a heterogeneous environment. Our approach is based on identifying interlinks dependencies between different model elements. By using these interlinks information we develop our evolution control policy and perform synchronization of models elements.
Cited by 0Open access
Pietsch, Pit, Kelter, Udo, Ringert, Jan Oliver · RWTH Publications (RWTH Aachen) · 2013
Cited by 0
Jaroslav Bauml, Přemek Brada · 2009
Consistency of component software is a crucial condition required for correct program execution. The existing consistency controls of OSGi at build time or in runtime cannot prevent type mismatch failures caused by independent client and server bundle development. This paper describes our solution to this problem using automated versioning of components. Version identifiers are generated from results of subtype-based comparison of component representations, thus achieving a consistent and formally backed interpretation of the version numbering scheme. The implementation of the approach allows its integration into standard OSGi bundle development and build cycle.
Cited by 24