How can a software developer become a software architect?

So you are a software developer who doesn't think about architecture? Then you have done somthing wrong within the past 11 years. All you want to do is replacing two words. When developing things you should always think about architecture and weather your code fits into the place you are supposted to write it. You should always see the big picture even though you should not code premature things. For me there is no difference between a software developer and a software architect except the wording. Sorry if that wasn't what you expected. But if you like we can continue that discussion.

The distinction may not be that great, depending on what kind of software system you develop. Generally in architecture you will focus more on the decomposition of your software system and looking to ensure that you have a stable base for meeting your requirements. It is only really in larger teams that the role of architect, distinct from developer, might start to take form. In that case the architect will ensure that different developers are writing modules that integrate and perform according to the design decisions in the architecture. So, to move to being 'an architect', I would suggest that you look into how well you work with others and how well you can co-ordinate work between different developers.

What I would do is a self-assessment using the Software Architecture CV of http://www.isaqb.org/?lang=en. This might help you to evaluate how your skills fit to a Software Architect skill set.

Expectations for the role of "Architect" vary widely between employers. An architect may write code all day or never write code, may attend meetings most of the day or almost no formal meetings, may interface primarily with developers or product owners, may have power to enforce standards or merely make recommendations, may have a background in hands in development or an academic background. The point is, the role of architect is really a catchall for any sort of technical leadership. You really won't know if it's a good fit until you are talking to the hiring manager. No matter what the technical expectation is, the role of software architect always requires excellent communication and people skills. In my experience this is a big cultural shift from working in software development.