Development Roles

By: aathishankaran Viewed: 153207 times  Printer Friendly Format    


Development Roles

Reusable modules make it possible to divide the application development and deployment process into distinct roles so that different people or companies can perform different parts of the process.

The first two roles involve purchasing and installing the J2EE product and tools. Once software is purchased and installed, J2EE components can be developed by application component providers, assembled by application assemblers, and deployed by application deployers.

In a large organization, different individuals or teams might execute each of these roles. This division of labor works because each of the earlier roles outputs a portable file that is the input for a subsequent role.

For example, in the application component development phase, an enterprise bean software developer delivers EJB JAR files. In the application assembly role, another developer combines these EJB JAR files into a J2EE application and saves it in an EAR file. In the application deployment role, a system administrator at the customer site uses the EAR file to install the J2EE application into a J2EE server.

Different people do not always execute the different roles. If you work for a small company, for example, or if you are prototyping a sample application, you might perform the tasks in every phase.



Most Viewed Articles (in Java )

Latest Articles (in Java)

Comment on this tutorial