Relevant bibliographies by topics / Code versioning

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Code versioning'

Author: Grafiati
Published: 4 June 2021
Last updated: 11 February 2022

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Code versioning.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Code versioning"

1

Poudel, Pavan, and Gokarna Sharma. "Adaptive Versioning in Transactional Memory Systems." Algorithms 14, no. 6 (May 31, 2021): 171. http://dx.doi.org/10.3390/a14060171.

Full text
Abstract:
Transactional memory has been receiving much attention from both academia and industry. In transactional memory, program code is split into transactions, blocks of code that appear to execute atomically. Transactions are executed speculatively and the speculative execution is supported through data versioning mechanism. Lazy versioning makes aborts fast but penalizes commits, whereas eager versioning makes commits fast but penalizes aborts. However, whether to use eager or lazy versioning to execute those transactions is still a hotly debated topic. Lazy versioning seems appropriate for write-dominated workloads and transactions in high contention scenarios whereas eager versioning seems appropriate for read-dominated workloads and transactions in low contention scenarios. This necessitates a priori knowledge on the workload and contention scenario to select an appropriate versioning method to achieve better performance. In this article, we present an adaptive versioning approach, called Adaptive, that dynamically switches between eager and lazy versioning at runtime, without the need of a priori knowledge on the workload and contention scenario but based on appropriate system parameters, so that the performance of a transactional memory system is always better than that is obtained using either eager or lazy versioning individually. We provide Adaptive for both persistent and non-persistent transactional memory systems using performance parameters appropriate for those systems. We implemented our adaptive versioning approach in the latest software transactional memory distribution TinySTM and extensively evaluated it through 5 micro-benchmarks and 8 complex benchmarks from STAMP and STAMPEDE suites. The results show significant benefits of our approach. Specifically, in persistent TM systems, our approach achieved performance improvements as much as 1.5× for execution time and as much as 240× for number of aborts, whereas our approach achieved performance improvements as much as 6.3× for execution time and as much as 170× for number of aborts in non-persistent transactional memory systems.
APA, Harvard, Vancouver, ISO, and other styles
2

Harshan, J., Anwitaman Datta, and Frédérique Oggier. "DiVers: An erasure code based storage architecture for versioning exploiting sparsity." Future Generation Computer Systems 59 (June 2016): 47–62. http://dx.doi.org/10.1016/j.future.2016.01.005.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Antoniol, Giuliano, Massimiliano Di Penta, Harald Gall, and Martin Pinzger. "Towards the Integration of Versioning Systems, Bug Reports and Source Code Meta-Models." Electronic Notes in Theoretical Computer Science 127, no. 3 (April 2005): 87–99. http://dx.doi.org/10.1016/j.entcs.2004.08.036.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

ARTIGAS, PEDRO V., MANISH GUPTA, SAMUEL P. MIKIFF, and JOSÉ E. MOREIRA. "AUTOMATIC LOOP TRANSFORMATIONS AND PARALLELIZATION FOR JAVA." Parallel Processing Letters 10, no. 02n03 (June 2000): 153–64. http://dx.doi.org/10.1142/s0129626400000160.

Full text
Abstract:
This paper describes a prototype Java compiler that achieves performance levels approaching those of current state-of-the-art Fortran compilers on numerical codes. We present a new transformation called alias versioning that takes advantage of the simplicity of pointers in Java. This transformation, combined with other techniques that we have developed, enables the compiler to perform high order loop transformations and parallelization completely automatically. We believe that our compiler is the first to have such capabilities of optimizing numerical Java codes. By exploiting synergies between our compiler and the Array package for Java, we achieve between 80 and 100% of the performance of highly optimized Fortran code in a variety of benchmarks. Furthermore, automatic parallelization achieves speedups of up to 3.8 on four processors. Our compiler technology makes Java a serious contender for implementing numerical applications.
APA, Harvard, Vancouver, ISO, and other styles
5

