Docstoc

Journal

Document Sample
Journal Powered By Docstoc
					                                            Journal
Nick’s Case Study Page:
Version 1 – Nothing

Version 2 – original Google Docs link added (No olverlaying hyperlink)

Version 3 – Introduction ofthe original hyperlink with text overlay

Version 4 – Added page dividing line, failed HTML text code, for Doc Stoc Widget

Version 5 – Deleted failed HTML text code (500-600 words deleted)

Version 6 – Added proper DocStoc Widget.

Version 7 – Resized DocStoc widget to a more reasonable size

Version 8 – Resized again.

Version 9 – Added minimum requirements to run some software and added page divider.

Version 10 – Added YouTube Video

Version 11 – Added SlideShare Powerpoint

Version 12 – Reformatted sizes to make the Case Study more user friendly.

Version 13 – Resized the widgets again.

Version 14 – Added picture and table: Representation of an instruction involving the ALU

Version 15 – Added another table explaining Operation Code

Version 16 – Added Bibliography.




Additions around the site.
#1 8.1.1.2 Intellectual Property (9 words added)

    -   Change: Heer bee teh lynx to teh anno-potatoed License :3 Dilbert: licence terminology
        Because of the legal nature of license agreements, they often use terminology that is
        difficult to understand. As license View changes from previous version. (Word count: 1359)

#2 8.1.1.3 Inclusivity (3 words added, 1 word deleted)

    -   Change: http://www.assistiveware.com/videos.php?video=Giesbert&format=mov Inclusivity
        Project Team: Ashleigh & Georgia• Case Study 3A: Inclusivity - the need for software design
        and development to be inclusive – cultural perspectives – economic perspectives – social
        perspectives – gender perspectives – disability perspectives> evaluate existing software
        interfaces in terms of its inclusivity• Case

#3 8.1.1.3 Inclusivity (2 words deleted)

    -   Change:
        http://www.assistiveware.com/videos.php?video=Giesbert&format=movhttp://www.assisti
        veware.com/videos.php?video=Giesbert&format=movInclusivity Project Team: Ashleigh &
        Georgia• Case Study 3A: Inclusivity - the need for software design and development to be
        inclusive – cultural perspectives – economic perspectives – social perspectives – gender
        perspectives – disability perspectives> evaluate existing software interfaces



#4 8.1.1.3 Inclusivity (2 words deleted)

    -   Change: http://www.assistiveware.com/videos.php?video=Giesbert&format=movInclusivity
        Project Team: Ashleigh & Georgia• Case Study 3A: Inclusivity - the need for software design
        and development to be inclusive – cultural perspectives – economic perspectives – social
        perspectives – gender perspectives – disability perspectives> evaluate existing software
        interfaces in terms of its inclusivity

#5 8.1.1.3 Inclusivity (4 words added, 1 word deleted)

    -   Change: Assistive Ware, Head Designed Assistive Technologies Assistive Technologies Inc.
        Youtube Video On Assistive Technologies Inclusivity Project Team: Ashleigh & Georgia• Case
        Study 3A: Inclusivity - the need for software design and development to be inclusive –
        cultural perspectives – economic perspectives – social perspectives – gender perspectives –

#6 8.1.2.3 The relationship between hardware and software (9 words added)

    -   Change: For more information on this topic follow the
        link:http://en.wikipedia.org/wiki/Instruction_cycle the initiation and running of an
        application start fetch-execute cycle locate on disk load into RAM display the start screen
        wait for user input the existence of minimum hardware requirements to run some software
        Due to technology

#7 8.1.2.3 The relationship between hardware and software (91 words added)

    -   Change: For example a game which has been released recently; Assassins Creed II, has
        requirements that may not be met by recent but not the newest PC's, these may have once
        been considered as "the best on the market" and are now being very quickly outdated

#8 8.1.2.3 The relationship between hardware and software (40 words added, 10 words deleted)

    -   Change: The term was coined in order to contrast to the old term hardware (meaning
        physical devices); in contrast to hardware, software is software. intangible, meaning it
        "cannot be touched". data Distinct pieces of information, usually formatted in a certain
#9 8.1.2.3 The relationship between hardware and software

EDIT NOTE: Update: Devices Link


Threads

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:79
posted:3/21/2010
language:English
pages:3