These models and checklists help anyone faced with the problem of whether to build, buy, reuse, or reengineer any software component, system, or subsystem of reasonable complexity. The book includes several models and reengineering checklists, as well as important case studies. Access reuse and disadvantages for your systems.ģ.Estimate total costs, including maintenance, using life-cycle-based models.ĥ.Certify software components that have been created at any phase of the software life cycle your organization uses.Ħ.Implement systematic reuse using COTS (commercial, off-the-shelf) components and other existing software. A case study using DoDAF (The Department of Defense Architectural Framework) in system design has been included to show some new thinking about reuse and some attributes of large-scale components of very large systems.Īfter an introduction to basics, the book shows you how to:ġ. Important new material has been added to this edition on the changed state-of-the-art and state-of-the-practice of software reuse, on product-line architectures, on the economics of reuse, on the maintenance of COTS-based systems. This book covers reuse in object-oriented systems, but goes far beyond in its coverage of complex systems – the type that may evolve into “systems of systems.” Software reuse has been called the central technical concept of object-oriented design. The bottom line is good news for designers of complex systems: Systematic software reuse can succeed, even if the underlying technology is changing rapidly. It explains in depth the fundamentals, economics, and metrics of software reuse. This book is an updated edition of the previous McGraw-Hill edition, which was an essential guide to successful reuse across the entire software life cycle.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |