|
![]() |
|||
|
||||
OverviewTwo of the most significant technological development trends of the past few years have been the Java 2 Platform, Enterprise Edition (J2EE), a platform specifically geared to the needs of enterprise systems, and the Rational Unified Process (RUP), a comprehensive development methodology.Building J2EE' Applications with the Rational Unified Process is the first book to bring these two key development concepts together. Featuring a non-trivial sample application, the book demonstrates a customized subset of RUP that is relevant and essential to J2EE development. The text guides readers through the entire development process, from initial requirements gathering through system implementation, illuminating real-world intricacies, complications, tradeoffs, and decision making.The book presents a review of the latest releases of J2EE and RUP, emphasizing the rationale behind their content. A developer roadmap helps readers navigate the development process successfully, and detailed discussions of each aspect of the process reveal practical strategies and techniques.Also provided is detailed coverage of the key aspects behind any successful software development effort:Requirements, including use-case modeling and the gathering of architecturally significant requirementsAnalysis, including the transformation of requirements into a first-cut design model and a user-experience modelDesign, including the refinement of a design model, introducing interfaces, framework components, design classes, and use-case realizationsImplementation, including the creation of source code and executable code based on the design, and the production of J2EE modules necessary for deployment Architectural concerns, including the production of a Software Architecture Document, Deployment Model, and Data ModelThe use of patterns, in particular J2EE design patternsThe use of UML to model J2EE technologies such as Enterprise JavaBeans'Written for anyone working in J2EE or using RUP, this book is an comprehensive guide that reveals how J2EE and the Rational Unified Process come together to produce a powerful, efficient, and effective approach to enterprise application development. Forewords were prepared by John Crupi, Distinguished Engineer at Sun Microsystems (and coauthor of Core J2EE Patterns, Prentice Hall, 2001), and Philippe Kruchten, Director of RUP Development at Rational Software (and author of The Rational Unified Process, Addison-Wesley, 2000). 0201791668B07242002 Full Product DetailsAuthor: Peter Eeles , Kelli Houston , Wojtek KozaczynskiPublisher: Pearson Education (US) Imprint: Addison Wesley Dimensions: Width: 18.70cm , Height: 1.30cm , Length: 23.50cm Weight: 0.450kg ISBN: 9780201791662ISBN 10: 0201791668 Pages: 288 Publication Date: 02 September 2002 Audience: College/higher education , Tertiary & Higher Education Format: Paperback Publisher's Status: Out of Print Availability: Out of print, replaced by POD ![]() We will order this item for you from a manufatured on demand supplier. Table of Contents(NOTE: Chapters 2-9 conclude with a Summary.) Foreword by Philippe Kruchten. Foreword by John Croupi. Preface. 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. Containers. Presentation Tier. Business Tier. Integration Tier. J2EE Deployment Configurations. J2EE Component Technologies. Applets. 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. Artifacts. Roles. Activities. Disciplines. Workflow Details. Iterations. Phases. 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. Testing. Deployment. Configuration and Change Management. Project Management. Environment. Other Considerations. In Conclusion — A Note from the Authors. Appendix A: Describing a Software Architecture. Introduction. 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. Terms. Acronyms. Index. 0201791668T05172002ReviewsAuthor InformationPeter Eeles works at Rational Software. He is a Senior Technical Consultant in Rational's Strategic Services Organization and assists organizations in their adoption of the Rational Unified Process and the Rational toolset in architecture-centric initiatives. He is coauthor of Building Business Objects (John Wiley & Sons, 1998) and a contributing author to Software Architectures (Springer-Verlag, 1999). Kelli Houston works at Rational Software. She is a Senior Architecture Consultant developing solution packages for accelerating J2EE and .NET development. She is a contributing author to Component-Based Software Engineering (Addison-Wesley, 2001). Wojtek Kozaczynski works at Rational Software. He is the Director of Architecture and Application Frameworks. He develops tools and processes for the development of architecture frameworks and reusable software assets. He is also a contributing author to Component-Based Software Engineering (Addison-Wesley, 2001). 0201791668AB07242002 Tab Content 6Author Website:Countries AvailableAll regions |