Relevant bibliographies by topics / Source code management systems

Academic literature on the topic 'Source code management systems'

Author: Grafiati
Published: 10 December 2022
Last updated: 28 January 2023

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

Select a source type:

Contents

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Source code management systems.'

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 "Source code management systems"

1

Yesin, Vitalii, Mikolaj Karpinski, Maryna Yesina, Vladyslav Vilihura, and Kornel Warwas. "Hiding the Source Code of Stored Database Programs." Information 11, no. 12 (December 9, 2020): 576. http://dx.doi.org/10.3390/info11120576.

Full text
Abstract:
The objective of the article is to reveal an approach to hiding the code of stored programs stored in the database. The essence of this approach is the complex use of the method of random permutation of code symbols related to a specific stored program, located in several rows of some attribute of the database system table, as well as the substitution method. Moreover, with the possible substitute of each character obtained after the permutation with another one randomly selected from the Unicode standard, a legitimate user with the appropriate privileges gets access to the source code of the stored program due to the ability to quickly perform the inverse to masking transformation and overwrite the program code into the database. All other users and attackers without knowledge of certain information can only read the codes of stored programs masked with format preserving. The proposed solution is more efficient than the existing methods of hiding the code of stored programs provided by the developers of some modern database management systems (DBMS), since an attacker will need much greater computational and time consumption to disclose the source code of stored programs.
APA, Harvard, Vancouver, ISO, and other styles
2

Gothard, A. "Back to the source [automatic code generation]." Information Professional 2, no. 4 (August 1, 2005): 38–42. http://dx.doi.org/10.1049/inp:20050407.

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

Althar, Raghavendra Rao, Abdulrahman Alahmadi, Debabrata Samanta, Mohammad Zubair Khan, and Ahmed H. Alahmadi. "Mathematical foundations based statistical modeling of software source code for software system evolution." Mathematical Biosciences and Engineering 19, no. 4 (2022): 3701–19. http://dx.doi.org/10.3934/mbe.2022170.

Full text
Abstract:
<abstract><p>Source code is the heart of the software systems; it holds a wealth of knowledge that can be tapped for intelligent software systems and leverage the possibilities of reuse of the software. In this work, exploration revolves around making use of the pattern hidden in various software development processes and artifacts. This module is part of the smart requirements management system that is intended to be built. This system will have multiple modules to make the software requirements management phase more secure from vulnerabilities. Some of the critical challenges bothering the software development community are discussed. The background of Machine Learning approaches and their application in software development practices are explored. Some of the work done around modeling the source code and approaches used for vulnerabilities understanding in software systems are reviewed. Program representation is explored to understand some of the principles that would help in understanding the subject well. Further deeper dive into source code modeling possibilities are explored. Machine learning best practices are explored inline with the software source code modeling.</p></abstract>
APA, Harvard, Vancouver, ISO, and other styles
4

Lawal Abba, Hadiza, Abubakar Roko, Aminu B. Muhammad, Abdulgafar Usman, and Abba Almu. "Enhanced Semantic Similarity Detection of Program Code Using Siamese Neural Network." International Journal of Advanced Networking and Applications 14, no. 02 (2022): 5353–60. http://dx.doi.org/10.35444/ijana.2022.14205.

Full text
Abstract:
Even though there are various source code plagiarism detection approaches, most of them are only concerned with lexical similarities attack with an assumption that plagiarism is only conducted by students who are not proficient in programming. However, plagiarism is often conducted not only due to student incapability but also because of bad time management. Thus, semantic similarity attacks should be detected and evaluated. This research proposes a source code semantic similarity detection approach that can detect most source code similarities by representing the source code into an Abstract Syntax Tree (AST) and evaluating similarity using a Siamese neural network. Since AST is a language-dependent feature, the SOCO dataset is selected which consists of C++ program codes. Based on the evaluation, it can be concluded that our approach is more effective than most of the existing systems for detecting source code plagiarism. The proposed strategy was implemented and an experimental study based on the AI-SOCO dataset revealed that the proposed similarity measure achieved better performance for the recommendation system in terms of precision, recall, and f1 score by 15%, 10%, and 22% respectively in the 100,000 datasets. In the future, it is suggested that the system can be improved by detecting inter-language source code similarity.
APA, Harvard, Vancouver, ISO, and other styles
5

Ganesh, Sundarakrishnan, Francis Palma, and Tobias Olsson. "Are Source Code Metrics “Good Enough” in Predicting Security Vulnerabilities?" Data 7, no. 9 (September 7, 2022): 127. http://dx.doi.org/10.3390/data7090127.

Full text
Abstract:
Modern systems produce and handle a large volume of sensitive enterprise data. Therefore, security vulnerabilities in the software systems must be identified and resolved early to prevent security breaches and failures. Predicting security vulnerabilities is an alternative to identifying them as developers write code. In this study, we studied the ability of several machine learning algorithms to predict security vulnerabilities. We created two datasets containing security vulnerability information from two open-source systems: (1) Apache Tomcat (versions 4.x and five 2.5.x minor versions). We also computed source code metrics for these versions of both systems. We examined four classifiers, including Naive Bayes, Decision Tree, XGBoost Classifier, and Logistic Regression, to show their ability to predict security vulnerabilities. Moreover, an ensemble learner was introduced using a stacking classifier to see whether the prediction performance could be improved. We performed cross-version and cross-project predictions to assess the effectiveness of the best-performing model. Our results showed that the XGBoost classifier performed best compared to other learners, i.e., with an average accuracy of 97% in both datasets. The stacking classifier performed with an average accuracy of 92% in Struts and 71% in Tomcat. Our best-performing model—XGBoost—could predict with an average accuracy of 87% in Tomcat and 99% in Struts in a cross-version setup.
APA, Harvard, Vancouver, ISO, and other styles
6

