Highlights of these reports follow. A domain is a specialized body of knowledge, e.g., ground-based command and control for satellites. Domain analysis is crucial because it essentially defines the high-level requirements for a product line. This would help limit the budget and time frame for completing the analysis. Long periods of perceived inactivity before benefits are visible may be counter-productive.
Few organizations have significant experience with the extraction of architectural assets.
The methods for evaluating software architecture are immature but promising. Asset evolution issues were tightly coupled with requirements issues. Requirements management was seen as a critical area for product line practice. An inability to compromise on requirements can be an impediment to product lines. Interestingly, most software engineering barriers identified were non-technical in nature.