زنده ماندن در پروژه‌های شیءگرا

Although much has been written about object technology and the benefits of this paradigm, there is still a shortage of compiled knowledge about what to expect and to plan for during project implementation. This book provides information that managers need to combat the unforeseen challenges that await them, allowing them to survive and ultimately succeed with an object-oriented project. To provide practical advice and guidelines for successfully managing an object-oriented project, the author borrows from the seasoned wisdom of numerous experts and successful consultants while also drawing on his personal experience and extensive knowledge. Surviving Object-Oriented Projects: A Managers Guide points out potential hazards and names workable solutions by addressing the important issues of scheduling, budgeting, staffing, and cost justification. Key points are supported and illustrated through short case studies taken from real object-oriented projects, and an appendix collects these workable guidelines and solutions into brief crib sheets ideal for handy reference. Cover......Page 1 Contents......Page 10 Foreword......Page 14 Preface......Page 16 Acknowledgments......Page 22 1.1 Why Use Cases at All?......Page 24 1.2 What’s So Hard about Telling Good Stories?......Page 25 1.3 Why a Use Case Pattern Language?......Page 28 1.4 What Are Patterns?......Page 29 1.5 How Should I Use This Pattern Language?......Page 32 1.6 What Is the Use Case Pattern Form?......Page 33 Stepping through a Sample Pattern......Page 34 Development Patterns......Page 42 Structural Patterns......Page 44 1.8 Supplement: A Brief Tutorial on Writing Use Cases......Page 46 Chapter 2 The Team......Page 52 2.1 Team Organizational Issues......Page 53 2.2 SmallWritingTeam......Page 54 Examples......Page 56 2.3 ParticipatingAudience......Page 58 Examples......Page 60 2.4 BalancedTeam......Page 62 Examples......Page 64 2.5 Trade-offs and Collaborations......Page 66 Chapter 3 The Process......Page 68 3.1 BreadthBeforeDepth......Page 71 BreadthBeforeDepth and UML......Page 74 3.2 SpiralDevelopment......Page 75 Examples......Page 77 SpiralDevelopment and UML Models......Page 80 3.3 MultipleForms......Page 81 Examples......Page 83 3.4 TwoTierReview......Page 87 Examples......Page 89 3.5 QuittingTime......Page 91 Examples......Page 94 3.6 WritersLicense......Page 96 3.7 Trade-offs and Collaborations......Page 98 Chapter 4 The Use Case Set......Page 100 4.1 SharedClearVision......Page 103 Examples......Page 105 4.2 VisibleBoundary......Page 109 Examples......Page 111 VisibleBoundary and UML Models......Page 112 4.3 ClearCastOfCharacters......Page 113 Examples......Page 115 4.4 UserValuedTransactions......Page 118 Examples......Page 121 4.5 EverUnfoldingStory......Page 125 Examples......Page 127 EverUnfoldingStory and UML Models......Page 134 4.6 Trade-offs and Collaborations......Page 136 Chapter 5 The Use Case......Page 138 5.1 CompleteSingleGoal......Page 141 Examples......Page 144 5.2 VerbPhraseName......Page 145 Examples......Page 146 5.3 ScenarioPlusFragments......Page 148 Examples......Page 151 5.4 ExhaustiveAlternatives......Page 152 Examples......Page 154 5.5 Adornments......Page 156 Examples......Page 158 5.6 PreciseAndReadable......Page 161 Examples......Page 163 5.7 Trade-offs and Collaborations......Page 165 Chapter 6 Scenarios and Steps......Page 168 6.1 DetectableConditions......Page 171 Examples......Page 173 6.2 LeveledSteps......Page 176 Examples......Page 177 6.3 ActorIntentAccomplished......Page 181 Examples......Page 182 6.4 ForwardProgress......Page 185 Examples......Page 186 6.5 TechnologyNeutral......Page 190 Examples......Page 192 6.6 Trade-offs and Collaborations......Page 194 Chapter 7 Use Case Relationships......Page 196 7.1 CommonSubBehavior......Page 199 Examples......Page 201 CommonSubBehavior and UML......Page 203 7.2 InterruptsAsExtensions......Page 205 Examples......Page 207 InterruptsAsExtensions and UML......Page 209 Extensions and UML Extension Points......Page 210 7.3 PromotedAlternative......Page 213 Examples......Page 214 PromotedAlternative and UML......Page 218 7.4 Trade-offs and Collaborations......Page 219 7.5 CapturedAbstraction—A Pattern for Applying UML Generalization......Page 221 Examples......Page 222 CapturedAbstraction and UML......Page 223 Chapter 8 Editing Existing Use Cases......Page 224 8.1 RedistributeTheWealth......Page 227 Examples......Page 229 8.2 MergeDroplets......Page 232 Examples......Page 234 8.3 CleanHouse......Page 236 8.4 Trade-offs and Collaborations......Page 238 References......Page 240 Photo Credits......Page 242 A......Page 246 C......Page 247 D......Page 248 E......Page 249 G......Page 250 M......Page 251 P......Page 252 R......Page 253 S......Page 254 T......Page 255 U......Page 256 W......Page 258 X......Page 259

