#designmodel

[techiio]

let's define the Design modeling in software, and principles of design modeling

[abhijitbansod]

#design #throwback Before 3D printing technology, we all used to make our model by hands. The model making was favourite part of design process. From planning, cutting, shaping, forming, painting and finally assembling, it used to take 20-30 days to complete the model. The anticipation and wait for completion was nothing less than an exciting journey. Here are images of few handmade models and me. Which was your last hand made model ? #modelmaking #designmodel #productdesign #indiandesigner #designstudio #designlovers @amrita.kaushal @studioabd_design https://www.instagram.com/p/CFpiNm3pYNB/?igshid=1imwkmjv493mf

[ninjin-art]

The result of 24 hours of slow, chilled sketching and lining. I really enjoyed chipping away at the shapes on this page, it's definitely one of my favourites. . . . #art #design #designmodel #sketch #model #fashion #pretty #cute #clothes #referencesheet #reference #artistreference #instaart #copic #pencil #sketchbook #drawingreference #stilllife #lifedrawing #nudesketch #woman #femalemodel #nudemodel #fashiontrends https://www.instagram.com/p/Bwr10PilIuZ/?utm_source=ig_tumblr_share&igshid=1azubrjznrw0j

[jennylittlefield]

Building a model for a big ol' musical theatre show. #dreamgirls #setdesign #designmodel #modelbuilder

[hdeksamen-blog]

To modeller af designprocessen. Den øverste er hentet fra http://haandvaerkogdesign.net/ og er lavet af to lærere fra Svendborg. De viser i en video hvordan de bruger modellen i et forløb om ure.

[team-omega-iot-blog]

Construction Phase week 3:

25 November - 2 December

We made some hardware cases designed in Autodesk Inventor and rendered in 3D Studio max for the daughterboards and sensorholders.

And see picture from 28th November 2013.

We managed to finish the Design model and send it to the account manager - B. Pijls - on Sunday 1 December. We also worked on the Alpha Test plan where we elaborate on our plan to setup the Alpha Test and what we expect what kind of feedback the Alpha Test will give us.

On Monday 2nd December we had a meeting with the account manager about our plans for the project, we wanted to introduce a social campaign, and we will give some more information next week. And we wanted to introduce a new piece of hardware that we wanted to introduce to the account manager.

The account manager was pleased with the results of the Design model and we discussed our plans with him about the social campaign and the new piece of hardware. Furthermore he gave us some feedback on the Alpha Test plan and we added some more goals and expectations in the document.

On the technical side, we worked on the OmegaInterface, which is a software package that is an interface between the Arduino and the Database, it uses TCP and JDBC to communicate between both ends. Now we have implemented a GUI that reads and analyses the messages that arrive on the TCP server and creates a User Interface which displays the occupancy in a carriage. We also improved the communication on the hardware- and the software side, we managed to get a delay which is less than a second to see the changes on the GUI.

We are currently planning for the new iterations 5 and 6 "Transition phase". Next week we will prepare the Alpha Test and try to debug our hardware and software so the public can see our idea and we would like to hear their opinion about the system.

[team-omega-iot-blog]

Construction Phase week 2:

18-24 November

We linked the daughterboard to the motherboard, and the motherboard to the TCP server and connected the TCP server with the database. We did some test and the database filled up as soon as the motherboard and the TCP server connected and exchanged some messages.

We also integrated a new type of I2C communication between the daughterboards and the motherboard. We now use an interrupt-driven communication instead of the mainstream polling, this way the records are more unique(less duplicates) and we can directly see when and where changes occur.

We added the code for the RGBLED in our design, so the devices can easily be debugged without using the serial monitor. We cleaned and revised our code on the back-end, we structured it better using custom hardware libraries and added some needed comments.

Furthermore we needed to document our system for the Design Model, so we drawn some Design Class Diagrams, Design Sequence Diagrams, Package Diagrams and wrote a few Operation Contracts for the hardware and the back-end of the software. The Design Model needed some more artifacts so we added database models and some sketches and prototypes.

In week three we are completing our hardware and software back-end, make some beautiful product design renders and finish the Design Model.