Kanellopoulos, Y., C. Makris, and C. Tjortjis. "An improved methodology on information distillation by mining program source code." Data & Knowledge Engineering 61, no. 2 (May 2007): 359–83. http://dx.doi.org/10.1016/j.datak.2006.06.002.

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

Naga Malleswari, D., and Dr K.Subrahmanyam. "SIS Framework for Risk Assessment Through Quantitative Analysis." International Journal of Engineering & Technology 7, no. 2.32 (May 31, 2018): 367. http://dx.doi.org/10.14419/ijet.v7i2.32.15715.

Full text
Abstract:
Now a days, risk management plays very important role in Information systems, currently there are various risk assessment techniques. When system is analysing the source code, automatically some disputes may arise which depends on various reasons. These disputes may arise some of the risks in information system which may leads to loss of some data. To avoid that, in this paper we are implementing a framework for source code analysis which is used for brief assessment of risk, which includes guidance to risk minimization. In this framework source based risk assessment is done through the source code analysis. In order to assess risk that arose from the source code, first we need to calculate complexity of a source code in Information System. Finally the complexity which is the result of this framework will indicates the risk intensity of the source code.
APA, Harvard, Vancouver, ISO, and other styles
8

Alawneh, Ali, Iyad M. Alazzam, and Khadijah Shatnawi. "Locating Source Code Bugs in Software Information Systems Using Information Retrieval Techniques." Big Data and Cognitive Computing 6, no. 4 (December 13, 2022): 156. http://dx.doi.org/10.3390/bdcc6040156.

Full text
Abstract:
Bug localization is the process through which the buggy source code files are located regarding a certain bug report. Bug localization is an overwhelming and time-consuming process. Automating bug localization is the key to help developers and increase their productivities. Expanding bug reports with more semantic and increasing software understanding using information retrieval and natural language techniques will be the way to locate the buggy source code file, in which the bug report works as a query and source code as search space. This research investigates the effect of segmenting open source files into executable code and comments, as they have a conflicting nature, seeks the effect of synonyms on the accuracy of bug localization, and examines the effect of “part-of-speech” techniques on reducing the manual inspection for appropriate synonyms. This research aims to approve that such methods improve the accuracy of bug localization tasks. The used approach was evaluated on three Java open source software, namely Eclipse 3.1, AspectJ 1.0, and SWT 3.1; we implement our dedicated Java tool to adopt our methodology and conduct several experiments on each software. The experimental results reveal a considerable improvement in recall and precision levels, and the developed methods display an accuracy improvement of 4–10% compared with the state-of-the-art approaches.
APA, Harvard, Vancouver, ISO, and other styles
9

Jadalla, Ameera, and Ashraf Elnagar. "PDE4Java: Plagiarism Detection Engine for Java source code: a clustering approach." International Journal of Business Intelligence and Data Mining 3, no. 2 (2008): 121. http://dx.doi.org/10.1504/ijbidm.2008.020514.

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

WONG, W. ERIC, and JENNY LI. "REDESIGNING LEGACY SYSTEMS INTO THE OBJECT-ORIENTED PARADIGM." International Journal of Software Engineering and Knowledge Engineering 14, no. 03 (June 2004): 255–76. http://dx.doi.org/10.1142/s0218194004001634.

Full text
Abstract:
Object-oriented languages support many modern programming concepts such as information hiding, inheritance, polymorphism, and dynamic binding. As a result, software systems implemented in OO languages are in general more reusable and reliable than others. Many legacy software systems, created before OO programming became popular, need to be redesigned and updated to OO programs. The process of abstracting OO designs from the procedural source code has often been done with limited assistance from program structural diagrams. Most reengineering focuses on the functionality of the original program, and the OO redesign often results in a completely new design based on the designers' understanding of the original program. Such an approach is not sufficient because it may take a significant amount of time and effort for designers to comprehend the original program. This paper presents a computer-aided semi-automatic method that abstracts OO designs from the original procedural source code. More specifically, it is a method for OO redesign based on program structural diagrams, visualization, and execution slices. We conducted a case study by applying this method to an inventory management software system. Results indicate that our method can effectively and efficiently abstract an appropriate OO design out of the original C code. In addition, some of the code from the original system can be automatically identified and reused in the new OO system.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Source code management systems"

1

Hopfner, Marbod. "Source Code Analysis, Management, and Visualization for PROLOG." Doctoral thesis, kostenfrei, 2008. http://www.opus-bayern.de/uni-wuerzburg/volltexte/2009/3630/.

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

Bexell, Andreas. "Software Source Code Readability : A Mapping Study." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-20164.