Global competition, the time sensitivity of the new Internet economy, and increasing customer demand for better software quality are pushing companies to undertake software process improvement (SPI) initiatives. Numerous software organizations worldwide have implemented these initiatives with varying degrees of success. Many have adhered to standard SPI practice, only to experience less-than-satisfactory results when the execution proves more difficult than expected and enthusiasm and resources wane.

Improving Software Organizations offers a modern perspective on SPI. It outlines and discusses what it takes to move from SPI theory to successful SPI initiatives. Based on the results of the three-year National Danish SPI Initiative, this book draws on the experiences of four world-class companies—Danske Data, Brüel & Kjær, Ericsson Denmark, and Systematic Software Engineering. It presents a proven roadmap for successful SPI. It distills in-depth studies of these organizations—the strategies, approaches, and specific techniques that yielded tangible results. It presents a comprehensive framework for planning and executing successful SPI projects throughout the project lifecycle.

Improving Software Organizations presents the major lessons learned in the four companies. It provides an overview of the theories and models that formed the basis of the SPI initiatives. It also provides an in-depth examination of the four companies¿ development organizations, how each began the SPI initiative, what mistakes were made, and how they ultimately succeeded.

You will learn:

• The five key principles of the SPIfocus on problems, emphasize knowledge creation, encourage participation, integrate leadership, and plan for continuous improvement
• How diverse companies adapt standard
• SPI theory to achieve desired results
• How to structure learning conditions in SPI initiatives
• Maturity level assessments, including CMM, BOOTSTRAP, and other customized approaches
• Knowledge transfer, customer maturity, and organizational learning
• Proper paths for carrying out risk assessments
• The specifics of implementing a metrics program
• Tips on improving requirements specification

For each of the five SPI principles, the book offers examples from practice that demonstrate how successful organizations approached the issue. From these examples and the more detailed case studies, you will gain the understanding of how to design, implement, and execute an SPI initiative that is right for your organization.

Writing use cases as a means of capturing the behavioral requirements of software systems and business processes is a practice that is quickly gaining popularity. Use cases provide a beneficial means of project planning because they clearly show how people will ultimately use the system being designed. On the surface, use cases appear to be a straightforward and simple concept. Faced with the task of writing a set of use cases, however, practitioners must ask: "How exactly am I supposed to write use cases?" Because use cases are essentially prose essays, this question is not easily answered, and as a result, the task can become formidable.

In Writing Effective Use Cases, object technology expert Alistair Cockburn presents an up-to-date, practical guide to use case writing. The author borrows from his extensive experience in this realm, and expands on the classic treatments of use cases to provide software developers with a "nuts-and-bolts" tutorial for writing use cases. The book thoroughly covers introductory, intermediate, and advanced concepts, and is, therefore, appropriate for all knowledge levels. Illustrative writing examples of both good and bad use cases reinforce the author's instructions. In addition, the book contains helpful learning exercises—with answers—to illuminate the most important points.

Highlights of the book include:

• A thorough discussion of the key elements of use cases—actors, stakeholders, design scope, scenarios, and more
• A use case style guide with action steps and suggested formats
• An extensive list of time-saving use case writing tips
• A helpful presentation of use case templates, with commentary on when and where they should be employed
• A proven methodology for taking advantage of use cases

With this book as your guide, you will learn the essential elements of use case writing, improve your use case writing skills, and be well on your way to employing use cases effectively for your next development project.

Booknews

A specialist in object technology presents software developers with a current guide to writing use cases as a means of capturing the behavioral requirements of software systems and business practices. Covers key elements of use cases, a style guide with suggested formats, a list of time-saving writing tips, a set of use case templates with commentary, and learning exercises with answers to clarify important points. Annotation c. Book News, Inc., Portland, OR (booknews.com)

