Wednesday 21 March 2012

Design coding 2

Don't know whether this will be any help, but I've been having a think about the design code hierachy we talked about last week and have come up with a few different options as to how we could classify the different levels. The idea - I think - is that there might be some general principles that apply to all areas, e.g. Use & Amount, Layout, Access, Sustainability & Energy from Mitti's draft of last week, then more detail for the sub-areas. Not sure whether we'd need to subdivide these further to allow for different typologies within each sub-area - maybe some but not others, or maybe we just allow enough options within the code for each sub-area to cover the full range...   Does this make any sense to anyone or am i talking complete gibberish??
Option 1:

Option 2: 
 Option 3:

Option 4:
 

And here are some additional headings for the design coding for whichever sub-areas we agree. Comments/ suggestions welcome.

Posted by at

6 comments:

  1. Dumitru Furnea21 March 2012 at 23:31

    I think that Option No. 2 describes the best our project as per individual areas... more related to what we do individually and the story board. The other options tend to overcomplicate the story and make it a little bit hard to understand in relation to individual details and how they link to our areas...

    ReplyDelete
  2. Unknown21 March 2012 at 23:55

    I thought the same to start with, but then I wondered whether there might be enough in common between some of our design areas, or some elements of them that maybe one of the other options might work better. For example, Sharon's area and mine are quite similar in many ways and it might make sense to use the same design coding for the residential parts of both, with individual variations. I guess it's a question of whether we prioritise the individuality of our design areas or a coherent overall apporach.
    I imagine for ease of working we will all produce our ideas for our own design areas (as Option 2) and then when we bring all the ideas together we'll probably find we have a lot of similarities - there's only so many types of paving you can choose from after all!

    ReplyDelete
  3. Miti22 March 2012 at 09:05

    I find that the best idea is the spreadsheet and will explain why...

    There are and will be some common elements of design but the differeces should not overcomplicate the design code. It should be simple and easy to read. What I posted last week should be taken as general and then elements from there plus whatever is particular for each area should be added to individual designs with some image examples or sketches. From everything that I saw I'd only use individual spreadsheets. (I'll explain below)

    We need to think further at how we include this in our presentation to understandable level. Therefore I think we need to stay simple, perhaps using the spreadsheet which is very organised and easy to read. The only problem with that would be to include the images and examples.

    So, what I suggest is to take the individual sections from that spreadsheet and fill them in with information and add the images, examples and sketches below the table. This way we would only have 1-2 pages each plus a general coding for the whole area which is another page or two - without having to fill in all the information on a similar spreadsheet again.

    Once we fill the individual spreadsheets we don't need to put them in one big spreadsheet as the images would be too many and hard to organise - which is more work. We only need to create one document to include the individual work.

    To complete the General coding from last week we only need to add the information that is missing without altering the format as it is easy to read and understand.

    Easy job... done. :)

    Mitti

    ReplyDelete
    Replies
    1. Unknown22 March 2012 at 14:30

      I think we use the images and examples in our presentation and only put the spreadsheet(s)/ document on the disk we hand in. I don't even know how practical the spreadsheet is going to be to fill in, it may be easier just to use as a prompt.

      Delete
    2. Miti22 March 2012 at 14:37

      I'll try to fill in a spreadsheet today and add the images as well to see how it looks ... as for individual areas. I'll try to keep everything on one sheet or maximum two...
      It would be ideal if we only use one sheet for the individual areas coding, then we can present them and also print them when it comes to pin them up - if we have to.

      Delete
    3. Miti22 March 2012 at 18:15

      Hi... I squeezed my brains and tried to go down the road with the spreadsheet.
      However I tried I found it difficult.
      Tamasin, I have to agree with you in your comment. the spreadsheet is not very practical no matter how attractive looks at the first look.

      I found that the mainframe set out in the spreadsheet doesn't apply in the same way to all areas. For instance there are a few things that repeat themselves on different columns and other headers simply don't apply using words as images are much more useful (i.e. layout, scale, appearance)
      I think the method looks good but unfortunately not very functional for me. Separating the images from the title would only create confusion. By tomorrow I will upload the way I found it most simple and straight forward, simply by following the way I've done it last week with the addition of images and examples.

      However, the spreadsheet was useful in terms of using the headers as guidance for coding the individual areas. By following them it is very easy to build up (fill in) the design code including the visual examples.

      Treating the last week's Design Code as general and following the spreadsheet headers as example/guidance for individual areas will complete the design code beautifully.. :)

      Of course there is still room for improvement.. :)

      Delete

Post your comments here

Subscribe to: Post Comments (Atom)