Full text
Abstract:
Background: Building software systems is an iterative and collaborative project, requiring developers not only to write code, but to maintain, expand, fix and enhance code already written. In order to do so, reading code is a central activity, and therefore it is important that code is written in a manner that makes it readable. Objectives: To map the state-of-the-art of software source code readability and find the definitions and methods to measure it, and provide an overview of the kinds of factors considered to impact software source code readability, and to compare this to practitioners' experiences of software source code readability. Methods: A systematic literature review of 76 studies in 72 papers from the last 40 years, explicitly concerning software source code readability, is compared with the results of five interviews with practitioners, of which three are case studies of commits explicitly targeting readability. Results: While individual factors' contribution towards readability is studied with some success, more general modelling studies often suffer from methodological problems, making them difficult to apply in practice or in studies of the correlation between software source code readability and other metrics. Conclusions: Key elements of the state-of-the-art have been implemented in practice, however, readability models are not used by the practitioners in this study. Several factors mentioned by practitioners are not considered by the studies included, and further qualitative study of software development practitioners may be needed.
APA, Harvard, Vancouver, ISO, and other styles
3

Carlsson, Emil. "Software Developers Use of Source Code Summarization Comments : A qualitative study of software developers practices to understand third party source code libraries." Thesis, Örebro universitet, Handelshögskolan vid Örebro Universitet, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:oru:diva-46066.

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

Mendes, Rodrigo Cavalcante. "Search and retrieval of source code using the faceted approach." Universidade Federal de Pernambuco, 2008. https://repositorio.ufpe.br/handle/123456789/2097.

Full text
Abstract:
Made available in DSpace on 2014-06-12T15:54:33Z (GMT). No. of bitstreams: 2 arquivo1977_1.pdf: 1819935 bytes, checksum: 4162d549c75996e549bcc53383212659 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2008
Software Reuse has been considered a key concept to increase the quality and productivity of the software development by the reuse of existing artifacts, avoiding build new ones from scratch. However, In order to obtain effective benefits from the software reuse is necessary a set of complementary resources such as: education, active management support and the introduction of appropriate process and tools. In fact, resources that provide mechanism to ease the access of reusable components, such as search and retrieval tools, appear as potential instruments in favor of reuse programs adoption in the organizations. One of the challenges of the search and retrieval tools is how to make that existing components returned have a significant relevance. In this sense, the use of the faceted approach rises as a suitable alternative. This approach proposes the creation of a vocabulary supported by attributes, dividing the components into group of classes based on pre-defined keywords, increasing the level of precision and providing a more flexible classification. Thus, this work presents an extension of search and retrieval tool of reusable components, source code in particular, using the faceted classification approach. In addition, also was developed an auxiliary tool to aid the Domain expert to perform his activities using this approach. Finally, an experimental study evaluates the proposed solution
APA, Harvard, Vancouver, ISO, and other styles
5

Ekmefjord, Morgan. "Evaluation of the Perforce Source Code Management Tool used in Agile Software Development." Thesis, Uppsala University, Department of Information Technology, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-98334.

Full text
Abstract:

Focus in this report is how the Perforce source code management tools can be used in the Extreme Programming methodology and how the different features of Perforce work with the challenges of managing source code while working in an agile way with extreme programming. The study shows how the extreme programming methodology users can use Perforce for their daily operation for paradigms such as continuous integration and 10 minutes build. The bridging between agile methods such as extreme programming and source code management tools are not very clear and in this report some aspects of uniting the two is explained.

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

Kiendys, Petrus, and Shadi Al-Zara. "Minimumkrav för ett CI-system." Thesis, Malmö högskola, Fakulteten för teknik och samhälle (TS), 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:mau:diva-20216.

Full text
Abstract:
När en grupp utvecklare jobbar med samma kodbas kan konflikter uppstå med avseende på implementationen av moduler eller delsystem som varje utvecklare individuellt jobbar på. Dessa konflikter måste snabbt lösas för att projektet ska fortskrida och inte stagnera. Utvecklare som sällan kommunicerar framför ofta okompatibla moduler eller delsystem som kan vara svåra eller omöjliga att integrera i kodbasen, detta leder ofta till s.k. “integration hell” där det kan ta väldigt lång tid att anpassa ny kod till en befintlig kodbas.En strategi som man kan ta till är “continuous integration”, ett arbetssätt som erbjuder en rad fördelar när man jobbar i grupp på en gemensam kodbas. Continuous integration är möjligt att tillämpa utan verktyg eftersom detta är ett arbetssätt. Däremot kan processen stödjas av ett s.k. “CI-system” som är något av en teknisk implementation eller påtagligt införlivande och stöd för arbetsmetoden “continuous integration”.Denna rapport syftar till att ge en inblick i vad ett CI-system är och vad den principiellt består av. Vi undersöker vad ett CI-system absolut måste bestå av genom en litteraturundersökning och en marknadsundersökning. Vi ställer upp dessa beståndsdelar som “funktionella” och “icke-funktionella” krav för ett typiskt CI-system. Vi kan på så vis kvantifiera och kategorisera olika komponenter och funktionaliteter som bör innefattas i ett typiskt CI-system. I denna rapport finns även ett bihang som visar hur man kommer igång med att bygga en egen CI-server mha. CI-systemmjukvaran “TeamCity”.Slutsatsen av vår rapport är att CI-system är ett viktigt redskap som kan underlätta mjukvaruutveckling. Med hjälp av CI-system kan man stödja utvecklingsprocessen genom att bl.a. förhindra integrationsproblem, automatisera vissa delar av arbetsprocessen (kompilering av källkod, testning av mjukvara, notifikation om stabilitet av kodbas och distribution av färdig mjukvara) samt snabbt hitta och lösa integrationsfel.
When a group of developers work on the same code base, conflicts may arise regarding the implementation of modules or subsystems that developers individually work on. These conflicts have to be resolved quickly in order for the project to advance at a steady pace. Developers who do not communicate changes or other necessary deviations may find themselves in a situation where new or modified modules or subsystems are impossible or very difficult to integrate into the mainline code-base. This often leads to so called “integration hell” where it could take huge amounts of time to adapt new code into the current state of the code-base. One strategy, which can be deployed to counteract this trend is called “continuous integration”. This practice offers a wide range of advantages when a group of developers collaborates on writing clean and stable code. Continuous integration can be put into practice without the use of any tools as it is a “way to do things” rather than an actual tool. With that said, it is possible to support the practice with a tangible tool called a CI-system.This study aims to give insight into the makings of a CI-system and what it fundamentally consists of and has to be able to do. A study of contemporary research reports regarding the subject and a survey was performed in order to substantiate claims and conclusions. Core characteristics of CI-systems are grouped into “functional requirements” and “non-functional requirements (quality attributes)”. By doing this, it is possible to quantify and categorize various core components and functionalities of a typical CI-system. This study also contains an attachment which provides instructions of how to get started with implementing your own CI-server using the CI-system software ”TeamCity”. The conclusion of this study is that a CI-system is an important tool that enables a more efficient software development process. By making use of CI-systems developers can refine the development process by preventing integration problems, automating some parts of the work process (build, test, feedback, deployment) and quickly finding and solving integration issues.
APA, Harvard, Vancouver, ISO, and other styles
7

