Relevant bibliographies by topics / Technical documentation

Contents

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

Academic literature on the topic 'Technical documentation'

Author: Grafiati
Published: 4 June 2021
Last updated: 21 February 2023

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

Select a source type:

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

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 "Technical documentation"

1

White, Hollie C. "Documentation in Technical Services." Serials Librarian 49, no. 3 (January 5, 2006): 47–55. http://dx.doi.org/10.1300/j123v49n03_04.

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

Caher, John M. "Technical Documentation and legal Liability." Journal of Technical Writing and Communication 25, no. 1 (January 1995): 5–10. http://dx.doi.org/10.2190/9xpr-qj5l-pul2-lw9j.

Full text
Abstract:
Litigation rooted in disputes over the interpretation and sufficiency of technical documentation is increasingly common as a number of suits have been filed in state and federal courts. This article describes the matter of Martin v. Hacker (83 NY2nd 1, Nov. 23, 1993), a recent case in which New York's highest court analyzed a technical writer's prose in the context of a lawsuit over a drug-induced suicide.
APA, Harvard, Vancouver, ISO, and other styles
3

Čurepić, Danko, and Zdravko Toš. "Technical Documentation in Traffic Technology." PROMET - Traffic&Transportation 21, no. 5 (March 2, 2012): 359–65. http://dx.doi.org/10.7307/ptt.v21i5.251.

Full text
Abstract:
The requirements for the prompt usage of traffic infrastructure capacities define the technological frames which ensure updated maintenance and development of new traffic infrastructure capacities by implementing graphical and computer systems. Technical documentation (TD) based on the technology of geographic information systems (GIS) allows fast analysis of graphical and alphanumerical data with the aim of identifying spatial relations among various cartographic elements. The paper analyses and presents the methodological bases of building GIS with the aim of designing the traffic network topology, as well as structural and functional analysis which uses the acquired knowledge to propose concrete solutions on connecting data about the position of infrastructure facilities with their properties in the railway traffic safety. KEY WORDS: technical documentation, geographic information system, structural and functional analysis, software for technical drawing, signalling devices, railway
APA, Harvard, Vancouver, ISO, and other styles
4

REITER, EHUD, CHRIS MELLISH, and JOHN LEVINE. "AUTOMATIC GENERATION OF TECHNICAL DOCUMENTATION." Applied Artificial Intelligence 9, no. 3 (May 1995): 259–87. http://dx.doi.org/10.1080/08839519508945476.

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

Andersen, Asbjørn, and Klaus Heje Munch. "Automatic generation of technical documentation." Expert Systems with Applications 3, no. 2 (January 1991): 219–27. http://dx.doi.org/10.1016/0957-4174(91)90150-d.

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

Shirk, Henrietta Nickels. "Technical Writing's Roots in Computer Science: The Evolution from Technician to Technical Writer." Journal of Technical Writing and Communication 18, no. 4 (October 1988): 305–23. http://dx.doi.org/10.2190/l65t-6lj1-pvkr-t6nl.

Full text
Abstract:
The history of Technical Writing closely parallels trends in the discipline of Computer Science. The early technical writers in the computer software industry were its own technicians (programmers and analysts), who used a variety of diagramming techniques to document computer systems. As a result of the widespread availability of computers and software which began in the 1970s, professional communicators joined the software industry and reinterpreted these diagramming techniques from technical source documents into user documentation. The impact of this assimilation process has influenced graphic representations in Technical Writing, as well as created the conceptual metaphors of the “user” and the “module” (which are emerging archetypes). In the past, Technical Writing's historical roots have been the result of reactions to Computer Science. However, the increasing presence of online documentation is now creating opportunities for technical writers to shape their own future by joining with computer scientists as influential equals.
APA, Harvard, Vancouver, ISO, and other styles
7

Tănase, Delia. "Teaching Professional and Technical Communication: The Case of Technical Documentation." Balkan Region Conference on Engineering and Business Education 2, no. 1 (December 20, 2017): 20–24. http://dx.doi.org/10.1515/cplbu-2017-0004.

