A framework for information systems architecture
IBM Systems Journal
Software architecture: perspectives on an emerging discipline
Software architecture: perspectives on an emerging discipline
PuLSE: a methodology to develop software product lines
SSR '99 Proceedings of the 1999 symposium on Software reusability
Applied software architecture
Design and use of software architectures: adopting and evolving a product-line approach
Design and use of software architectures: adopting and evolving a product-line approach
Evaluating software architectures: methods and case studies
Evaluating software architectures: methods and case studies
Documenting Software Architectures: Views and Beyond
Documenting Software Architectures: Views and Beyond
The 4+1 View Model of Architecture
IEEE Software
Software Reflexion Models: Bridging the Gap between Design and Implementation
IEEE Transactions on Software Engineering
A Comparison of Static Architecture Compliance Checking Approaches
WICSA '07 Proceedings of the Sixth Working IEEE/IFIP Conference on Software Architecture
IEEE Transactions on Software Engineering
A scalable goal-oriented approach to software variability recovery
Proceedings of the 15th International Software Product Line Conference, Volume 2
| Hi-index | 0.00 |
Reuse promises cost-effective development and maintenance of software systems. Profiting from reuse, however, requires an upfront investment into creating building blocks to be reused by applications. When therefore required resources are limited, creating reusable building blocks practically often means migrating existing software assets into reusable components while concurrently realizing new developments. This pragmatic approach, which is especially often found in small organizations, often frustrates the vision of successful reuse across similar products.This paper, however, presents a success story of iteratively introducing architecture-centric development at Wikon GmbH. This small German company develops remote monitoring and controlling devices with a small team of three engineers only. The presented approach for adopting systematic reuse eventually reduced effort for development and testing by more than 35% without any decline in quality.