|
|
(8 intermediate revisions by 2 users not shown) |
Line 1: |
Line 1: |
− | Okay, for now I am going to use the two terms of Structured and Unstructured to define two unique types of applications used collecting and presenting data.<br>
| + | [[Category:Structured Or Unstructured]] |
− | | + | = Benefits of Structured = |
− | == Attributes of Structured ==
| |
− | | |
− | I need to come up with a term to describe the type of application that Sugar CRM represents. Applications like Sugar typify Entity based application development. A table of data is an entity and therefore corresponding view, edit, list views need to be created. This is the mentality of hard-core entity based appliactions.
| |
− | | |
− | A more process focused, entity based application will present data elements of one or many entities in a single view/form to better represent the process or task being performed.
| |
− | | |
− | | |
− | == Attributes of Unstructured ==
| |
− | My initial perception of the wiki was that it was that it was a giant scratch pad that allowed for ongoing classification or categorization of random content.
| |
− | | |
− | | |
− | == Benefits of Structured ==
| |
− | | |
− | | |
| == Benefits of Unstructured == | | == Benefits of Unstructured == |
| Comment on stream of conciousness. | | Comment on stream of conciousness. |
Line 21: |
Line 7: |
| | | |
| == How They Can Play Together == | | == How They Can Play Together == |
− |
| |
− | [[Category:Structured Or Unstructured]]
| |
Latest revision as of 18:46, 13 November 2006
Benefits of Structured
Benefits of Unstructured
Comment on stream of conciousness.
How They Can Play Together