Maintain the application and information portfolio

In the left navigation panel, expand the Application Architecture section to capture and maintain data for applications and application groups . Expand the Information Architecture section to capture information flows , business data, and data categories.

Here's how you can begin:

	Capture information about your applications. All applications should be documented to ensure that the application portfolio is reliable to make good strategic decisions. A variety of information can be documented about applications via standard attributes as well as generic attributes . Define the users and organizations that have a role for the application, the application lifecycle, and evaluate the applications based on preconfigured indicators. generic attribute A generic attribute is a custom attribute that allows the ad-hoc capture of information for a class. role A role describes the functional relationship that a user or organization has for an object. lifecycle The lifecycle describes the planned schedule of a current real-world object in different lifecycle phases of a product. Lifecycle phases will be different depending on the object class. Lifecycle phases for an application are Pilot, Production, Retired, and Sunset.
	Capture information about the application's relevance for the business. Document which business capabilities the applications provide, which business processes the applications support, etc.
	Add application groups to the repository and assign applications to them for analysis.
	Describe the information context of the application portfolio. Document the information flows between applications and the business data that the information flows transfer.