Before continuing, it may be beneficial to remember why reusability, architected libraries, and domain analysis are being discussed. The purpose is to use an understanding of an organization's business objectives and reuse principles to define what parts (architected sets) will most benefit the organization by their creation and reuse.
The methods described here have been used on software projects to achieve significant cost savings over traditional software development methods. Informal use of these methods has resulted in similar savings in the documentation arena. A cost analysis should always be performed before doing the domain analysis and producing the architected libraries.