Full text
Abstract:
Abstract The present article highlights important aspects that need to be considered in the design of the academic linguistic training oriented to develop students’ technical documentation-related writing skills viewed as critical career-boosting skills that influence and condition employees’ promotion and graduates’ hiring chances. Technical documentation is an umbrella term covering different types of technical documents (e.g. technical reports, manufacturing standards, installation guides, quick references cards, troubleshooting guides, release notes, etc.) which, irrespective of usage or function, observe general characteristics and share essential features whose effective recognition and knowledgeability facilitate students’ upward career trajectory. The topic is discussed from the perspective of two teaching priorities - awareness of stylistic features characteristic of technical documentation and awareness of performance standards in terms of technical documentation production - within the ESP (English for Specific Purposes) and BELF (English as Business Lingua Franca) frameworks that prioritize the performative and lingua franca dimensions of the English language use in the currently-emerging globalized workplaces.
APA, Harvard, Vancouver, ISO, and other styles
8

Dychka, Nataliia, and Nataliia Hordiienko. "STYLISTIC FEATURES OF ENGLISH TECHNICAL DOCUMENTATION." Young Scientist 1, no. 65 (January 2019): 357–60. http://dx.doi.org/10.32839/2304-5809/2019-1-65-81.

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

Strassmann, Paul. "Measuring the Productivity of Technical Documentation." Journal of Information Technology 3, no. 1 (March 1988): 25–33. http://dx.doi.org/10.1177/026839628800300105.

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

Strassmann, Paul. "Measuring the Productivity of Technical Documentation." Journal of Information Technology 3, no. 1 (March 1988): 25–33. http://dx.doi.org/10.1057/jit.1988.5.

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

Dissertations / Theses on the topic "Technical documentation"

1

Pasantonopoulos, Charilaos. "Automatic construction of virtual technical documentation." Thesis, Cardiff University, 2005. http://orca.cf.ac.uk/54556/.

Full text
Abstract:
The main objective of the research reported in this thesis is the generation of intelligent documentation of complex manufactured products. The construction of documentation is a major part of product support that increases the competitiveness of the product and its effective and proper use during its life-time. At the same time, it is also a complicated and time-consuming task occupying highly trained personnel. The need for systems that increase the productivity of documentation authoring teams becomes even more apparent as other design and manufacturing activities progress towards their automation and integration through the various CAD/CAM systems. The first target of this research is to provide a system to assist the integration of the documentation authoring to the Product Data Management System, the primary source of product data. The second target is to increase the efficiency of the information systems used for this purpose and automate the process to the extent that is feasible using the available tools and ideas that are proposed in this thesis. The first contribution presented in this thesis is an Object-Oriented framework that aims to assist software developers in the design and implementation of electronic documentation systems. The second contribution is a novel distributed architecture for an intelligent documentation system that will allow the automation of a major part of the authoring procedure and the generation of electronic manuals based on information reused from the Product Data Management System. The third contribution is a new technique for the generation of virtual documents. The technique is rule-based so as to support the decision-oriented nature of data selection within the authoring procedure. The technique follows knowledge-based principles allowing authors to design documents at a higher level of abstraction.
APA, Harvard, Vancouver, ISO, and other styles
2

Parris, Tyler A. "Interning at Convergys Corporation technical editing in a technical documentation team /." Oxford, Ohio : Miami University, 2004. http://rave.ohiolink.edu/etdc/view?acc%5Fnum=miami1101253214.

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

Parris, Tyler. "INTERNING AT CONVERGYS CORPORATION: TECHNICAL EDITING IN A TECHNICAL DOCUMENTATION TEAM." Miami University / OhioLINK, 2004. http://rave.ohiolink.edu/etdc/view?acc_num=miami1101253214.

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

Rinaldi, Fabio. "Knowledge mining over scientific literature and technical documentation." [S.l.] : [s.n.], 2009. http://opac.nebis.ch/cgi-bin/showAbstract.pl?sys=000292610.

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

Troy, Matthew A. "Producing Online Software Documentation at Ontario Systems, LLC." Miami University / OhioLINK, 2005. http://rave.ohiolink.edu/etdc/view?acc_num=miami1114178834.

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

Maninjwa, Prosecutor Mvikeli. "Managing an information security policy architecture : a technical documentation perspective." Thesis, Nelson Mandela Metropolitan University, 2012. http://hdl.handle.net/10948/d1020757.

