I have never worked with a software architect or aspired to become one in near future. Just a thought I get on thinking about a Software architect guy is that he knows more technologies than any one else in the team
So to get to know more technologies shouldn't he have worked in many number of teams and got more than 10+ development experience?
Have you ever experienced a fellow tester or support team member nurtured to the role of an architect?
And if you were or are an architect currently what point of time in your career did you realized - "I am an architect now" What made you feel confident about writing an architecture for a new software?
I have a 4.5 years of experience in IT but the experience is shared on development, maintenance and support projects. I don't see myself working in many different technologies and projects to become a software architect...
Hey really I don't have any question here... just sharing my thought and trying to poke any software architects busy participating in this forum
It's not just about knowing a lot of technologies. You also have to know about how to make decisions about non-functional (and functional requirements), how to make decisions on a team level and the like. It also helps to have an understanding of the bigger picture and management concerns.
Thanks Jeanne - should an architect also take care of the financial constraints? while drafting the architecture of the software will he be having the project budget in mind? Or managing budget falls under Project Manager's duty?
John Jai wrote:Thanks Jeanne - should an architect also take care of the financial constraints? while drafting the architecture of the software will he be having the project budget in mind? Or managing budget falls under Project Manager's duty?
I am neither Jeanne nor a software architect, but I do think I can share what I have.
Decisions of organizations are not taken by a single person, there are more people involved and when it comes anything 'financial', even the people who are nowhere associated, try to push their influences. From software architect's perspective, he would more often provide suggestions on products and solutions, he himself may not be involved in the whole budget or the buying process. But if he has to make his presence felt, he should know if the company can afford to buy a product, if yes he should have figures like how many such licenses are required by the company and if there are chances that will increase/decrease later after the first purchase and the factors for their increase or decrease in numbers.
Most detailed estimates that I help produce are made by a group of individuals. Depending on the nature of the estimate, we may provide multiple options for the business to select. This enables them to get the most for the money they are looking to invest and can weigh some of tactical versus strategic aspects of what they are looking to accomplish. We may also include a confidence level in the estimate.