We specialize in hard to find items
(1)
Framing Software Reuse: Lessons From the Real World
Share Tweet
*Price and Stocks may change without prior notice
*Packaging of actual item may differ from photo shown
- Electrical items MAY be 110 volts.
- 7 Day Return Policy
- All products are genuine and original
About Framing Software Reuse: Lessons From The Real World
Product Description Written by the inventor of the Bassett Frame Technology, this authoritative volume explains how cost-effectiveness of large I.S. departments can be improved 50-fold by implementing highly effective software engineering techniques. It identifies those techniques that work well together, and explains why they do. From the Publisher The complete guide to frame-based code reuse techniques -- by their inventor! 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. It explains basic concepts, especially the central role of reuse in software engineering, and presents the software assembly commands of frame technology. Learn frame engineering principles through simple examples and case studies. Explore the software design and development process, both for reusable frame components and for systems assembled from them. Understand the design principles for software construction tools, and connects frames to advanced mathematical ideas such as context-sensitivity. This is an ideal guide for software practitioners, managers, consultants, researchers, faculty and students involved in software engineering and reuse. From the Inside Flap This book shows software developers, analysts, and managers how to make reuse work. The book highlights frame technology: a language-independent way to manufacture software from components that can adapt each other. Why should you read this book? Because of what adaptive reuse can do for you. Example: One Fortune 50 company's entire information systems development staff numbers only 40 people (with no outside contractors). Yet they satisfy over 28,000 user requests for software changes and enhancements each year. Further example: A major retailer developed and deployed its mission-critical purchase-order management system in 80% less time and effort than development projects used to take them before they embarked on adaptive reuse. The project was enormous--over 1300 programs and 5 million lines of code. On the last four subsystems alone they saved $11 million in development costs, and $12 million in early deployment benefits. Frames solve thorny, long-standing software industry problems. Finally, we can combine high productivity with high quality, preserve flexibility without sacrificing performance, port systems to multiple platforms with native look-and-feel functionality, reduce complexity (in addition to hiding it), and, most importantly, reduce the cost of so-called maintenance. Sounds like magic, right? Wrong. It is not magic. Reuse is so fundamental to all mature engineering disciplines, it is not even part of their jargon! But effective software reuse is harder, because nonphysical things have more degrees of freedom available to them. Physical parts are reused as is. Software parts often need unpredictable modifications before they can be reused. Software practice has begun to mature, to acquire some of the substance and rigor that are the hallmarks of an engineering discipline. As with all new paradigms, there has been an initial period of healthy confusion. Software's "craft" phase has been an exciting half-century of brash precocity, experimentation, fads, buzzwords, religious wars--an on-going turmoil. Emerging from this pandemonium are principles that can effectively lead us out of the wilderness. Origins I have a very clear memory of that fall day in 1978, standing at the greenboard in my York University office, talking to my colleague, professor Gunnar Gotshalks, about the frustrations of code generators. In addition to teaching computer science, I had recently founded a software house, called Sigmatics Computer Corporation, to serve the needs of local businesses. Gunnar was under contract for Sigmatics; we were installing a custom software system for the city of Barrie, Ontario. We were using code generators I had
