4101
Comment:
|
4093
|
Deletions are marked like this. | Additions are marked like this. |
Line 7: | Line 7: |
Implementaiton covers implementation of a bug, a feature request a patch or a task from the current [:Development#CurrentIterationTaskOverview: current iteration task overview]. | Implementation covers implementation of a bug, a feature request a patch or a task from the [:Development#CurrentIterationTaskOverview: current iteration task overview]. |
Line 9: | Line 9: |
This means that implementation can cover anything e.g. code implmentation, script implementations, documentation updates, softaware upgrades etc. | This means that implementation can cover anything e.g. code implementation, script implementations, documentation updates, software upgrades etc. |
Line 22: | Line 22: |
1. Definition af the task implemntation is to be release tested on basis of defined success criterias. Involve [:Process_Role/Test Coordinator:test coordinator] if necessary. | 1. Definition of the task implementation is to be release tested on basis of defined success criteria. Involve [:Process_Role/Test Coordinator:test coordinator] if necessary. |
Line 33: | Line 33: |
1. For code, make [:Process:Code Review:code review] on success criterias and the unit tested, sanity tested code with updated documentation 1. For documentation, make [:Process:Document Review:document review] on success criterias and updated documentation 1. For other, make review inspired by [:Process:Document Review:document review] |
1. For code, make [:Process/Code Review:code review] on success criterias and the unit tested, sanity tested code with updated documentation 1. For documentation, make [:Process/Document Review:document review] on success criterias and updated documentation 1. For other, make review inspired by [:Process/Document Review:document review] |
The Implementation process contains [#ImplementationDescription Description], [#ImplementationPurpose Purpose], [#ImplementationResponsible Responsible], [#ImplementationMethod Method], [#ImplementationTime Time], [#ImplementationInput Input] and [#ImplementationOutput Output].
Anchor(ImplementationDescription) DescriptionBR Implementation covers implementation of a bug, a feature request a patch or a task from the [:Development#CurrentIterationTaskOverview: current iteration task overview].
This means that implementation can cover anything e.g. code implementation, script implementations, documentation updates, software upgrades etc.
Anchor(ImplementationPurpose) PurposeBR To get implementations of high quality ready for release test/release.
Anchor(ImplementationResponsible) ResponsibleBR This can either be
[:Process Role/Task Holder:Task holder] according to Iteration plan for iterations tasks or
[:Process Role/Module Owner:Module Owner] of new tracker issue for that specific module.
Anchor(ImplementationMethod) MethodBR
- The task examined and unclear point clarified.
Definition of the task implementation is to be release tested on basis of defined success criteria. Involve [:Process_Role/Test Coordinator:test coordinator] if necessary.
For code, Unit test must be implemented, see [:Guidelines/Unit Test Guideline:unit test guideline]
- Make implementation:
for code use [:Guidelines/Coding Guideline:coding guideline]
- for release documentation use [:Maintaining_Documentation:guideline for maintaining documentation]
- for assignment writing use [:Guidelines/Assignment_Writing:guideline for assignment writing]
- for new processes/roles use [:Guidelines/NewProcess: guideline for new processes]
Make release test description, involve [:Process_Role/Test Coordinator:test coordinator] if necessary.
- Sanity test, i.e. make seek to make the described release test.
Update documentation and note in the [:Development#CurrentIterationReviewOverview: current iteration review overview] if any release documentation (e.g. manuals) are affected
- Review work:
For code, make [:Process/Code Review:code review] on success criterias and the unit tested, sanity tested code with updated documentation
For documentation, make [:Process/Document Review:document review] on success criterias and updated documentation
For other, make review inspired by [:Process/Document Review:document review]
Release test description is accepted by [:Process_Role/Test Coordinator:test coordinator]
Must also include follwing in translated form:
- Komponentejeren informerer test koordinator omkring rettede bugs, således at disse bugs evt. kan blive en del af release testen. Hvis bugs ikke indgår i release testen vil de blive testet via unit tests. De rettede bugs vil endvidere blive noteret i release test beskrivelsen af test-koordinatoren.
- Ved kritiske produktions bugs kan det være nødvendigt at branche den aktuelle released produktionskode.
Anchor(ImplementationTime) TimeBR
After iteration has been started and tasks distributed by [:Process_Role/Project Leader:project leader]
- Before [:Process/Code_Freeze:code freeze] within the itereation
Anchor(ImplementationInput) InputBR This can either be
A task from [:Development#CurrentIterationTaskOverview: current iteration task overview] or
A tracker issue that is evaluated to have small implementation time by the [:Process Role/Module Owner:Module Owner] of new tracker issue for that specific module.
Anchor(ImplementationOutput) OutputBR
Release test input to [:Process_Role/Test Coordinator:test coordinator] (may be that there are none)
- Implemented, sanity checked (if code) and reviewed implementation of task
- Documentation update (if any needed)