Gotowe bibliografie tematyczne / Code inspection

Gotowa bibliografia na temat „Code inspection”

Autor: Grafiati
Data publikacji: 4 czerwca 2021
Data aktualizacji: 20 lutego 2023

Utwórz poprawne odniesienie w stylach APA, MLA, Chicago, Harvard i wielu innych

Wybierz rodzaj źródła:

Spis treści

Zobacz listy aktualnych artykułów, książek, rozpraw, streszczeń i innych źródeł naukowych na temat „Code inspection”.

Przycisk „Dodaj do bibliografii” jest dostępny obok każdej pracy w bibliografii. Użyj go – a my automatycznie utworzymy odniesienie bibliograficzne do wybranej pracy w stylu cytowania, którego potrzebujesz: APA, MLA, Harvard, Chicago, Vancouver itp.

Możesz również pobrać pełny tekst publikacji naukowej w formacie „.pdf” i przeczytać adnotację do pracy online, jeśli odpowiednie parametry są dostępne w metadanych.

Artykuły w czasopismach na temat "Code inspection"

1

Moles, Michael, Noël Dubé, Simon Labbé i Ed Ginzel. "Review of Ultrasonic Phased Arrays for Pressure Vessel and Pipeline Weld Inspections". Journal of Pressure Vessel Technology 127, nr 3 (29.03.2005): 351–56. http://dx.doi.org/10.1115/1.1991881.

Pełny tekst źródła
Streszczenie:
Major improvements in weld inspection are obtained using Phased Array technology with capability for beam steering, electronic scanning, focusing, and sweeping the ultrasonic beams. Electronic scanning is much faster than raster scanning, and can optimize angles and focusing to maximize defect detection. Pressure vessel (PV) inspections typically use “top, side, end” or “top, side, TOFD” views, though other imaging is possible. Special inspections can be performed, e.g., for specific defects, or increased coverage. Defects can be sized by pulse-echo as per code, by time-of-flight Diffraction or by back diffraction. New PV inspection codes, particularly ASME Code Case 2235, permit the use of advanced ultrasonic inspection techniques. Pipeline girth weld inspections use a unique inspection approach called “zone discrimination,” and have their own series of codes. While similar equipment is used in pipeline as in PV inspections, the pipeline philosophy is to tailor the inspection to the weld profile and predicted lack of fusion defects. Pipeline displays are specifically designed for near real-time data analysis. Both ASME CC 2235 and the pipeline codes permit the use of Fitness-For-Purpose, which reduces construction costs. Overall, phased array systems meet or exceed all PV and pipeline codes.
Style APA, Harvard, Vancouver, ISO itp.
2

DE VREEDE, GERT-JAN, PUSHPA G. KONERI, DOUGLAS L. DEAN, ANN L. FRUHLING i PETER WOLCOTT. "A COLLABORATIVE SOFTWARE CODE INSPECTION: THE DESIGN AND EVALUATION OF A REPEATABLE COLLABORATION PROCESS IN THE FIELD". International Journal of Cooperative Information Systems 15, nr 02 (czerwiec 2006): 205–28. http://dx.doi.org/10.1142/s0218843006001347.

Pełny tekst źródła
Streszczenie:
The use of software products in today's world has increased dramatically making quality an important aspect of software development. There is a continuous need to develop processes to control and increase software quality. Software code inspection is one way to pursue this goal. This paper presents a collaborative code inspection process that was designed during an action research study using Collaboration Engineering principles and techniques. Our inspection process was implemented as a sequence of thinkLets, chunks of facilitation skill, that were subsequently field tested in a traditional paper-based and Group Support System (GSS)-based environment. Four inspections were performed on four different pieces of software code in two different organizations. Results show that regardless of the implementation, the process was found to be successful in uncovering many major, minor, and false-positive defects in inspected pieces of code. Overall observations and feedback suggest that the collaborative inspection process was considered to be productive and satisfactory. GSS inspections were more effective, especially in terms of major defects. GSS inspections were also found to be more efficient. Finally, the GSS inspections outperformed the paper inspections from a practical perspective: logging and managing defects in a GSS was far superior.
Style APA, Harvard, Vancouver, ISO itp.
3

Barnard, J., i A. Price. "Managing code inspection information". IEEE Software 11, nr 2 (marzec 1994): 59–69. http://dx.doi.org/10.1109/52.268958.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Agarwal, Puneet, Kyle Hunt, Shivasubramanian Srinivasan i Jun Zhuang. "Fire Code Inspection and Compliance: A Game-Theoretic Model Between Fire Inspection Agencies and Building Owners". Decision Analysis 17, nr 3 (wrzesień 2020): 208–26. http://dx.doi.org/10.1287/deca.2020.0410.

Pełny tekst źródła
Streszczenie:
Fire-code inspection and compliance are among the highest priorities for fire-inspection agencies to reduce the loss of life and property that can result from fire incidents. Requirements for code compliance and inspection vary throughout towns and states within the United States, and building owners who violate these codes can be penalized via fines and mandated compliance measures. To the best of our knowledge, no previous study has investigated the strategic behavior of players in a fire-code inspection process. This paper fills the gap by presenting the game-theoretic approach to modeling building owners’ behaviors with respect to fire-code compliance and the inspection strategies of fire-inspection agencies. Both a decentralized model (sequential game in which the fire-inspection agency moves first) and a centralized model (simultaneous game controlled by one central decision maker) are developed to identify the best inspection strategies for the agency and the best compliance strategies for the building owner. This study provides prescriptive insights that can enable policymakers to improve fire-code compliance and inspection by identifying the conditions that motivate the players to participate positively in the inspection and compliance processes. Numerical sensitivity analyses of the equilibrium strategies and the expected losses of the players are provided, along with a comparison of the results between the decentralized and centralized models.
Style APA, Harvard, Vancouver, ISO itp.
5

