Designers with Sketchbooks who work a lot on the computer
Target User
Slide 3
Concept: Connected Sketchbook Ingredients A sketchbook with
integrated storage A GUI showing a virtual sketchbook. How it works
When flipping the pages of the physical sketchbook, the program
flips along. One can drag and drop files on the virtual pages, thus
flip through their digital files. Added value Handwritten notes and
digital files are now linked and stored in one portable sketchbook,
increasing workflow. NOT: DIGITALIZING ANYTHING or SHOW DIGITAL
FILES IN BOOK
Slide 4
Scenario
Slide 5
Value ladder
Slide 6
Architecture
Slide 7
Proposal for Modularity Cover The cover is a separate module
which will be used as cover. This will be used a module which can
be used for another version if needed. It includes connectors for
the pages. Case The case should be a module, with the fittings for
the other modules, so it can be replaced or reused as a part in a
new model. Bundles of pages with tags Because there probably will
be models which will have less/more pages. The pages should be in a
bundle of the amount which the thinnest book will have.
Slide 8
Proposal for Modularity Power / Signal transformer (Hard Disk)
+Power / Signal transformer (RFID) These modules will control
translate the RFID data/ power, and Hard Disk data/power. They will
be separate so if you only change one module (for example the hard
disk), you only need to change one transformer. RFID reader There
are different RFID readers available with different ranges and
different amount of tags which it can read at once. Therefore the
RFID should be a part which can be replaced or reused in another
model. Hard Disk The hard disk should be a separate module, so it
can be used in next models or be easily be replicable for more/less
storage. It should be replaceable with a Flash Drive.
Slide 9
Proposal for Modularity USB connector Since USB is developing,
it is good to leave the USB connector as a separate module, so it
can be replaced with a more advanced one in next versions. Software
+ User interface The software should be created in such a manner
that it will read out the amount of pages, so it can be used in
different models. The software structure could be build out
different classes so it will be easily adaptable for new versions
with different functions. By creating some kind of library for the
buttons and graphics used in the interface, it will be possible to
reuse these in a new design for a new version or update.
Slide 10
Product Specification System behaviour Desired: Storage
Responsive Browsing Automatic Synchronisation Unavoidable: Wear
& Tear Tag Collision Weight Heat Needed supplies & means PC
(with minimum system requirements) USB port External conditions
& regulations Humidity Distortion by magnetic field Distortion
by metal Shocks/vibration Weight (on the product)
