WebSphere Studio and XDE build applications

Brief introduction

Using both the rational extended development environment (XDE) and IBM's WebSphere Studio, you can have a complete and excellent integration platform for building e-business applications. You can do requirements analysis, object-oriented design, and modeling the same information model that you use to build and test your code. In other words, all the participants in a project can now "sing with the same score". In the past, when developers were developing process tasks, repetitive tools often required them to export information from one tool to another. To give you a visual understanding of the functions of these different tools, I'll use the following scenario in this article.

Sometimes a new engineering designer or architecture designer works from scratch to completely control every aspect of the application. However, they usually have to deal with pre-existing components and almost always have to deal with pre-existing relational databases.

In this scenario, assume that you want to implement a network financial application that allows end users to make payments from their accounts. As a small application designer and implementation, you are also required to use a table in a database that is available and used well.

In your organization, there is also a recent rigid requirement that all new development projects must follow a formal "requirements, analysis and design" process. The tool selected at this stage of the development process is rational XDE, while IBM's WebSphere Studio application developer is used for secondary development and application server testing. Break this system down into smaller modules:

1. Get some requirements that describe the applications you need to build.

2. Create a use case pattern diagram to show the relationship between actors and usage cases within the system.

3. Create a sequence diagram that shows the interaction (message) of an object in a chronological order.

4. Reverse manipulate a relational database to create some enterprise JavaBean (EJB) components.

5. Create a class pattern diagram and modify a Java class.

6. Configure the code into a WebSphere application server, using the Unit tester test provided by WebSphere Studio.

Collect requirements

The first step is generally the collection of requirements, usually by visiting the potential end users of the applications built by this program. Requirements can also come from people who perform specific tasks by hand or by using an existing application. For our network ATM case, the requirement we collect is a customer who pays the payee from the account. Generate the documentation for this requirement as follows:

Requirement A: "End users need to enter their ID number, and a password to verify that these accounts are their own." Once approved, the customer can choose "Make Payment (Payment)". The user then selects a specified account, enters the amount to be paid and the payee's ID number (user name). "

In the real world, it is important to get as much detail at this stage as possible, because later in the development process, you will need to implement or generate program logic to perform these tasks. To get this task, you will need to start a plug-in program that XDE;XDE is designed to be a product of WebSphere studio or other integrated Eclipse technology. You can enter the requirements into XDE and save them under engineering and version controls, regardless of which source code management system you choose. From these requirements, you can start to develop your use case. The use case is a description of the usage scenario. At this point, you need to know who your users are, and they are an integral part of this use case.

Next I will go into a brief use case to describe the use of payment using a network financial application.

Create a project and model

Before you can enter a usage case, you need to build a XDE modeling project and a model. I assume that you have installed the XDE and WebSphere Studio application Developer and have started the tool environment. Make sure you are in the modeling window. To enter the modeling window, choose Open > Other from the Perspective menu. Select modeling and click OK. To create a new XDE model project, you need to:

1. On the File menu, select New > Project. The New Project dialog box appears.

2. In the left pane of the New Project dialog box, select Modeling. In the right-hand pane, select Basic Modeling Project.

3. Click Next.

4. In the Project Name dialog box, enter the name of a new project. In this scenario, it is called Webbankmodel.

5. Select the Use default location check box.

6. Click Finish.