Yan, Ran, i Shuaian Wang. "Ship detention prediction using anomaly detection in port state control: model and explanation". Electronic Research Archive 30, nr 10 (2022): 3679–91. http://dx.doi.org/10.3934/era.2022188.

Pełny tekst źródła
Streszczenie:
<abstract><p>Maritime transport plays an important role in global supply chain. To guarantee maritime safety, protect the marine environment, and enhance the living and working conditions of the seafarers, international codes and conventions are developed and implemented. Port state control (PSC) is a critical maritime policy to ensure that ships comply with the related regulations by selecting and inspecting foreign visiting ships visiting a national port. As the major inspection result, ship detention, which is an intervention action taken by the port state, is dependent on both deficiency/deficiencies (i.e., noncompliance) detected and the judgement of the inspector. This study aims to predict ship detention based on the number of deficiencies identified under each deficiency code and explore how each of them influences the detention decision. We innovatively view ship detention as a type of anomaly, which refers to data points that are few and different from the majority, and develop an isolation forest (iForest) model, which is an unsupervised anomaly detection model, for detention prediction. Then, techniques in explainable artificial intelligence are used to present the contribution of each deficiency code on detention. Numerical experiments using inspection records at the Hong Kong port are conducted to validate model performance and generate policy insights.</p></abstract>
Style APA, Harvard, Vancouver, ISO itp.
6

BESSON, FRÉDÉRIC, THOMAS DE GRENIER DE LATOUR i THOMAS JENSEN. "Interfaces for stack inspection". Journal of Functional Programming 15, nr 2 (marzec 2005): 179–217. http://dx.doi.org/10.1017/s0956796804005465.

Pełny tekst źródła
Streszczenie:
Stack inspection is a mechanism for programming secure applications in the presence of code from various protection domains. Run-time checks of the call stack allow a method to obtain information about the code that (directly or indirectly) invoked it in order to make access control decisions. This mechanism is part of the security architecture of Java and the .NET Common Language Runtime. A central problem with stack inspection is to determine to what extent the local checks inserted into the code are sufficient to guarantee that a global security property is enforced. A further problem is how such verification can be carried out in an incremental fashion. Incremental analysis is important for avoiding re-analysis of library code every time it is used, and permits the library developer to reason about the code without knowing its context of deployment. We propose a technique for inferring interfaces for stack-inspecting libraries in the form of secure calling context for methods. By a secure calling context we mean a pre-condition on the call stack sufficient for guaranteeing that execution of the method will not violate a given global property. The technique is a constraint-based static program analysis implemented via fixed point iteration over an abstract domain of linear temporal logic properties.
Style APA, Harvard, Vancouver, ISO itp.
7

Zhang, Daxin, Jinyue Zhang, Haiming Xiong, Zhiming Cui i Dan Lu. "Taking Advantage of Collective Intelligence and BIM-Based Virtual Reality in Fire Safety Inspection for Commercial and Public Buildings". Applied Sciences 9, nr 23 (24.11.2019): 5068. http://dx.doi.org/10.3390/app9235068.

Pełny tekst źródła
Streszczenie:
Commercial and public buildings are more vulnerable to fires because of their complex use functions, large number of centralized occupants, and the dynamic nature of the use of space. Due to the large number of these types of buildings and the limited availability of manpower, annual fire inspections cannot ensure the continuous compliance of fire codes. A crowdsourcing application, iInspect, is proposed in this paper to harvest collective intelligence in order to conduct mass inspection tasks. This approach is supported by building information modeling (BIM) based virtual reality (VR) and an indoor real-time localization system. Based on the International Fire Code and 27 fire inspection checklists compiled by various local authorities, a generic list of inspection items suitable for iInspect is proposed, along with a reputation-based monetary incentive model. A prototype of iInspect was created for Android mobile phones, and a case study was performed in an office building in Tianjin, China, for verification of this crowdsourcing inspection approach.
Style APA, Harvard, Vancouver, ISO itp.
8

Panko, Raymond R. "Applying Code Inspection to Spreadsheet Testing". Journal of Management Information Systems 16, nr 2 (wrzesień 1999): 159–76. http://dx.doi.org/10.1080/07421222.1999.11518250.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

MACDONALD, F., J. MILLER, A. BROOKS, M. ROPER i M. WOOD. "Applying Inspection to Object-Oriented Code". Software Testing, Verification and Reliability 6, nr 2 (czerwiec 1996): 61–82. http://dx.doi.org/10.1002/(sici)1099-1689(199606)6:2<61::aid-stvr107>3.0.co;2-3.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Zhao, Kun, Shu Tao Zhao, Pei Zhang, Lu Shen i Ce Liu. "2-D Bar Code Technology Based Substation Patrol Robot’s Visual Navigation". Advanced Materials Research 765-767 (wrzesień 2013): 2008–11. http://dx.doi.org/10.4028/www.scientific.net/amr.765-767.2008.

