IN which role are you going to work in Service Team?
If you are Service Designer you have to know following things
1. Responsible for placing service reference documents in the Registry (WSDL and XSD) / Repository (usage scenarios annotated with non-functional requirements...)
2.Reconcile candidate service interfaces with existing infrastructure and identify missing pieces (e.g. mainframe service enablement)
3.Analyze all candidate service interfaces and check for gaps, inconsistencies or redundancies (e.g. overlapping service boundaries)
4.Match technical solutions to outlined design constraints (e.g. WS-Security to solve integrity and confidentiality constraints)
5.Formalize Service Descriptions into WSDL, XSD, etc
6.Work with Application Architect and Data Architect to ensure consistency with existing XML data formats and conventions
7.Create virtualized end points in the SM to be used in the Registry
8.Define policy in SM in collaboration with the Application Architect and IT Security
9.When changing the interface for pre-existing services, the Service Designer is responsible for defining appropriate elements (e.g., namespaces, versioning, and content based routing) that facilitate simultaneous deployment of multiple versions of the service
10.Responsible for ensuring compliance with published WS-Basic Profile
If you are a service developer you will do the following responsibilities
1. Identify (in collaboration with the Application Architect) and document the design patterns that will be used in implementing the service
2.Participate in creating recommendations for the WS implementation framework (e.g. WAS, RAD) Participate in design and code reviews
3.Implement services (by means of a specific development language and design pattern(s))
4.Successfully execute unit tests created by Service Tester(s)
5.Other services should be leveraged as appropriate with any direct data access designed in cooperation with the DBA and the Data Architect
6.Document service implementation
7.Responsible for re-factoring and regression testing when changes are made to an existing service
8.Ensure all relevant implementation related documentation is placed into the service repository
If you are a service tester you will do following things
1. Develop test plans and associated test cases for both unit tests and integration tests for services and service groups, using a web services specific testing tool
2.Ensure successful unit test completion prior to elevation to the Integration environment
3.Ensure successful integration test completion prior to elevation to the System Test environment
4.Ensure SLA performance metrics are met prior to elevation to Production environment
5.Ensure test results are logged
6.Ensure defects identified through Integration and System Test environment testing are communicated to the Service Implementer(s) and Service Designer(s) for the involved services, as well as to the Application Architect [ Only integration tests should fail since unit tests were confirmed prior to elevation to integration environment ]
7.Test for interoperability and other standards conformance
If you are a SOA Architect you WILL
1.Understand application design, SOA technologies, database and data warehouse design, network design, and the many other aspects of information technology
2.Responsible for documenting patterns that support SOA
3.Responsible for end to end service requestor and provider design
4.Responsible for stating non-functional service requirements
5.Responsible for the recommendation of the architectural framework, its maintenance and communication to Application Architects
6.Responsible for adherence to architectural frameworks
7.Ensure appropriate computational and data capacity are accounted for Know the capabilities of current technologies and work with business to recommend the best technologies to achieve the units strategic goals
8.Work with business units to evaluate software options from an investment point of view
9.Help business to obtain predictable benefits and recommend organizational and SDLC process changes depending on the recommended architecture
10.Work closely with Business Analysts to carefully consider business processes across business units; with the goal to reduce overall cost and improve effectiveness
11.Endeavor to stay abreast of emerging technologies and make appropriate recommendations for changes and additions to the enterprise architecture
12.Support change management impact analysis
13.Defines the standard naming conventions to be used for managed services
14.Plays a key role in defining the various enterprise architectural frameworks to be utilized
15.Responsible for defining, and ensuring adherence to application architecture framework guidelines and communicating them to the Application, Information and Data Architects etc.
16.Define work flow and approval process for service additions and changes to be made to the Registry
17.Responsible for identification of services and definition of service interfaces
18.Mediate between business and technology
FINALLY,
if you stick with a SOA enabled tools guy and try to learn SOA around it, you will remain a blind SOA guy.
SOA is an architecture approach which allow us to do IT enablemenet of business using loose couples services which can be defined by INTERFACES.
SOA introduce a new layer into enterprise architecture which enforce partially and fully following concepts
1. Enterprise Service Bus (ESB), provide mediation, routing, transformation, translation of interface messages between service consumer and provider. Examples of ESBs are Netweaver XI, IBM Websphere 6.0 ESB, BEA Aqualogic, TIBCO's business works.
2. Enterprise Service Registry: This tool provide SERVICe goverance views by providing a place for create/admin and manage service policies. Service policies are applied to service in different phase of service life cycle such as service plan, design, build, deploy and manage. Some examples of service registry are XI registry, Systinet from HP, WSSR from IBM. All registries has to follow UDDI specifications
3. Service Repository: A unified place holder for service metadata and artifacts. Service artifacts are generally based on Object Management Groups Reusable Asset Definition. Some good example of service repository are XI repository, WSSR, Systinet etc
4. Service Management framework. This is the tool manage the deployed services using service management framework. Examples IBM Tivoli SOA manager, HP SOA manager, XI Run time work Bench etc
Please do not try to learn SOA with respect to a tool. Learn SOA as an Architecture displine to build solution using implementation independent interfaces with supporting contracts and data.
WEB Services, XML, XSD, ESB, Registry, Repository etc are just frameworks supporting SOA concept, it is not really SOA. You can do SOA with CORBA AND IDL if you want.
SAP, IBM, HP, BEA, TIBCO, ORACLE etc are companies building tools using SOA frammework enabled technologies. A tool is not SOA, it is just using SOA as a foundation for thoughts.
When you learn SOA, think outside the BUNN
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.