"Coming of age for software developers means understanding that software is a cooperative effort, not something individuals do in isolation. This is a book that teams of software developers can thrive upon, full of sensible advice for a cooperative development approach."

--Tom DeMarco, The Atlantic Systems Guild

Software development paradigms are shifting. The development group's "team" ability, and the effects of the individual developer, become more important as organizations recognize that the traditional approach of increasing process pressure and overworking team members is not meeting getting the job done. The pioneers of Agile methodologies question the preconceived processes within which development teams work. Rather than adding to the burden of the individual developer, Agile asks "how can we change the process so that the team is more productive, while also improving quality?" The answer is in learning to play the "game."

Written for developers and project managers, Agile Software Development compares software development to a game. Team members play the game knowing that the ultimate goal is to win--always remembering what they have learned along the way, and always keeping in mind that they will never play the same way twice. Players must keep an open mind to different methodologies, and focus on the goal of developing quality software in a short cycle time.

Based on a decade's work and research, and interviews with software project teams, this book presents sound advice for bringing difficult projects to successful conclusion with a minimum of stress. It includes advice on:

• The principals behind agilemethodologies
• Which methodologies fit different projects--including appendixes to select the appropriate methodology on a project
• New vocabulary for describing methodologies
• Just-in-time methodology tuning
• Managing the incompleteness of communication
• Continuous methodology reinvention
• The manifesto for agile software development

Today's software developers need to recognize that they have a number of methodologies to choose from. With this book as a guide, they can break free of nonproductive habits, move beyond old routines, and clear a new path to success.

today, Many Organizations Claim Competitive Market Advantages Resulting From The Application Of Object-oriented Technology And Approaches In Their Software Development Efforts. As The Use Of Object Technology Has Become Increasingly Widespread And Mainstream, A Growing Number Of Project Managers Are Faced With A Daunting Task: Keeping The Object Technology Project On Track And Within Budget. These Project Managers Are Burdened By The Weight Of Knowing That The Survival And Ultimate Success Of The Project Hinges On Their Insight When Planning The Project And Their Responses To Events That Lie Ahead. Unfortunately, Hidden Costs, Unpleasant Surprises And Unrealistic Expectations Lie In Wait For The Unprepared Manager.

Although Much Has Been Written About Object Technology And The Benefits Of This Paradigm, There Is Still A Shortage Of Compiled Knowledge About What To Expect And To Plan For During Project Implementation. This Book Provides Information That Managers Need To Combat The Unforeseen Challenges That Await Them, Allowing Them To Survive And Ultimately Succeed With An Object-oriented Project.

To Provide Practical Advice And Guidelines For Successfully Managing An Object-oriented Project, The Author Borrows From The Seasoned Wisdom Of Numerous Experts And Successful Consultants While Also Drawing On His Personal Experience And Extensive Knowledge. surviving Object-oriented Projects: A Manageris Guide Points Out Potential Hazards And Names Workable Solutions By Addressing The Important Issues Of Scheduling, Budgeting, Staffing, And Cost Justification. Key Points Are Supported And Illustrated Through Short Case Studies Taken From Real Object-orientedprojects, And An Appendix Collects These Workable Guidelines And Solutions Into Brief Icrib Sheetsio Ideal For Handy Reference.

booknews

synthesizing The Insights Of Managers And Consultants Who Have Lived To Tell The Tale, Offers Advice On Keeping A Software Development Project Using Object-oriented Technology And Approaches On Track And Within Budget Despite The Inevitable Pitfalls That Await. Includes A Tear-out Crib Sheet With Handy Data And Some Soothing Mantras To Chant. Annotation C. By Book News, Inc., Portland, Or.

In a highly volatile software development environment, developers must be nimble, responsive, and able to hit a moving target--in short, they must be agile. Agile software development is designed to address this need for speed and flexibility. Agility describes a holistic, collaborative environment in which you can both create and respond to change by focusing on adaptability over predictability, people over process. Agile software development incorporates proven software engineering techniques, but without the overhead and restrictions of traditional development methodologies. Above all, it fulfills its promise of delivering software that serves the client's business needs.

Written by one of the leaders of the Agile movement, and including interviews with Agile gurus Kent Beck, Robert Charette, Alistair Cockburn, Martin Fowler, Ken Schwaber, and Ward Cunningham, Agile Software Development Ecosystems crystallizes the current understanding of this flexible and highly successful approach to software development. It presents the key practices of all Agile development approaches, offers overviews of specific techniques, and shows how you can choose the approach that best suits your organization.

