The classic waterfall model of software engineering is used throughout the production software development community. The escalating costs associated with software development and the unsatisfactory reliability, performance, and functionality of the resulting software have motivated software engineers to develop new alternate models of software development including prototyping, software synthesis, and reusable software. It is difficult to compare and contrast these new models of software development because their disciples often use different terminology, and the models often have little in common except their beginnings (marked by a recognition that a problem exists) and ends (marked by the existence of a software solution). This paper provides a framework which can serve 1) as a hasis for analyzing the similarities and differences among alternate life cycle models; 2) as a tool for software engineering researchers to help describe the probable impacts of a new life cycle model; and 3) as a means to help software practitioners decide on an appropriate life cycle model to utilize on a particular project or in a particular application area.' Index Terms-Reusable software, software development life cycles, software prototyping, software synthesis, waterfall model.

This paper describes the concept for a future automated environment supporting systems engineering, named Catalyst. Catalyst will enhance the effectiveness of the systems engineering process to produce more successful, higher quality systems. Sponsored by the Air Force Rome Laboratory, the Systems Engineering Concept Demonstration Program researched the needs and defined the requirements and conceptual design of Catalyst. The paper discusses the operational concept, architecture, and important features and characteristics for Catalyst.

The purpose of this effort is to analyze the domain process and its relationship to the development and use of reusable components. It includes an identification of the critical issues and risks involved throughout the process. Capabilities of automated tools which could be used to perform various aspects of a domain analysis are also investigated. Finally, it provides a set of guidelines for conducting a domain analysis for embedded systems. 14. SUBJECT TERMS IS. NUMBER OF PAGES Domain Analysis, Reuse Methods, Software Components 223 16. PRICE CODE 17. SECURrTY CLASSIFICATION 18. SECURITY CLASSIFICATION i19. SECURITY CLASSIFICATION 20. LIMITATION OF ABSTRACT