Chien, A., P. Balaji, N. Dun, A. Fang, H. Fujita, K. Iskra, Z. Rubenstein, et al. "Exploring versioned distributed arrays for resilience in scientific applications." International Journal of High Performance Computing Applications 31, no. 6 (September 8, 2016): 564–90. http://dx.doi.org/10.1177/1094342016664796.

Full text
Abstract:
Exascale studies project reliability challenges for future HPC systems. We present the Global View Resilience (GVR) system, a library for portable resilience. GVR begins with a subset of the Global Arrays interface, and adds new capabilities to create versions, name versions, and compute on version data. Applications can focus versioning where and when it is most productive, and customize for each application structure independently. This control is portable, and its embedding in application source makes it natural to express and easy to maintain. The ability to name multiple versions and “partially materialize” them efficiently makes ambitious forward-recovery based on “data slices” across versions or data structures both easy to express and efficient. Using several large applications (OpenMC, preconditioned conjugate gradient (PCG) solver, ddcMD, and Chombo), we evaluate the programming effort to add resilience. The required changes are small (< 2% lines of code (LOC)), localized and machine-independent, and perhaps most important, require no software architecture changes. We also measure the overhead of adding GVR versioning and show that overheads < 2% are generally achieved. This overhead suggests that GVR can be implemented in large-scale codes and support portable error recovery with modest investment and runtime impact. Our results are drawn from both IBM BG/Q and Cray XC30 experiments, demonstrating portability. We also present two case studies of flexible error recovery, illustrating how GVR can be used for multi-version rollback recovery, and several different forward-recovery schemes. GVR’s multi-version enables applications to survive latent errors (silent data corruption) with significant detection latency, and forward recovery can make that recovery extremely efficient. Our results suggest that GVR is scalable, portable, and efficient. GVR interfaces are flexible, supporting a variety of recovery schemes, and altogether GVR embodies a gentle-slope path to tolerate growing error rates in future extreme-scale systems.
APA, Harvard, Vancouver, ISO, and other styles
6

Wiltshire, Andrew J., Maria Carolina Duran Rojas, John M. Edwards, Nicola Gedney, Anna B. Harper, Andrew J. Hartley, Margaret A. Hendry, Eddy Robertson, and Kerry Smout-Day. "JULES-GL7: the Global Land configuration of the Joint UK Land Environment Simulator version 7.0 and 7.2." Geoscientific Model Development 13, no. 2 (February 7, 2020): 483–505. http://dx.doi.org/10.5194/gmd-13-483-2020.

Full text
Abstract:
Abstract. We present the latest global land configuration of the Joint UK Land Environment Simulator (JULES) model as used in the latest international Coupled Model Intercomparison Project (CMIP6). The configuration is defined by the combination of switches, parameter values and ancillary data, which we provide alongside a set of historical forcing data that defines the experimental setup. The configurations provided are JULES-GL7.0, the base setup used in CMIP6 and JULES-GL7.2, a subversion that includes improvements to the representation of canopy radiation and interception. These configurations are recommended for all JULES applications focused on the exchange and state of heat, water and momentum at the land surface. In addition, we provide a standardised modelling system that runs on the Natural Environment Research Council (NERC) JASMIN cluster, accessible to all JULES users. This is provided so that users can test and evaluate their own science against the standard configuration to promote community engagement in the development of land surface modelling capability through JULES. It is intended that JULES configurations should be independent of the underlying code base, and thus they will be available in the latest release of the JULES code. This means that different code releases will produce scientifically comparable results for a given configuration version. Versioning is therefore determined by the configuration as opposed to the underlying code base.
APA, Harvard, Vancouver, ISO, and other styles
7

Jennings-Antipov, Laura D., and Timothy S. Gardner. "Digital publishing isn't enough: the case for ‘blueprints’ in scientific communication." Emerging Topics in Life Sciences 2, no. 6 (December 21, 2018): 755–58. http://dx.doi.org/10.1042/etls20180165.

