Format for documenting metric rules

[jdg3352]

Does anyone have any suggestions on a good way to document metric specifications while collecting business requirements? This would be very useful for new developers to make sure they are able to translate business requirements into metric objects. Perhaps a spreadsheet that would track each object and the rules to create it (e.g. compound metrics, level, conditionality, transformation). Basically, the good 'ol writing specs before programming. This would help ensure everyone understands as well as verify the work that needs to be done.

Thanks.

 

[nlim]

hmmm...not the first time I've heard this. Truthfully, that's the job of the business analyst, no? I would not recommend making them learn dimensionality, they might just ask the end user the same question.

What I have seen before is the business requirements are first documented. THen the BA has to create for each business metric, the corresponding MSTR metric or model.
just 2cents.