Full text
Abstract:
Information and the related assets form critical business assets for most organizations. Organizations depend on their information assets to survive and to remain competitive. However, the organization’s information assets are faced with a number of internal and external threats, aimed at compromising the confidentiality, integrity and/or availability (CIA) of information assets. These threats can be of physical, technical, or operational nature. For an organization to successfully conduct its business operations, information assets should always be protected from these threats. The process of protecting information and its related assets, ensuring the CIA thereof, is referred to as information security. To be effective, information security should be viewed as critical to the overall success of the organization, and therefore be included as one of the organization’s Corporate Governance sub-functions, referred to as Information Security Governance. Information Security Governance is the strategic system for directing and controlling the organization’s information security initiatives. Directing is the process whereby management issues directives, giving a strategic direction for information security within an organization. Controlling is the process of ensuring that management directives are being adhered to within an organization. To be effective, Information Security Governance directing and controlling depend on the organization’s Information Security Policy Architecture. An Information Security Policy Architecture is a hierarchical representation of the various information security policies and related documentation that an organization has used. When directing, management directives should be issued in the form of an Information Security Policy Architecture, and controlling should ensure adherence to the Information Security Policy Architecture. However, this study noted that in both literature and organizational practices, Information Security Policy Architectures are not comprehensively addressed and adequately managed. Therefore, this study argues towards a more comprehensive Information Security Policy Architecture, and the proper management thereof.
APA, Harvard, Vancouver, ISO, and other styles
7

Furth, Sebastian [Verfasser], Joachim [Gutachter] Baumeister, and Frank [Gutachter] Puppe. "Linkable Technical Documentation / Sebastian Furth ; Gutachter: Joachim Baumeister, Frank Puppe." Würzburg : Universität Würzburg, 2018. http://d-nb.info/1174143533/34.

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

Waleszonia, Nicholas W. "A SOFTWARE DEVELOPMENT DOCUMENTATION INTERNSHIP WITH BLUESPRING SOFTWARE, INC." Miami University / OhioLINK, 2011. http://rave.ohiolink.edu/etdc/view?acc_num=miami1303179151.

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

Dubois, Simon. "Offline Approximate String Matching forInformation Retrieval : An experiment on technical documentation." Thesis, Tekniska Högskolan, Högskolan i Jönköping, JTH. Forskningsmiljö Informationsteknik, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-22566.

Full text
Abstract:
Approximate string matching consists in identifying strings as similar even ifthere is a number of mismatch between them. This technique is one of thesolutions to reduce the exact matching strictness in data comparison. In manycases it is useful to identify stream variation (e.g. audio) or word declension (e.g.prefix, suffix, plural). Approximate string matching can be used to score terms in InformationRetrieval (IR) systems. The benefit is to return results even if query terms doesnot exactly match indexed terms. However, as approximate string matchingalgorithms only consider characters (nor context neither meaning), there is noguarantee that additional matches are relevant matches. This paper presents the effects of some approximate string matchingalgorithms on search results in IR systems. An experimental research design hasbeen conducting to evaluate such effects from two perspectives. First, resultrelevance is analysed with precision and recall. Second, performance is measuredthanks to the execution time required to compute matches. Six approximate string matching algorithms are studied. Levenshtein andDamerau-Levenshtein computes edit distance between two terms. Soundex andMetaphone index terms based on their pronunciation. Jaccard similarity calculatesthe overlap coefficient between two strings. Tests are performed through IR scenarios regarding to different context,information need and search query designed to query on a technicaldocumentation related to software development (man pages from Ubuntu). Apurposive sample is selected to assess document relevance to IR scenarios andcompute IR metrics (precision, recall, F-Measure). Experiments reveal that all tested approximate matching methods increaserecall on average, but, except Metaphone, they also decrease precision. Soundexand Jaccard Similarity are not advised because they fail on too many IR scenarios.Highest recall is obtained by edit distance algorithms that are also the most timeconsuming. Because Levenshtein-Damerau has no significant improvementcompared to Levenshtein but costs much more time, the last one is recommendedfor use with a specialised documentation. Finally some other related recommendations are given to practitioners toimplement IR systems on technical documentation.
APA, Harvard, Vancouver, ISO, and other styles
10

Zeitz, Rebecca Ann. "TechCommix: A Tool and Foundation for Rethinking and Restructuring Technical Documentation." Thesis, Virginia Tech, 2014. http://hdl.handle.net/10919/49431.

Full text
Abstract:
Comics is a writing style that is often written off as just something done for entertainment or design. However, there are many facets of comics that make it a suitable candidate for technical documentation. By nature, comics is a visual and universal language and, as such, is the basis for an investigation of comics within the scope of technical communication. This research investigates whether comics can be automatically generated, based on a set of predefined panel templates, for such purposes while also providing for flexibility in both content and ultimate consumption format. A within-subjects study run with over 200 participants compared comics to two of its traditional documentation style contenders, prose and step-oriented, in terms of understanding and evaluation metrics, including those related to user experience. Results indicate that comics as a documentation style can offer enhanced, more positive user experiences, albeit not being overall better than the other styles.
Master of Science
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Technical documentation"

1

Technical documentation. Cambridge, MA: NCC Blackwell, 1995.

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

Michaël, Steehouder, ed. Quality of technical documentation. Amsterdam: Rodopi, 1994.

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

Marlow, A. J. The technical documentation handbook. Manchester: NCC Publications, 1988.

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

Haramundanis, Katherine. The art of technical documentation. Maynard, Mass: Digital Press, 1992.

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

Haramundanis, Katherine. The art of technical documentation. Maynard, Mass: Digital Press, 1992.

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

Haramundanis, Katherine. The art of technical documentation. 2nd ed. Boston: Digital Press, 1998.

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

Hoppe, Jirka, ed. Integrated Management of Technical Documentation. Berlin, Heidelberg: Springer Berlin Heidelberg, 1992. http://dx.doi.org/10.1007/978-3-642-84840-7.

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

Hackos, JoAnn T. Managing your documentation projects. New York: J. Wiley, 1994.

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

Single sourcing: Building modular documentation. Norwich, NY: William Andrew Pub., 2003.

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

Lewis, Ruby E. Census of agriculture, 1992.: Technical documentation. Washington, DC: U.S. Dept. of Commerce, Economics and Statistics Administration, Bureau of the Census, 1993.

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

Book chapters on the topic "Technical documentation"

1

Emond, Justin, and Chris Steins. "Technical Documentation." In Pro Web Project Management, 89–116. Berkeley, CA: Apress, 2011. http://dx.doi.org/10.1007/978-1-4302-4084-6_7.

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

Smardzewski, Jerzy. "Technical Documentation." In Furniture Design, 285–317. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-19533-9_5.

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

Toole, Stuart, and Mike Winfield. "Computerised Technical Documentation." In COMADEM 89 International, 231–37. Boston, MA: Springer US, 1989. http://dx.doi.org/10.1007/978-1-4684-8905-7_38.

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

Duhovnik, Jože, Ivan Demšar, and Primož Drešar. "Technical Documentation (Drawing)." In Space Modeling with SolidWorks and NX, 413–53. Cham: Springer International Publishing, 2014. http://dx.doi.org/10.1007/978-3-319-03862-9_14.

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

Duhovnik, Jože, Ivan Demšar, and Primož Drešar. "Modellers and Technical Documentation." In Space Modeling with SolidWorks and NX, 455–87. Cham: Springer International Publishing, 2014. http://dx.doi.org/10.1007/978-3-319-03862-9_15.

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

Baeten, Johan, and Joris De Schutter. "Appendix E: Technical Documentation." In Integrated Visual Servoing and Force Control, 161–65. Berlin, Heidelberg: Springer Berlin Heidelberg, 2003. http://dx.doi.org/10.1007/978-3-540-45057-3_14.

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

Mayer, Renate. "Workbench for Technical Documentation." In Database and Expert Systems Applications, 266–69. Vienna: Springer Vienna, 1992. http://dx.doi.org/10.1007/978-3-7091-7557-6_46.

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

Hoppe, Jirka. "Requirements." In Integrated Management of Technical Documentation, 2–6. Berlin, Heidelberg: Springer Berlin Heidelberg, 1992. http://dx.doi.org/10.1007/978-3-642-84840-7_1.

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

Liu, Ling, and Robert Meersman. "Extensibility in Object-Oriented Database Systems." In Integrated Management of Technical Documentation, 127–49. Berlin, Heidelberg: Springer Berlin Heidelberg, 1992. http://dx.doi.org/10.1007/978-3-642-84840-7_10.

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

Weigand, Hans, and Berrie Kremers. "An Object-Oriented Active Data Dictionary to Support Database Evolution." In Integrated Management of Technical Documentation, 150–67. Berlin, Heidelberg: Springer Berlin Heidelberg, 1992. http://dx.doi.org/10.1007/978-3-642-84840-7_11.

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

Conference papers on the topic "Technical documentation"

1

Mendes, Leonardo, Cristina Cerdeiral, and Gleison Santos. "Documentation Technical Debt." In SBES 2019: XXXIII Brazilian Symposium on Software Engineering. New York, NY, USA: ACM, 2019. http://dx.doi.org/10.1145/3350768.3350773.

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