This book describes--in depth--the most important principles of Agile development: delivering value to the customer, focusing on individual developers and their skills, collaboration, an emphasis on producing working software, the critical contribution of technical excellence, and a willingness to change course when demands shift. All major Agile methods are presented:

• Scrum
• Dynamic Systems Development Method
• Crystal Methods
• Feature-Driven Development
• Lean Development
• Extreme Programming
• Adaptive Software Development

Throughout the book, case stories are used to illustrate how Agile practices empower success around the world in today's chaotic software development industry. Agile Software Development Ecosystems also examines how to determine your organization's Agile readiness, how to design a custom Agile methodology, and how to transform your company into a truly Agile organization.

0201760436B03042002

Surviving Object-Oriented Projects is an extraordinary compendium of useful strategies for organizing object-oriented projects. Independent of language or programming environment, it explains how to build good OO software despite all the conflicting forces at work. For all those OO projects that have set sail with no more than high concepts and a shiny new language, this book is the compass that will see them safely through."- Jeremy Raw, Independent Consultant Today , many organizations claim competitive market advantages resulting from the application of object-oriented technology and approaches in their software development efforts. As the use of object technology has become increasingly widespread and mainstream, a growing number of project managers are faced with a daunting keeping the object technology project on track and within budget. These project managers are burdened by the weight of knowing that the survival and ultimate success of the project hinges on their insight when planning the project and their responses to events that lie ahead. Unfortunately, hidden costs, unpleasant surprises and unrealistic expectations lie in wait for the unprepared manager. Although much has been written about object technology and the benefits of this paradigm, there is still a shortage of compiled knowledge about what to expect and to plan for during project implementation. This book provides information that managers need to combat the unforeseen challenges that await them, allowing them to survive and ultimately succeed with an object-oriented project. To provide practical advice and guidelines for successfully managing an object-oriented project, the author borrows from the seasoned wisdom of numerous experts and successful consultants while also drawing on his personal experience and extensive knowledge. Surviving Object-Oriented A Manager's Guide points out potential hazards and names workable solutions by addressing the important issues of scheduling, budgeting, staffing, and cost justification. Key points are supported and illustrated through short case studies taken from real object-oriented projects, and an appendix collects these workable guidelines and solutions into brief "crib sheets"- ideal for handy reference. Writing use cases as a means of capturing the behavioral requirements of software systems and business processes is a practice that is quickly gaining popularity. Use cases provide a beneficial means of project planning because they clearly show how people will ultimately use the system being designed. On the surface, use cases appear to be a straightforward and simple concept. Faced with the task of writing a set of use cases, however, practitioners must ask:'How exactly am I supposed to write use cases?'Because use cases are essentially prose essays, this question is not easily answered, and as a result, the task can become formidable. In Writing Effective Use Cases, object technology expert Alistair Cockburn presents an up-to-date, practical guide to use case writing. The author borrows from his extensive experience in this realm, and expands on the classic treatments of use cases to provide software developers with a'nuts-and-bolts'tutorial for writing use cases. The book thoroughly covers introductory, intermediate, and advanced concepts, and is, therefore, appropriate for all knowledge levels. Illustrative writing examples of both good and bad use cases reinforce the author's instructions. In addition, the book contains helpful learning exercises--with answers--to illuminate the most important points. Highlights of the book include: A thorough discussion of the key elements of use cases--actors, stakeholders, design scope, scenarios, and more A use case style guide with action steps and suggested formats An extensive list of time-saving use case writing tips A helpful presentation of use case templates, with commentary on when and where they should be employed A proven methodology for taking advantage of use cases With this book as your guide, you will learn the essential elements of use case writing, improve your use case writing skills, and be well on your way to employing use cases effectively for your next development project.

Use cases have become an integral part of modeling software requirements, but many software developers are discovering that writing effective use cases is more difficult than they had anticipated. An understanding of the basic principles of use cases is not enough. Software developers need a source of objective criteria by which to 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 that contains over thirty patterns, providing simple, elegant, and proven solutions to the most common problems in use case development. These patterns distill and define the properties and characteristics of quality use cases. As such, they facilitate the development of original use cases and provide a diagnostic tool for evaluating existing ones.

