File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes OO, Patterns, UML and Refactoring and the fly likes UI in Robert Martin's ASD PPP Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "UI in Robert Martin Watch "UI in Robert Martin New topic
Author

UI in Robert Martin's ASD PPP

HS Thomas
Ranch Hand

Joined: May 15, 2002
Posts: 3404
In ASD PPP does not cover UI.
Isn't designing the User Interface an Analysis activity as the UI ought to be geared to the user's tasks ?

This obviously has a corresponding effect on the design (which tasks get lumped together).
So even though it's not mentioned I think it's crucial to agree on that early with User Acceptance. I think Robert Martin left it out wisely because this stage is usually crucial in the early stages of the project and thereafter set in stone.
And the analysts would need early feedback from the Designers that it is doable.
regards
[ October 08, 2003: Message edited by: HS Thomas ]
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
Originally posted by HS Thomas:
Isn't designing the User Interface an Analysis activity as the UI ought to be geared to the user's tasks ?

No, it isn't. The UI is part of the solution to the problem you try to solve.

This obviously has a corresponding effect on the design (which tasks get lumped together).

No, it shouldn't. The UI can as easily be developed incrementally, as any other part of the system. The only thing you need to take care of is that it is reasonably decoupled from the business logic (by using MVC, MVP or something similar).
So even though it's not mentioned I think it's crucial to agree on that early with User Acceptance. I think Robert Martin left it out wisely because this stage is usually crucial in the early stages of the project and thereafter set in stone.

By no means at all. See http://groups.google.com/groups?selm=iuj1hv0lh1lcu3rfbn07042s9f377e2n9c%404ax.com&rnum=1


The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
HS Thomas
Ranch Hand

Joined: May 15, 2002
Posts: 3404
Thanks. I'll have a stab at writing 'Hunt the Wumpus'.
regards
HS Thomas
Ranch Hand

Joined: May 15, 2002
Posts: 3404
Does TDD lend itself to writing the UI with JSP and JSTL Tags ?
Can I have a Hunt the Wumpus UI of web components ? I suppose I can decide on the point of creating the UI whether it should be a Swing or Web component interface ,for example.

regards
[ October 08, 2003: Message edited by: HS Thomas ]
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
Originally posted by HS Thomas:
Does TDD lend itself to writing the UI with JSP and JSTL Tags ?

Unit testing JSPs is a little bit tricky. But that only makes it more important to make them as thin and dumb as possible.
Can I have a Hunt the Wumpus UI of web components ? I suppose I can decide on the point of creating the UI whether it should be a Swing or Web component interface, for example.

I'd think you could do that, too. Try it and tell us what happened...
Stan James
(instanceof Sidekick)
Ranch Hand

Joined: Jan 29, 2003
Posts: 8791
I think UI can go through the same conceptual phases of analysis and design as anything else. Start abstract with business requirements, work down to implementation decisions.
Repeating from above: TDD seems to be hardest with UI. Decoupling the logic from the UI can let you build all the algorithms and data with no UI, plug in any one or more UI later.
That may not be the most efficient for distributed systems like web or n-tier client-server, because it doesn't necessarily yield services chunked up in UI-function sized bits. But starting with the UI and building one back-end call per UI function can give you a very inflexible back end. Been there, done that with a PowerBuilder front-end and a set of MQ-Series calls to the mainframe optimized to fit the screens. Some of those MQ-structures were very hard to re-use for the next client with different screen flows!


A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: UI in Robert Martin's ASD PPP