1. Generic setup: list of project
phases |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
0.
Project Setup |
|
1.
Concepting phase |
|
2.
Prototype |
|
3.
Content input |
|
4.
Service setup |
|
5.
Publication |
|
|
2.
Subsequent work packages (in this example: for tasks where the Web Developer
(WD) has the lead) |
|
0.
Project Setup |
|
|
(WD): definition of
coding standards and compatible browsers |
|
1.
Concepting phase |
|
|
(WD): service map, site
level hierarchy, information architecture, metadata definitions. |
|
2.
Prototype |
|
|
(WD): development site in
Drupal; identification and configuration of needed modules |
|
3.
Content input |
|
|
(WD): setup asset
repository and site level element structure |
|
4.
Service setup |
|
|
(WD): cross-browser
compliance; functionality tests, degradation tests, mobile devices tests |
|
5.
Publication |
|
|
(WD): post-publication
tests |
|
|
3.
Input relations (for WD tasks), example output relation for phases
4./5.:testing/publication (WD and Project Manager (PM), WD and Backend
Developer (BD)) |
|
0.
Project Setup |
|
|
(WD): [input->
service scope as defined by customer] definition of (1) coding standards and
(2) compatible browsers |
|
1.
Concepting phase |
|
|
(WD): [input ->site
contents, initial copy texts & content concept] (1) service map, (2) site
level hierarchy, (3) information architecture, (4) metadata definitions. |
|
2.
Prototype |
|
|
(WD): [input->virtual
server w drupal installation] (1) development site in Open Source CMS; (2)
identification and configuration of needed modules |
|
3.
Content input |
|
|
(WD):
[input->predefined texts/teaser structure, site element design] (1) setup
asset repository and (2) site level element structure |
|
4.
Service setup |
|
|
(WD): [input->test
plan, specifying 50 % of site contents to be tested; use case documents for
signup functionality] (1) cross-browser compliance; (2) degradation tests,
(3) functionality tests, (4) mobile devices tests [test protocols->] |
|
(BD): [input->use
case documents]: (1), extract, (2) review and (3) delete submitted contents
in submission database |
|
5.
Publication |
|
|
(WD): post-publication
tests [test protocols->, tickets->] |
|
|
(PM): [input->test
protocols, tickets] [launch report->] |
|
|
4.
Task breakdown and detailed output relation (example for phase 4: Service
setup, WD tasks) |
|
|
(WD): [input->test
plan, specifying 50 % of site contents to be tested] |
|
|
NEW (WD): assemble
report sheet, containing column entries for (1) page layout OK, (2) placement
layout OK, (3) content rendering OK, (4) link functionality OK [test
protocols->5.] |
|
|
(WD): [input->use case
documents for signup functionality] |
|
|
4.1.1 (WD): test signup functionality with (1) priority A browsers
(full compatibility, perfect rendering) and with (2) priority B browsers
(functionality given, elements displayed as standard HTML) [test
protocols->5.] |
|
|
4.1.2 (WD): cross-browser compliance; degradation tests: (1): go
back in version histories until the rendering breaks, (2) turn off Flash,
Javascript, CSS with latest browser versions (and the two previous ones)
[test protocols->5.] |
|
4.1.3 (WD): do all lists, links and input fields work? [test
protocols->5.] |
|
|
4.1.4 (WD): mobile device tests [test protocols->5.] |
|
|
4.2.1 (BD): extract submitted data from database and send to WD [csv
file ->4.2.2] |
|
|
4.2.2 (WD): [input->submitted data csv file] review and compare
data to use case documents |
|
|
4.2.3 (BD): delete submitted contents in submission database |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|