The book opens with a review of use cases and pattern fundamentals, along with a discussion of the requirements-gathering team. These patterns address the use case development process, the internal structure of use cases, and the relationships among use cases within the system as a whole. Examples of patterns include:

• BreadthBeforeDepth
• VisibleBoundary
• EverUnfoldingStory
• IntentionRevealingName
• PreciseAndReadable
• LeveledSteps
• InterruptsAsExtensions
• RedistributeTheWealth

Each pattern discussion includes at least one example demonstrating its real-world application, highlighting both the benefits of using the pattern and the consequences of not doing so. In addition, the book presents guidelines for the effective use of UML with relevant patterns.

Anyone involved in use case writing or requirements gathering will find Patterns for Effective Use Cases an indispensable handbook and reference.

0201721848B07302002

-- Not just a lightweight approach: highly scalable and completely customizable!-- Sound advice for completing even the most complex and difficult projects -- without burnout.-- Based on more than ten years of research with highly functional software development teams.Lightweight methodologies are exploding in popularity because their flexibility is ideal for today's fast-changing development environments. In Agile Software Development, legendary software expert Alistair Cockburn reviews the advantages and disadvantages of lightweight methods, synthesizing the field's key lessons into a simplified approach that allows developers to focus on building quality software rapidly, cost-effectively, and without burnout. Ideal for managers seeking to transcend yesterday's failed approaches, the agile movement views software development as a cooperative game. As players move throughout the game, they use markers and props to inform, remind, and inspire themselves and each other. The goal of the game: to deliver a working software system -- and to use the lessons of each project to build a new, smarter "game" for the next project. For every IT executive and manager, software developer, team leader, team member, and client concerned with building robust, cost-effective software. Use cases have never been this easy to understand -- or this easy to create! In Writing Effective Use Cases , Alistair Cockburn offers a hands-on, soup-to-nuts guide to use case development, based on the proven concepts he has refined through years of research, development, and seminar presentations. Cockburn begins by answering the most basic questions facing anyone interested in use cases: "What does a use case look like? When do I write one?" Next, he introduces each key element of use cases: actors, stakeholders, design scope, goal levels, scenarios, and more. Writing Effective Use Cases contains detailed guidelines, formats, and project standards for creating use cases -- as well as a detailed chapter on style, containing specific do's and don'ts. Cockburn shows how use cases fit together with requirements gathering, business processing reengineering, and other key issues facing software professionals. The book includes practice exercises with solutions, as well as a detailed appendix on how to use these techniques with UML. For all application developers, object technology practitioners, software system designers, architects, and analysts. Annotation Use cases have become a very popular requirements-gathering technique, yet many developers struggle when faced with writing them. They grasp the basic concepts, but find that writing effective use cases turns out to be more difficult than they expected. One factor contributing to this difficulty is that the community lacks objective criteria for judging the quality of use cases. This new book articulates the qualities of effective use cases by applying the proven patterns concept of development to this requirements-gathering technique. The authors present a catalog of thirty-six patterns that help the reader become proficient at judging the quality of their (and other's) patterns. These patterns represent solutions to recurring problems that application developers have faced in writing use cases. Each pattern is presented with examples that help the reader understand the benefit of the pattern, and just as importantly, the consequences of ignoring its proper use The survival and ultimate success of an object-oriented software development project hinges on the project manager's prior planning and knowledge of what to expect and his or her active management to keep the project on track. This guide will help managers gain that background as it explores issues of scheduling, budgeting, staffing, and cost justification, all supported and illustrated by short case studies of actual projects. Simple, elegant, and proven solutions to the specific problems of writing use cases on real projects, this workbook has 36 specific guidelines that readers can use to measure the quality of their use cases. This is the first book to specifically address use cases with the proven and popular development concept of patterns. Aimed at development managers and engineers who are frustrated by software processes, this text is practical in that it supplies the major learning points of a three-year collaborative project, and also an overview of the theories and models that form the basis of SPI practice In this book, Jim Highsmith explains what agile software development methods are, how they compare, and how to make the most of them. He includes case studies and interviews with the leaders who are driving each approach Alastair Cockburn offers advice on bringing difficult software development projects to a successful conclusion with a minimum of stress. The volume is based on over 10 years of interviewing software project teams. Presents sound advice for bringing difficult projects to successful conclusion with a minimum of stress. Written for developers and project managers, comparing software development to a game. Softcover. This guide will help readers learn how to employ the significant power of use cases to their software development efforts. It provides a practical methodology, presenting key use case concepts