1. Bailin, S. (1992). KAPTUR: A tool for the preservation and use of engineering legacy. Rockville, MD: CTA Inc.
2. Bailin, S. C., Moore, J. M., Bentz, R., & Bewtra, M. (1990). KAPTUR: Knowledge acquisition for preservation of tradeoffs and underlying rationale. In Proceedings of the 5th Annual Knowledge-Based Software Assistant Conference (pp. 95–104).
3. Barber, K. S., Graser, T. J., Grisham, P. S., & Jernigan, S. R. (1999). Requirements evolution and reuse using the Systems Engineering Process Activities (SEPA). Australian Journal of Information Systems, 7(1), 75–97.
4. Barber, K. S., & Jernigan, S. R. (1999). Changes in the model creation process to ensure traceability and reuse. In 1999 International Conference on Artificial Intelligence (ICAI’99), Las Vegas, Nevada.
5. Bratthall, L., Johansson, E., & Regnell, B. (2000). Is a design rationale vital when predicting change impact?—A controlled experiment on software architecture evolution. In Proceedings of Conference on Product Focused Software Process Improvement (PROFES’2000) (pp. 126–139). Springer.