Surviving Object-Oriented Projects

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-oriented projects, and an appendix collects these workable guidelines and solutions into brief icrib sheetsio ideal for handy reference.

0201498340B06012001

(Pearson)

Bli först med att recensera och betygsätt boken Surviving Object-Oriented Projects - du kan vinna 200 kr varje månad i tävlingen "Månadens recension".

Alistair Cockburn is a recognized expert on use cases. He is consulting fellow at Humans and Technology, where he is responsible for helping clients succeed with object-oriented projects. He has more than twenty years of experience leading projects in hardware and software development in insurance, retail, and e-commerce companies and in large organizations such as the Central Bank of Norway and IBM. 0201498340AB07302002

(Pearson)

Preface.


Acknowledgements.


1. Success and Failure.

Basic Concepts.

Object Technology.

Class.

Object.

Inheritance.

Encapsulation.

Polymorphism.

Framework.

Incremental and Iterative Development.

2. Project Expectations.

Project Histories.

Alfred: Success with Changing Requirements.

@AHEADS = Brooklyn Union Gas: Success Through Attentiveness.

Ingrid: Success in Migrating to C++.

Manfred: Failure in Prototyping.

Mentor Graphics: Trouble Migrating to C++.

Object Technology International: Success in Productivity and Speed.

Reginald: Failure with Changing Rules.

Stanley: Too Much Cutting Edge.

Tracy: Failure Through Naivete.

Udall: Success by Restarting Smaller.

Winifred: Inattentive but Persistent.

Possible Benefits of Object Technology.

Responsiveness to Variations on a Theme.

Responsiveness to Change.

Time-to-Market.

Communication Between Developers, Users, and Executives.

Maintainability.

Reuse.

Productivity.

Window-Based User Interfaces.

Morale.

Automated Code Generation.

Software Process.

OO Design, Encapsulation, and System Evolution (Tom Morgan).

Costs.

Are You Underestimating.

Time to Get New Developers Productive.

Immaturity of the OO Industry.

Hazards of C++.

The Difficulty of Reuse.

Establishing a Software Process.

Business Modeling versus Software Design.

The Cost of CASE Modeling Tools.

Probable Costs.

Nonobject Issues Checklists.

3. Selecting and Setting Up an OO Project.

Project Suitability.

Variations on a Theme.

Simplified Program Structure.

Memory Management Features.

What Is Not Suited.

Project Purpose.

SWAT.

Investigative.

Production.

Full-Commit.

Other Project Categories.

People.

Executive Sponsor.

Project Manager.

Technical Lead.

Technical Staff.

Users.

Personality Types.

Technology.

The Selection Process.

One Person is Persuasive or Stubborn.

The Team Knows a Similar Technology.

The Technology is Safe, Popular, or Standard.

The Technology is the Rational Choice.

Programming Languages.

Managing Smalltalk.

Managing C++.

...

(Pearson)