Kim, John Yongchae. "Resource management techniques for CDMA cellular systems." Diss., Georgia Institute of Technology, 2001. http://hdl.handle.net/1853/13906.

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

Kalkan, Olcay Altınkaya Mustafa Aziz. "Independent component analysis applications in CDMA systems/." [s.l.]: [s.n.], 2004. http://library.iyte.edu.tr/tezler/master/elektronikvehaberlesme/T000473.rar.

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

Hortlund, Andreas. "Security smells in open-source infrastructure as code scripts : A replication study." Thesis, Karlstads universitet, Handelshögskolan (from 2013), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:kau:diva-84422.

Full text
Abstract:
With the rising number of servers used in productions, virtualization technology engineers needed a new a tool to help them manage the rising configuration workload. Infrastructure as code(IaC), a term that consists mainly of techniques and tools to define wanted configuration states of servers in machine readable code files, which aims at solving the high workload induced by the configuration of several servers. With new tools, new challenges rise regarding the security of creating the infrastructure as code scripts that will take over the processing load. This study is about finding out how open-source developers perform when creating IaC scripts in regard to how many security smells they insert into their scripts in comparison to previous studies and such how developers can mitigate these risks. Security smells are code patterns that show vulnerability and can lead to exploitation. Using data gathered from GitHub with a web scraper tool created for this study, the author analyzed 400 repositories from Ansible and Puppet with a second tool created, tested and validated from previous study. The Security Linter for Infrastructure as Code uses static code analysis on these repositories and tested these against a certain ruleset for weaknesses in code such as default admin and hard-coded password among others. The present study used both qualitative and quantitative methods to analyze the data. The results show that developers that actively participated in developing these repositories with a creation date of at latest 2019-01-01 produced less security smells than Rahman et al (2019b, 2020c) with a data source ranging to November 2018. While Ansible produced 9,2 compared to 28,8 security smells per thousand lines of code and Puppet 13,6 compared to 31,1. Main limitation of the study come mainly in looking only at the most popular and used tools of the time of writing, being Ansible and Puppet. Further mitigation on results from both studies can be achieved through training and education. As well as the use of tools such as SonarQube for static code analysis against custom rulesets before the scripts are being pushed to public repositories.
APA, Harvard, Vancouver, ISO, and other styles
10

Sama, Sanjana. "An Empirical Study Investigating Source Code Summarization Using Multiple Sources of Information." Youngstown State University / OhioLINK, 2018. http://rave.ohiolink.edu/etdc/view?acc_num=ysu1527673352984124.

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

Books on the topic "Source code management systems"

1

Sim, Susan Elliott. Finding Source Code on the Web for Remix and Reuse. New York, NY: Springer New York, 2013.

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

Frederick, Jolitz William, ed. Source code secrets: The basic kernel. San Jose, Calif: Peer-to-Peer Communications, 1996.

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

PGP source code and internals. Cambridge, Mass: MIT Press, 1995.

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

Lions, John. Lions' Commentary on UNIX 6th edition with source code. San Jose, Calif: Peer-to-Peer Communications, 1996.

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

Free and open source enterprise planning: Systems and strategies. Hershey, PA: Business Science Reference, 2012.

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

Thought leaders: The source code of exceptional managers and entrepreneurs. New Delhi: Tata McGraw Hill Pub. Co., 2001.

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

Thought leaders: The source code of exceptional managers and entrepreneurs. New Delhi: Tata McGraw Hill Publishing Company., 2008.

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

Andreu, Rafael. Information systems strategic planning: A source of competitive advantage. Oxford: Blackwell NCC, 1992.

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

Open source software: Implementation and management. Amsterdam: Elsevier Digital Press, 2004.

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

Eltschinger, Cyrill. Source code China: The new global hub of IT outsourcing. Hoboken, N.J: John Wiley & Sons, Inc., 2007.

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

Book chapters on the topic "Source code management systems"

1

Marwedel, Peter. "Optimization." In Embedded Systems, 349–79. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-60910-8_7.

