OpenUP

Abstract: (NOTE: Each chapter concludes with a summary.) Preface. I. THE PROCESS. 1. Software Development Best Practices. The Value of Software. Symptoms and Root Causes of Software Development Problems. Software Best Practices. Develop Software Iteratively. Manage Requirements. Use Component-Based Architectures. Visually Model Software. Continuously Verify Software Quality. Control Changes to Software. The Rational Unified Process. 2. The Rational Unified Process. What Is the Rational Unified Process? The Rational Unified Process as a Product. Software Best Practices in the Rational Unified Process. Other Key Features of the Rational Unified Process. A Brief History of the Rational Unified Process. 3. Static Structure: Process Description. A Model of the Rational Unified Process. Roles. Activities. Artifacts. Disciplines. Workflows. Additional Process Elements. A Process Framework. 4. Dynamic Structure: Iterative Development. The Sequential Process. Overcoming Difficulties: Iterate! Gaining Control: Phases and Milestones. A Shifting Focus across the Cycle. Phases Revisited. Benefits of an Iterative Approach. 5. An Architecture-Centric Process. The Importance of Models. Architecture. The Importance of Architecture. A Definition of Architecture. Architecture Representation. An Architecture-Centric Process. The Purpose of Architecture. Component-Based Development. Other Architectural Concepts. 6. A Use-Case-Driven Process. Definitions. Identifying Use Cases. Evolving Use Cases. Organizing Use Cases. Use Cases in the Process. II. PROCESS DISCIPLINES. 7. The Project Management Discipline. Purpose. Planning an Iterative Project. The Concept of Risk. The Concept of Measurement. Roles and Artifacts. Workflow. Building an Iteration Plan. 8. The Business Modeling Discipline. Purpose. Why Business Modeling? Using Software Engineering Techniques for Business Modeling. Business Modeling Scenarios. Roles and Artifacts. Workflow. From the Business Models to the Systems. Modeling the Software Development Business. Tool Support. 9. The Requirements Discipline. Purpose. What Is a Requirement? Types of Requirements. Capturing and Managing Requirements. Requirements Workflow. Roles in Requirements. Artifacts Used in Requirements. Tool Support. 10. The Analysis and Design Discipline. Purpose. Analysis versus Design. How Far Must Design Go? Roles and Artifacts. Designing a User-Centered Interface. The Design Model. The Analysis Model. The Role of Interfaces. Artifacts for Real-Time Systems. Component-Based Design. Workflow. Tool Support. 11. The Implementation Discipline. Purpose. Builds. Integration. Prototypes. Roles and Artifacts. Workflow. Tool Support. 12. The Test Discipline. Purpose. Testing in the Iterative Lifecycle. Dimensions of Testing. Roles and Artifacts. Workflow. Tool Support. 13. The Configuration and Change Management Discipline. Purpose. The CCM Cube. Roles and Artifacts. Workflow. Tool Support. 14. The Environment Discipline. Purpose. Process Engineering Process. Roles and Artifacts. Workflow. Tool Support. 15. The Deployment Discipline. Purpose. Roles and Artifacts. Workflow. 16. Typical Iteration Plans. Defining the Product Vision and the Business Case. Building an Architectural Prototype. Implementing the System. 17. Implementing the Rational Unified Process. Introduction. The Effect of Implementing a Process. Implementing the Rational Unified Process Step by Step. Implementing a Process Is a Project. Appendix A: Summary of Roles. Appendix B: Summary of Artifacts. Appendix C: Acronyms. Glossary. Bibliography. Index. 0321197704T11172003

Abstract: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Abstract: Producing a commercial-quality plug-in means going above and beyond the minimal requirements needed to integrate with Eclipse It means attending to all those details that contribute to the fit and polish of a commercial offering This comprehensive guide covers the entire process of plug-in development, including all the extra steps needed to achieve the highest quality resultsBuilding on two internationally best-selling previous editions, Eclipse Plug-ins, Third Edition, has been fully revised to reflect the powerful new capabilities of Eclipse 34 Leading Eclipse experts Eric Clayberg and Dan Rubel present detailed, practical coverage of every aspect of plug-in development, as well as specific, proven solutions for the challenges developers are most likely to encounter All code examples, relevant API listings, diagrams, and screen captures have been thoroughly updated to reflect both the Eclipse 34 API and the latest Java syntax In addition, Clayberg and Rubel have completely revamped their popular Favorites View case study, reworking much of its content and recreating its code from scratch The authors carefully cover new functionality added to existing Eclipse features, such as views and editors, and fully explain brand-new features such as Commands, GEF, and PDE BuildThis extensively revised edition Thoroughly covers Eclipses new preferencesIlluminates the powerful new Eclipse Command Framework, which replaces Eclipses older Action FrameworkPresents extensive new discussions of using commands with views and editorsIntroduces Mylyn, the new task-focused interface that reduces information overload and simplifies multi-taskingContains an all-new chapter on using the Graphical Editing Framework (GEF) to build dynamic, interactive graphical user interface elementsWalks you step by step through the entire PDE Build processShows how to create update sites with p2, which replaces Eclipses old Update Manager This book is designed for every experienced developer interested in extending the Eclipse platform, the Rational Software Development Platform, or any other platform that supports Eclipse plug-ins

Abstract: The book starts with a useful overview of the history, motivation, key concepts, and terminology of the Univied Process. The author then details the five pillars of development: requirements, analysis, design, implementation, and test workflows. In addition, the book enumerates the four phases of Unified Process development: inception, elaboration, construction, and transition; and it shows how the workflows are integrated into these phases. In laying out the details of this integration, the book illustrates the Unified Process's most useful feature --- its iterative nature.