Editing Technical drawing (section)

=== 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}}