Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
39 Cards in this Set
- Front
- Back
|
Web 1.0 |
The “Traditional” Web Publishers and consumers: -Content published by organisations -Content passively consumed users “Read-only” Web Information “pulled” by consumers |
|
|
Problems with Web 1.0 |
1. Publisher-generated content: Restricts type of content available 2. Inflexible: Data presented the way publisher demands 3. Limited interaction: “Round-trip” model 4. Pull technology: User must know where content is, proactively seek the information, and anticipate when it’s likely tobe updated |
|
|
Web 2.0 |
Rethinking of goals of the Web: Not a redesign or fundamental technology change Focus away from publish & consume: Move toward enable & create |
|
|
Key Concepts of Web 2.0 |
User-generated content(e.g. Wikipedia, TripAdvisor, Amazon) Rich user experience (content responsive to user interaction) Relevant information pushed to consumers (e.g. RSS feeds, Twitter feeds) |
|
|
Characteristics of Social Media |
User-generated content Community formation Conversational |
|
|
Social Media and Business |
Marketing: Advertisements, promotions (e.g. Dell uses Twitter) Customer relationship management: Engaging with customers by sharing news, receiving feedback on products (e.g. Dell uses blogs) Recruitment (e.g. LinkedIn) |
|
|
Issues with Social Media |
1.Privacy 2.Security 3. Copyright 4. Permanence 5. Quality 6. Ethics 7. Legal |
|
|
Cloud Computing Motivations |
Replace internal infrastructure with dynamic “outsourced” platform: -Served via the Internet -Data and processing served “in the cloud” Reduced hardware requirements: -Organisation concentrates on “client” hardware Encourages on-demand scaling of IS requirements |
|
|
Software as a Service (SaaS) Model |
Application-oriented Subscribe to established software service
e.g. Gmail, Office365, Xero, Vend, Timely |
|
|
Platform as a Service (PaaS) Model |
Provides framework for building applications Build to specific development model e.g. Force.com, Google App Engine, Microsoft Azure |
|
|
Infrastructure as a Service (IaaS) Model |
Provides “virtual machine” in the cloud Highly flexible and configurable Development model unchanged e.g. Amazon Elastic Compute Cloud (EC2), Google Compute Engine,Catalyst |
|
|
Benefits of Cloud Computing |
Lowered infrastructure requirements: Less “big iron” hardware needed Dynamic scaling and on-demand pricing Location independence “Reduced” costs Robustness: Off-site backups, quick disaster recovery, ... Economies of scale: Potentially lower support costs |
|
|
Drawbacks to Cloud Computing |
1. Reliability: What if telecommunications goes down? 2. Trust: What is the third party doing to my data? 3. Legal issues: What if the data is hosted in another jurisdiction? 4. Buying into hype: Won’t always deliver as promised 5. Service agreements not met |
|
|
The "Five Pillars" of Information Assurance |
1. Availability 2. Integrity 3. Authentication 4. Confidentiality 5. Non-Repudiation |
|
|
Availability with Information Assurance |
Continuity of Service Availability System Performance |
|
|
Integrity with Information Assurance |
Accuracy: -Sound -Unimpaired -Perfect Condition Timeliness Network Design |
|
|
Authentication with Information Assurance |
Verification of: 1. User, device or other entity Identity 2. Integrity of data stored or transmitted 3. Right to see or use data |
|
|
Types of Authentication |
1. What you know - Passwords 2. What you have - Tokens (Keycards etc) 3. What you are - Biometric (Facial Recognition) |
|
|
Confidentiality with Information Assurance |
Holding sensitive data in confidence Allowing ONLY authorised use or access Providing protection of confidential data in transit and/or at rest (stored) |
|
|
Non - Repudiation with Information Assurance |
Proof of integrity and origin of data Both in an unforgettable relationship That can be verified by a third partyat any time Cannot be subsequently refuted |
|
|
Risks to the "Five Pillars" |
Natural (Floods, Earthquakes, Lightning etc) Accidental (Internal/External) Deliberate (Hacking, Virus, Espionage etc) |
|
|
Email Security |
Practically anyone can see an email it seems |
|
|
Browser Threats |
1. Cookies 2. Java 3. Javascript 4. ActiveX 5. VBS (Visual Basic Scripting) 6. Flash |
|
|
Botnet |
A botnet is a collection, sometimes more than a million machines, of PCs that have been compromised (owned) – and can then be controlled by the bot master (not you). The process of owning a machine often takes place through the execution of a Javascript on the targeted machine. |
|
|
Cryptography with Data in Transit |
It secures: 1. Secure electronic commerce 2. User and data authentication 3. Email security 4. Secure software update (technical) 5. Wireless network traffic |
|
|
Cryptography with Data at Rest (Stored Data) |
It secures: 1. Privacy of stored data (notebooks, etc) 2. Secure audit logs (technical) |
|
|
Bluetooth and Phone Security |
Attackers can access your phone from very far away through bluetooth |
|
|
EMF (Electro Magnetic Frequencies) |
Can damage your body, is a carcinogenic (Apparently) |
|
|
Ubiquitious Computing |
"Computing Everywhere" For example, phone, smart watch, tablet, laptop etc. Owned all by one user. |
|
|
Three basics forms for Ubiquitious Computing |
Tabs: wearable centimetre sized devices (smart watch) Pads: hand-held decimetre-sized devices (phones) Boards: metre sized interactive display devices (airport terminals) |
|
|
Principles for ubiqitious computing |
The purpose of a computer is to help you do something else The best computer is a quiet, invisible servant The more you can do by intuition the smarter you are; the computer should extend your unconscious Technology should create calm (calm technology) |
|
|
Automatic capture and access in Ubiqitious Computing |
Can remove burden of doing something humans are not good at (i.e., recording). Humans can focus attention on activities they are good at (i.e., indicating relationships, summarising, and interpreting). |
|
|
Context Awareness in Ubiqitious Computing |
Application development that allows for collection of context and dynamic program behaviour dictated by knowledge of the current context (e.g., environment and the users state). |
|
|
Natural User Interfaces in Ubiqitious Computing |
Physical interaction between humans and computation will be less like current desktop keyboard/mouse/display paradigm, more like the way humans interact with physical world. New interfaces have better usability, learn ability, ease of use. |
|
|
User Experience or Usability before usage? |
User Experience Trust, Design, Packaging, Utility, Fancy, Brand, etc. |
|
|
User Experience or Usability while using? |
Usability Accessibility, Readability, Efficiency, Errors, Operability |
|
|
User Experience or Usability after usage? |
User Experience Joy, Disappointment, Frustration, Emotion, Happiness etc. |
|
|
Types of people needed for Human Computer Interface Development |
Computer and Information Scientist Psychologists Designers Tech Writers Human Factor and Ergonomics Experts Domain Experts |
|
|
Human Computer Interface Development Process |
1. Acceptance 2. Analysis 3. Definition 4. Ideation 5. Idea Selection 6. Implementation 7. Evaluation |
