 |
 |
 |
|
 |
|||
| RE 2.3: Reformatting |
 Contents
|
|
|---|
Product Flow
| From | Product | to | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Activity | State | Chapter | Title | Activity | State | ||||||||||||||
| RE1.5 | accepted | All | User Demand | - | -
| RE2.2 |
being proc. |
All |
Implementation Document: Module |
RE2.4 |
RE3.2 RE3.3 RE3.4 RE3.5 RE3.6 RE3.8 RE5.1 RE5.2 being proc.
| All |
SW ModuleAll |
Implementation Document: Database |
RE2.4 |
RE3.2 RE3.4 RE3.5 RE3.6 RE3.8 RE5.1 RE5.2 being proc.
| All |
Database | ||
Handling
During reformatting, the layout and thus the readability of subproduct User Demand.Possible Solutions as well as the code remodularized and restructured in the preceding subactivity will be improved.
The following measures might be appropriate:
- indents to demonstrate the logical structure,
- insertion of comments to point of the beginning and the end of certain program sections,
- highlighting (bold or italics) of procedural calls,
- underlining of conditions like if or case,
- insertion of empty lines before and after lengthy program structures,
- marking of areas, e. g. declarative program section,
- marking of identifiers valid for a global range.
|
|
|
GDPA Online
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster
|