Software architecture and reuse-an inherent conflict?

Software reusability, which covers both developing software with the help of existing artifacts as well as developing software for reuse in other applications, is one of the key factors for increasing productivity and decreasing costs in software development costs. The proposed scenario for future software production is that programs will be mostly composed out of existing components rather than writing them from scratch. However, although there are successful approaches to support software reusability and although reusable components have been built, this ideal scenario has not yet become reality. Many programs, especially in industry, are still written from scratch and software reuse just plays a minor role in software development. Currently software reuse approaches take little advantage of the techniques provided by software architecture, techniques which are based on existing requirements for the development of industrial and commercial software. Thus, there doesn´t seem to be a conflict between software reuse and software architecture, but there is a strong need to better integrate them with each other. Software reusability has a wider focus on software production, it comprises lots of managerial and organizational aspects. Software architecture provides sufficient techniques for the development of software both with and for reuse. These techniques have to be exploited in current approaches to reusability in order to implement a successful reuse organization