D=
Monday, February 22, 2010
Sunday, February 14, 2010
owh blah
context diagram - Summary. Uses circles (Processes?) , Squares (External entity) and arrows (Data Flow)
data flow diagram -
_____________________________________________
Telephone number as 'text' rather then 'number' because less storage as there is no mathematical blah blah. :)
Boolean - yes-no answers only. Data Type.
_____________________________________________
blah
Posted by LouisaK at 2:05 PM 0 comments
Sunday, February 7, 2010
Siri, Artificial Intelligence.
Article:
___________________________
-App on an iPhone
-Decoding what we are saying (Voice command)
-Location needs to be known to cross reference with other data for best interpretation
-Not Sophisticated enough to find website and book restaurant nor call up probably has data stored from participating restaurants :)
-Could probably only just tell you whereabouts rather then actually booking.
-Suggests it has to be able to do more then other data bases... i.e book a restaurant it should be able to tell its a command however unless you are near the location of the city book then it'll find a restaurant there.
-Privacy, social and ethical implications. Booking a restaurant near your home... you must tell it where your home is. Data which could be shared with the company.. within the whole system. You could also tell it when you're working so it knows your best leisure times, pretty much builds up a profile on you on its system. stalk stalk stalk.
-To book something.. gotta give it credit card details. If Hacked BAM bye bye money. (Security fail)
-Starts of with simple small none critical tasks. Shall develop later on.
Posted by LouisaK at 4:44 PM 0 comments
Sunday, January 31, 2010
NEW YEAR ~
Database fun.
PAGE 44 TEXT BOOK
*Flat file data bases - Ideal for simple lists ie.... appointments diary and phone lists.
*Relational databases -Ideal for larger more complex lists. ie..Personal Records and stock inventory
For store sales and product lists for bigger companies such as woolworths it would be far to complex for a simple flat file data base to hold all records of their products. Instead of paper handouts hypermedia would be much more easier to maintain and run.
For Personal records in companies its a bit too complex to use flat file databases as theres only one table therefore there are many columns within the one table and the data is messy and harder to use. Relational databases much easier. DON'T use hypermedia, privacy issues poor security. Data Stolen, hacked, Better into files in an office.
encryption: Data coded, so unauthorized people cant read it.
for more info page 46-49.
____________
Data Dictionary (Metadata)
tell us the:
*data type - ie text, numeric
*field names
*Field Size
Sorta telling us how its built, telling us about the data.
Usually refers to a table. If you have 4 tables you have 4 Data dictionaries one for each.
PAGE 49 for more info on data dictionaries.
Inquires and hypermedia time to refresh when i get home. uftt lol actually just go through EVERYTHING from yr 11 before i die in confusion.. funny enough i have no idea what the answer is when he asks until he says it and im like ohhh i knew that! why am i sooo gaaahh >_> dont forget protocols ie file transfer protocols.
Posted by LouisaK at 2:07 PM 0 comments
Wednesday, November 25, 2009
26-11-09 :: long time no post
Well i havent posted here in ages..... and ages.
The past couple of lessons we've been school enrollment databases on access. The instructions provided have been a great help with the first 2 sections with creating the data and making a report etc... however once i reached section 3 i hit a couple of issues with te information growing from simplicity to something more difficult as if expecting me to know what it was on about. Gah. I know i wasnt the only problem who hit a dead end a couple of people had made a mistake somewhere a rather stuffing up the rest -.-" I've some-what given up i'll ask jess to help explain to me later. :)
I guess the major issue was creating the relationships. Gosh it seems so simple and yet its a PAIIIINNNN to make.
________________________________
Posted by LouisaK at 3:19 PM 0 comments
Tuesday, September 22, 2009
Definition of some stuffies;;
Well considering my IPT exam was a flunk ._. i dont know about the rest of the class though we gotta look up some stuff. ga
Bar code reader:
any device that can convert a bar code image into data
http://www.blogger.com/www.lomag-man.org/glossaire%20dico/glossairelinventaire/glossary-of-inventoryaccuracy.php
Magnetic stripe:
A magnetic stripe card is a type of card capable of storing data by modifying
the magnetism of tiny iron-based magnetic particles on a band of magnetic material
on the card. The magnetic stripe, sometimes called a magstripe, is read by physical contact and swiping past a reading head.
- thankyou wiki :P
http://en.wikipedia.org/wiki/Magnetic_stripe
Posted by LouisaK at 4:53 PM 0 comments
Wednesday, August 26, 2009
Software Processing:
Large amounts of data processing such as spreadsheets and data bases i.e access.
Take good images on your camera you don't always use them as they are, you can edit and manipulate etc... This is processing
Movie maker is also a manipulating thing, video editing software. i.e adobe premiere - process high quality movie editing.
Sound files are also something you can process and manipulate.
________________________________________________________________
another software process thing involving sound ;;
Software that can take an appropriate voice and turn it into a command.. talk to the computer and it should be intelligent enough to process it into a command. :) recognise voice.
example - Dragon Naturallyspeaking
Posted by LouisaK at 5:09 PM 0 comments