Home > Store

Building J2EE Applications with the Rational Unified Process

Register your product to gain access to bonus material or receive a coupon.

Building J2EE Applications with the Rational Unified Process


  • Sorry, this book is no longer in print.
Not for Sale


  • Copyright 2003
  • Dimensions: 7-3/8" x 9-1/4"
  • Edition: 1st
  • Book
  • ISBN-10: 0-201-79166-8
  • ISBN-13: 978-0-201-79166-2

This book is a Rational Software Corporation-specific book focusing on the development of J2EE applications (version 1.3) within a RUP (Rational Unified Process) environment. As such, the book has a heavy dependency on UML (version 1.4). The authors aim to give the reader a basic understanding of component architectures and associated technologies, and how these component architectures and technologies are applied in the context of systematic development, specifically the Rational Unified Process. The reader will learn a set of proven best practices, guidelines, and standards that apply to systems development. It will reflect the next version of RUP which is scheduled for release during in 2002. This version of RUP will be a considerable departure from the current version.

Sample Content

Online Sample Chapter

J2EE: An Introduction to the Rational Unified Process

Downloadable Sample Chapter

Click below for Sample Chapter(s) related to this title:
Sample Chapter 4

Table of Contents

(NOTE: Chapters 2-9 conclude with a Summary.)

Foreword by Philippe Kruchten.

Foreword by John Croupi.


1. Introduction.

How this Book is Organized.

2. An Introduction to the Java 2(TM) Platform, Enterprise Edition.

Enterprise Concerns.

Business Concerns.

Integration Concerns.

Development Concerns.

Multi-Tier Architectures and the J2EE Platform.

J2EE Platform Overview.

J2EE Technology Overview.


Presentation Tier.

Business Tier.

Integration Tier.

J2EE Deployment Configurations.

J2EE Component Technologies.


Application Clients.

Java Servlets.

JavaServer Pages (JSP).

Enterprise JavaBeans (EJB).

Assembly and Deployment.

J2EE Modules.

3. An Introduction to the Rational Unified Process.

Best Practices — The Foundation of RUP.

RUP Key Concepts.





Workflow Details.



RUP as a Process Framework.

4. An Introduction to the J2EE Developer Roadmap.

What is a RUP Roadmap?

J2EE Developer Roadmap — Scope and Rationale.

J2EE Developer Roadmap — J2EE-Specific Content.

5. An Introduction to the Sample Application.

Application Overview.

Problem Statement.

Stakeholders and Users.

Stakeholders, Their Concerns and Responsibilities.

Users, Their Concerns and Responsibilities.

Functional Features and Constraints.

Other Requirements and Properties.

Non-Functional Properties.

User Environment.

Deployment Environment.

6. Requirements.

Requirements and Iterative Development.

Requirements Overview.

Workflow Detail: Define the System.

Activity: Capture a Common Vocabulary.

Activity: Find Actors and Use Cases.

Activity: Prioritize Use Cases.

Activity: Review the Requirements.

Workflow Detail: Refine the System Definition.

Activity: Detail a Use Case.

Activity: Structure the Use-Case Model.

Activity: Review the Requirements.

7. Analysis.

Analysis and Iterative Development.

Analysis Overview.

Workflow Detail: Define an Initial Architecture.

Activity: Architectural Analysis.

Activity: Review the Initial Architecture.

Workflow Detail: Analyze Behavior.

Activity: Model the User Experience.

Activity: Review the User Experience.

Activity: Use-Case Analysis.

Activity: Review the Analysis.

8. Design.

Design and Iterative Development.

Design Overview.

Workflow Detail: Refine the Architecture.

Activity: Identify Design Mechanisms.

Activity: Identify Design Elements.

Activity: Incorporate Existing Design Elements.

Activity: Describe Distribution and Concurrency.

Activity: Review the Architecture.

Workflow Detail: Detail the Design.

Activity: Use-Case Design.

Activity: Subsystem Design.

Activity: Component Design.

Activity: Class Design.

Activity: Database Design.

Activity: Review the Design.

9. Implementation.

Implementation and Iterative Development.

Implementation Overview.

Workflow Detail: Structure the Implementation Model.

Activity: Structure the Implementation Model.

Activity: Review the Implementation.

Workflow Detail: Implement Design Elements.

Activity: Implement Design Elements.

Activity: Perform Unit Tests.

Activity: Review the Implementation.

10. Additional Topics.

Business Modeling.



Configuration and Change Management.

Project Management.


Other Considerations.

In Conclusion — A Note from the Authors.

Appendix A: Describing a Software Architecture.


What Is Architecture?

Communicating the Architecture of a System.

The Software Architecture Document.

Appendix B: Modeling Conventions.

UML Representation of J2EE Developer.

Roadmap Elements.

Requirements Artifacts.

Analysis Artifacts.

Design Artifacts.

Implementation Artifacts.

Design Relationships.

Design Class Attributes and Operations.

J2EE Developer Roadmap Model Structure Guidelines.

Use-Case Model.

User-Experience Model.

Design Model.

Implementation ModeL.

Appendix C — Glossary.



Index. 0201791668T05172002


About This Book

This book is about developing Java 2 Platform, Enterprise Edition (J2EE) applications with the Rational Unified Process (RUP) and the Unified Modeling Language (UML). There are a number of books describing the J2EE platform and its associated technologies. There are also books about software development processes and about RUP, in particular. However, we could not find a book that described and exemplified how to use a subset of RUP that contains only the most relevant parts of an otherwise large and comprehensive process, to build J2EE applications. The book bridges this gap between the RUP and J2EE technologies.

