CRIP Methodology

From Wikipedia, the free encyclopedia

Please help improve this article or section by expanding it. Further information might be found on the talk page or at requests for expansion. (May 2008)

This article may not meet the general notability guideline or one of the following specific guidelines for inclusion on Wikipedia: Biographies, Books, Companies, Fiction, Music, Neologisms, Numbers, Web content, or several proposals for new guidelines. If you are familiar with the subject matter, please expand or rewrite the article to establish its notability. The best way to address this concern is to reference published, third-party sources about the subject. If notability cannot be established, the article is more likely to be considered for redirection, merge or ultimately deletion, per Wikipedia:Guide to deletion. This article has been tagged since May 2008.

This article does not cite any references or sources. (May 2008) Please help improve this article by adding citations to reliable sources. Unverifiable material may be challenged and removed.

This article is orphaned as few or no other articles link to it. Please help introduce links in articles on related topics. (January 2008)

This page has few or no links to other articles. (Tagged since April 2008). You can improve this article by adding links to related material, within the existing text. For some link suggestions, you can try Can We Link It tool. (You can help!)

CRIP Enterprise Component Architecture

(Acronym)

The CRIP methodology for system architecture is defined as building enterprise solutions with a dynamic componentized architecture. It defines enterprise applications as being made up of Content, Relationships, Information, and Process. This allows for users to be able to retrofit solutions around their business needs without being reliant on IT.