Full text
Abstract:
Since the time of Newton and Galileo, the tools for capturing and communicating science have remained conceptually unchanged — in essence, they consist of observations on paper (or electronic variants), followed by a ‘letter’ to the community to report your findings. These age-old tools are inadequate for the complexity of today's scientific challenges. If modern software engineering worked like science, programmers would not share open source code; they would take notes on their work and then publish long-form articles about their software. Months or years later, their colleagues would attempt to reproduce the software based on the article. It sounds a bit silly, and yet even, this level of prose-based methodological discourse has deteriorated in science communication. Materials and Methods sections of papers are often a vaguely written afterthought, leaving researchers baffled when they try to repeat a published finding. It's time for a fundamental shift in scientific communication and sharing, a shift akin to the advent of computer-aided design and source code versioning. Science needs reusable ‘blueprints’ for experiments replete with the experiment designs, material flows, reaction parameters, data, and analytical procedures. Such an approach could establish the foundations for truly open source science where these scientific blueprints form the digital ‘source code’ for a supply chain of high-quality innovations and discoveries.
APA, Harvard, Vancouver, ISO, and other styles
8

González-Torres, Antonio, José Navas-Sú, Marco Hernández-Vásquez, Franklin Hernández-Castro, and Jennier Solano-Cordero. "A visual analytics architecture for the analysis and understanding of software systems." Enfoque UTE 10, no. 1 (March 29, 2019): 218–33. http://dx.doi.org/10.29019/enfoqueute.v10n1.455.

Full text
Abstract:
Visual analytics facilitates the creation of knowledge to interpret trends and relationships for better decision making. However, it has not being used widely for the understanding of software systems and the change process that takes place during their development and maintenance. This occurs despite the need of project managers and developers to analyze their systems to calculate the complexity, cohesion, direct, indirect and logical coupling, detect clones, defects and bad smells, and the comparison of individual revisions. This research considers the design of an extensible and scalable architecture to incorporate new and existing methods to retrieve source code from different versioning systems, to carry out the analysis of programs in different languages, to perform the calculation of software metrics and to present the results using visual representations, incorporated as Eclipse and Visual Studio extensions. Consequently, the aim of this work is to design a visual analytics architecture for the analysis and understanding of systems in different languages and its main contributions are the specification of the design and requirements of such architecture, taking as base the lessons learned in Maleku (A. González-Torres et al., 2016).
APA, Harvard, Vancouver, ISO, and other styles
9

Willighagen, Lars G. "Citation.js: a format-independent, modular bibliography tool for the browser and command line." PeerJ Computer Science 5 (August 12, 2019): e214. http://dx.doi.org/10.7717/peerj-cs.214.

