1. A method of handling changes to a software system in a business environment comprising: capturing customer requirements of the software system in a schema; modeling business-software architecture of the software system in a first level of the schema as business functions, business activities, forms, actions, and business rules, wherein each of the business functions comprises functions performed in a business process of the software system, wherein each of the business activities comprises activities performed in each of the business functions, wherein each of the forms comprises semantics to capture and retrieve information for each of the business activities, wherein each of the actions comprises tasks performed in each of the forms, and wherein each of the business rules comprises rules that govern each of the actions; modeling design architecture of the software system in a second level of the schema as components, system entry points, user interfaces, services, and methods, wherein each of the components corresponds to each of the business functions of the business process, wherein each of the system entry points corresponds to visual-interface elements of each of the business activities, wherein each of the user interfaces with visual-interface elements corresponds to each of the forms, wherein each of the services corresponds to each of the actions performed in each of the user interfaces, and wherein each of the methods corresponds to each of the business rules that are invoked in handling each of the services; defining events that connect the first level and second level of the schema, wherein events comprise entry events and exit events, and wherein each of the entry events is a stimulus that triggers a business function, a business activity, or a form and each of the exit events is a response from the respective business function, business activity, or form to the stimulus; defining links that represent interactions between the user interfaces, wherein each of the links comprises cross connections between the visual-interface elements in the user interfaces and the events associated with at least one of the business functions, business activities, and forms; defining integration services for each of the events, wherein integration services define cross connections for data updates between the events associated with at least one of the business functions, business activities, and forms in the first level and services and methods in the second level; mapping each of the business functions, business activities, forms, actions, and business rules in the first level to a corresponding one of the components, system entry points, user interfaces, services, and methods in the second level using the events, links, and integration services; creating a knowledge repository with a traversable user interface representing the mappings between the first level and the second level of the schema; identifying changes to the software system in the business environment, wherein the changes are associated with at least one of the business functions, business activities, forms, actions, and business rules; and analyzing impact of the changes to the software system using the knowledge repository with the traversable user interface.
1. A method of handling changes to a software system in a business environment comprising: capturing customer requirements of the software system in a schema; modeling business-software architecture of the software system in a first level of the schema as business functions, business activities, forms, actions, and business rules, wherein each of the business functions comprises functions performed in a business process of the software system, wherein each of the business activities comprises activities performed in each of the business functions, wherein each of the forms comprises semantics to capture and retrieve information for each of the business activities, wherein each of the actions comprises tasks performed in each of the forms, and wherein each of the business rules comprises rules that govern each of the actions; modeling design architecture of the software system in a second level of the schema as components, system entry points, user interfaces, services, and methods, wherein each of the components corresponds to each of the business functions of the business process, wherein each of the system entry points corresponds to visual-interface elements of each of the business activities, wherein each of the user interfaces with visual-interface elements corresponds to each of the forms, wherein each of the services corresponds to each of the actions performed in each of the user interfaces, and wherein each of the methods corresponds to each of the business rules that are invoked in handling each of the services; defining events that connect the first level and second level of the schema, wherein events comprise entry events and exit events, and wherein each of the entry events is a stimulus that triggers a business function, a business activity, or a form and each of the exit events is a response from the respective business function, business activity, or form to the stimulus; defining links that represent interactions between the user interfaces, wherein each of the links comprises cross connections between the visual-interface elements in the user interfaces and the events associated with at least one of the business functions, business activities, and forms; defining integration services for each of the events, wherein integration services define cross connections for data updates between the events associated with at least one of the business functions, business activities, and forms in the first level and services and methods in the second level; mapping each of the business functions, business activities, forms, actions, and business rules in the first level to a corresponding one of the components, system entry points, user interfaces, services, and methods in the second level using the events, links, and integration services; creating a knowledge repository with a traversable user interface representing the mappings between the first level and the second level of the schema; identifying changes to the software system in the business environment, wherein the changes are associated with at least one of the business functions, business activities, forms, actions, and business rules; and analyzing impact of the changes to the software system using the knowledge repository with the traversable user interface. 7. The method of claim 1 , further comprising using the knowledge repository to examine proper technology mapping in response to the changes.