Full text
Abstract:
AbstractEmbedded systems have to be efficient (at least) with respect to the objectives considered in this book. In particular, this applies to resource-constrained mobile systems, including sensor networks embedded in the Internet of Things. In order to achieve this goal, many optimizations have been developed. Only a small subset of those can be mentioned in this book. In this chapter, we will present a selected set of such optimizations. This chapter is structured as follows: first of all, we will present some high-level optimization techniques, which could precede compilation of source code or could be integrated into it. We will then describe concurrency management for tasks. Section 7.3 comprises advanced compilation techniques. The final Sect. 7.4 introduces power and thermal management techniques.
APA, Harvard, Vancouver, ISO, and other styles
2

Lepiller, Julien, Ruzica Piskac, Martin Schäf, and Mark Santolucito. "Analyzing Infrastructure as Code to Prevent Intra-update Sniping Vulnerabilities." In Tools and Algorithms for the Construction and Analysis of Systems, 105–23. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-72013-1_6.

Full text
Abstract:
AbstractInfrastructure as Code is a new approach to computing infrastructure management that allows users to leverage tools such as version control, automatic deployments, and program analysis for infrastructure configurations. This approach allows for faster and more homogeneous configuration of a complete infrastructure. Infrastructure as Code languages, such as CloudFormation or TerraForm, use a declarative model so that users only need to describe the desired state of the infrastructure. However, in practice, these languages are not processed atomically. During an upgrade, the infrastructure goes through a series of intermediate states. We identify a security vulnerability that occurs during an upgrade even when the initial and final states of the infrastructure are secure, and we show that those vulnerability are possible in Amazon’s AWS and Google Cloud. We call such attacks intra-update sniping vulnerabilities. In order to mitigate this shortcoming, we present a technique that detects such vulnerabilities and pinpoints the root causes of insecure deployment migrations. We implement this technique in a tool, Häyhä, that uses dataflow graph analysis. We evaluate our tool on a set of open-source CloudFormation templates and find that it is scalable and could be used as part of a deployment workflow.
APA, Harvard, Vancouver, ISO, and other styles
3

Piper, Ian. "Source-Code Management with Subversion." In Learn Xcode Tools for Mac OS X and iPhone Development, 187–206. Berkeley, CA: Apress, 2009. http://dx.doi.org/10.1007/978-1-4302-7220-5_10.

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

Mens, Kim, and Angela Lozano. "Source Code-Based Recommendation Systems." In Recommendation Systems in Software Engineering, 93–130. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-45135-5_5.

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

Yadav, Krishna, Rutuja Kamble, Sumit Kale, Yash Pazare, and Pallavi Ahire. "Source Code Obfuscation: Novel Technique and Implementation." In ICT Systems and Sustainability, 197–204. Singapore: Springer Singapore, 2022. http://dx.doi.org/10.1007/978-981-16-5987-4_21.

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

Silva, Clóvis Daniel Souza, Leonardo Ferreira da Costa, Leonardo Sampaio Rocha, and Gerardo Valdísio Rodrigues Viana. "KNN Applied to PDG for Source Code Similarity Classification." In Intelligent Systems, 471–82. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-61380-8_32.

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

Gupta, Aakanshi, Bharti Suri, and Bimlesh Wadhwa. "A Detection Tool for Code Bad Smells in Java Source Code." In Advances in Intelligent Systems and Computing, 479–88. Singapore: Springer Singapore, 2020. http://dx.doi.org/10.1007/978-981-15-1275-9_39.

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

Jain, Amay Dilip, Ankur Gupta, Diksha Choudhary, Nayan, and Ashish Tiwari. "A Comprehensive Source Code Plagiarism Detection Software." In Advances in Intelligent Systems and Computing, 343–50. Singapore: Springer Nature Singapore, 2022. http://dx.doi.org/10.1007/978-981-19-0475-2_30.

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

Lokuciejewski, Paul, and Peter Marwedel. "WCET-Aware Source Code Level Optimizations." In Worst-Case Execution Time Aware Compilation Techniques for Real-Time Systems, 61–129. Dordrecht: Springer Netherlands, 2011. http://dx.doi.org/10.1007/978-90-481-9929-7_4.

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

Patel, Smit, and Roopak Sinha. "Combining Holistic Source Code Representation with Siamese Neural Networks for Detecting Code Clones." In Testing Software and Systems, 148–59. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-031-04673-5_12.

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

Conference papers on the topic "Source code management systems"

1

Majumdar, Rana, Rachna Jain, Shivam Barthwal, and Chetna Choudhary. "Source code management using version control system." In 2017 6th International Conference on Reliability, Infocom Technologies and Optimization (Trends and Future Directions) (ICRITO). IEEE, 2017. http://dx.doi.org/10.1109/icrito.2017.8342438.

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

Ilk, Noyan, J. Leon Zhao, and Paul Hofmann. "On Reuse of Source Code Components in Modernizing Enterprise Systems." In 2008 IEEE Symposium on Advanced Management of Information for Globalized Enterprises, AMIGE. IEEE, 2008. http://dx.doi.org/10.1109/amige.2008.ecp.65.

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

Ajmal, Omer, M. M. Saad Missen, Tazeen Hashmat, M. Moosa, and Tenvir Ali. "EPlag: A two layer source code plagiarism detection system." In 2013 Eighth International Conference on Digital Information Management (ICDIM). IEEE, 2013. http://dx.doi.org/10.1109/icdim.2013.6693984.

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