Pełny tekst źródła
Streszczenie:
The development of robot technology and AI makes it possible using outdoor mobile robots inspecting substations instead of manual work [. To solve the technical problems of substation patrolrobots navigation, a general scheme of substation intelligent inspection based on the red guide line is put forward. The 2-D bar code records main inspected equipments information, aiding patrol robot positioning navigation. The system utilizing LabVIEW virtual instrument software with IMAQ Vision module has been successfully written and related to pictures image processing, detecting and reading 2-D bar code. It has practical significance to improve the efficiency and to enhance the portability and flexibility of substation inspection scheme.
Style APA, Harvard, Vancouver, ISO itp.
Więcej źródeł

Rozprawy doktorskie na temat "Code inspection"

1

HONORATO, GUSTAVO DE SA CARVALHO. "NCL INSPECTOR. A NCL CODE INSPECTION TOOL". PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2010. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=16321@1.

Pełny tekst źródła
Streszczenie:
COORDENAÇÃO DE APERFEIÇOAMENTO DO PESSOAL DE ENSINO SUPERIOR
Ginga-NCL e a linguagem NCL foram recomendadas como ambiente de multimídia interativo e linguagem para IPTV, pela União Internacional das Telecomunicações (ITU do Inglês: International Telecommunication Union). Para promover o uso dessas tecnologias, é necessária a criação de ferramentas que ajudem a desenvolver aplicações usando NCL. Atualmente, o suporte de ferramentas para o desenvolvimento em NCL é um pouco limitado. Existem apenas poucos sistemas que auxiliam o desenvolvimento de aplicações NCL. Esses programas não ajudam muito os desenvolvedores em avaliar se o código NCL está bem escrito. Neste trabalho apresentamos o NCL-Inspector, um sistema de críticas para código NCL, que objetiva aumentar a capacidade do desenvolvedor em detectar aplicações NCL suscetíveis a erros. Também foram levantados requisitos desejáveis em sistemas de críticas para código. A forma como esses requisitos foram apresentados possibilita que sejam aplicados em qualquer sistema de crítica de código fonte.
Ginga-NCL and the NCL language were selected as a recommendation as the interactive multimedia environment and language for IPTV by the International Telecommunication Union (ITU). In order to promote the use of these technologies, it is necessary to create tools to help developing applications using NCL. At present, the support provided by tools for NCL development is quite limited. There are only few available systems that can create NCL applications. These softwares do not help developers in assessing the quality of the written NCL code. In this dissertation, we propose NCLInspector, a critique system of the NCL code, which aims at leveraging the developer s skills in detecting error-prone NCL applications. Also, we specified the requirements for critiquing systems for source code inspection.
Style APA, Harvard, Vancouver, ISO itp.
2

Adams, Charles E. "Code inspection for NPSNET". Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 1995. http://handle.dtic.mil/100.2/ADA294263.

Pełny tekst źródła
Streszczenie:
Thesis (M.S. in Computer Science) Naval Postgraduate School, March 1995.
Thesis advisor(s): Timothy J. Shimeall, John S. Falby. "March 1995." Includes bibliographical references. Also available online.
Style APA, Harvard, Vancouver, ISO itp.
3

Stiernborg, Sebastian. "Automated Code Inspection: Investigating Deployment of Continuous Inspection". Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-254959.

Pełny tekst źródła
Streszczenie:
Developing high quality software is a challenging task and there are various techniques and processes proposed to achieve high quality of software. This project examines the process of continuous inspection that automatically reviews source code using modern technology, such as repository management services, continuous integration services and continuous code analysis tools. More specifically, this study examines how the continuous inspection process can be deployed effectively in a software team. The deployment was performed together with an interview-based study in order to get feedback on the integration alternatives of the process. The project resulted in a set of guidelines on how continuous inspection can be effectively integrated and how to establish a process that developers perceive as useful and seamlessly integrating into their workflow. These guidelines help to understand the benefits and drawbacks of integrating the continuous inspection process. Further studies are needed to investigate the integration of the continuous inspection process with different tools and features to fully answer the question how the continuous inspection process can be effectively deployed into software team’s development processes.
Att utveckla högkvalitativ mjukvara är en utmanande uppgift och det finns olika tekniker och processer som kan användas för att uppnå hög kvalitet på mjukvaran. Detta arbete undersöker den moderna processen kontinuerlig kodinspektion som automatiskt granskar koden med hjälp av modern teknologi, till exempel webbaserade versionshanteringssystem, kontinuerliga integrationsservrar och kontinuerliga kodinspektionsverktyg. Mer specifikt undersöker denna studie hur den kontinuerliga inspektionsprocessen kan integreras i ett mjukvaruteams utvecklingsprocesser. Studiens integration genomfördes tillsammans med en intervjubaserad studie för att få feedback kring de olika integrationsalternativen för processen. Projektet resulterade i en uppsättning riktlinjer för hur kontinuerlig inspektion effektivt kan integreras och hur man etablerar en process som utvecklare uppfattar som användbar och som smidigt kan integreras i arbetsflödet. Dessa riktlinjer hjälper till att förstå fördelarna och nackdelarna med att integrera den kontinuerliga inspektionsprocessen. Ytterligare studier behövs för att undersöka integrationen av den kontinuerliga inspektionsprocessen med olika verktyg och funktioner. Detta för att kunna fullt ut svara på hur den kontinuerliga inspektionsprocessen effektivt kan integreras i mjukvaruteams utvecklingsprocesser.
Style APA, Harvard, Vancouver, ISO itp.
4

Moriggl, Irene. "Intelligent Code Inspection using Static Code Features : An approach for Java". Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4149.

Pełny tekst źródła
Streszczenie:
Effective defect detection is still a hot issue when it comes to software quality assurance. Static source code analysis plays thereby an important role, since it offers the possibility for automated defect detection in early stages of the development. As detecting defects can be seen as a classification problem, machine learning is recently investigated to be used for this purpose. This study presents a new model for automated defect detection by means of machine learn- ers based on static Java code features. The model comprises the extraction of necessary features as well as the application of suitable classifiers to them. It is realized by a prototype for the feature extraction and a study on the prototype’s output in order to identify the most suitable classifiers. Finally, the overall approach is evaluated in a using an open source project. The suitability study and the evaluation show, that several classifiers are suitable for the model and that the Rotation Forest, Multilayer Perceptron and the JRip classifier make the approach most effective. They detect defects with an accuracy higher than 96%. Although the approach comprises only a prototype, it shows the potential to become an effective alternative to nowa- days defect detection methods.
Style APA, Harvard, Vancouver, ISO itp.
5

Nguyen, Tang-Hung. "Building inspection with automated code compliance checking". Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1996. http://www.collectionscanada.ca/obj/s4/f2/dsk3/ftp04/MQ44876.pdf.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Dunsmore, Alastair Peter. "Investigating effective inspection of object-oriented code". Thesis, University of Strathclyde, 2002. http://oleg.lib.strath.ac.uk:80/R/?func=dbin-jump-full&object_id=9349.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Trumble, Brandon. "Using Code Inspection, Code Modification, and Machine Learning to prevent SQL Injection". Thesis, Kutztown University of Pennsylvania, 2015. http://pqdtopen.proquest.com/#viewpdf?dispub=1590429.

Pełny tekst źródła
Streszczenie:

Modern day databases store invaluable information about everyone. This information is assumed to be safe, secure, and confidential. However, as technology has become more widespread, more people are able to abuse and exploit this information for personal gain. While the ideal method to combat this issue is the enhanced education of developers, that still leaves a large amount of time where this information is insecure. This thesis outlines two potential solutions to the problem that SQL Injection presents in the context of databases. The first modifies an existing code base to use safe prepared statements rather than unsafe standard queries. The second is a neural network application that sits between the user-facing part of a web application and the application itself. The neural network is designed to analyze data being submitted by a user and detect attempts at SQL injection.

Style APA, Harvard, Vancouver, ISO itp.
8

Melin, Tomas. "Implementation and Evaluation of a Continuous Code Inspection Platform". Thesis, Linköpings universitet, Institutionen för datavetenskap, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-130575.

Pełny tekst źródła
Streszczenie:
Establishing and preserving a high level of software quality is a not a trivial task, although the benefits of succeeding with this task has been proven profitable and advantageous. An approach to mitigate the decreasing quality of a project is to track metrics and certain properties of the project, in order to view the progression of the project’s properties. This approach may be carried out by introducing continuous code inspection with the application of static code analysis. However, as the initial common opinion is that these type of tools produce a too high number of false positives, there is a need to investigate what the actual case is. This is the origin for the investigation and case study performed in this paper. The case study is performed at Ida Infront AB in Linköping, Sweden and involves interviews with developers to determine the performance of the continuous inspection platform SonarQube, in addition to examine the general opinion among developers at the company. The author executes the implementation and configuration of a continuous inspection environment to analyze a partition of the company’s product and determine what rules that are appropriate to apply in the company’s context. The results from the investigation indicate the high quality and accuracy of the tool, in addition to the advantageous functionality of continuously monitoring the code to observe trends and the progression of metrics such as cyclomatic complexity and duplicated code, with the goal of preventing the constant increase of complex and duplicated code. Combining this with features such as false positive suppression, instant analysis feedback in pull requests and the possibility to break the build given specified conditions, suggests that the implemented environment is a way to mitigate software quality difficulties.
建立和保持高水平的软件质量可以带来经济利益等诸多好处，然而这是一项很困难的任务。其中一种防止软件项目质量下降的方法是通过跟踪项目的度量值和某些属性，来查看项目的属性的变化情况。通过引入持续的代码审查和应用静态代码分析方法可以实现这种方法。然而，在人们的印象中，这类工具往往具有较高的误检，因此需要进一步调查实际情况、研究其可行性，这是本文的初始研究目标。本文在瑞典林雪平的Ida Infront AB公司开展了案例研究，调研了该公司开发人员的意见，并通过访问开发人员，确定持续的代码审查平台SonarQube的性能。作者对持续的代码审查环境进行了配置，分析了公司的部分产品，进而确定哪些规则适用于该公司。调查结果表明该工具是高质量并且准确的，还提供了持续监测代码来观察度量值的趋势和进展等先进功能，例如通过监测环路复杂度和重复代码等度量值，来防止复杂度和重复代码的增加。通过组合误检压缩、对pull requests的瞬间分析反馈、以及分解和建立给定的条件等特征，使得所实现的环境成为一种可以降低软件质量保障难度的方式。
Style APA, Harvard, Vancouver, ISO itp.
9

Dybdahl, Andreas. "Source Code Inspection : Measuring the Difference Between Individual and Group Performance". Thesis, Norges teknisk-naturvitenskapelige universitet, Institutt for datateknikk og informasjonsvitenskap, 2013. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-22989.

Pełny tekst źródła
Streszczenie:
The purpose of this study is to examine the relationship between the performances of group efforts versus individual efforts. Study of previous research on software inspection has shown that opinions are divided on whether to have a group work stage in the inspection or not. Initially believed to be beneficial for finding defects in source code it has in more recent years shown to be not as effective as once believed and possibly not worth the cost. This study examines the result of an experiment that conducts a slightly altered version of software inspection where subjects work either solely in groups or solely as individuals where the traditional method has subjects first inspect the code alone and then forming a group to discuss their findings. The hypothesis was that the subjects working in groups in such a fashion will perform better, but it is shown that neither group of subjects outperforms the other at finding defects. These results are consistent with previous research in the field, however it is interesting to note that even without individual preparation groups perform similarly to how they have performed in other studies. Since one of the chief arguments against group work is its high cost eliminating a stage from the review process would make it less costly and thus perhaps more desirable as an inspection method.
Style APA, Harvard, Vancouver, ISO itp.
10

Powell, Daniel, i n/a. "Formal Methods For Verification Based Software Inspection". Griffith University. School of Computing and Information Technology, 2003. http://www4.gu.edu.au:8080/adt-root/public/adt-QGU20030925.154706.

Pełny tekst źródła
Streszczenie:
Useful processes, that are independently repeatable, are utilised in all branches of science and traditional engineering disciplines but seldom in software engineering. This is particularly so with processes used for detection and correction of defects in software systems. Code inspection, as introduced by Michael Fagan at IBM in the mid 1970's is widely recognised as an effective technique for finding defects in software. Despite its reputation, code inspection, as it is currently practiced, is not a strictly repeatable process. This is due to the problems faced by inspectors when they attempt to paraphrase the complicated semantics of a unit of computer code. Verification based software inspection, as advocated by the cleanroom software engineering community, requires that arguments of correctness be formulated with the code and its specification. These arguments rely on the reader being able to extract the semantics from the code. This thesis addresses the requirement for an independently repeatable, scalable and substantially automated method for yielding semantics from computer code in a complete, unambiguous and consistent manner in order to facilitate, and make repeatable, verification based code inspection. Current literature regarding the use of code inspection for verification of software is surveyed. Empirical studies are referenced, comparing inspection to software testing and program proof. Current uses of formal methods in software engineering will be discussed, with particular reference to formal method applications in verification. Forming the basis of the presented method is a systematic, and hence repeatable, approach to the derivation of program semantics. The theories and techniques proposed for deriving semantics from program code extend current algorithmic and heuristic techniques for deriving invariants. Additionally, the techniques introduced yield weaker forms of invariant information which are also useful for verification, defect detection and correction. Methods for using these weaker invariant forms, and tools to support these methods, are introduced. Algorithmic and heuristic techniques for investigating loop progress and termination are also introduced. Some of these techniques have been automated in supporting tools, and hence, the resulting defects can be repeatably identified. Throughout this thesis a strong emphasis is placed on describing implementable algorithms to realise the derivation techniques discussed. A number of these algorithms are implemented in a tool to support the application of the verification methods presented. The techniques and tools presented in this thesis are well suited, but not limited to, supporting rigorous methods of defect detection as well as formal and semi-formal reasoning of correctness. The automation of these techniques in tools to support practical, formal code reading and correctness argument will assist in addressing the needs of trusted component technologies and the general requirement for quality in software.
Style APA, Harvard, Vancouver, ISO itp.
Więcej źródeł

Książki na temat "Code inspection"

1

Orr, Kay. Code inspection instructional validation. [Houston, Tex.?]: Research Institute for Computing and Information Systems, 1992.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

International Fire Service Training Association, red. Fire inspection and code enforcement. Wyd. 7. Stillwater, OK: Fire Protection Publications, Oklahoma State University, 2009.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Diamantes, David. Fire prevention: Inspection and code enforcement. Albany: Delmar Publishers, 1998.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Fire prevention: Inspection and code enforcement. Wyd. 3. Clifton Park, NY: Thomson Delmar Learning, 2007.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Fire prevention: Inspection and code enforcement. Wyd. 2. Albany, NY: Thomson Delmar Learning, 2003.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Taylor, G. L. International code check for home building. Washington, DC: BuilderBooks/National Association of Home Builders, 2002.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Building code compliance for contractors & inspectors. Carlsbad, CA: Craftsman Bk. Co., 2010.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Michael, Casey. Code check building: A field guide to the building codes. [Newtown, CT]: Taunton Press, 2003.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

Malek, Mohammed A. Power boiler design, inspection, and repair: ASME code simplified. New York: McGraw-Hill, 2005.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Building Officials and Code Administrators International. Performing International residential code plumbing inspections: Based on the 2000 International residential code (IRC). Country Club Hills, IL: Building Officials & Code Administrators International, 2001.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
Więcej źródeł

Części książek na temat "Code inspection"

1

Hoffman, Edward S., David P. Gustafson i Albert J. Gouwens. "Field Inspection and Construction". W Structural Design Guide to the ACI Building Code, 432–36. Boston, MA: Springer US, 1998. http://dx.doi.org/10.1007/978-1-4757-6619-6_17.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Christel, Michael G. "Experiences with an interactive video code inspection laboratory". W Software Engineering Education, 395–411. Berlin, Heidelberg: Springer Berlin Heidelberg, 1992. http://dx.doi.org/10.1007/3-540-55963-9_65.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Reinbacher, Thomas, Jörg Brauer, Daniel Schachinger, Andreas Steininger i Stefan Kowalewski. "Automated Test-Trace Inspection for Microcontroller Binary Code". W Runtime Verification, 239–44. Berlin, Heidelberg: Springer Berlin Heidelberg, 2012. http://dx.doi.org/10.1007/978-3-642-29860-8_18.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Macik, Miroslav, Tomas Cerny, Jindrich Basek i Pavel Slavik. "Platform-Aware Rich-Form Generation for Adaptive Systems through Code-Inspection". W Lecture Notes in Computer Science, 768–84. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-39062-3_55.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Mao, Lin-wei, Yao-guang Hu, Jing-qian Wen i Jia-wei Ke. "Design of the Integrity Inspection System for the Resistor Color Code". W Proceedings of the 21st International Conference on Industrial Engineering and Engineering Management 2014, 335–37. Paris: Atlantis Press, 2015. http://dx.doi.org/10.2991/978-94-6239-102-4_69.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Zou, DeYi, Ming Cai, Feng Chen, Pan Deng i Huahua Ning. "The Application of RFID and Two-Dimensional Bar Code in Substation Inspection". W Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering, 197–203. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-16050-4_20.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Park, Seong-Min, Han-Chul Bae, Young-Tae Cha i Hwan-Kuk Kim. "Code Modification and Obfuscation Detection Test Using Malicious Script Distributing Website Inspection Technology". W Advances in Computer Science and Ubiquitous Computing, 74–80. Singapore: Springer Singapore, 2016. http://dx.doi.org/10.1007/978-981-10-3023-9_12.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Koneri, Pushpa G., Gert-Jan de Vreede, Douglas L. Dean, Ann L. Fruhling i Peter Wolcott. "The Design and Field Evaluation of a Repeatable Collaborative Software Code Inspection Process". W Groupware: Design, Implementation, and Use, 325–40. Berlin, Heidelberg: Springer Berlin Heidelberg, 2005. http://dx.doi.org/10.1007/11560296_26.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

O’Brien, James J. "Codes and Standards". W Construction Inspection Handbook, 37–48. Boston, MA: Springer US, 1997. http://dx.doi.org/10.1007/978-1-4615-6017-3_3.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

O’Brien, James J. "Codes and Standards". W Construction Inspection Handbook, 33–44. Boston, MA: Springer US, 1989. http://dx.doi.org/10.1007/978-1-4757-1191-2_3.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.

Streszczenia konferencji na temat "Code inspection"

1

Bollock, Douglas. "NRC Inspection Manual Inspection Procedure 71111 Attachment 21N.02: Design-Basis Capability of Power-Operated Valves Under 10 CFR 50.55a Requirements Inspection Implementation Update and Lessons Learned". W ASME/NRC 2022 14th OM Code Symposium. American Society of Mechanical Engineers, 2022. http://dx.doi.org/10.1115/nrc2022-76952.

Pełny tekst źródła
Streszczenie:
Abstract On July 26, 2019, the NRC issued Inspection Procedure 71111, Attachment 21N.02 (IP 71111.21N.02), “Design-Basis Capability of Power-Operated Valves Under 10 CFR 50.55a Requirements.” The objective of this inspection procedure is to assess the reliability, functional capability, and design basis of risk-important power-operated valves (POVs) as required by Section 55a, “Codes and Standards,” in Part 50, “Domestic Licensing of Production and Utilization Facilities,” of Title 10, “Energy,” in the Code of Federal Regulations (10 CFR 50.55a). The NRC staff has implemented this inspection procedure at operating nuclear power plants in the United States (U.S.) since January 2020 and has gained lessons learned through implementation of and feedback from the inspections. The staff has held a public meeting with nuclear power plant licensees to discuss the lessons learned from the inspection activities in December 2020. This paper describes the status of the ongoing NRC staff activities for POV inspections at operating U.S. nuclear power plants and the lessons learned through implementation of the inspections.
Style APA, Harvard, Vancouver, ISO itp.
2

"CODE INSPECTION: A REVIEW". W 9th International Conference on Enterprise Information Systems. SciTePress - Science and and Technology Publications, 2007. http://dx.doi.org/10.5220/0002366505370540.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Brothers, L., V. Sembugamoorthy i M. Muller. "ICICLE: groupware for code inspection". W the 1990 ACM conference. New York, New York, USA: ACM Press, 1990. http://dx.doi.org/10.1145/99332.99353.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Fujiwara, Shin, Hideaki Hata, Akito Monden i Kenichi Matsumoto. "Bug report recommendation for code inspection". W 2015 IEEE 1st International Workshop on Software Analytics (SWAN). IEEE, 2015. http://dx.doi.org/10.1109/swan.2015.7070481.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Kantorowitz, E., T. Kuflik i A. Raginsky. "Estimating the Required Code Inspection Team Size". W IEEE International Conference on Software-Science, Technology & Engineering (SwSTE'07). IEEE, 2007. http://dx.doi.org/10.1109/swste.2007.18.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Kantorowitz, E., T. Kuflik i A. Raginsky. "Estimating the Required Code Inspection Team Size". W IEEE International Conference on Software-Science, Technology & Engineering (SwSTE'07). IEEE, 2007. http://dx.doi.org/10.1109/swste.2007.4384090.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Belgamo, Anderson, Auri Marcelo Rizzo Vincenzi, Fabiano Cutigi Ferrari i Sandra Fabbri. "Using auxiliary artifacts during code inspection activity". W SBQS'19: XVIII Brazilian Symposium on Software Quality. New York, NY, USA: ACM, 2019. http://dx.doi.org/10.1145/3364641.3364658.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Subrahmaniyan, Neeraja, Laura Beckwith, Valentina Grigoreanu, Margaret Burnett, Susan Wiedenbeck, Vaishnavi Narayanan, Karin Bucht, Russell Drummond i Xiaoli Fern. "Testing vs. code inspection vs. what else?" W Proceeding of the twenty-sixth annual CHI conference. New York, New York, USA: ACM Press, 2008. http://dx.doi.org/10.1145/1357054.1357153.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

Huang, Fuqun, i Henrique Madeira. "Targeted Code Inspection based on Human Errors". W 2021 IEEE International Symposium on Software Reliability Engineering Workshops (ISSREW). IEEE, 2021. http://dx.doi.org/10.1109/issrew53611.2021.00076.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Hill, Ralph S. "A Life-Cycle Risk-Informed Systems Structured Nuclear Code". W 10th International Conference on Nuclear Engineering. ASMEDC, 2002. http://dx.doi.org/10.1115/icone10-22739.

Pełny tekst źródła
Streszczenie:
Current American Society of Mechanical Engineers (ASME) nuclear codes and standards rely primarily on deterministic and mechanistic approaches to design. The design code is a separate volume from the code for inservice inspections and both are separate from the standards for operations and maintenance. The ASME code for inservice inspections and code for nuclear plant operations and maintenance have adopted risk-informed methodologies for inservice inspection, preventive maintenance, and repair and replacement decisions. The American Institute of Steel Construction and the American Concrete Institute have incorporated risk-informed probabilistic methodologies into their design codes. It is proposed that the ASME nuclear code should undergo a planned evolution that integrates the various nuclear codes and standards and adopts a risk-informed approach across a facility life-cycle — encompassing design, construction, operation, maintenance and closure.
Style APA, Harvard, Vancouver, ISO itp.

Raporty organizacyjne na temat "Code inspection"

1

Sartor, Raymond Francis, i Forrest B. Brown. Whisper Source Code Inspection Report. Office of Scientific and Technical Information (OSTI), maj 2015. http://dx.doi.org/10.2172/1183391.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Phillips, Jake. Understanding the impact of inspection on probation. Sheffield Hallam University, 2021. http://dx.doi.org/10.7190/shu.hkcij.05.2021.

Pełny tekst źródła
Streszczenie:
This research sought to understand the impact of probation inspection on probation policy, practice and practitioners. This important but neglected area of study has significant ramifications because the Her Majesty’s Inspectorate of Probation has considerable power to influence policy through its inspection regime and research activities. The study utilised a mixed methodological approach comprising observations of inspections and interviews with people who work in probation, the Inspectorate and external stakeholders. In total, 77 people were interviewed or took part in focus groups. Probation practitioners, managers and leaders were interviewed in the weeks after an inspection to find out how they experienced the process of inspection. Staff at HMI Probation were interviewed to understand what inspection is for and how it works. External stakeholders representing people from the voluntary sector, politics and other non-departmental bodies were interviewed to find out how they used the work of inspection in their own roles. Finally, leaders within the National Probation Service and Her Majesty’s Prisons and Probation Service were interviewed to see how inspection impacts on policy more broadly. The data were analysed thematically with five key themes being identified. Overall, participants were positive about the way inspection is carried out in the field of probation. The main findings are: 1. Inspection places a burden on practitioners and organisations. Practitioners talked about the anxiety that a looming inspection created and how management teams created additional pressures which were hard to cope with on top of already high workloads. Staff responsible for managing the inspection and with leadership positions talked about the amount of time the process of inspection took up. Importantly, inspection was seen to take people away from their day jobs and meant other priorities were side-lined, even if temporarily. However, the case interviews that practitioners take part in were seen as incredibly valuable exercises which gave staff the opportunity to reflect on their practice and receive positive feedback and validation for their work. 2. Providers said that the findings and conclusions from inspections were often accurate and, to some extent, unsurprising. However, they sometimes find it difficult to implement recommendations due to reports failing to take context into account. Negative reports have a serious impact on staff morale, especially for CRCs and there was concern about the impact of negative findings on a provider’s reputation. 3. External stakeholders value the work of the Inspectorate. The Inspectorate is seen to generate highly valid and meaningful data which stakeholders can use in their own roles. This can include pushing for policy reform or holding government to account from different perspectives. In particular, thematic inspections were seen to be useful here. 4. The regulatory landscape in probation is complex with an array of actors working to hold providers to account. When compared to other forms of regulation such as audit or contract management the Inspectorate was perceived positively due to its methodological approach as well as the way it reflects the values of probation itself. 5. Overall, the inspectorate appears to garner considerable legitimacy from those it inspects. This should, in theory, support the way it can impact on policy and practice. There are some areas for development here though such as more engagement with service users. While recognising that the Inspectorate has made a concerted effort to do this in the last two years participants all felt that more needs to be done to increase that trust between the inspectorate and service users. Overall, the Inspectorate was seen to be independent and 3 impartial although this belief was less prevalent amongst people in CRCs who argued that the Inspectorate has been biased towards supporting its own arguments around reversing the now failed policy of Transforming Rehabilitation. There was some debate amongst participants about how the Inspectorate could, or should, enforce compliance with its recommendations although most people were happy with the primarily relational way of encouraging compliance with sanctions for non-compliance being considered relatively unnecessary. To conclude, the work of the Inspectorate has a significant impact on probation policy, practice and practitioners. The majority of participants were positive about the process of inspection and the Inspectorate more broadly, notwithstanding some of the issues raised in the findings. There are some developments which the Inspectorate could consider to reduce the burden inspection places on providers and practitioners and enhance its impact such as amending the frequency of inspection, improving the feedback given to practitioners and providing more localised feedback, and working to reduce or limit perceptions of bias amongst people in CRCs. The Inspectorate could also do more to capture the impact it has on providers and practitioners – both positive and negative - through existing procedures that are in place such as post-case interview surveys and tracking the implementation of recommendations.
Style APA, Harvard, Vancouver, ISO itp.
3

Robinson, Darrin G., i Douglas P. Collins. Advanced Test Reactor Sub-core Internal Inspection Report. Office of Scientific and Technical Information (OSTI), marzec 2006. http://dx.doi.org/10.2172/1481184.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Steele, D. E., J. L. Doyle, D. O. Monserud i P. J. Miles. Ultrahigh-Pressure Waterjets for Coke Removal in Jet Engine Fuel Tubes, with Laser-Optic Inspection. Fort Belvoir, VA: Defense Technical Information Center, kwiecień 1996. http://dx.doi.org/10.21236/ada368857.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Andrews, Nathan, i Randall Gauntt. Insights on Fukushima Damage Progression based on PCV Inspections and Implications for Decommissioning Data Collection and Code Model Refinement. Office of Scientific and Technical Information (OSTI), październik 2018. http://dx.doi.org/10.2172/1854713.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Qamhia, Issam, Erol Tutumluer i Han Wang. Aggregate Subgrade Improvements Using Quarry By-products: A Field Investigation. Illinois Center for Transportation, czerwiec 2021. http://dx.doi.org/10.36501/0197-9191/21-017.

Pełny tekst źródła
Streszczenie:
This report presents a case study for constructing aggregate subgrade improvement (ASI) layers using quarry by-product aggregates (QBA), a quarry mix of large primary crushed rocks (PCR) and sand-sized quarry fines. The construction took place at Larry Power Road in Bourbonnais Township in Kankakee County, Illinois, where the Illinois Department of Transportation placed two QBA mixes. The first mix (QBA_M1) consisted of 45% quarry by-products and 55% railroad ballast–sized 3×1 PCR. The second mix (QBA_M2) consisted of 31% and 69% quarry by-products and PCR, respectively. Two conventional ASI sections were also constructed conforming to Illinois Department of Transportation’s CS02 gradation. All sections consisted of a 9 in. (229 mm) QBA/PCR layer topped with a 3 in. (76 mm) dense-graded capping layer. Laboratory studies preceded the construction to recommend optimum quarry by-product content in the QBA materials and construction practice. The Illinois Center for Transportation research team monitored the quality and uniformity of the construction using nondestructive testing techniques such as dynamic cone penetrometer, lightweight deflectometer, and falling weight deflectometer. The segregation potential was monitored by visual inspection and imaging-based techniques. Short-term field evaluation of the constructed QBA layers, particularly QBA_M2 with a 31% quarry by-product content, showed no evidence of abnormal segregation and did not jeopardize the structural integrity of the QBA ASI layers, which had slightly lower but comparable strength and stiffness profiles to the conventional ASI sections. The use of QBA materials in ASI was field validated as a sustainable construction practice to provide stable pavement foundation layers.
Style APA, Harvard, Vancouver, ISO itp.
7

Innovative Solutions to Human-Wildlife Conflicts: National Wildlife Research Center Accomplishments, 2012. U.S. Department of Agriculture, Animal and Plant Health Inspection Service, kwiecień 2013. http://dx.doi.org/10.32747/2013.7206797.aphis.

Pełny tekst źródła
Streszczenie:
The National Wildlife Research Center (NWRC) is the research arm of Wildlife Services (WS), a program within the U.S. Department of Agriculture’s (USDA) Animal and Plant Health Inspection Service (APHIS). NWRC’s researchers are dedicated to finding biologically sound, practical, and effective solutions to resolving wildlife damage management issues. There are four spotlights for 2012 show the depth and breadth of NWRC’s research expertise and its holistic approach to address today’s wildlife-related challenges. NWRC remains committed to its other core mission areas of agriculture and natural resource protection, invasive species control, and product development. Product development takes center stage in this year’s report with accomplishments organized by specific types of products and methods.
Style APA, Harvard, Vancouver, ISO itp.
Możesz być także zainteresowany rozszerzonymi bibliografiami na temat „Code inspection” dla poszczególnych typów źródeł:
Artykuły w czasopismach Rozprawy doktorskie Książki
Oferujemy zniżki na wszystkie plany premium dla autorów, których prace zostały uwzględnione w tematycznych zestawieniach literatury. Skontaktuj się z nami, aby uzyskać unikalny kod promocyjny!

Do bibliografii