OverviewNewsDownloadDocumentationDeveloper toolsContact
Imagen izquierda
You are in: PhpReport > EvaluationBriefs2007Story Edit - Attach

EvaluationBriefs2007Story

Story summary Evaluation briefs by area, customer type and customer
Iteration PracticeSummer2007
FEA 07LOW03
Story Lead TeamPlanningSpreadSheet2007Story
Next Story CustomerDetails2007Story
Passed acceptance test No

Acceptance Criteria

Implement new evaluation briefs by area, customer type and customer.

Additional Specification Comments

In a way similar to the existing "user evaluation" and "project evaluation", write three new pages (or one valid for the three purposes depending of a parameter) showing a table that performs the following matches:

   1. Area evaluation
      1. Area / project (*)
      2. Area / person (*)
      3. Area / task type
      4. Area / customer (*)
      5. Area / customer type
   2. Customer type evaluation
      1. Customer type / area (*)
      2. Customer type / project (*)
      3. Customer type / person
      4. Customer type / task type
      5. Customer type / customer (*)
   3. Customer evaluation
      1. Customer / area
      2. Customer / project (*)
      3. Customer / person (*)
      4. Customer / task type

Those combinations marked with an asterisk (*) are the most important ones to implement. It would be a good idea to think of a generic system to get the column and row titles and the data, maybe writing one query for each of them. Then, a big table would be filled with the results and there can be a unique piece of code to render the table into html, making the page design very flexible and only depending on a set of sql sentences.

The row and column totals and percents could be automatically computed. Have a look at the way it's already done in projevaluation.php.

All the customer, customer type and area information is already implemented. You have all the labels in the label table:

  • Customer: label type "customer"
  • Customer type: label type "ctype"
  • Area: label type "parea"

Besides "labels", you may find also useful the "customer", "projects" and "project_user" tables.

If you have any question about this use case, get in touch with jota at igalia dot com.

Implementation Notes

Delay Causes

Final or Pending Considerations

Tasks in this story

Tasks Est Spent To do Risk Reviewer Developer Task Name Start Date Est End Date End Date
Task 60 0 60 Low EnriqueOcana   Evaluation briefs      


div class="twikiTopicInfo twikiRevInfo twikiGrayText twikiMoved"<&/div>-->

Igalia, S.L. © A Coruña-Pontevedra (Galicia), 2001-2007 - Aviso Legal - Política de privacidad
Igalia™ is a registered trademark of Igalia, S.L. Powered by TWiki

Wiki actions