Home   FAQs   New Arrivals   Specials   Pricing & Shipping   Location   Corporate Services   Why Choose Bookware?  
Call our store: 9955 5567 (from within Sydney) or 1800 734 567 (from outside Sydney)
 View Cart   Check Out   
Browse by Subject
 TAFE Accounting
 TAFE I.T./Computing
 TAFE - Other
 Windows 8
 Adobe CS6
 CCNA 2012
 CCNP 2012
 Web Design
 Project Management
 Mobile Devices
 Windows Server 2012
 SQL Server 2012
Economics and Business
 Business Information Systems
 Human Resources

Framework Process Patterns: Lessons Learned Developing Application Frameworks

by: James Carey ; Brent Carlson

Notify me when in stock

On-line Price: $67.95 (includes GST)

Paperback package 256

20%Off Retail Price

You save: $17.00

Usually ships within 4 - 5 business days.

Retail Price: $84.95

Publisher: ,19th April 2002


ISBN: 0201731320
ISBN13: 9780201731323

Add to Shopping Cart


      Frameworks represent a rapidly growing field within object-oriented programming and development. A framework is a set of cooperating classes that make up a reusable design that addresses a specific application domain. Yet, for all of their value, frameworks are widely misunderstood.

  In this book, two framework development experts borrow from their extensive real-world experience to introduce a successful patterns approach to framework development. The authors reveal proven techniques and useful solutions for successful framework development. Through this book, you can enhance your skills and learn to make the transition from object-oriented programmer to framework developer.

  Framework Process Patterns presents working patterns that apply to all phases of the framework development process, from requirements and analysis through documentation. It focuses on the essential issue of what constitutes an appropriate domain, and how to strike the delicate balance between reusability and content. This book also examines the human side of framework development, with advice on effective communication and optimal team organization. Many of these patterns have broad applicability not just to framework development, but to object-oriented and component-based development in general.

  You will read about important topics, including:

  Applying patterns to framework development

Maintaining consistency throughout the framework

Reducing refinement iterations

Distinguishing implementations from requirements

Balancing capabilities versus keeping the framework focused

Decomposing the development of a framework

Using a framework by mapping to it

Providing documentation that addresses various framework audiences

Promoting domain-technical cross-team communication

Establishing framework consistency by defining 'Consistency Czar'

  A single case study runs throughout the book to illustrate the application of principles and techniques. The book also includes two valuable appendices. The first looks at the relationship between frameworks and components, and the second documents the IBM SanFrancisco framework development process.

  Written for proficient object-oriented programmers who want to learn more about this important field or want to validate their own real-life experiences in the trenches of object-oriented development, Framework Process Patterns will bring you far along the path toward fully understanding frameworks and maximizing their potential.



                  Author Bio

      James Carey is the Base Component (fine-grained component) architect for IBM's WebSphere Business Components. He previously served as a lead designer for the Common Business Objects and General Ledger Core Business Processes part of the IBM SanFrancisco frameworks.

  Brent Carlson is Vice President of Technology for LogicLibrary, a provider of software asset management products and services. He previously served as the lead architect for the IBM SanFrancisco project and lead designer for its Warehouse and Order Management Core Business Processes.


Table of Contents


  Why Listen to Us?

How to Read This Book.


      1. Introduction.

  What Is a Framework?

Framework Artifacts.

Developing Frameworks.

Using Frameworks.

The Framework Process Patterns.

      2. Case Study.

  The Clothing Management Domain.


Selecting Clothing.

Cleaning Clothing.

Reparing Clothing.

Purchasing Clothing.

      3. The Development Process.

  Alles in Ordnung.

          Follow a Methodical Development Process.

  Innocent Questions.

          Connecting Domain and Technical Experts.

  Divide and Conquer.

          Making the Framework Consumable.

  Consistency Is King.

          Maintain Consistency throughout the Framework.

  Iterate, Iterate, Iterate.

          Three Iterations to Validate.

  Exposing It All.

          A Framework's Customer Is Its Partner.

  4. Requirements.

  It Depends.

          Identifying Customization.

  Tor's Second Cousin.

          How Extreme Is Too Extreme?

  What, Not How.

          Implementations Masquerading as Requirements.

  The Stupid Test.

          Include Obvious Domain Capabilities While Keeping the Framework Focused.

  5. Analysis.

  Eating the Elephant (One Byte at a Time).

          Decomposing the Problem.

  Something Is Better Than Nothing.

          Document What You Know When You Know It.

  Where's Mr. Spock When You Need Him?

          Domain-Technical Cross-Team Communication.

  6. Design.

  Pass the Buck.

          Knowing When a Framework Shouldn't Do Something.

  Missed It by That Much.

          Developing and Applying Patterns.

  That's the Way the Cookie Crumbles.

          Patterns Can Be Mini-Frameworks.

  It's Still OO to Me.

          Frameworks Aren't Exempt from Good and Bad Object-Oriented Practices.

  7. Documentation.


          Keeping Just Enough to Write Documentation Later.

  Give 'Em What They Want.

          Different Framework Audiences Have Different Needs.

  8. Social Aspects.

  There Is No 'I' in Team.

          The Importance of Team Dynamics.

  The Great Communicator.

          Translating between Domain and Technical Terminology and Concepts.

  Consistency Czar.

          Making Sure Consistency Happens.

  9. Framework Use.

  Just Learn It.

          Using Frameworks Requires Up-Front Education.

  Map Early, Map Often.

          Use Frameworks by Mapping.

  Color Inside the Lines.

          Change Only What You Need to Change.

  10. Conclusion.

Appendix A. Frameworks and Components.

  What Is a Component?

Fine- and Coarse-Grained Components.

Building Coarse-Grained Components.

      Appendix B. The IBM SanFrancisco Frameworks Development Process.

  Process Flow.

Process Artifacts.

Process Participants.

Process Step Details.