Web service project role
Writing / OLAF Zimmermann, Frank Mueller
This article describes how different work roles involved in the Web service development project, including how their objectives, tasks, and how to cooperate with each other. This article has not discussed the actual tasks performed in detail (such as the service from WSDL to create document / text style); How to think. The purpose is to help IT departments understand how to organize their own projects and formulate the entire blueprint of the project.
Web services have experienced only a few eras used in the use of a small number of enthusiasts. At that time they were not mature but they were highly praised, they worked hard to achieve everything - even simple and unsafe basic data structure exchange. In the last two years, this technology proves its own maturity in a large number of actual projects. Therefore, many technical director now believe that Web services are another powerful components of an enterprise application and software integration toolbox, which can be used in large projects in this area. In this way, when the use of web services is extended to the "normal" enterprise application project you are organized, you may find that you have become a member of the web service project group, even if you have never used himself as above A fan mentioned. So, what role will you play now? Let's take a look at what is feasible!
There are many reasons for reading to make you feel that you should consider reading this article: If you are an project manager, the Chief Architect or another technical supervisor, you can get some suggestions to guide you how to construct your A web service project and a staff member. The role and responsibilities of our collection can be used for your work breakdown structure. If you are developers who have just contacted Web services, you can learn which tasks and tools exist - and should add which important words in your resume, so that your name can appear closely with you. The next Web service project project project. Please note that this is not an articles about the group development. Our focus is on the specific aspects of Web services; for example, you can't find roles in the usual J2EE project, as well as professionals assigned to one or more characters. Personnel tools and information sources. You may not understand why we decide to write such an article, see it seems a bit boring. To be honest, we also agree that application technology to solve real business issues is very interesting for any project. However, good structures and methods are the key to success, and unsuccessful projects will never have fun, even if it uses the most popular technology in the world. So, please believe us, you have made efforts to do it!
Overview: Web Services Introduction Web Services Solutions and Service - oriented Architecture (SOA) include the implementation of the service requestor (client) and service provider (server), which communicate through SOAP (XML messaging). Web Services Description Language (WSDL) provides contact between the requester and the provider. Optional service proxy (such as unified description, discovery, and integrated protocol, UNIVESAL Description, Discovery and Integration, UDDI) Registry may also need it. The service description and interaction must be modeled, and XML Schema is also true. In addition, it is necessary to design, develop, deploy and test implementation. So far, everything is not bad. If you have visited the developerWorks SOA & Web service area, you may say that this is not a special place. The current problem is: How do I have these purposes?
Project Phase and Roles Any development project must experience different stages and require different skills and collaboration in its life cycle. Web services are no exception in this regard. Depending on the methods used in your environment, you may have already encountered the general terms listed below: l Demand Engineering L Business Domain Analysis L Solution Architectural Contour L Summary Design and Detailed Design L Object - Oriented Objective Analysis (OOAD) 1 Period (such as unit test, integrated test, system test, acceptance test) L implementation L Maintenance L Some aspects (such as service modeling (such as thick or fine-grained interface), SOAP engine (IBM WebSphere SOAP, Apache Axis) Or APACHE SOAP 2.3) Selection and Organizational Interoperability Tests) is a specific matter that the Web service needs to be considered first. The nature of these issues is different, for example, the prerequisite for service modeling is to have different skills and thinking, not interoperability testing. This metaphor has proven to be very useful in this context, which makes the confusion order. The role is related to the project phase, which defines an abstraction layer that will work with the execution resource. All project group members are in one or more characters. The role model is an ordinary structure in the project management and design method. The concept of role creates a vocabulary that is easy to understand, which has proven to be a very powerful tool when the project is started. Therefore, let us find a role model in the Web service development project. We divide the roles in the model into three categories. Since the Web service project is just another type of development project, we see that there are many familiar roles that are well known. We define a category called existing roles. However, some existing roles have assume additional duties related to Web services; we classify these characters under extended roles. Finally, there are some new roles with special responsibilities related to Web services, and we classify these roles under additional roles.
The existing role lets us start from all the four roles that you have seen (or taken) in the project: the project administrator is responsible for the comprehensive management and leadership of the project team. Define and track the project plan and work decomposition structure. Business analysts obtain the functional needs of commercial users and provide the project group to provide knowledge in the relevant fields. It is necessary to understand the business language and have the skills of the relevant industry and the field. The technical supervisor of architect project. Develop the logic and physical layout of the entire solution and its components (structure). Developers also known as coders. This role is not required here. Security experts are responsible for defining a security guideline (strategy) and is responsible for implementing security measures to follow these security guidelines. Systems and database administrators perform hardware, operating systems, and database systems, and installation and ongoing maintenance work. Please note that this list is definitely not unique. We can list all roles without the specific aspects of Web services, as they are suitable for this category. However, we will limit the list to the most common roles that appear in the web service project - this article is not a general project method tutorial.
Extended role five standard roles Receive additional duties in Web service projects. These roles and their new role are: product vendors provide compliance with WS-i's Web service runtime container and optional service registry and SOAP gateway services. Deployment personnel get development components and install them in the target runtime environment. Generate the stub and skeleton of the target environment in WSDL and install them with the service implementation. The JAX-RPC mapping and handler configuration are provided through a specific deployment descriptor through the web service. Test staff are responsible for all types of standard testing phases, such as unit testing, integration testing, loading testing and acceptance testing. In addition, it also defines the test cases of Web service interoperability testing and consistency testing. Developers designed and implemented specific scripts, builders, and other utilities. The standard level in the field of Web services makes it possible to develop custom tools such as understanding WSDL, JAX-RPC, or JSR-109. Knowledge transfer service providers provide opportunities for experts and technical guidance in contact related topics, they will bring web services concepts and achieve resources in resources. At the end of the extra role, it is time to define the extra role you can see in the Web service item: SOA architect is responsible for end-to-end service requestors and providers. Respond to and express non-function service requests. Service modeling staff applies data and function modeling techniques to define the service interface contract, including the SCHEMA of the exchange message. Differential designers study explicit, declarative service arrangements (polymerization, combination) functions. This is an optional role. Service developers are familiar with Web Service Concepts and XML J2EE Developers. Develop service interface, implementation (provider end) and service call code (requester). Interoperability testers verify that the requester and provider of the development can achieve seamless interoperability and ensure that the Web Service Interoperability (WS-I) is followed. UDDI administrator defines how the general UDDI data model is customized and implanted. This is an optional role. Please note that we divide the extended role and additional roles are arbitrary. Extended roles and additional characters are from existing roles (for example, SOA architects and service developers). However, we believe that for additional characters, introduce the new name reasonable. From now on, we will only focus on extra roles. The specific role of the web service is now, let us study the specific roles of the web service more deeply. Figure 1 shows these roles and the tasks they do. The next page shows how these roles interact between each other, which skills are required when performing, and which tools can be used: About tool discussions, we have assumed J2EE to be the selected service implementation platform. If a platform such as Microsoft .NET must be added to the figure, other skills and tools must be added. In addition, so far, we have been deliberately not mentioning the name of the product; you can imagine that a set of tools for web services can be obtained from IBM and open source commissions. Check out the Eclipse and Apache Web service open source projects, do not forget to study the technology reviews on IBM WebSphere Studio Application Developer products and AlphaWorks.
Personnel to the role assignment each role is responsible for a different aspect of the entire project. As we said, a person can usually wear a few hats, in other words, take a plurality of characters. If a variety of people who have a world-wide knowledge and multi-purpose skills will reduce the risk of the project. In some cases, only such a variety of people will have a purposeful cooperation will reveal the problem of the project and propose reasonable solutions. On the other hand, the communication overhead increases as the addition of each new member. There is no single and simple answers to solve the problem of the role to the mapping. There are many different opinions and debates that should be handled in this problem (even the two authors of this article have not reached an agreement!). We don't continue these debates, now let us look at a small example. Consider the following scenario: Our fictional companies from the insurance industry, this company decides to build a new group of Mid-Office business applications for risk and policy management, which inevitably involves two different backend systems. Both backend systems have been constructed as J2EE applications - one uses EJB, another only servlet, JSP, and JDBC to connect to its customers and contract databases. In the initial phase of the launched development project, the roles defined above will be assigned to the team member. In addition to specific activities of the Web service, you have to determine and assign standard item tasks and roles. The table two is listed in this work decomposition training. You can see that all other group members have wear a top hat in addition to project administrators and business analysts. And it is not assigned a process of flowing model that belongs to an additional role because it is not required in this scenario. At the same time, it should be noted that this example is quite simple; in the actual project, there is a need to have a larger item group. According to our success, the size of the core group is preferably 7 to 10. This depends entirely on the scene you are; in order to avoid your work decomposition structure, it becomes difficult to handle because it is too complicated, you can break the project into several phases. In other words, to ensure that the project is progressing step by plan. This allows project group members to have the opportunity to learn this work and reduce project risk. In the flexible development, this principle is called continuous integration. We will no longer further detail this fictional insurance example. In fact, it comes from Perspective on Web Services (see http://www.ibm.com/developerworks/cn/webservices/ws-roles/#6), in the book, it is a end-to-end case study And the scene of future reference implementation is described. If you like, you can think of this article as a small learning guide of the book - the extension of the ENGAG-Ement Perspective. Conclusion In all actual application development projects, it is only possible to succeed. Some conditions such as reasonable work decomposition structures, the correct skill combination, and a good teamwork are the key to success, and they are even more important in many times they compare factors for technology solutions. Since the Web service is a quite new technology, there is a lack of experience in this field. Some of the specific roles of Web services and other well-known roles from standard development projects have assumed additional responsibilities. You can need to use some additional skills and many suitable tools to assist you. To coordinate the assignment of roles to resources; we must weigh the pros and cons of highly specialized and related communication overhead. In any case, the "Separate Action" method is undoubted to be important projects, and general project management technologies are applied to the Web service project, just as in any other project. As a member of the IBM service organization, in the recent two years, we have the opportunity to participate in a large number of Web service projects. We hope to be able to share our personal experience in these items through this small article.
