(Untitled)

Sep 28, 2003 11:59

ah, what a lovely way to spend a sunday afternoon: writing programming documentation ( Read more... )

Leave a comment

Comments 13

chickenlips999 September 28 2003, 09:19:57 UTC
what are you designing????

Reply

k8tey September 28 2003, 09:21:31 UTC
An 8000 square foot borders bookstore in mankato minnesota. Must have "cutting-edge, sustainable design."

Reply

chickenlips999 September 28 2003, 09:30:56 UTC
nice!! is this for work or skool??? does borders have any special design requirements to keep a theme with the rest of their stores.....

when i was at bruner cott, i worked on a building for a lexus car dealership and they had very detailed instructions about the facade design and materials, but didnt really care anything else....

Reply

k8tey September 28 2003, 09:46:39 UTC
it's for studio...I am supposed to "design a new prototype"- so I don't have to follow any current design guidelines. Rather, I'm supposed to create them.

Reply


(The comment has been removed)

k8tey September 28 2003, 09:52:26 UTC
I had no idea that the idea of a functional spec/requirements doc would also exist in the architectural arena. Though it makes a lot of sense.

As far as I can tell, most computer-related design processes have been modeled from architecture/product design standards. :)

The audience is my studio professor. :P No, really - it would be for the client. It's a checkpoint before doing anything "visual" to make sure you are making provisions for all requirements.

Reply

(The comment has been removed)

k8tey September 28 2003, 17:06:27 UTC
No. That's a great question, though. I think use cases are more readily apparent in physical design - typologies as well as building codes are already well-defined.

If I was developing a new type of building, maybe use cases would be a good tool? But it's a bookstore, so basic functions are already defined. Does that make sense?

I suppose there is some use case scenarios going on in my head though as I delineate adjacencies and apply square footage. For instance, I have to put the cash wrap near the entry - for way-finding and for security. I also know I need "x" percentage of square footage devoted to a childrens section, because 27% of my customer demo is married with kids. I know that storage and the employee breakroom are back-of-house. I run through the user scenarios that tell me this in my head - but writing them out would seem odd.

User scenarios are something I always tried to do for interface architecture, even if it was just an introduction to a functional spec.

Yay! I'm procrastinating! Ask me more!

Reply


dinkydo September 28 2003, 09:42:47 UTC
quick question since I'm working on my office plan at the moment and can't get a hold of my usual person I call.

How wide do corridors need to be in a public space, minimum? (ada, and all...)

Reply

k8tey September 28 2003, 09:48:55 UTC
48" corridors(minimum)
36" wide door openings(minimum)
60" turning radius

:)

Reply

dinkydo September 28 2003, 09:50:05 UTC
thanks... I thought it was 48, but I couldn't remember...

Oh, and I so feel you on the programming. If I'd wanted to crunch #'s I'd have been an accountant. I did the numbers for this particular program last sunday... so you're only one week behind me.

Reply

k8tey September 28 2003, 10:17:59 UTC
I thought you were way ahead and already doing plans? Or is that what you are doing this week?

Reply


Leave a comment

Up