Surviving Object-Oriented Projects

Surviving Object-Oriented Projects

          
5
4
3
2
1

Out of Stock


Premium quality
Premium quality
Bookswagon upholds the quality by delivering untarnished books. Quality, services and satisfaction are everything for us!
Easy Return
Easy return
Not satisfied with this product! Keep it in original condition and packaging to avail easy return policy.
Certified product
Certified product
First impression is the last impression! Address the book’s certification page, ISBN, publisher’s name, copyright page and print quality.
Secure Checkout
Secure checkout
Security at its finest! Login, browse, purchase and pay, every step is safe and secured.
Money back guarantee
Money-back guarantee:
It’s all about customers! For any kind of bad experience with the product, get your actual amount back after returning the product.
On time delivery
On-time delivery
At your doorstep on time! Get this book delivered without any delay.
Notify me when this book is in stock
Add to Wishlist

About the Book

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

Table of Contents:
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++. Disciplined Use of C++ (Jeremy Raw). Managing OO COBOL. Managing Java. Tools. Upper-CASE Tools. Using Java (Sam Griffith). The Scanner Challenge. Minimum CASE Tool Requirements. The Cutting Edge. Training and Getting Advice. What to Teach. Developers Do Not Know How to Think in Objects. Developers Do Not Know How to Make Design Trade-Offs. Developers Program Poorly or Use Tools Badly. Different Programmers Write Differently, Making The Code Hard to Learn. Developers Create Redundant Classes Because They Do Not Know What Is in the Class Library. No One Knows How to Document a Framework Well. Developers Do Not Understand Their Role On The Project And Who Depends on Them. When to Teach. Getting Advice. Legacy Issues. Mainframes. Relational Databases. Project Setup (C.D.). Review. 4. Getting Started. Methodology. Big-M Methodology. A Base Methodology to Tailor. Discussion of the Methodology. Roles, Skills, Techniques. Tools. Teams. Ownership. Deliverables. Standards. Activities. Building Consumer Understanding of the Design (Ward Cunningham). Estimates. Two Weeks per Noncommercial Class. Domain Classes. Screen Classes. Utility Classes. Frameworks. Plans. An Estimation and Planning Session (Alistair Cockburn). Milestones. Measurements. Take the Time to Design. Design, and Two Smalltalk Projects (K.L.). 5. Making Corrections. A Study Project. Stage 0: The Usual Ignorance. Stage 1: Disaster. Stage 2: Rebuild. Stage 3: Improve. Stage 4: Functioning. Stage 5: Overconfidence in Scaling Up. Lessons From This Study Project. Managing Precision, Accuracy, and Scale. Managing Work According to Precision and Accuracy. Increments and Iterations. Increments and V-W Staging. Iterations. Combining Increments and Iterations. Burn Some Pancakes (Luke Hohmann). Project Increments. Increment 1. The Architecture Team. The Training Team. The Intentions. Two Stories. Increment 2. Pause and Learn. Move On. Increment N. User Involvement. Watching Users (K.L.). Project Teams. Ownership. Involve the Users (Jon Marshall). Total-Ownership Teams. Matrixed Teams. Domain Modeling and Reuse. The Domain Model. Hazardous Situations. The Common Domain Model. Why Are There Multiple Valid Domain Models. PolyBloodyHardReuse. Conflicting Reward Systems. Lack of Trust. I Can Write It Faster Myself. Further Reading. 6. Advice From Hindsight. Costs and Benefits Revisited. Sentences You Hope Never to Hear. Writing 500 Lines of Code per Day. Model the World, Then Code. Design the Screen, Then Code. Iterate Prototypes. Classes. Reuse is Easy. More on Iterations. Self-Test. Two Increments Delivered. Thirty People. Analysts, Programmers, and Tools. Learning OO From the Compiler. Programmers Between Projects. On the Cutting Edge. Designers and Programmers Separated. Six-Month Pilot Started. 7. Expand to Larger Projects. Your First Big Project. Project Charter. Communication. Staffing, Skill Dilution, and Project Teams. Methodology. Increments and Iterations. The Cutting Edge. Domain Modeling. Risk Reduction. PolyBloodyHarderReuse. Class Duplication. Training the Tidal Wave. Ten Lessons the Hard Way (Glenn House). Train Fewer People. Train More Effectively. Training 50 or More People. Set up a Full-Time Classroom Program. Set up 6 to 10 Connected Projects. Use a Full-Time Mentor. Maintain Tight Standards and Review Policies. Rotate People. Productivity. Size. Staff Skill Mix. Team Structure. Even Mix. Progress Team/Training Team. Productivity Changes Over Time. Lines of Code Per Month. Frameworks. Productivity Revisited. Migrating the organization. 8. Rechecking a Case Study. Winifred Revisited. Summary. History. Stage 1: Good Start, with Experience and Support. Stage 2: No Architecture, Almost No First Delivery. Stage 3: New Increment; Add Teams, Mentors, Architecture. Stage 4: Owner per Deliverable; New Infrastructure. Analysis. Relation to Book's Topics. Technology Is Only Part of the Story. Organizations (Jim Coplien). Appendix A. Collected Risk-Reduction Strategies. Appendix B. Crib Sheet. Index 000 0201498340T04062001