A world that combines J2EE, RUP and UML is complex. This world requires a good map if you are to successfully navigate your way through it. This book provides such a map both metaphorically and literally. It is metaphorical because the very objective of the book is to provide a description of a "safe path" through the J2EE application development activities. It is also literal because we define a "J2EE Developer Roadmap," which is a process map, to guide us. We describe the content of the book in more detail in Chapter 1, Introduction.

Who This Book Is For

While writing the book we kept three audiences in mind. The first audience is software architects, designers and developers familiar with the J2EE platform and its technologies, wanting to understand how to apply them in the context of a software development process. The second audience is development team members familiar with RUP, looking for help in applying the process to J2EE development. The third audience is software professionals who are neither familiar with J2EE nor with RUP, and are looking for an example of how to use RUP in the development of a J2EE application.

Conventions Used in This Book

The book is roughly divided into two parts. The first part, Chapters 2–5, summarizes the J2EE technologies, introduces RUP and the J2EE Developer Roadmap, and briefly describes our sample application. The rest of the book is what we refer to as the "process chapters" and contains a guided tour through a J2EE application development project.

We structured the process chapters to make them easy to read "at a glance," and to make it easy to refer to specific topics of interest. Each process chapter is organized primarily by activities. We provide diagrams that indicate the overall flow between the activities and the key artifacts that are consumed and produced by the activities. For each activity, we provide an overview table that summarizes the purpose of the activity, its input and output artifacts, and a summary of the steps performed within the activity. Following the table, we then describe the details of each of these steps, using the sample application.

In the process chapters, we use only one simple editing convention: we emphasize all references to process elements such as activities, steps, and artifacts.



Click below to download the Index file related to this title:



Errata for Building J2EE™ Applications With the Rational Unified Process

Peter Eeles, Kelli Houston, Wojtek Kozaczynski

Chapter 2

  • Page 9: Figure 2.2. The text "Applet" is missing from the box in the box labeled "Applet Container". The text "Application" in the box in the "Application Client Container" box should read "Application Client". See corrected PDF file on this site.
  • Page 18: Figure 2.8. The box in the "Client Device" box should contain the text "HTML Client". See corrected PDF file on this site.
  • Page 31: Figure 2.13. The unlabeled box in the box containing "Servlets" and "Java Classes" should be labeled "JSPs". The unlabeled graphic in the box containing "Java Classes" should be labeled "EJBs". See corrected PDF file on this site.

Chapter 3

  • Page 49: "RUP as a Process Framework" section: Remove bold-faced character format for the word "customization" since this is not a RUP process element. The text should still be italicized.

Chapter 4

  • Page 54: Figure 4.1. The text "defined in" between the Implementation Model and the Deployment Model should read "deployment defined in". See corrected PDF file on this site.
  • Page 55: 1st paragraph: last sentence: Change "...the physical files of the Implementation Model can be maintained using roundtrip engineering" to "...the physical files and directories can be maintained using roundtrip engineering".

Chapter 6

  • Page 74: Figure 6.4: The arrows should not have plain arrowheads, but should have open triangles as their heads. See corrected PDF file on this site.
  • Page 83: 3rd paragraph: 1st sentence: Change "documented in the Requirements Review of the Software Architecture Document" to "documented in the Software Architecture Document".
  • Page 88: 1st paragraph after the bulleted list: 2nd sentence: Change "on relationships between Use Cases, see the Structure the Use-Case Model activity" to "on relationships between Use Cases, see the Structure the Use-Case Model activity". In other words, bold the activity name.

Chapter 7

  • Page 127: Footnote 12. Second sentence. The text "The stereotypes are only used..." should read "The stereotypes and icons are only used...".
  • Chapter 8
  • Page 148: Figure 8.5. The line between client and FrontController should not be a solid line, but a dashed line with an arrowhead at the FrontController end. This line should also be labeled with "send request." See corrected PDF file on this site.
  • Page 150: Figure 8.7. The line between client and FrontController should not be a solid line, but a dashed line with an arrowhead at the FrontController end. This line should also be labeled with "send request." The BusinessEntity element should have the stereotype ‹‹EJBEntityBean›› and not ‹‹EJBSessionBean››. See corrected PDF file on this site.
  • Page 161: Figure 8.16. The AuctionEJB, BidEJB and CategoryEJB elements should all have the stereotype ‹‹EJBEntityBean›› and not ‹‹EJBSessionBean››. See corrected PDF file on this site.
  • Page 166: Figure 8.20. The stereotyped "use" between the PresentationRequestController and the CreateAuctionDispatcher should be removed. The stereotype ‹‹use›› should be placed next to the dashed line between AuctionManagerDelegate and AuctionManagerHomeLocator, and next to the dashed line between UserAccountManagerDelegate and UserAccountManagerHomeLocator. See corrected PDF file on this site.
  • Page 182: Third paragraph. Third sentence. The stereotype ‹‹interface realization›› should read ‹‹InterfaceRealization››.

Chapter 10

  • Page 231: Footnote 3. This should read "The Deployment Model shows the allocation of implementation elements to system nodes".

Appendix C

Add the following term and definition at their correct position in the Glossary:

Enterprise Component     A software implementation of a business concept or business process. It is a collection of related elements that should be a unit of design, implementation and deployment.

Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020