XM Documenation Strategy: Difference between revisions
Jump to navigation
Jump to search
(Created page with "The basic documentation strategy involves creation modules at Connexions for every one of the ~100 documentation steps. This way, a team can rapidly synthesize a documentatio...") |
No edit summary |
||
| Line 1: | Line 1: | ||
The general documentation strategy pattern for OSE work revolves around breaking development into components, defining relationships between the components, and remixing publications readily from the components. | |||
Component breakdown begins with the [[SEBD]] on the technology level, and it begins with breakdown into the ~100 development steps (for each technology component) at the Development Process level. | |||
The basic documentation strategy involves creation modules at [[Connexions]] for every one of the ~100 documentation steps. This way, a team can rapidly synthesize a documentation publication in working Flash Mobs. | The basic documentation strategy involves creation modules at [[Connexions]] for every one of the ~100 documentation steps. This way, a team can rapidly synthesize a documentation publication in working Flash Mobs. | ||
[[Category:XM]] | [[Category:XM]] | ||
Revision as of 01:31, 23 April 2012
The general documentation strategy pattern for OSE work revolves around breaking development into components, defining relationships between the components, and remixing publications readily from the components.
Component breakdown begins with the SEBD on the technology level, and it begins with breakdown into the ~100 development steps (for each technology component) at the Development Process level.
The basic documentation strategy involves creation modules at Connexions for every one of the ~100 documentation steps. This way, a team can rapidly synthesize a documentation publication in working Flash Mobs.