Jeong-Hoon Ji, Su-Hyun Park, Gyun Woo, and Hwan-Gue Cho. "Source code management system for E-learning based programming education." In 2007 2nd International Conference on Digital Information Management. IEEE, 2007. http://dx.doi.org/10.1109/icdim.2007.4444250.

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

John, Gordon H., Nigel Reeves, Amy C. Nisbet, Clive R. Williams, and Andrew Garnet. "UK Surplus Source Disposal Programme." In ASME 2009 12th International Conference on Environmental Remediation and Radioactive Waste Management. ASMEDC, 2009. http://dx.doi.org/10.1115/icem2009-16097.

Full text
Abstract:
The UK Surplus Source Disposal Programme (SSDP), managed by the Environment Agency, was designed to remove redundant radioactive sources from the public domain. The UK Government Department for Environment, Food and Rural Affairs (Defra) was concerned that disused sources were being retained by hospitals, universities and businesses, posing a risk to public health and the environment. AMEC provided a range of technical and administrative services to support the SSDP. A questionnaire was issued to registered source holders and the submitted returns compiled to assess the scale of the project. A member of AMEC staff was seconded to the Environment Agency to provide technical support and liaise directly with source holders during funding applications, which would cover disposal costs. Funding for disposal of different sources was partially based on a sliding scale of risk as determined by the IAEA hazard categorisation system. This funding was also sector dependent. The SSDP was subsequently expanded to include the disposal of luminised aircraft instruments from aviation museums across the UK. These museums often hold significant radiological inventories, with many items being unused and in a poor state of repair. These instruments were fully characterised on site by assessing surface dose rate, dimensions, source integrity and potential contamination issues. Calculations using the Microshield computer code allowed gamma radiation measurements to be converted into total activity estimates for each source. More than 11,000 sources were disposed of under the programme from across the medical, industrial, museum and academic sectors. The total activity disposed of was more than 8.5E+14 Bq, and the project was delivered under budget.
APA, Harvard, Vancouver, ISO, and other styles
6

Cho, Dong-Keun, GwangMin Sun, JongWon Choi, Donghyeun Hwang, Hak-Soo Kim, and Tae-Won Hwang. "Verification of Source Term Analysis System for Decommissioning Wastes From a CANDU Reactor." In ASME 2010 13th International Conference on Environmental Remediation and Radioactive Waste Management. ASMEDC, 2010. http://dx.doi.org/10.1115/icem2010-40202.

Full text
Abstract:
There are now twenty commercial nuclear power reactors operating as of May 2010 in South Korea. As nuclear capacity becomes higher and installations age, the Korean government and industry have launched R&D to estimate appropriate decommissioning costs of power reactors. In this paper, MCNP/ORIGEN2 code system which is being developed as a source term evaluation tool was verified by comparing the estimated nuclide inventory from MCNP/ORIGEN2 simulation with the measured nuclide inventory from chemical assay in an irradiated pressure tube discharged from Wolsong Unit 1 in 1994. Equilibrium core model of Wolsoung unit 1 was used as a neutron source to activate in-core and ex-core structural components. As a result, the estimated values from the analysis system agreed with measured data within 20% difference. Therefore, it can be concluded that MCNP/ORIGEN system could be a reliable tool to estimate source terms of decommissioning wastes from CANDU reactor, although this system assumes constant flux irradiation and snapshot equilibrium core model as a reference core.
APA, Harvard, Vancouver, ISO, and other styles
7

Fadhil, Hilal Adnan, S. A. Aljunid, and R. B. Ahmad. "New Code Structures Based on Coherent and Incoherent Sources for Spectral Amplitude Coding-OCDMA Systems." In 2009 International Conference on Information Management and Engineering. IEEE, 2009. http://dx.doi.org/10.1109/icime.2009.156.

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

Herb, Joachim. "A Continuous Integration Platform for the Deterministic Safety Analyses Code System AC2." In 2018 26th International Conference on Nuclear Engineering. American Society of Mechanical Engineers, 2018. http://dx.doi.org/10.1115/icone26-81123.

Full text
Abstract:
At GRS, a continuous integration platform based on the software Jenkins is used to verify and validate the code system AC2 consisting of the codes ATHLET, ATHLET-CD and COCOSYS. It automates different steps of the verification and validation process. If these steps were done manually, they would take up significant resources. Each time new or changed code is sent to the source code management system, the software is built for all supported operating systems and configurations and verifications as well as validation tests are executed. If test builds do not work or the results of verification or validation show deviations from the specified test targets, immediate actions can be taken to resolve any problems. During the last years the continuous integration platform has helped to improve both the quality of the software and productivity. It helps to maintain the robust quality management regime of the development process of AC2.
APA, Harvard, Vancouver, ISO, and other styles
9

Cepraga, D. G., G. Cambi, M. Frisoni, and D. Ene. "Cemented Containers Radiological Data From a Disused Uranium Mine Low-Level Waste Repository: A Calculated-Experiment Cross-Check for Data Verification and Validation." In ASME 2003 9th International Conference on Radioactive Waste Management and Environmental Remediation. ASMEDC, 2003. http://dx.doi.org/10.1115/icem2003-4516.

