| Re: [epf-dev] Feedback on : Review and Strategy for Design, visual and non-visual |
Hi Brian,
Thanks for taking the time to organize your content and questions so well-
Here are my thoughts...
I like the level of detail for your steps." Identify Design Elements," "Design Components" etc. They should scale well.
But I need to spend a bit more time reviewing the visual and non-visual modeling packages. I have some questions here from a scaling perspective, and need to prototype likely scenarios for building on top of this structure. I'll try to work through some of this by Thursday in order to better respond to your question about collapsing those visual modeling steps into one.
An Area to Address - How about data? I think in order to give everyone a better base from which to scale, it would be good to see some targeted content here. I like the separation of UI, Data, and application tasks. This separation will be helpful to practitioners IMHO - so they won't have to sift through too much to find what's relevant for their area of focus. If Data was not considered for the Sept release, I'd like to revisit that decision.
Refactoring - I prefer leaving this as a concept/guideline. It's something we do as we build/code as a best practice, and I see you are using it in your "Refine Design Decisions" step as well. It's logical to have some Guidance for refactoring in this step - rather than calling out an additional step. (Refactoring guidance will help you accomplish that step)
I have some suggested refinements for the content, but I see this morning that Scott has sent out a version of your doc with comments. I'll put mine in-line with his and forward back to you.
Regards,
Denise
_______________________
Denise Cook
IBM Rational
RUP Content Development
denisecook@xxxxxxxxxx
(303) 570-3748