Template:OOPM:Templates:Documentation:Development:ReleaseIterationStatement:1.0
OOPM:Templates:Documentation:Development:IterationStatement:1.0
This is an initial draft of the IterationStatement template version 1.0
Iteration Statement
Iteration | not defined |
Release | not defined |
Previous Iteration | not defined |
Next Iteration | not defined |
Schedule
Begin Date | not defined |
End Date | not defined |
Duration | not defined |
Goals
none defined
unordered list of goals where individual entries are categorized by Documentation, Learning, etc.
additional sub categories such as Documentation::Process, or Development::Process, or Documentation::HowTo
can be defined and must be documented in the wiki, the categories are named based on the types of produces
being produced by the iteration
Produces
none defined
unordered list of produces where individual entries are categorized by Wiki, Repository and IssueTracker
additional categories can be added as required, however, they must be documented in the wiki
the categories are named based on the storage being used for the individual produces of the iteration
example
|produces= * Wiki * [[WikiProduce1]] * [[WikiProduce2]] * Repository * [[RepositoryProduce1]] * [[RepositoryProduce2]] * IssueTracker * https://.../IssueTrackerProduce1 * https://.../IssueTrackerProduce2
Subprojects
none defined
tree of subprojects affected by the iteration using an unordered list, depicting the subproject hierarchy
individual items can be laid out as links to individual sub project pages in the wiki
Example
|subprojects= * [[Requirements Analysis]] * [[Prototype Development]] ** [[Architecture and Design]] ** [[Prototype Implementation]] ** [[Prototype Maintenance]]
References
no references defined
Purpose of this section
provides an unordered list of references to either internal a/o external documents and other resources
individual items may be categorized by reference categories, where individual categories must be named
by the content type of the resource referenced, e.g. Media, Files, Documents and so on
Example
|references= * Documents ** [http://foo/bar.html document describing a bar] * Media ** [https://foo/bar_visiting.mov movie on bar visiting] * Files ** [http://foo/bar_draining.java sample source implementing a bar draining algorithm]
Preview