Disciplines of a Software Architect

There are four terms (or perhaps roles) which come in my mind concerning my "learning-path" in the future:

1. Software-Developer
2. Software-Engineer
3. Software-Architect
4. IT Project-Manager

I think elements of all terms are important for becoming a good software-architect. You must be able to code e.g. to create prototypes, so you must be a good developer.Software Development today is an engineering discipline in which for example design patterns are used. A good software-architect shoul in my opinion also be a good software-engineer.Architectural patterns describe approved solutions for designing software at a higher level than design patterns. For sure a very important point to work as a software-architect. And last but not least a software-architect should know things about project management. For example should he have knowledge about risc management to evaluate the different possible architectural solutions.

Of course I have to enlighten these roles more in the future. The upper paragraph is a first shot to describe the possible roles of a software-architect and will be enhanced in the future. But I think the contents of my studies will allways fit in one of these four roles and bit by bit it will become apparent what these roles really mean and in what way they are different.