Software Engineering with Reusable Components
by Johannes Sametinger
Publisher: Springer 2001
ISBN/ASIN: 3540626956
ISBN-13: 9783540626954
Number of pages: 285
Description:
The book provides the reader with a clear understanding of what software reuse is, where the problems are, what benefits to expect, the activities, and different forms of software reuse. The reader is also given an overview of what software components are, different kinds of components and compositions, a taxonomy thereof, and examples of successful component reuse. An introduction to software engineering and software process models is also provided. Consequences and influences of systematic reuse of software components are depicted, and activities like domain engineering, component engineering and application engineering are described.
Download or read it online for free here:
Download link
(1.2MB, PDF)
Similar books
Case Studies in Systematic Software Developmentby Cliff B. Jones and Robert C. F. Shaw - Prentice Hall
This book covers the case studies on the application of the most widely known formal methods in software development, the Vienna Development Method. VDM was developed in an industrial environment but has also evoked considerable academic research.
(16757 views)
Practical Tips for Software-Intensive Student Projectsby Damith C. Rajapakse
A collection of practical tips gathered from the authors' software engineering experience and from many books on the topic. It does not intend to cover software engineering theory. The book is meant for software engineering project courses.
(21388 views)
The Grand Unified Theory of Software Engineeringby Mathias Ekstedt - Industrial Info Systems
This book is the result of innumerable longwinded, oftentimes unnecessarily complicated, discussions between the authors on the nature of software engineering, machines, minds, design, software, engineering, organizations and more.
(15137 views)
Software Architectureby A. Bijlsma, B.J. Heeren, E.E. Roubtsova, S. Stuurman - FTA
The central theme of this book is balancing the concerns and requirements of stakeholders, combining these into an architecture proposal by employing known tactics and patterns, producing a description of the architecture that can be communicated.
(16814 views)