#wk04

I found it difficult to implement xcopy specifically for batch files, not from the windows comman prompt line and could not find any documentations that switched between command prompt and batch files. I figured it might be easier to try looking for ways to backup files as a way to copy files and stumbled across this guide to back up files. This is the code section which does the backing up:

@echo off :: variables set drive=G:\Backup set backupcmd=xcopy /s /c /d /e /h /i /r /y

echo ### Backing up email and address book (Outlook Express)... %backupcmd% "%USERPROFILE%\Application Data\Microsoft\Address Book" "%drive%\Address Book" %backupcmd% "%USERPROFILE%\Local Settings\Application Data\Identities" "%drive%\Outlook Express"

echo ### Backing up email and contacts (MS Outlook)... %backupcmd% "%USERPROFILE%\Local Settings\Application Data\Microsoft\Outlook" "%drive%\Outlook"

echo ### Backing up the Registry... if not exist "%drive%\Registry" mkdir "%drive%\Registry" if exist "%drive%\Registry\regbackup.reg" del "%drive%\Registry\regbackup.reg" regedit /e "%drive%\Registry\regbackup.reg"

:: use below syntax to backup other directories... :: %backupcmd% "...source directory..." "%drive%\...destination dir..."

echo Backup Complete! @pause

Below I have recreated a more simplified code to work with using the above as a guideline :

@echo off title Downloading Data :: variables set drive=E:\ set backupcmd=xcopy /s /c /d /e /h /i /r /y echo off %backupcmd% "%USERPROFILE%" "%/DRIVE%\test\backup" @echo off cls

It’s very similar to the guideline except I decided to change ‘@pause” with ‘cls’ which clears the screen. The code I recreated simply backs up everything in the computer just to simplify things. As previously mention @echo off  stops command prompt from displaying the command itself when executing and title sets the title for the command prompt window. Variable tells command prompt that we want to se the variables drive to ‘E:\’ and backupcmd defines the command to be used (which in this case is xcopy).  I have implemented the code on Notepad and saved the batch file onto my USB drive as copy.bat, where my copied files will be stored in the folder i called ‘test’ and sub folder ‘backup’. The below picture is evidence that the batch file is able to copy files from my computer.

Integrity

Integrity was the main focus of the lecture. It is a way to determine if the message recieved is the real message given, not twisted or faked by someone else. Cryptographic hash functions are a great way to keep the integrity of the message. It basically computes a hash (some jumpled code) from the message, where if the person from the recieving end were to get it, they can compute the hash of the message and see it if matches the sender’s hash function. This hash function is difficult to reverse. However, it does have vulnerabilities such as someone changing the orginal message and hash code, so the reviever would recieve the original message but would think it is after comparing the hash to the one attached to the fake message’s one. MACs (message authenticated codes fix this problem as it ensures the message hasnt been modified by anyone by combining the hash with a key. however, this method still has a few vulnerabilities. This includes pre-image attacks, second pre-image resistance, lengthy extension attacks and collision resistance.

This week was a secret case study and it was based on designing a physical site security. We had to analyse main things that needed to be protected as well as 3 key features of the security design. I believed that the utmost important thing to protect was data, so servers and computer hardware that contained important data was first priority. Next were people who work in the building as safety of employees is extremely important in any workplaces. So the main features of my design were:

Personal ID This is to limit access to certain people and also have the person be verified. Their ID will be able give them access to certain parts of the facility but also them from entering important labs (e.g. a receptionist has an ID card to let her enter theb uilding, but she is unable to access labs)

Hidden security cameras inside and outside the building There should be security cameras in every room in the building. There should be no blind spots so that everyone who access a specific room can be identified in case something is stolen or destroyed.

Lock Out Laws

For Tuesday afternoon, Read –> Gather –> Sketch!

Read chapters 2 and 3 of The Functional Art.

Optional readings in Dropbox:

1. A primer on semiotics*

2. Chapter 1 from Envisioning Information, "Escaping Flatland" (Tufte)

*If you've yet to take Sign & Symbol, I recommend you read this.

Gather visual inspiration:

1. Browse these info design patterns 

2. Do visual research for aesthetic inspiration

3. Compile the above into a mood board (PDF format).

Sketch:

1. Thumbnails for each of your subcategories (aim for 10–15 per)

Read

The Design of Design Studio

Bridging the Gap with Requirements Definition

Collaboratively create a single Requirements Document:

Compile each of your requirements in a Google doc.

Condense redundant requirements into single bullet points.

Use specific language to describe user needs in context (when + where) by using concrete nouns (what) and vivid verbs (how) .

Don't worry about design. Be sure to spellcheck and proofread!

Talk to potential users of your interface:

Why do they (or would they) engage in the process? What is the value of the process to them?

How do they carry out the process? What activities and tasks do they perform?

Document your findings.

Articulate your interface's epicenter:

Ground your epicenter in the user input outlined above.

Describe 2–3 core features that support user goals and activities.

Be clear and concise (max 150 words to articulate your epicenter).

Revise and refine your your taskflows:

Derive your taskflows from your user input and core features (above).

Determine: Does each feature need a separate taskflow?

Use verbs to describe tasks.

Use a visual language to describe nuances of your taskflows. (Refer to Communicating Design chapter 6: Flow Charts.)

Place your user research findings, epicenter description, and taskflows in a tidy document. Content must be legible and readable.