Software architecture [[diagrams]] are graphical notation representations of software architecture. They are useful for guiding software development, communicating with stakeholders, and retrospectively documenting existing systems. If you are documenting an existing system, make sure the diagram is up-to-date and accurately reflects the system. Incorrect documentation is worse than no documentation! Diagraming software architecture is often done to meet multiple objectives and for different audiences. As with any product, you should consider why you are diagraming and for whom you are diagraming the software architecture. You may need multiple diagrams for different objectives and audiences. For complex diagrams or to create multiple views of the same system, consider developing a [[software architecture model]], which can be rendered as multiple diagrams depending on the audience and use case.