Home » Community » Coffee corner » Tools or methodologies you use when developing software
|
|
| Re: Tools or methodologies you use when developing software [message #13195 is a reply to message #13194] |
Thu, 20 December 2007 07:27   |
Mindtraveller
Messages: 917
Registered: August 2007
Location: Russia, Moscow rgn.
|
Experienced Contributor |
|
|
I tried UML too, but came to simplified version of action diagrams on scratches of paper.
Every time having some programming task, first of all I use my imagination. Pretending to be simple user, I get sheet of paper and drawing what will I see on the screen.
Yes, I start with drawing sketches of program GUI and ideas how it should behave. I start with being simple user.
Then I put these sketches to some corner of the table for day, 2 days or even week. After these days I take papers, look at the interface and start thinking what should be erased from there. Interface should be as simple as possible making program functionality most native and clear for user.
For example, I try to use 1 toggle button where most programmers use two buttons or switches - it all depends on exact situation.
Only after polishing GUI, I memorize that I`m a programmer and think of program structure that implements my exact GUI and it`s behaviour.
I do this by taking another sheet of paper and writing big program components and their dependencies. Polished that general model, I make sketches of more detailed versions of components (modules, classes).
|
|
|
|
|
|
| Re: Tools or methodologies you use when developing software [message #13220 is a reply to message #13194] |
Sun, 23 December 2007 13:32 |
 |
tvanriper
Messages: 85
Registered: September 2007
Location: Germantown, MD, USA
|
Member |
|
|
I rarely-to-never have time to get into huge UML sessions or worry about Rational Rose and so on.
I might spend a little time on the whiteboard (since much of what I do involves communicating across various forms of hardware), working out the component design so I know what to program, but once I get programming, I see everything in my head.
I have a tendency to program both from the bottom up and from the top down. Eventually, the code meets somewhere in the middle.
Experience has taught that if I only go from the bottom up, I wind up with a butt-ugly GUI that few people can use. If I only go from the top-down, I wind up with a crappy design that I cannot extend later. Working both ways, I wind up creating a glue-layer between the two, and everything works well.
|
|
|
|
Goto Forum:
Current Time: Sun May 11 20:12:26 CEST 2025
Total time taken to generate the page: 0.02071 seconds
|
Members
Pages
Help
Register
Login
Home