Best Sellers


Product Details
  • ISBN-13: 9780201498349
  • Publisher: Pearson Education (US)
  • Publisher Imprint: Addison Wesley
  • Depth: 19
  • Language: English
  • Returnable: N
  • Spine Width: 100 mm
  • Width: 100 mm
  • ISBN-10: 0201498340
  • Publisher Date: 06 Feb 1998
  • Binding: Paperback
  • Height: 100 mm
  • No of Pages: 280
  • Series Title: Agile Software Development Series
  • Weight: 100 gr


Similar Products

How would you rate your experience shopping for books on Bookswagon?

Add Photo
Add Photo

Customer Reviews

REVIEWS           
Click Here To Be The First to Review this Product
Surviving Object-Oriented Projects
Pearson Education (US) -
Surviving Object-Oriented Projects
Writing guidlines
We want to publish your review, so please:
  • keep your review on the product. Review's that defame author's character will be rejected.
  • Keep your review focused on the product.
  • Avoid writing about customer service. contact us instead if you have issue requiring immediate attention.
  • Refrain from mentioning competitors or the specific price you paid for the product.
  • Do not include any personally identifiable information, such as full names.

Surviving Object-Oriented Projects

Required fields are marked with *

Review Title*
Review
    Add Photo Add up to 6 photos
    Would you recommend this product to a friend?
    Tag this Book
    Read more
    Does your review contain spoilers?
    What type of reader best describes you?
    I agree to the terms & conditions
    You may receive emails regarding this submission. Any emails will include the ability to opt-out of future communications.

    CUSTOMER RATINGS AND REVIEWS AND QUESTIONS AND ANSWERS TERMS OF USE

    These Terms of Use govern your conduct associated with the Customer Ratings and Reviews and/or Questions and Answers service offered by Bookswagon (the "CRR Service").


    By submitting any content to Bookswagon, you guarantee that:
    • You are the sole author and owner of the intellectual property rights in the content;
    • All "moral rights" that you may have in such content have been voluntarily waived by you;
    • All content that you post is accurate;
    • You are at least 13 years old;
    • Use of the content you supply does not violate these Terms of Use and will not cause injury to any person or entity.
    You further agree that you may not submit any content:
    • That is known by you to be false, inaccurate or misleading;
    • That infringes any third party's copyright, patent, trademark, trade secret or other proprietary rights or rights of publicity or privacy;
    • That violates any law, statute, ordinance or regulation (including, but not limited to, those governing, consumer protection, unfair competition, anti-discrimination or false advertising);
    • That is, or may reasonably be considered to be, defamatory, libelous, hateful, racially or religiously biased or offensive, unlawfully threatening or unlawfully harassing to any individual, partnership or corporation;
    • For which you were compensated or granted any consideration by any unapproved third party;
    • That includes any information that references other websites, addresses, email addresses, contact information or phone numbers;
    • That contains any computer viruses, worms or other potentially damaging computer programs or files.
    You agree to indemnify and hold Bookswagon (and its officers, directors, agents, subsidiaries, joint ventures, employees and third-party service providers, including but not limited to Bazaarvoice, Inc.), harmless from all claims, demands, and damages (actual and consequential) of every kind and nature, known and unknown including reasonable attorneys' fees, arising out of a breach of your representations and warranties set forth above, or your violation of any law or the rights of a third party.


    For any content that you submit, you grant Bookswagon a perpetual, irrevocable, royalty-free, transferable right and license to use, copy, modify, delete in its entirety, adapt, publish, translate, create derivative works from and/or sell, transfer, and/or distribute such content and/or incorporate such content into any form, medium or technology throughout the world without compensation to you. Additionally,  Bookswagon may transfer or share any personal information that you submit with its third-party service providers, including but not limited to Bazaarvoice, Inc. in accordance with  Privacy Policy


    All content that you submit may be used at Bookswagon's sole discretion. Bookswagon reserves the right to change, condense, withhold publication, remove or delete any content on Bookswagon's website that Bookswagon deems, in its sole discretion, to violate the content guidelines or any other provision of these Terms of Use.  Bookswagon does not guarantee that you will have any recourse through Bookswagon to edit or delete any content you have submitted. Ratings and written comments are generally posted within two to four business days. However, Bookswagon reserves the right to remove or to refuse to post any submission to the extent authorized by law. You acknowledge that you, not Bookswagon, are responsible for the contents of your submission. None of the content that you submit shall be subject to any obligation of confidence on the part of Bookswagon, its agents, subsidiaries, affiliates, partners or third party service providers (including but not limited to Bazaarvoice, Inc.)and their respective directors, officers and employees.

    Accept

    New Arrivals


    Inspired by your browsing history


    Your review has been submitted!

    You've already reviewed this product!
    ASK VIDYA