Hi all, I am a senior developer(10 years exp) trying to explore the "architect" path.I am sure there are few J2EE architects here at ranch.I would appreciate your response.
#1. Just wondering what are your daily responsibilities as J2EE architect? #2. Do you really do UML diagrams? #3. Do you architect web services? #4. Do you have to make lot of key decisions while designing ejb's? #5. what else do you do? #6. What does a junior J2EE architect do? and what does senior architect do?and what does chief architect (if any) do?How is the typical structure/hierarchy?
These questions may sound naive but in our company there are no architects - product has been there for years.So, I have absolutely no Idea what are the typical responsibilities.Books typically list the architect's responsibilities but I believe they do exaggerate, I would like to know from "real" architects.
Really really appreciate your response.This would help me a lot in making right decisions.
Originally posted by Rahul Toaikani: Hi all, I am a senior developer(10 years exp) trying to explore the "architect" path.
It depends on the size of the project. If you're working on a multi-million dollar high volume high frequency, pricing, trading and risk management system for a large investment bank then obviously there will be a much larger hierarchy with possibly different levels of architects. Ultimately, you will probably have a chief architect at the top.
If you are working on a simple e-commerce system for an online retailer, the size of the budget/team will be much smaller and perhaps you only have one architect.
- Yes architects do use UML LOL!
It also depends on the development methodology as to what level of UML is undertaken and when it happens.
Obviously, if you are purely doing maintenance work to an existing system then there is less requirement for architecture unless you plan on re-architecting parts of the system. Just as you don't need to get an architect involved when it comes to doing minor maintenance around the house. If you want to build an extension however, you may need to get an architect involved. Depending on your country, you may just get an expereience builder (senior developer) in to do the job without an architect.
Some jobs entail working on new/greenfield projects every few months. These are the kind of job where you get to experience building applications from scratch lots of times and therefore you can get good at it quite quickly and is a more conducive route to being an architect.
Being an architect is often just a matter of calling yourself an architect. Given a business problem, can you conceive of a solution to solve that problem? Can you see how the solution will be structured and put together? Can you choose which technologies to use and why? Can you communicate the solution to people who are going to be building it? Can you make all of these decisions without anyone's help? As a senior developer, you probably can. If you were given a job that did all of those things then you'd be an architect in my book.
It's largely just semantics and common sense. I don't know why people obsess over book definitions etc. you are what you want to be.