If you think that software architecture or design is drawing something you are on a wrong way. Drawing only helps you to conduct and document architecture or design decisions, and yes, sometimes it helps to think about them. But drawing is not directly related to design and architecture.
The leading method of graphical representation of architecture, design and development method is UML. It's too broad topic for discussion in this forum. Please see:
http://en.wikipedia.org/wiki/Unified_Modeling_Language[
^].
It's important to understand that UML is not just graphical notation, which is a part of it. As with all significant languages, it suggests certain ways of thinking about analysis, architectures, design, development, development method and cycle. It can be considered as one of its weaknesses. The method strongly reflect certain stage in development of the software development discipline and cannot be considered as a final recipe for the method. I would invite all developers to use critical thinking.
You can some suggestion on "drawing" if you explain what do you mean by that and your goals.
—SA
Submit an article or tip