Full text
Abstract:
Code validation problems involve calculation of experiments and a comparison experiment-calculation. Experimental data and physical properties of these systems are used to determine the range of applicability of the validation. Once a sequence-code of calculations has been validated, it has to be underlined that the comparison experimental-calculated results involving “complex systems” or “complex experimental measures” permits also a bi-lateral cross-check between the calculation scheme and the experimental procedures. The results of the testing and the validation effort related to the collection of information and measured data and the comparison between code results with experimental data coming from a “low-level waste” repository are presented in this paper. The Baita-Bihor repository, sited into former disused uranium mine in Transylvania, has been considered as the source of experimental data. The study was developed through the following steps: a) collection and processing of measured data (radioactivity content and dose rate), from the cemented containers of the Baita-Bihor repository; b) decay gamma source calculation by the ANITA-2000 code package (the input data for the calculations are the measured isotope activities for each container); c) decay gamma transport calculation by the SCALENEA-1 shielding Sn sequence approach (Nitawl-Xsdrnpm-Xsdose modules of the Scale 4.4a code system, using the Vitenea-J library, based on FENDL/E-2 data) to obtain dose rates on the surfaces and at various points outside the containers; d) comparison experimental-calculated dose rates, taking into account also the measurement uncertainties. The new version of the ANITA-2000 activation code package used makes possible to assess the behaviour of irradiated materials independently from the knowledge of the irradiation scenario but using only data on the isotope radioactive material composition. Radioactive waste disposed of at Baita Bihor repository consists of worn reactor parts, resins and filters, packing materials, mop heads, protective clothing, temporary floor coverings and tools, the sources normally generated during the day-to-day operation of research reactors, the remediation-treatment stations and the medicine and biological activities. The low and intermediate wastes are prepared for shipping and disposal in the treatment stations by confining them in a cement matrix inside 220 litre metallic drums. Each container consists of an iron cladding filled by concrete Portland. Radioisotope composition and radioactivity distributions inside the drum are measured. The gamma spectroscopy has been used for. The calibration technique was based on the assumption of a uniform distribution of the source activity in the drum and also of a uniform sample matrix. Dose rate measurements are done continuously, circularly, in the central plan on the surface of the drum and 1 m from the surface, in the air. A “stuffing factor” model has been adopted to simulate, for the calculation, the spatial distribution of the gamma sources in the concrete region. In order to guarantee a complete Quality Assurance for codes and procedures, a simulation of the radioactive containers to evaluate the dose rates was done also by using the Monte Carlo MCNP-4C code. Its calculation results are in a very good agreement with those obtained by the Sn approach (discrepancies are around 2%, using the spherical approximation).
APA, Harvard, Vancouver, ISO, and other styles
10

Watanabe, Masato, and Motonori Nakagami. "Evaluation of the Activated Radioactivity of Turbine Equipments in BWR." In ASME 2010 13th International Conference on Environmental Remediation and Radioactive Waste Management. ASMEDC, 2010. http://dx.doi.org/10.1115/icem2010-40294.

Full text
Abstract:
The activated radioactivity of turbine equipments irradiated by neutron originating from 17N in the main stream is evaluated for an introduction of clearance system to boiling-water reactor (BWR) plant. The 17N, main neutron source is generated by 17O(n, p)17N reaction in the core region. The evaluation results clarified that the activated radioactivity of the turbine equipment is extremely small comparing to the clearance level. The feature of the evaluation is as follows. (1) Actual radioactive concentration of the 17N in the main steam in Hamaoka nuclear power station unit 5 (Hamaoka-5) which is an advanced boiling-water reactor (ABWR) was measured with solid-state track detector (SSTD). The 17N concentration is used for the neutron transport calculation as initial neutron sources. (2) The turbine equipments were modeled as two-dimensional geometry for DORT code. (3) Activation cross-sections for major nuclides subject to the clearance evaluation were based on JENDL3.3 on 175 energy group structure (VITAMIN-J). (4) Minor nuclides subject to the clearance evaluation were calculated with ORIGEN-S code.
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Source code management systems"

1

Ehrenshaft, A. R., and L. L. Wright. The SRWCP database management system: Users guide, data definitions, and source code. Office of Scientific and Technical Information (OSTI), February 1989. http://dx.doi.org/10.2172/6240075.

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

Seacord, Robert C., William Dormann, James McCurley, Philip Miller, Robert Stoddard, David Svoboda, and Jefferson Welch. Source Code Analysis Laboratory (SCALe) for Energy Delivery Systems. Fort Belvoir, VA: Defense Technical Information Center, December 2010. http://dx.doi.org/10.21236/ada537058.

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

Harris, James, James Harris, James Harris, James Harris, James Harris, James Harris, James Harris, et al. Build Guide for the Geophysical Monitoring Systems Common Source Code. Office of Scientific and Technical Information (OSTI), August 2019. http://dx.doi.org/10.2172/1763206.

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

Wagner, D., and M. Foster. Integrated Information Support System (IISS). Volume 3. Configuration Management. Part 17. VAX Installation Guide for Source Code0. Fort Belvoir, VA: Defense Technical Information Center, September 1990. http://dx.doi.org/10.21236/ada250121.

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

Laramée, R. M. Source code for GlobalDBSystem, data management interfaces for mineral deposit databases, World Minerals Geoscience Database Project. Natural Resources Canada/ESS/Scientific and Technical Publishing Services, 2015. http://dx.doi.org/10.4095/296953.

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

UNISYS CORP RESTON VA. Software Technology for Adaptable, Reliable Systems (STARS). Reuse Library Framework Source Code Installation Guide. Version 4.1. Fort Belvoir, VA: Defense Technical Information Center, March 1993. http://dx.doi.org/10.21236/ada284935.

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

Khan, Mahreen. Evaluating External Government Audit. Institute of Development Studies, September 2022. http://dx.doi.org/10.19088/k4d.2022.140.

