Hi All,
I think Stefan has captured my concern very well, I had assumed that the use
cases model and map to real world scenarios, rather than just buckets to
capture all requirements with somewhat arbitrary boundaries.
The point of confusion I still have is that during the call a comment was
made that "look & feel was orthogonal to all use cases", this was
re-enforced in Rex's recent email as well.
Whilst I agree that look & feel could in general be considered a consumer
issue and common to all use cases, it needs to be captured somewhere and
understood.
The emails thus far appear to favor using the embedded use case as the LCD,
including consumer flows.
Regards
Greg