[ 
http://jira.codehaus.org/browse/MOJO-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92848
 ] 

Olivier Dassaud commented on MOJO-732:
--------------------------------------


Hello !

First, thanks David for the work done with the Maven2 Dashboard with 
multi-module support that really answers project manager needs.

So, you're right, the next step is clearly to follow the evolution of such 
aggregated metrics.

In order to build historical graphs, data need first to be stored, and then to 
be shown in such a "beautiful" way, easily human-readable.

So about what to save, and what to show I'd make a distinction between two 
different solutions or functionalities :
- a +simple solution+ that would satisfied most of project manager needs : to 
+store only metrics shown by now+ by the actual Maven2 Dashboard plug-in into a 
database, and to show historical graphs of these metrics with JFreeChart
- a +more complex+, that I call +"business intelligence"+ solution : to store 
+whole data+ of every quality report (in more complex and coherent database 
schema, huge work), and to allow reporting with tools like birt, jasper report 
or others...

In my own opinion, the two ways can live together, but +the first requires less 
development effort, and provides most of the functionalities needed+.
I think that people, and especially project manager, doesn't have for now the 
ability to interpret too low level metrics. It may changes...
The second solution could be a new "Maven2 Quality Business Intelligence 
plug-in".
With the first solution, it could be possible to someone to display, in a 
portal for example, or with a business intelligence tool, a comparison between 
metrics of different projects, and to do business intelligence with some data, 
sufficient data I think for most of the people.

I've noticed too that daily builds could represent such a lot of bytes 
(particularly on enterprise project-shared servers we're managing). So I think 
that the best way is, with simple solution one :
- to store in a database metrics that would be shown in historical graphs, so 
actual Dashboard selected metrics for each module
- to keep on file system only few quality reports (with time digressive 
philosophy : all the last month reports, one day a week report for the month 
before, one day a month for the months before...) in order to see what the 
project looked like before (nostalgic mood).

Hope it would help.

Regards

Olivier.


> database support and historic view
> ----------------------------------
>
>                 Key: MOJO-732
>                 URL: http://jira.codehaus.org/browse/MOJO-732
>             Project: Mojo
>          Issue Type: New Feature
>          Components: dashboard
>            Reporter: David Vicente
>            Assignee: David Vicente
>
> Hi all,
> i will start the database support for the dashboard-maven-plugin.
> I'll create a third view for each dashboard report to generate an history 
> page with JFreechart time series graph representing the indicators's 
> evolution.
> At this time, i generate an xml result file (dashboard-report.xml) which 
> contains only aggregate results.
> If i send you this email, it is to synthesize your needs relating this 
> historical view or quality statistics :
> - do I save in the base only the aggregated data coming from the dashboard 
> xml result file
> - must I store the whole of the reports (cobertura, pmd etc...) and make the 
> aggregation then
> i will use an external database (selected by the user) to make possible the 
> base's re-use  with another tool allowing more precise statistics than what 
> could be made by the dashboard or to create statistics of projects wallet
> for example, to compare cobertura ratio between 5 projects.
> it could be interesting to create an issue in JIRA to follow this 
> conversation?
> I await your answers impatiently.
> Thanks for your help.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to