A new blog tag to share the New Year Wish List.
Wish you all HAPPY NEW YEAR !!
My wish list for new year -
1. To improve my leadership and negotiation skills
2. To maintain work life balance in New Year.
3. To visit at least two new places and make at least ten new friends.
No rules for number of New Year Wishes and number of bloggers to be tagged. I am starting my New Year Wish Tag with my favourite bloggers
Todd Biske, Sam Lowe and James McGovern
Hope and Wish to receive support from them. One more wish ;))
Saturday, December 23, 2006
Wednesday, December 20, 2006
Blog Tagged
Todd Biske tagged me. Thanks for giving me chance to join the bandwagon.
I love the blog-tag idea of Jeff Pulver. See the simplicity of idea. I feel simple and powerful ideas are best to catch fire and create positive impact.
Five things to share about me -
1. I had done my Masters from IIT, Roorkee, India in Chemical Engineering. I started my career in well known Telecom Company. After working in Telecom R&D and pre-sales, I switched to Financial Company. Suddenly, SIP/IMS jargon changed to Buy/Sell Mutual Fund. Obviously, few underlying things remain same like UML, J2EE and patterns/concepts.
2. I never studied during my school days (Lucky to survive in school). Things dramatically change afterwards and now I never want to stop learning.
3. I am married and have one little cute daughter.
4. I enjoy travelling. I have been to few beautiful places in Europe, Middle East and Far East.
5. Few projects in which I was involved were Product development for Telecom Billing, ESB for Telecom industry, Prepaid Service on VoIP/SIP, Persistence Framework and many more. My latest interest areas are SOA, WS and Agile. I do lot of consultancy, reviews and governance.
Time to tag five interesting people - Jeff Schneider , Gregor Hohpe , Anne Thomas Manes , Bhagvan Kommadi and Scott Mark
In last, Wish you all MERRY CHRISTMAS and HAPPY NEW YEAR
I love the blog-tag idea of Jeff Pulver. See the simplicity of idea. I feel simple and powerful ideas are best to catch fire and create positive impact.
Five things to share about me -
1. I had done my Masters from IIT, Roorkee, India in Chemical Engineering. I started my career in well known Telecom Company. After working in Telecom R&D and pre-sales, I switched to Financial Company. Suddenly, SIP/IMS jargon changed to Buy/Sell Mutual Fund. Obviously, few underlying things remain same like UML, J2EE and patterns/concepts.
2. I never studied during my school days (Lucky to survive in school). Things dramatically change afterwards and now I never want to stop learning.
3. I am married and have one little cute daughter.
4. I enjoy travelling. I have been to few beautiful places in Europe, Middle East and Far East.
5. Few projects in which I was involved were Product development for Telecom Billing, ESB for Telecom industry, Prepaid Service on VoIP/SIP, Persistence Framework and many more. My latest interest areas are SOA, WS and Agile. I do lot of consultancy, reviews and governance.
Time to tag five interesting people - Jeff Schneider , Gregor Hohpe , Anne Thomas Manes , Bhagvan Kommadi and Scott Mark
In last, Wish you all MERRY CHRISTMAS and HAPPY NEW YEAR
Thursday, December 14, 2006
Does I deserve to be called an ARCHITECT ?
When a IT professional deserves to be called an Architect? I am trying to list down few attributes of an Architect. I am not trying to find specific attributes for product, business, information, technical, software, specialist, application, system architects and whatsoever.
Its a fare trial to find out generic attributes, when a software professional is mature enough to be called an Architect.
1) When everyone around is in hurry to find the solution. Architect understands the problem first, its origin and future roadmap. See things from 10,000 ft. Afterwards, comes up with solution with blink in his mind. Its time to build consensus around the solution.
2) It is not based on number of years of experince. It is based when you start thinking at abstract level with very ambiguous information. You don't complain that information is not enough to take decision and try to dig it out.
3) He keeps track of emerging technologies. Understand when they are ready for enterprise.
4) He follows process and influence others to follow process. Believes in quality of work.
5) He is capable of taking difficult decisions on behalf of others and have courage to own it.
6) Able to understand, create and communicate the solution to team in their language (most of time UML/patterns).
7) He understands the concepts and principles of loose coupling, high cohesion, abstraction, encapsulation, information hiding, polymorphism. All these are independent of technology used in project.
Its a fare trial to find out generic attributes, when a software professional is mature enough to be called an Architect.
1) When everyone around is in hurry to find the solution. Architect understands the problem first, its origin and future roadmap. See things from 10,000 ft. Afterwards, comes up with solution with blink in his mind. Its time to build consensus around the solution.
2) It is not based on number of years of experince. It is based when you start thinking at abstract level with very ambiguous information. You don't complain that information is not enough to take decision and try to dig it out.
3) He keeps track of emerging technologies. Understand when they are ready for enterprise.
4) He follows process and influence others to follow process. Believes in quality of work.
5) He is capable of taking difficult decisions on behalf of others and have courage to own it.
6) Able to understand, create and communicate the solution to team in their language (most of time UML/patterns).
7) He understands the concepts and principles of loose coupling, high cohesion, abstraction, encapsulation, information hiding, polymorphism. All these are independent of technology used in project.
Wednesday, December 06, 2006
Nuke in the arsenal of Enterprise Architect : SOA
Architecture skill demands continuous improvement. Its a journey not an end. Architect should be able to enhance his skillset as and when job demands.
It is predicted that SOA will reduce the overall IT expenses in enterprise. It means time is right to build SOA skill and campaign for SOA adoption in enterprise .
I love analogies to explain my point, compare SOA with a nuke in arsenal of EA. Not every country in world has Nuke, still they survive and most of them have ambition to develop one in future. Furthermore, same nuclear technology can boost the country economy or can destroy it. Depends how it is handled. Advise is to handle SOA with care.
It is predicted that SOA will reduce the overall IT expenses in enterprise. It means time is right to build SOA skill and campaign for SOA adoption in enterprise .
I love analogies to explain my point, compare SOA with a nuke in arsenal of EA. Not every country in world has Nuke, still they survive and most of them have ambition to develop one in future. Furthermore, same nuclear technology can boost the country economy or can destroy it. Depends how it is handled. Advise is to handle SOA with care.
Monday, December 04, 2006
Software Selection
As an Architect oftenly one would evaluate different presentation technologies, reporting tools, application servers, databases, open source components, ORM, CM tools and a lot more.
Most of time selection depends on perception of team instead of facts available. Try to evaluate the options by leaving behind all perceptions. It is not difficult to find the best fit for your requirements.
We could look into the Software selection through three main aspects - Functional requirements, Non functional requirements and Strategic requirements. Every requirement has its own weight. Combination of all these scores finally help to select the software.
But sometimes it is difficult to start Software selection. For a same requirement, there can be multiple COTS and FOSS available. One may need to start with Elimination technique first based on main requirements. Narrow down the number of options. Go into Evaluation stage. And finally selection happens.
Few techniques which helps in evaluation are conducting POC's, going through case studies, finding references, identifying gaps between requirements and features available in COTS/FOSS and cost analysis covering licenses, software, hardware, customisation, implementation and maintenance costs.
Most of time selection depends on perception of team instead of facts available. Try to evaluate the options by leaving behind all perceptions. It is not difficult to find the best fit for your requirements.
We could look into the Software selection through three main aspects - Functional requirements, Non functional requirements and Strategic requirements. Every requirement has its own weight. Combination of all these scores finally help to select the software.
But sometimes it is difficult to start Software selection. For a same requirement, there can be multiple COTS and FOSS available. One may need to start with Elimination technique first based on main requirements. Narrow down the number of options. Go into Evaluation stage. And finally selection happens.
Few techniques which helps in evaluation are conducting POC's, going through case studies, finding references, identifying gaps between requirements and features available in COTS/FOSS and cost analysis covering licenses, software, hardware, customisation, implementation and maintenance costs.
Subscribe to:
Posts (Atom)
