Currently in the developer guide under the glossary, there appears to be quite a lot of terms that the developer should be expected to know, such as the following ones in the screenshots below:
Most developers should be able to understand and know what these terms are, so I don't think they are necessary and relevant that is unique to your application concept.
The components here have been described and explained above in the developer guide (along with the UML diagrams), repeating them here may be unnecessary.
These are also common tools/frameworks that most Java developers would know (at least the majority), and as such it is not something unique to your application/project that needs to be brought up and explained in detail.
Currently in the developer guide under the glossary, there appears to be quite a lot of terms that the developer should be expected to know, such as the following ones in the screenshots below:
Most developers should be able to understand and know what these terms are, so I don't think they are necessary and relevant that is unique to your application concept.
The components here have been described and explained above in the developer guide (along with the UML diagrams), repeating them here may be unnecessary.
These are also common tools/frameworks that most Java developers would know (at least the majority), and as such it is not something unique to your application/project that needs to be brought up and explained in detail.
Labels:
severity.Low
type.DocumentationBug
original: sayomaki/ped#16