The lifecycle of a successful system is the time period that covers all activities associated with developing, configuring, deploying, operating, and retiring the system. Variations in system lifecycles can be expected, for example, differences may arise as a result of the inclusion of physical parts in the system and the number of installations. In addition, software retirement activities may extend over a long period of time, for example, in cases where access to data provided by a system may be required long after the system is terminated. Lifecycle management has a lot to do with managing the available information about a system. A significant amount of this information can typically be found in the models produced during various development. Softwaremodels can thus play a vital role in system lifecycle management. For example, requirement models can be used to support management of requirements, feature models can be used to manage system and user specific variabilities as well as commonalities, and architecture and design models can provide information that supportmanagement of deployment and validation activities. The potential role thatmodels can play in lifecyclemanagement raises the following questions: “To what extent do the models produced during software development help (or hinder) lifecycle management?” “Should the software modeling activity be integrated with the lifecycle management of systems, and, if yes, how can this be done?” “What tools are needed to better leverage the use of models in lifecycle management?” “Does a model also have a lifecycle that needs to be managed?”