Buy Our Books
An Introduction to the Rational Unified Process – Philippe Kruchten
"The Rational Unified Process, Third Edition," is a concise introduction to IBM's Web-enabled software engineering process. Rational Unified Process(R), or RUP(R), Lead Architect Philippe Kruchten quickly and clearly describes the concepts, structure, content, and motivation that are central to the RUP. Readers will learn how this approach to software development can be used to produce high-quality software, on schedule and on budget, using the Unified Modeling Language (UML), software automation, and other industry best practices.
The RUP unifies the entire software development team and optimizes the productivity of each team member by bringing them the experience of industry leaders and lessons learned from thousands of projects. It provides detailed and practical guidance through all phases of the software development life cycle, but it is not inflexible. The RUP can be tailored to suit a wide variety of projects and organizations.
The Rational Unified Process Made Easy – Per Kroll, Philippe Kruchten
Per Kroll and Philippe Kruchten are especially well suited to explain the RUP...because they have been the central forces inside Rational Software behind the creation of the RUP and its delivery to projects around the world.""--From the Foreword by Grady Booch This book is a comprehensive guide to modern software development practices, as embodied in the Rational Unified Process, or RUP. With the help of this book's practical advice and insight, software practitioners will learn how to tackle challenging development projects--small and large--using an iterative and risk-driven development approach with a proven track record.
"The Rational Unified Process Made Easy" will teach you the key points involved in planning and managing iterative projects, the fundamentals of component design and software architecture, and the proper employment of use cases. All team members--from project managers to analysts, from developers to testers--will learn how to immediately apply the RUP to their work. You will learn that the RUP is a flexible, versatile process framework that can be tailored to suit the needs of development projects of all types and sizes. Key topics covered include: How to use the RUP to develop iteratively, adopt an architecture-centric approach, mitigate risk, and verify software quality. Tasks associated with the four phases of the RUP: Inception, Elaboration, Construction, and Transition, Roles and responsibilities of project managers, architects, analysts, developers, testers, and process engineers in a RUP project Incrementally adopting the RUP with minimal risk Common patterns for failure with the RUP--and how to avoid them Use this book to get quickly up to speed with the RUP, so you can easily employ the significant power of this process to increase the productivity of your team.
Patterns for Effective Use Cases – Steve Adolph, Paul Bramble, Andy Pols, Alistair Cockburn
Writing use cases was supposed to be easy. One reason for their popularity is that a well-written use case is relatively easy to read. People may suppose that easy to read also means easy to write, but that is a mistake. It can be terribly hard to write easy to read stories. An understanding of basic principles is not enough, software developers need an objective criteria by which they can judge quality and effectiveness.
Patterns for Effective Use Cases provides this set of objective criteria. Written by experienced use case practitioners, this book fills a critical information gap by presenting a pattern language providing simple, elegant and proven solutions to the most common problems in use case development.
This book is organized as a catalog of three dozen patterns offering criteria for evaluating the quality of use cases. Each pattern describes a specific guideline or “sign of quality” that you can use to judge the caliber of a use case in a particular area. Because each organization has its own culture and its own way of doing things, use cases that work well for one organization may completely miss the mark in another. Patterns document generalized solutions and as such provide a simple and yet effective mechanism for describing the characteristics of quality use cases. As such, patterns can transcend organizational differences, allowing people to tailor the solution to their specific needs.