6. A method of developing an operational model for an IT architecture application comprising: developing an information technology (IT) architecture upper merged ontology for a given IT architecture application comprising: an upper merged ontology that is a representation framework for combined knowledge sources that are used in business and information technology, the upper merged ontology including a plurality of business, architecture and service domain models; an upper merged ontology knowledge base containing information derived from an analysis of business and technical services pertaining to the IT architecture application; a plurality of semantic web APIs that allow access to the upper merged ontology as a semantic web; and a reasoning and constraint language (RaCL) that is a scripting language having the capabilities of model creation, automated reasoning and search and query operations such that scripts developed in the reasoning and constraint language can be executed through use of the semantic web APIs; populating the upper merged ontology knowledge base with information derived from an analysis of business and technical services pertaining to the IT architecture application; executing RaCL processes to search the upper merged ontology knowledge base and extract knowledge pertaining to the IT architecture application and processing the results to generate dependency and interface relationships within an operational model domain ontology; creating an architecture for the IT architecture application from the operational model domain ontology, dependency and interface relationships; and a computer processor for performing the method.
8. The method of claim 6 wherein the plurality of domain models include: a domain model representing business or technical subject matter knowledge in a plurality of domains; a business model facilitating business organization and strategic knowledge; an IT architecture model representing component elements and relationships of IT architectures; an operational model representing real-world systems at an operational level; a services library representing common descriptions of services in different domains; a metrics library representing measurement indicators, their calculation and interpretations in the different domains; a use case library representing use cases and business processes in business processes in business and IT architecture contexts; a pattern library representing problem-solving patterns, their implementations, constraints and usage in IT architecture; and a case library representing an historical view of systems developments, pattern application, results and experiences.