[Book Cover]

Framing Software Reuse: Lessons From the Real World, 1/e

Paul G. Bassett, Netron, Inc., Toronto, Canada

Published August, 1996 by Prentice Hall PTR (ECS Professional)

Copyright 1997, 384 pp.
Cloth
ISBN 0-13-327859-X
$52.00


Sign up for future
mailings on this subject.

See other books about:
    Object Oriented Programming

 [Preface]





Written by the inventor of the Bassett Frame Technology, this authoritative volume explains how IS cost-effectiveness can be dramatically improved through reuse technologies that really work.

Explains basic concepts, especially the central role of reuse in software engineering. Presents the software assembly commands of frame technology. Introduces frame engineering principles through simple examples and case studies. Explores the software design and development process, both for reusable frame components and for systems assembled from them. Presents design principles for software construction tools, and connects frames to advanced mathematical ideas such as context-sensitivity.



The complete guide to frame-based code reuse techniques -- by their inventor!

  • Discusses software engineering techniques for reuse that work remarkably well together, and explains why they do.
  • Shows why, after 40 years of effort, fads and hyperbole, most software systems are late, over-budget and ineffective.
  • Exposes deeply held fallacies about the nature of software with principles that are demonstrated to work.




I. EXECUTIVES; OVERVIEW; REUSE THAT WORKS.
    1. Reuse: Its Time Has Come.

      Major Oganizations Participated. Process Productivity About Ten Times Better. Bottom Line Results.

    2 Reuse: What Is It?

      Use at Run Time. Reuse at Construction Time. Enabling Reuse: Frame Technology. Software Source Module. Design Templates. Processing a Frame Hierarchy. Adaptable Reuse is a Gateway.

    3. How Reuse Changes Software Development.

      Software is not a Kind of Hardware. Software is the Same as Hardware Except. . . Iterative Design Refinement.

    4. Gear Your Organization for Reuse.

      Reuse Maturity Levels. Barriers to Systemic and Cultural Reuse. Business Effectiveness Through Systemic Reuse. It has been done.

    5. An Advanced Form of Object Orientation.

      First Exception: How Frame Hierarchies are Organized. Second Exception: Unify Abstraction and Component Relationships. Third Exception: Adapt Rather than Inherit. A Visit to the Object-Oriented.

    6. Reuse Underlies the Practice of Engineering.

      What is Engineering? Sharing Solutions. Software Engineering: A Definition. Is Software a Synonym for Programs? Getting There From Here.

II. FRAMES ENABLE REUSE.
    7. Use Is to Reuse as Run Time Is to Construction Time.

      Overcoming the Malaise. Principle of Reuse. The World its NOT Made Out of Lego Blocks! Need for Construction-Time Variability. The Construction-Time Run-Time Duality.

    8. An Introduction to Frame Technology.

      Copy-and-Modify. Same-as-Except. Frames are Software Parts. Frames Work.

    9. The Main Frame Commands.

      Variables and Expressions. The Frame Processor. Main Commands.

    10. Frames: Like, ut Oh How Different!

      Frames in Artificial Intelligence. Skeleton Code. Macros. Generators.

    11. Adaptively Reusing the Tried and True.

      Subroutines. Structured Programming. SoftwareÕs Tower of Babel

    12. Plain Talk, Not Smalltalk: An Object-Oriented Primer.

      OO at Run Time. OO at Construction Time.

    13. Extending the OO Paradigm for Reuse.

      Inheritance: Single or Multiple? Frames are Classes on Steroids Complexity Management.

    14. Domain Analysis.

      Back to Basics. The Functional Analysis of a Domain. Sanity Check.

    15. Parts-Oriented Analysis and Design.

      Resolving Reusable Parts. Frame Organization.

    16. The Second Dimension: Reuse Across Time.

      Frame Generalization. Generalizing with SELECTs. The Role of WHILE Generalizing with Frame Variables. When in Doubt Leave it Out.

    17. Noma Industries.

      A Sample Application: Electronic Data Interchange (EDI). Generic MOVE Frame. Generic EDIT Frame. Data-Dictionary Frames. Generic Logic Frame. Customer Specification Frames.
III. REUSE CHANGES THE SOFTWARE ENGINEERING PROCESS.
    18. People Make Technology Work.

      A Partnership with Users. The Hybrid is Organization. One Reuse Infrastructure. The Waterfall is Our Downfall. Minimizing Risk. Designing from Adaptable Models.

    19. The Iterative Refinement of Frameworks.

      Frames Co-Evolve with Systems. Setting Realistic Expectations. Ownership and Resource Issues.

    20. The Frame Refinement Process.

      The Initial Application Project. Refine Alternate Versions. Consolidation and Stable Release. Manage Evolutionary Refinements.

    21. The Iterative Refinement of Software Applications.

      An Overview of IDR. Phase One: Produce a Conceptual Model. From Breadth-First to Depth-First: Gearing for Phase Two. Time-Box Each Prerelease Cycle. Releasing the System into Production. Maximizing Bang for Buck. IDR Benefits.

    22. Software Maintenance Considered Harmful.

      Postproduction Releases. Decoupling Application Evolution from Component Evolution. Handling Retrofits. The Evolution of Purchased Packages. Frame-Based Evolution.

    23. A Statewide System Uses IDR.

      Genesis of the System. Constraints Faced. System Strategy. System Results.
IV. MANAGING THE TRANSITION.
    24. Is Your Organization Ready for Reuse?

      The Self View. The UsersÕ View. The Senior Management View. Focusing on Reuse. The State of the Practice.

    25. Key Business Drivers. Management Commitment. Strategic Goals.

      Organizational Fitness. Accountability Structure. Some Potholes to Pave. Getting to Systemic Reuse: Lessons from the Real World. Internal Publicity.

    26. Reengineering the Infrastructure.

      Reengineering the Business. Reusing Business Process Reengineering in IS Departments.

    27. Doing Better with Less.

      Use of People. Use of Standards. Effective Control of Uncertainty. Use of Metrics. Instrumentation Guidelines.

    28. Alleviate Staff Insecurity.

      Career Paths. Professional SWAT Teams. Education and Training. Changing the Relationships with other Departments.

    29. What Next? Three Paths Ahead. Frame Technology. HudsonÕs Bay Company.
    References.
    Glossary.
    Index.

[Help] [Home]

© Prentice-Hall, Inc. A Pearson Education Company
Comments To webmaster@prenhall.com