The use cases need a user first which in most cases is a human, so it's equally important to design your UI use cases also. Software is built for humans first.
Agreed. Use cases is a bit of a loaded word so perhaps a bad choice.
My intent was that shared understanding of the goals based on user needs would need to be established before starting the formal UI or the backend. Starting without will likely be a difficult road regardless.
The Formal UI and backend knowledge would leverage mockups and wireframes that were made during the quest for shared understanding. Keeping in mind it'll likely change as the process moves forward. ;)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm totally with you on building domain use cases first.
I'd take it a step further and try to remove the technical from it. Then the order doesn't matter and can potentially be worked on in parallel.
The use cases need a user first which in most cases is a human, so it's equally important to design your UI use cases also. Software is built for humans first.
Agreed. Use cases is a bit of a loaded word so perhaps a bad choice.
My intent was that shared understanding of the goals based on user needs would need to be established before starting the formal UI or the backend. Starting without will likely be a difficult road regardless.
The Formal UI and backend knowledge would leverage mockups and wireframes that were made during the quest for shared understanding. Keeping in mind it'll likely change as the process moves forward. ;)