Friday, September 29, 2006

w9-w10 break d5

out of the fire...

looks like things are starting to turn around for me. This semester break was exactly what i needed: more time. I managed to complete alot of things i've been putting off and in good time and manner too. Even with unexpected new tasks arising, I've still managed to stay on top...let's hope things stay that way...


broadband will return in 3-5 business days...

w9-w10 break d4

man, the break went so fast!

link to an article about the dotMobi domain. Could be useful, seems very relevant to my project.

This site is quite comprehensive in terms of ISPs: Broadband whirlpool

i started on that 1000 word report...i've been bogged down in other activities-finding a new broadband provider, resolving my eBay dispute, upgrading my mobile HDD, scouting photography oppotunities, it never ends!

please sir, can i have some more? more break!

Monday, September 25, 2006

w9-w10 break d1

"Evaluation of Submission Four (Revised Design Brief with Functional
Requirements)

This mark is an evaluation of the quality of your design brief. It has been my experience in that the quality of the design project almost always correlates with the quality of the design brief.

I have made comments and suggestions to your design briefs in the documents themselves. You should be able to retrieve the modified design briefs from the dropbox. Please note that I have not read your technical specifications. These will change as you firm up your functional requirements. Finally, please be aware that the standard for the design brief will be much higher when I assess the final design briefs. Errors of the types identified in your current brief will be negatively appraised. So, just because you received a D does not mean that you will get a D next time if you do not improve your brief based on the comments provided. In fact, some of your design briefs regressed, and as such you were asked to re-do the brief.

My main concern is that most of the functional requirements in the design briefs lack specificity. They are vague and describe characteristics of a function but do not describe the function itself, that is, what the application does. Second, most of the functional requirements are incomplete, based on our discussions in the studio. Think of the functional requirements as a list of functions you might hand over to a software developer to write code in Java. Would the programmer understand enough from the requirements list to write the code without further elaboration?"

righty-oh...