Rationale » History » Version 1
J. Wienke, 10/05/2011 04:19 PM
| 1 | 1 | J. Wienke | h1. Structure Proposal |
|---|---|---|---|
| 2 | 1 | J. Wienke | |
| 3 | 1 | J. Wienke | h2. Requirements |
| 4 | 1 | J. Wienke | |
| 5 | 1 | J. Wienke | * *Visibility*: data definitions must be easily visible when searching for them. This includes: |
| 6 | 1 | J. Wienke | ** Folder browsing |
| 7 | 1 | J. Wienke | ** Code completion |
| 8 | 1 | J. Wienke | * *Structure*: a structured view on the data is required as an orthogonal perspective to the general visibility in order to find functionally coherent groups of data definitions |
| 9 | 1 | J. Wienke | * *Stability*: a core set of data definitions must be kept stable as much as possible in order to shield depending software from frequent changes |
| 10 | 1 | J. Wienke | * *Extendability*: |