Full text
Abstract:
Background Given the vast number of standards and formats for bibliographical data, any program working with bibliographies and citations has to be able to interpret such data. This paper describes the development of Citation.js (https://citation.js.org/), a tool to parse and format according to those standards. The program follows modern guidelines for software in general and JavaScript in specific, such as version control, source code analysis, integration testing and semantic versioning. Results The result is an extensible tool that has already seen adaption in a variety of sources and use cases: as part of a server-side page generator of a publishing platform, as part of a local extensible document generator, and as part of an in-browser converter of extracted references. Use cases range from transforming a list of DOIs or Wikidata identifiers into a BibTeX file on the command line, to displaying RIS references on a webpage with added Altmetric badges to generating ”How to cite this” sections on a blog. The accuracy of conversions is currently 27% for properties and 60% for types on average and a typical initialization takes 120 ms in browsers and 1 s with Node.js on the command line. Conclusions Citation.js is a library supporting various formats of bibliographic information in a broad selection of use cases and environments. Given the support for plugins, more formats can be added with relative ease.
APA, Harvard, Vancouver, ISO, and other styles
10

Zou, Qing. "Represent Changes of Knowledge Organization Systems on the Semantic Web." International Journal of Librarianship 3, no. 1 (July 17, 2018): 67. http://dx.doi.org/10.23974/ijol.2018.vol3.1.64.

Full text
Abstract:
Traditional knowledge organization systems (KOS) including thesauri, classification schemes, taxonomies, subject heading systems, name authorities, and other lists of terms and codes have been playing important roles in indexing, information organization, and retrieval. With the advent of the semantic web, a large number of them have been converted into Linked Open Data (LOD) datasets. Since the Simple Knowledge Organization Systems (SKOS) and SKOS eXtension for Labels (SKOS-XL) are languages for representation of knowledge organization systems, they have been applied to knowledge organization systems. In this article, the issues surrounding changes, versioning control, and evolution of KOS are investigated. From KOS services providers and consumers perspectives, this study focuses on representation of changes on the semantic web.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Code versioning"

1

Rolfe, P. Alexander (Philip Alexander) 1979. "Code versioning in a workflow management system." Thesis, Massachusetts Institute of Technology, 2001. http://hdl.handle.net/1721.1/87294.

Full text
Abstract:
Thesis (M.Eng.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, February 2002.
Includes bibliographical references (p. 81-82).
by P. Alexander Rolfe.
M.Eng.
APA, Harvard, Vancouver, ISO, and other styles
2

Saxena, Rahul. "Profile merging and code versioning for automated profile guided optimization systems." Connect to online resource, 2007. http://gateway.proquest.com/openurl?url_ver=Z39.88-2004&rft_val_fmt=info:ofi/fmt:kev:mtx:dissertation&res_dat=xri:pqdiss&rft_dat=xri:pqdiss:1442969.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Ott, Bryce Daniel. "Web Based Resource Management for Multi-Tiered Web Applications." BYU ScholarsArchive, 2007. https://scholarsarchive.byu.edu/etd/1255.

Full text
Abstract:
The currently emerging trend of building more complex web applications to solve increasingly more involved software problems has led to the the need for a more automated and practical means for deploying resources required by these advanced web applications. As web based applications become more complex and involve more developers, greater system redundancy, and a larger number of components, traditional means of resource deployment become painfully inadequate as they fail to scale sufficiently. The purpose of this research is to provide evidence that a more sound and scalable test and deployment process can be employed and that many of the components of this improved process can be automated and/or delegated to various system actors to provide a more usable, reliable, stable, and efficient deployment process. The deployable resources that have been included for their commonality in web based applications are versioned resources (both ASCII based and binary files), database resources, cron files, and scripting commands. In order to achieve an improved test and deployment process and test its effectiveness, a web-based code deployment tool was developed and deployed in a production environment where its effects could be accurately measured. This deployment tool heavily leverages the use of Subversion to provide the management of versioned resources because of its extensive ability to manage the creation and merging of branches.
APA, Harvard, Vancouver, ISO, and other styles
4

Zanini, Davide. "Progettazione di CoVE: studio di tecniche e tecnologie per un editor collaborativo con gestione di versioni per documenti strutturati." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2016. http://amslaurea.unibo.it/11946/.

Full text
Abstract:
In questa dissertazione verrà affrontata la mancanza di uno strumento che permetta la stesura e la gestione delle versioni di documenti strutturati, proponendo il modello CoVE. Tale modello si fonda sull'integrazione di due tecnologie: Operational Transformation e Versioning Management System. La prima si occupa di fornire un sistema collaborativo pensato per la produzione di documenti, la seconda si occupa di gestire le possibili versioni/varianti che un documento può assumere. Una possibile implementazione di tale modello abbatterebbe tempi e costi necessari alla stesura di documenti strutturati.
APA, Harvard, Vancouver, ISO, and other styles
5

Benjes, Michael Stangel Walter. "Stammzellapherese gesunder verwandter Stammzellspender mit dem Zellseparator "Spectra", Firma Cobe : Vergleich der Versionen 4 und 6 /." 2003. http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&doc_number=012969069&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Books on the topic "Code versioning"

1

Santacroce, Ferdinando. Git Essentials: Create, merge, and distribute code with Git, the most powerful and flexible versioning system available, 2nd Edition. Packt Publishing, 2017.

Find full text
APA, Harvard, Vancouver, ISO, and other styles

Book chapters on the topic "Code versioning"

1

Privat, Michael, and Rob Warner. "Versioning and Migrating Data." In Pro Core Data for iOS, 251–81. Berkeley, CA: Apress, 2011. http://dx.doi.org/10.1007/978-1-4302-3356-5_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Privat, Michael, and Robert Warner. "Versioning and Migrating Data." In Pro Core Data for iOS, 253–84. Berkeley, CA: Apress, 2011. http://dx.doi.org/10.1007/978-1-4302-3657-3_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Bendix, Lars, Per Nygaard Larsen, Anders Ingemann Nielsen, and Jesper Lai Søndergaard Petersen. "CoEd — A tool for versioning of hierarchical documents." In System Configuration Management, 174–87. Berlin, Heidelberg: Springer Berlin Heidelberg, 1998. http://dx.doi.org/10.1007/bfb0053888.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

"16 Versioning code and Jupyter notebooks." In Data Science in Chemistry, 80–82. De Gruyter, 2020. http://dx.doi.org/10.1515/9783110629453-016.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Rech, Jörg. "Handling of Software Quality Defects in Agile Software Development." In Software Applications, 242–65. IGI Global, 2009. http://dx.doi.org/10.4018/978-1-60566-060-8.ch020.

Full text
Abstract:
Software quality assurance is concerned with the efficient and effective development of large, reliable, and high-quality software systems. In agile software development and maintenance, refactoring is an important phase for the continuous improvement of a software system by removing quality defects like code smells. As time is a crucial factor in agile development, not all quality defects can be removed in one refactoring phase (especially in one iteration). Documentation of quality defects that are found during automated or manual discovery activities (e.g., pair programming) is necessary to avoid wasting time by rediscovering them in later phases. Unfortunately, the documentation and handling of existing quality defects and refactoring activities is a common problem in software maintenance. To recall the rationales why changes were carried out, information has to be extracted from either proprietary documentations or software versioning systems. In this chapter, we describe a process for the recurring and sustainable discovery, handling, and treatment of quality defects in software systems. An annotation language is presented that is used to store information about quality defects found in source code and that represents the defect and treatment history of a part of a software system. The process and annotation language can not only be used to support quality defect discovery processes, but is also applicable in testing and inspection processes.
APA, Harvard, Vancouver, ISO, and other styles
6

Tiwana, Amrit. "Incremental Cross-Generation Versioning in Decomposable Internet Software Products." In Advances in Computer and Electrical Engineering, 220–42. IGI Global, 2001. http://dx.doi.org/10.4018/978-1-930708-04-4.ch016.

Full text
Abstract:
The most important factor distinguishing firms is the possession of knowledge, and the core differentiating skill is the ability to deploy that knowledge to their competitive advantage (Scott, 1998). Products of the turbulent information industries (Mendelson and Kraemer, 1998), especially those facilitated by the Internet, show the hitherto unseen promise of increasing returns. The flexibility to survive in turbulent technological environments, however, can only be achieved if positive feedback is not suppressed (Hall, 1997). This chapter examines incremental development and maintenance of software products designed to be used, delivered, and maintained through the Internet. Complex software products often go through a process of iterative evolution across several rapidly delivered versions, and the opportunities for knowledge management and application that arise in the midst of their evolution are discussed. We describe how both development and maintenance/upgrading of Internet software must be addressed in ways extending beyond traditional methods used for “traditional” information systems maintenance. Drawing on a diverse theory base, including information economics, emergence theory, and knowledge-based innovation, characteristics of Internet-based software applications are described; linkages between application modularity and decomposability with process knowledge are first explored; feasibility of managing component knowledge and renewing architectural knowledge is discussed; and finally, a conceptual model for managing process knowledge across generations and versions of decomposable applications to support software maintenance and evolution is presented.
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Code versioning"

1

Barbar, Mohamad, Yulei Sui, and Shiping Chen. "Object Versioning for Flow-Sensitive Pointer Analysis." In 2021 IEEE/ACM International Symposium on Code Generation and Optimization (CGO). IEEE, 2021. http://dx.doi.org/10.1109/cgo51591.2021.9370334.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

"SOFTWARE VERSIONING IN THE CLOUD - Towards Automatic Source Code Management." In 6th International Conference on Software and Data Technologies. SciTePress - Science and and Technology Publications, 2011. http://dx.doi.org/10.5220/0003609001600165.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Raemaekers, Steven, Arie van Deursen, and Joost Visser. "Semantic Versioning versus Breaking Changes: A Study of the Maven Repository." In 2014 IEEE 14th International Working Conference on Source Code Analysis and Manipulation (SCAM). IEEE, 2014. http://dx.doi.org/10.1109/scam.2014.30.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

"A Novel Approach to Versioning and Merging Model and Code Uniformly." In International Conference on Model-Driven Engineering and Software Development. SCITEPRESS - Science and and Technology Publications, 2014. http://dx.doi.org/10.5220/0004699802540263.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

De Lucia, Andrea, Fausto Fasano, Rocco Oliveto, and Domenico Santonicola. "Improving context awareness in subversion through fine-grained versioning of Java code." In Ninth international workshop. New York, New York, USA: ACM Press, 2007. http://dx.doi.org/10.1145/1294948.1294975.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Zangerl, Peter, Peter Thoman, and Thomas Fahringer. "Characterizing Performance and Cache Impacts of Code Multi-versioning on Multicore Architectures." In 2017 25th Euromicro International Conference on Parallel, Distributed and Network-based Processing (PDP). IEEE, 2017. http://dx.doi.org/10.1109/pdp.2017.77.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Opdebeeck, Ruben, Ahmed Zerouali, Camilo Velazquez-Rodriguez, and Coen De Roover. "Does Infrastructure as Code Adhere to Semantic Versioning? An Analysis of Ansible Role Evolution." In 2020 IEEE 20th International Working Conference on Source Code Analysis and Manipulation (SCAM). IEEE, 2020. http://dx.doi.org/10.1109/scam51674.2020.00032.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Oliveira, Joao C. B., Ricardo A. Rios, Eduardo S. de Almeida, Claudio N. Sant'Anna, and Tatiane Nogueira Rios. "Fuzzy Software Analyzer (FSA): A New Approach for Interpreting Source Code Versioning Repositories." In 2021 IEEE International Conference on Fuzzy Systems (FUZZ-IEEE). IEEE, 2021. http://dx.doi.org/10.1109/fuzz45933.2021.9494513.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Rivero, Luis, Italo Silva, Pedro Cutrim, Anselmo Paiva, Milton Oliveira, Erika Alves, Geraldo Braz Junior, and Domingos Dias. "Implementando o Gitflow para Gerencia de Configuração em um Projeto de Desenvolvimento de Software Ágil: Um Relato de Experiência." In Computer on the Beach. São José: Universidade do Vale do Itajaí, 2021. http://dx.doi.org/10.14210/cotb.v12.p178-185.

Full text
Abstract:
In software engineering, Software Configuration Management is a set of support activities that allows for the orderly absorption of changes inherent to software development. For that, organization models for code versioning like Gitflow have been proposed. In Gitflow, two fixed branches (master and develop) are used to store the project history and be the starting point for changes. Despite the popularity of Gitflow for being considered a simple workflow, there are few: (a) reports of its use in practice and / or (b) documentation on how to deploy it in a real environment. This paper presents the process of adapting Gitflow and creating rules for its application in a real software development project. This adaptation took into account the opinions of managers and developers of a team of approximately 30 people within an agile Scrum life cycle. As a result, definitions and documents were generated to keep track of development, in addition to defining the necessary steps for its application considering the development process adopted by the team.
APA, Harvard, Vancouver, ISO, and other styles
10

Herrmannsdoerfer, Markus. "Operation-based versioning of metamodels with COPE." In 2009 ICSE Workshop on Comparison and Versioning of Software Models (CVSM). IEEE, 2009. http://dx.doi.org/10.1109/cvsm.2009.5071722.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Code versioning"

1

Goodson, Garth R., Jay J. Wylie, Gregory R. Ganger, and Micahel K. Reiter. Efficient Consistency for Erasure-Coded Data via Versioning Servers. Fort Belvoir, VA: Defense Technical Information Center, March 2003. http://dx.doi.org/10.21236/ada461126.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Code versioning' for particular source types:
Journal articles
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography