Editing Technical drawing (section)

==Applications==
{{See also|List of computer-aided manufacturing software}}
===Architecture===
[[File:Architect Anthony Murphy working on a kitchen renovation project in New Jersey.jpg|thumb|upright|To plan a renovation, this architect takes measurements he will later enter into his [[computer-aided design]] system.]]
{{Main article|Architectural drawing}}
{{See also|Building information modeling}}
The art and design that goes into making buildings is known as [[architecture]]. To communicate all aspects of the shape or design, detail drawings are used. In this field, the term ''[[Plan (drawing)|plan]]'' is often used when referring to the full section view of these drawings as viewed from three feet above finished floor to show the locations of doorways, windows, stairwells, etc.<ref>Jefferis, Alan; Madsen, David (2005), Architectural Drafting and Design (5th ed.), Clifton Park, NY: Delmar Cengage Learning, {{ISBN|1-4018-6715-4}}</ref>  Architectural drawings describe and document an architect's design.<ref>Goetsch et al. (2000) p. 792</ref>
{{Clear left}}

===Engineering===
{{Main article|Engineering drawing}}
{{See also|Mechanical engineering}}

Engineering can be a very broad term. It stems from the Latin ''ingenerare'', meaning "to create".<ref>Lieu, Dennis K; Sorby, Sheryl (2009), ''Visualization, Modeling, and Graphics for Engineering Design'' (1st ed.), Clifton Park, NY: Delmar Cengage Learning, {{ISBN|978-1-4018-4249-9}}, pp. 1–2</ref>  Because this could apply to everything that humans create, it is given a narrower definition in the context of technical drawing. Engineering drawings generally deal with mechanical engineered items, such as manufactured parts and equipment.

[[File:DIN 69893 hsk 63a drawing.png|thumb|left|[[Engineering drawing]] of a [[machine tool]] part]]
Engineering drawings are usually created in accordance with standardized conventions for layout, nomenclature, interpretation, appearance (such as [[typeface]]s and line styles), size, etc.

Its purpose is to accurately and unambiguously capture all the geometric features of a product or a component. The end goal of an engineering drawing is to convey all the required information that will allow a manufacturer to produce that component.

=== Software engineering ===
[[Software engineering]] practitioners make use of diagrams for designing software. Formal standards and [[modelling language]]s such as [[Unified Modelling Language]] (UML) exist but most diagramming happens using informal ad hoc diagrams that illustrate a [[conceptual model]].<ref name="Baltes 530–541">{{Cite book|last1=Baltes|first1=Sebastian|last2=Diehl|first2=Stephan|title=Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering |chapter=Sketches and diagrams in practice |date=2014-11-11|chapter-url=https://doi.org/10.1145/2635868.2635891|series=FSE 2014|location=Hong Kong, China|publisher=Association for Computing Machinery|pages=530–541|doi=10.1145/2635868.2635891|isbn=978-1-4503-3056-5|arxiv=1706.09172|s2cid=2436333 }}</ref>

Practitioners reported that diagramming helped with analysing [[Requirements analysis|requirements]],<ref name="Baltes 530–541"/>{{Rp|539}} design, [[refactoring]], documentation, [[onboarding]], communication with stake holders.<ref name=":0">{{Citation|last1=Cherubini|first1=Mauro|date=2007-04-29|url=https://doi.org/10.1145/1240624.1240714|work=Proceedings of the SIGCHI Conference on Human Factors in Computing Systems|pages=557–566|place=New York, NY, US|publisher=Association for Computing Machinery|doi=10.1145/1240624.1240714|isbn=978-1-59593-593-9|access-date=2021-09-08|last2=Venolia|first2=Gina|last3=DeLine|first3=Rob|last4=Ko|first4=Amy J.|author4-link=Amy J. Ko|title=Let's go to the whiteboard: How and why software developers use drawings |s2cid=6604218 }}</ref>{{Rp|560}} Diagrams are often transient or redrawn as required. Redrawn diagrams can act as a form of shared understanding in a team.<ref name=":0" />{{Rp|561}}

{{Clear}}