Full text
Abstract:
This rapid literature review of primary and grey sources found substantial evidence of the merits of donor support to Public Financial Management (PFM) initiatives but no specific evidence assessing donor support for external government audit, such as Supreme Audit Institutions (SAIs). PFM reforms are established as being generally beneficial, assist in reducing or preventing corruption, increasing transparency and accountability, as well as improving service delivery quality, although the exact impacts are difficult to measure. Performance auditing has recently attracted more attention than traditional financial or compliance auditing and is seen by many sources to be conducive to improving accountability, although compliance and financial auditing are still viewed as the core of external audit. There is a substantial body of literature on donor-assisted PFM reforms but a paucity of focused study or discussion of donor support to external audit specifically. This evidence gap may be due to the cost of examining the narrow focus required on donor-assisted external audit specifically. This is compounded by the complexity of gathering a sufficiently large database through surveys combined with the lack of access (for individual academics) to official datasets across countries. Furthermore, measuring the impact of SAIs, for example, is difficult due to the variety of regulatory structures that exist, inhibiting comparative cross-country studies, which has resulted in a preference for in-depth analyses. Only multilateral institutions have conducted comprehensive cross-country surveys. However, the evidence does show that strengthened PFM systems and SAIs,1 if they are independent and fully resourced, increase transparency and accountability, helping to combat corruption, when governments are made answerable to their audit findings. The evidence on the effectiveness of SAIs (against corruption) is mixed and not as strong as for PFM reforms in general. The impact of PFM interventions in preventing or reducing corruption increases when reforms are sector-specific and complemented by societal awareness initiatives, citizen participation, and infomediary advocacy. This finding seems applicable to SAIs as the discourse is increasingly on improving comprehension of audit reports and wider dissemination to relevant stakeholders.
APA, Harvard, Vancouver, ISO, and other styles
8

Cruickshank, Garry, and Don Mardle. Wetback Research: Thermodynamic Flow Characteristics of Passive Thermosyphon Energy Transfer from Independent Heat Source to Remote Storage Using Both Direct and Indirect Systems. Unitec ePress, December 2022. http://dx.doi.org/10.34074/rsrp.094.

Full text
Abstract:
The method of heating water by means of a water jacket installed in the firebox of a solid-fuel burner, connected by pipes to a hot-water cylinder (HWC), was once commonplace in New Zealand, but has become less so in recent years. These systems, known as wetbacks, are covered by Building Code Clause G12, but considerable confusion has been caused by conflicting rules specified in the two main compliance documents, G12/AS1 and AS/NZS 3500.4 (hot water). In both compliance documents, wetback systems are defined as ‘uncontrolled heat sources’ with specific rules and limitations that stipulate how they are to be installed, and to keep them safe. However, other than common safety rules, each has entirely different ‘mandatory’ installation rules that affect the efficiency of the systems. They couldn’t both be right, but they could both be wrong. This is further confused by another standard, NZS 4603:1985, being mentioned in G12 as ‘another acceptable solution’ and differing from and contradicting both of the above. This standard is often quoted by manufacturers in their instructions. One driver of this research, from a regulatory view, was to determine which of the two main compliance documents was correct, if either.
APA, Harvard, Vancouver, ISO, and other styles
9

Razdan, Rahul. Unsettled Issues Regarding Autonomous Vehicles and Open-source Software. SAE International, April 2021. http://dx.doi.org/10.4271/epr2021009.

Full text
Abstract:
As automobiles morph from stand-alone mechanical objects to highly connected, autonomous systems with increasing amounts of electronic components. To manage these complex systems, some semblance of in-car decision-making is also being built and networked to a cloud architecture. This cloud can also enable even deeper capabilities within the broader automotive ecosystem. Unsettled Issues Regarding Autonomous Vehicles and Open-source Software introduces the impact of software in advanced automotive applications, the role of open-source communities in accelerating innovation, and the important topic of safety and cybersecurity. As electronic functionality is captured in software and a bigger percentage of that software is open-source code, some critical challenges arise concerning security and validation.
APA, Harvard, Vancouver, ISO, and other styles
10

Maletta, Giovanna, and Mike Lewis. Post-shipment On-site Inspections and Stockpile Management Assistance: Bridging Gaps. Stockholm International Peace Research Institute, August 2022. http://dx.doi.org/10.55163/ulfp1679.

Full text
Abstract:
Post-shipment on-site inspections and international assistance in physical security and stockpile management (PSSM) have different scopes and objectives. On-site inspections allow exporting states to check exported military materiel to ensure that the importer is complying with its commitments, while PSSM assistance aims to improve states’ weapons and ammunition management systems. However, both instruments allow foreign specialists to visit a state’s weapons and ammunition storage facilities and enable information gathering to assess their integrity and identify possible diversion risks. This policy brief highlights that building informal linkages between these instruments, especially with regard to states and actors that conduct inspections and are involved in funding or implementing PSSM assistance, could contribute towards establishing more comprehensive forms of post-shipment cooperation. In addition, applying lessons learned from PSSM assistance in terms of gaining access to states’ facilities, cooperating with the beneficiary importing states, and identifying limitations and opportunities associated with the use of tracking technologies could help to address some of the challenges encountered when conducting on-site inspections. PSSM assistance programmes could also include modules to raise awareness about on-site inspections and be a source of expertise that could assist states when implementing these controls.
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Source code management systems' for particular source types:
Journal articles Dissertations / Theses Books
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