Anderson, William, and Glen Anderson. "Multimedia training and technical documentation." In 36th Structures, Structural Dynamics and Materials Conference. Reston, Virigina: American Institute of Aeronautics and Astronautics, 1995. http://dx.doi.org/10.2514/6.1995-1471.

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

Richardson, Kyle, and Jonas Kuhn. "Learning Semantic Correspondences in Technical Documentation." In Proceedings of the 55th Annual Meeting of the Association for Computational Linguistics (Volume 1: Long Papers). Stroudsburg, PA, USA: Association for Computational Linguistics, 2017. http://dx.doi.org/10.18653/v1/p17-1148.

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

Stamey, John W., and Thomas M. Roth. "Technical documentation and related contractual liability." In the 17th annual international conference. New York, New York, USA: ACM Press, 1999. http://dx.doi.org/10.1145/318372.318566.

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

Schönberg, Christian, Franz Weitl, Mirjana Jakšić, and Burkhard Freitag. "Logic-based verification of technical documentation." In the 9th ACM symposium. New York, New York, USA: ACM Press, 2009. http://dx.doi.org/10.1145/1600193.1600250.

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

MacKinnon, Neil, and Steve Murphy. "Designing UML diagrams for technical documentation." In the 21st annual international conference. New York, New York, USA: ACM Press, 2003. http://dx.doi.org/10.1145/944868.944891.

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

MacKinnon, Neil, and Steve Murphy. "Designing UML diagrams for technical documentation." In the 22nd annual international conference. New York, New York, USA: ACM Press, 2004. http://dx.doi.org/10.1145/1026533.1026565.

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

Bist, Gary, Neil MacKinnon, and Steve Murphy. "Sequence diagram presentation in technical documentation." In the 22nd annual international conference. New York, New York, USA: ACM Press, 2004. http://dx.doi.org/10.1145/1026533.1026566.

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

Stock, Ingo, Michael Weber, and Eckhard Steinmeier. "Metadata based authoring for technical documentation." In the 23rd annual international conference. New York, New York, USA: ACM Press, 2005. http://dx.doi.org/10.1145/1085313.1085330.

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

Mongeau, D. "Business planning in technical documentation organizations." In the 7th annual international conference. New York, New York, USA: ACM Press, 1989. http://dx.doi.org/10.1145/74311.74313.

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

Reports on the topic "Technical documentation"

1

Zmud, Johanna. Technical documentation for survey administration :. Gaithersburg, MD: National Institute of Standards and Technology, 2005. http://dx.doi.org/10.6028/nist.ncstar.1-7b.

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

de Bruin, Kelly, and Aykut Mert Yakut. Technical documentation of I3E model. ESRI, March 2019. http://dx.doi.org/10.26504/sustat74.

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

McIlroy, Bartholomew J., and Jr. Final Technical Report and Software Documentation. Fort Belvoir, VA: Defense Technical Information Center, August 1997. http://dx.doi.org/10.21236/ada328617.

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

E., Kemp-Benedict. The national bioenergy investment model: Technical documentation. Center for International Forestry Research (CIFOR), 2012. http://dx.doi.org/10.17528/cifor/003774.

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

de Bruin, Kelly, and Aykut Mert Yakut. Technical documentation of I3E model, Version 2. ESRI, September 2019. http://dx.doi.org/10.26504/sustat77.

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

Yakut, Aykut Mert, and Kelly de Bruin. Technical documentation of I3E model, Version 3. ESRI, May 2020. http://dx.doi.org/10.26504/sustat91.

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

de Bruin, Kelly, and Aykut Mert Yakut. Technical Documentation of the I3E Model, v4.0. ESRI, October 2021. http://dx.doi.org/10.26504/sustat109.

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

Hanna, S. R., J. C. Chang, and J. X. Zhang. Technical documentation of HGSYSTEM/UF{sub 6} model. Office of Scientific and Technical Information (OSTI), January 1996. http://dx.doi.org/10.2172/203219.

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

Prichard, Susan J., David V. Sandberg, Roger D. Ottmar, Ellen Eberhardt, Anne Andreu, Paige Eagle, and Kjell Swedin. Fuel Characteristic Classification System version 3.0: technical documentation. Portland, OR: U.S. Department of Agriculture, Forest Service, Pacific Northwest Research Station, 2013. http://dx.doi.org/10.2737/pnw-gtr-887.

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

Portier, Rebecca W. Fire data management system, FDMS 2.0, technical documentation. Gaithersburg, MD: National Bureau of Standards, 1994. http://dx.doi.org/10.6028/nist.tn.1407.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Technical documentation' 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