There are architectural properties that are unrelated to specific application requirements but are nevertheless important.  A technical architecture should show how it addresses these properties:

• Coherence - any one thing is "about" one thing and does one thing
• Consistency - each part of the application follows the same principles
• Loose coupling - each part of the application is attached loosely to other parts, being as ignorant as possible of other parts of the application
• Maintainability - the application is structured so that it is relatively easy to find any given piece that must be modified and the change can be made in an atomistic way

Perhaps a rebranding of the application section of the Enterprise Architecture, Application Portfolio Management (APM) is a healthy way to inventory, and rationalize an organization's applications.

By rationalize, we mean "to form a rational conception of". In other words, are all the applications that IT currently supports governed by reason?

Applications are assets provided their costs do not exceed delivered value.

• How can I marshal the resources required for new projects and initiatives?
• What applications are impacted by a new project?
• If we eliminate this application, what other applications and databases will need modification?
• What applications should be integrated, consolidated or eliminated?
• What applications provide redundant functionality?
• Which applications cost the most to support?
• What can I do to control costs?
• Where are we underutilizing assets due to fragmentation, lack of common definitions or lack of integration?

Resources:

• DCI Web Seminar - Application Rationalization: Taking Stock of the IT Portfolio to Accommodate Business Needs (PDF / Watch Presentation)

The Enterprise Application Architecture (EAA) defines the collection of application systems required to support the business processes and information needs as expressed in the Enterprise Business Architecture (EBA) and Enterprise Information Architecture (EIA).

• Includes an inventory of currently deployed applications and components.
• Each set of applications are linked to the business processes that they support.
• Used for gap analysis to determine what applications are needed in the future based on business functions not well supported, or the removal of applications no longer linked to business needs.
• Relationships to the supporting infrastructure and ETA are shown.
• Highlights interfaces between components in the ETA.

Recently, I have been considering Application Portfolio Management, as a practical method for building and maintaining the Enterprise Application Architecture inventory and rationalization.