Originally posted by SAFROLE YUTANI:
where my responsibilites included overall architecture, design, requirements gathering, documentation, etc, I think you get the point. If you're stuck doing coding, then you're not working at the capacity of an architect since coders are the low-level business logic builders, and architects operate at a much higher level.
[ June 10, 2003: Message edited by: SAFROLE YUTANI ][/QB]
Originally posted by Sankar Subbiah:
Raffi,
Very good points. I have only one question in your points (Sorry to jump in). IMHO, the things you have said as your role is a mix of Business analyst as well as System Architect. Isn't the B/A's role to gather requirement and document it and pass it on the the architects for system design based on the requirements?
Thanks,
Originally posted by SAFROLE YUTANI:
Ok, so now I'm a Business Analyst too!
Raffi
Originally posted by Matt Cao:
Hi Safrole,
Very good job. I see you are a proactive individual. Any company lucky enough to have you onboard will not let you go easily.
I think the reason company not granted you the Business Analyst/Developer/etc. probably you do not have a business degree or credential.
FYI. Don't care much about title, only the roles counted. If anyone read your resume could not interpret your roles, then that individual should not have any business to interview you for the position.
Originally posted by Nicholas Turner:
what do you suggest I do to become an architect?
Don't get me started about those stupid light bulbs. |