Differences between revisions 20 and 21
⇤ ← Revision 20 as of 2009-05-12 16:52:39 →
Size: 2333
Editor: SoerenCarlsen
Comment:
← Revision 21 as of 2009-05-14 10:15:55 → ⇥
Size: 2304
Editor: EldZierau
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
 * remember to include [:Process/Assignment Creation:Assignment Creation] as process or as description  * remember to include description & links concerning Assignment Creation

Action(edit)

TODO: Translate http://kb-prod-udv-001.kb.dk/twiki/bin/view/Netarkiv/IBmetodikDec2006SImplementering

TODO: Take Time from http://kb-prod-udv-001.kb.dk/twiki/bin/view/Netarkiv/CurrentUdviklingsMetodik

The Implementation process contains [#ImplementationDescription Description], [#ImplementationPurpose Purpose], [#ImplementationResponsible Responsible], [#ImplementationMethod Method], [#ImplementationTime Time], [#ImplementationInput Input] and [#ImplementationOutput Output].

Anchor(ImplementationDescription) DescriptionBR

  • See if it is necessary to distiguish between Bug/Feature Request and Patch

  • remember to include description & links concerning Assignment Creation

  • remember to include documentation update tasks
  • other ?

Anchor(ImplementationPurpose) PurposeBR

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 Includes Code review. Please refer to the [:Process/Code Review:Code Review Process].

Includes Document review. Please refer to the [:Process/Document Review:Document Review Process].

Includes documentation and sanity check.

NOTE: the process needs to be adjusted to introduction of a tool that can assist in the Code Review Process.

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 by project manager
  • Before codefreeze

Anchor(ImplementationInput) InputBR

Anchor(ImplementationOutput) OutputBR

Process/Implementation WithoutTitle (last edited 2010-08-16 10:25:11 by localhost)