SOA as career track

Question

Hi ,
from last 1 year I am working in Web dynpro ABAP .I am facinated by SOA ...and feel like exploring it ...I have started with first by making r /3 basic clear by going through ERP for dummies (ESA version ) and then planning to switch SOA books..as recommended by seniors .
But before that I would like to know can I move this track ? If yes how I should take my career ? any suggestions ...welcome .
Regards ,
Parry

Answer 1

Parag
See, it seems you have good exposure to SAP Netweaver stacks. So u r very much eligible to SOA as a career . As I already told u SOA is basically about Architecture.So first u need to prepare a case study of a relatively large business that may incorporate many of the netweaver components e.g XI,BI,EP,MI. Transform their business requirement to technical requirements and then design the objects. Most importantly it should be designed so that every functionality in respective stacks of Netweaver can be exposed as a service </b>e.g Webservice so that their business partner can access the business object without interfering into their systems.
for an architect.......
What is an architect?
I often get resumes with architect in title. Judging by these resumes, an architect is supposed to have the following qualities:
1.     Knowledge of UML
2.     Being able to draw architecture diagrams
3.     Experience as a developer
Architect: Someone who knows the difference between that which could be done and that which should be done. -- Larry McVoy
The predominant thought seems to be progrmmers with long years of experience in coding either become managers or architects. Typically, all the people with an interest in technology become architects. But, what is the role of an architect in software development?
1.     Defining the problem in technical terms: Normally, the problem is stated in the terms of the domain -- it could be scientific, business, or any other area where the solution is needed. To solve that problem using the computer, you must be able to state the problem in "computerese", which means, in the terms of established technical frameworks. Typically, it takes:
1.     Understanding the problem as explained by the customers
2.     Translating into the computer solution domain
3.     Guiding the customer to well understood problem-solution patterns, and
4.     Understanding where true innovation is required
2.     Specifying the technologies needed: A given problem can be solved with diverse combinations of technologies. It is the architect's job to specify what technologies to be used.
3.     Defining the major modules of the system: The architect also must break down the system into modules and define interactions between modules. In fact, she should also specify the guidelines of interactions so that the module dependencies are well understood.
4.     Recommending patterns and frameworks: Since there is nothing new under the sun, each problem, in some fashion must have been solved earlier. It is the architect that should identify the relevant previous patterns to apply in the current project. In addition, she may need to define new patterns to be used in the application.
5.     Establishing code quality measures: For example, code reviews and design reviews fall under the code quality measures. The architect should establish the guidelines and practices in the team.
6.     Establishing Best Practices: Any given task can be done in many ways, some of which are equally good. However, an architect must establish best practices for doing even these mundane tasks so that consistency is maintained, and unnecessary effort is spared in looking for solutions.
7.     Maintaining conceptual integrity of the application: As the project grows, requirements change; new technologies get added; new people come into the project. With all these changes, it becomes imperative to maintain a coherent and consistent vision of the project. An architect should be able to do that.
Reward points if it helps u