فرآیند یکپارچه منطقی: مقدمه‌ای بر آن (ویرایش سوم)

The Rational Unified Process is a software engineering process developed and marketed by Rational Software. It is a disciplined approach to assigning and managing tasks and responsibilities in a development organization. The goal of this process is to produce, within a predictable schedule and budget, high-quality software that meets the needs of its end users. The Rational Unified Process captures many of the best practices in modern software development and presents them in a tailorable form that is suitable for a wide range of projects and organizations. The Rational Unified Process delivers these best practices to the project team online in a detailed, practical form. This book provides an introduction to the concepts, structure, contents, and motivation of the Rational Unified Process. Goals of This Book In this book, you will learn what the Rational Unified Process is and what it is not; master the vocabulary of the Rational Unified Process and understand its structure; develop an appreciation for the best practices that we have synthesized in this process; and understand how the Rational Unified Process can give you the guidance you need for your specific responsibility in a project. This book is an integral part of the Rational Unified Process, but it is not the complete Rational Unified Process. Rather, it is a small subset. In the full Rational Unified Process you will find the detailed guidance needed to carry out your work. The full Rational Unified Process product - the online knowledge base - can be obtained from Rational Software. This book makes numerous references to the Unified Modeling Language (UML), but it is not an introduction to the UML.That is the focus of two other books: The Unified Modeling Language User Guide and The Unified Modeling Language Reference Manual. This introductory book speaks about modeling and object-oriented techniques, but it is not a design method, and it does not teach you how to model. Detailed steps and guidance on the various techniques that are embedded in the Rational Unified Process can be found only in the process product. Several chapters of this book discuss project management issues. They describe aspects of planning an iterative development, managing risks, and so on. This book, however, is by no means a complete manual on project management and software economics. For more information, we refer you to the book Software Project Management: A Unified Framework. The Rational Unified Process is a specific and detailed instance of a more generic process described in the textbook The Unified Software Development Process. Who Should Read This Book? The Rational Unified Process, An Introduction, Second Edition is written for a wide range of people involved in software development: project managers, developers, quality engineers, process engineers, method specialists, system engineers, and analysts. This book is relevant especially to members of an organization that has adopted the Rational Unified Process or is about to adopt it. It is likely that an organization will tailor the Rational Unified Process to suit its needs, but the core process described in this book should remain the common denominator across all instances of the Rational Unified Process. This book will be a useful companion to students taking one of the many professional education courses delivered by Rational Software and its partners in industry and academia. It provides a general context for the specific topics covered by the course. This book assumes that you have a basic understanding of software development. It does not require specific knowledge of a programming language, of an object-oriented method, or of the Unified Modeling Language. Cover......Page 1 Contents......Page 8 Preface......Page 14 Part I: The Process......Page 20 The Value of Software......Page 22 Symptoms and Root Causes of Software Development Problems......Page 23 Software Best Practices......Page 24 Develop Software Iteratively......Page 25 Manage Requirements......Page 27 Use Component-Based Architectures......Page 28 Visually Model Software......Page 30 Continuously Verify Software Quality......Page 32 Control Changes to Software......Page 33 The Rational Unified Process......Page 34 Summary......Page 35 What Is the Rational Unified Process?......Page 36 The Rational Unified Process as a Product......Page 37 Software Best Practices in the Rational Unified Process......Page 42 Other Key Features of the Rational Unified Process......Page 48 A Brief History of the Rational Unified Process......Page 51 Summary......Page 52 A Model of the Rational Unified Process......Page 54 Roles......Page 55 Activities......Page 57 Artifacts......Page 59 Disciplines......Page 63 Workflows......Page 64 Additional Process Elements......Page 66 Summary......Page 70 The Sequential Process......Page 72 Overcoming Difficulties: Iterate!......Page 79 Gaining Control: Phases and Milestones......Page 81 A Shifting Focus across the Cycle......Page 84 Phases Revisited......Page 85 Benefits of an Iterative Approach......Page 95 Summary......Page 97 The Importance of Models......Page 100 The Importance of Architecture......Page 101 A Definition of Architecture......Page 103 Architecture Representation......Page 104 An Architecture-Centric Process......Page 109 The Purpose of Architecture......Page 111 Component-Based Development......Page 112 Other Architectural Concepts......Page 113 Summary......Page 115 Definitions......Page 116 Identifying Use Cases......Page 122 Evolving Use Cases......Page 123 Organizing Use Cases......Page 124 Use Cases in the Process......Page 126 Summary......Page 128 Part II: Process Disciplines......Page 130 Purpose......Page 132 Planning an Iterative Project......Page 133 The Concept of Risk......Page 136 The Concept of Measurement......Page 138 Roles and Artifacts......Page 141 Workflow......Page 142 Building an Iteration Plan......Page 152 Summary......Page 158 Purpose......Page 160 Why Business Modeling?......Page 161 Using Software Engineering Techniques for Business Modeling......Page 162 Business Modeling Scenarios......Page 164 Roles and Artifacts......Page 165 Workflow......Page 167 From the Business Models to the Systems......Page 169 Modeling the Software Development Business......Page 174 Summary......Page 175 Purpose......Page 176 What Is a Requirement?......Page 177 Types of Requirements......Page 179 Capturing and Managing Requirements......Page 182 Requirements Workflow......Page 183 Roles in Requirements......Page 185 Artifacts Used in Requirements......Page 187 Tool Support......Page 189 Summary......Page 190 Analysis versus Design......Page 192 How Far Must Design Go?......Page 193 Roles and Artifacts......Page 194 Designing a User-Centered Interface......Page 195 The Analysis Model......Page 196 Artifacts for Real-Time Systems......Page 197 Component-Based Design......Page 198 Workflow......Page 199 Summary......Page 203 Purpose......Page 206 Integration......Page 207 Prototypes......Page 209 Roles and Artifacts......Page 211 Workflow......Page 212 Summary......Page 215 Purpose......Page 216 Testing in the Iterative Lifecycle......Page 218 Dimensions of Testing......Page 220 Roles and Artifacts......Page 223 Workflow......Page 227 Tool Support......Page 231 Summary......Page 232 Purpose......Page 234 The CCM Cube......Page 235 Roles and Artifacts......Page 240 Workflow......Page 242 Tool Support......Page 245 Summary......Page 246 Purpose......Page 248 Roles and Artifacts......Page 251 Workflow......Page 252 Summary......Page 255 Purpose......Page 256 Roles and Artifacts......Page 258 Workflow......Page 261 Summary......Page 264 16 Typical Iteration Plans......Page 266 Defining the Product Vision and the Business Case......Page 267 Building an Architectural Prototype......Page 269 Implementing the System......Page 274 Summary......Page 277 Introduction......Page 278 The Effect of Implementing a Process......Page 279 Implementing the Rational Unified Process Step by Step......Page 281 Implementing a Process Is a Project......Page 288 Summary......Page 290 Appendix A: Summary of Roles......Page 292 Appendix B: Summary of Artifacts......Page 296 Appendix C: Acronyms......Page 300 C......Page 302 D......Page 303 I......Page 304 P......Page 305 R......Page 306 T......Page 307 W......Page 308 Bibliography......Page 310 A......Page 318 B......Page 319 C......Page 320 E......Page 321 I......Page 322 P......Page 323 R......Page 325 S......Page 326 T......Page 327 V......Page 328 X......Page 329 The Rational Unified Process (RUP) is a saleable product from Rational/IBM.The RUP unifes the entire software development team and seeks to optimizethe productivity of each and every team member by putting the collectiveexperience derived from thousands of development projects and many industryleaders at the user's fingertips. It is a very popular product, and this bookrepresents the most thorough documentation for the latest version of theproduct (RUP v2003), which was released in May of 2003. Annotation Reflects all of the changes that were integrated into RUP v2003-the latest version of the very popular produc t Learn the key concepts, fundamentals of structure, integral content, and motivation behind the RUP Covers all phases of the software development lifecycle -from concept, to delivery, to revision Provides a concise introduction to IBM's Web-enabled software engineering process. This book describes the concepts, structure, content, and motivation that are central to the Rational Unified Process (RUP). It provides detailed and practical guidance through various phases of the software development life cycle.