Tuesday, March 29, 2011

2-days and still an error!

-_- I worked on this on the first day all went well till i ran the program then the error appeared. I then played around with the code and the same error appeared... It was definatly not my weekend...

Sunday, March 20, 2011

Blog Task Week 5

Self Study Questions:

1) DAO Stands for Data Access Object
2) CRUD stands for Create,Repeat,Update,Delete
3) The default "datadirectory" is called App _ Data
4) 'Injected" durning a SQL injection attack is malicious SQL commands
5) an example of a one to many relationship is one car company may have many types of cars.
6) three methods that are supported by the sqldatareader class are "read" , "getint32" and "getstring"
7) a property that must be set to allow the code behind file to respond to users selecting a new item in a drop down list is Autopostback.
8) the event's name that is triggered by the selection is onselectedindexchanged
9) a delegation method is something that calls some other method to do the work.
10) three problems that covered by the term 'object relational impedance mismatch' are unique object and table identifiers, mapping of the data types, relationshipd and normalization.

Tuesday, March 8, 2011

Web Accessibility task (Draft)

Part One

1. What is in WCAG 2.0?

It has 12 guidelines that are under 4 principles which are "perceivable", "Operable", "understandable", and "Robust" each one has a testable success criteria which has three levels A,AA and AAA.

2. Who poduces WCAG 2.0?

The people who produce WCAG 2.0 is the web content accessiblity guidelines working group or WCAG WG for short. They are part of the W3C (World wide web consortium) web accessibility initiative (WAI).

3. Who are the guidelines design to assist?

The guidelines are designed to assist web content developers, web authoring tool developers, web accessibility evaluation tool developers and other people who need or want the standereds for web accessibility.

4. What are the essential components of Web Accessibility?

The essential components of web accessibility are content, web browsers, media players, assistive technology, users, developers, authoring tools, evaluation tools.

Part Two:
Choose one guideline from each of the four principals (perceivable, operable, understandable, and robust) and discuss the ‘intent’, benefits & give an example of use.

Perceivable -
"1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure."

1.3.1
Intent: to ensure that info and relationships are implied through visual or auditory formatting are preserved when presentation format changes.

Benefits: Helps people with disabilities by allowing users agents to adapt content accordingly to the needs of the users. Blind users benefit when he information is conveyed through color is also there in text. Deaf - Blind users using braille may be unable to access color dependent information.

Example: A text document where its formatted with 2 blank lines befor the titles, asterisks that indicate list items and othere fomatting conventions so that structure can be programmatically determined.

1.3.2
Intent:to enable user agents to provide alternative presentation of the content while perserving reading order needed to understand meaning.

Benefits: help people who rely on assistive tech that reads text out load.

Example: css is used to postition a nav bar, main story of a page and side story. the visuals dont match programmatically but the meaning of the page doesnt depend on that order of the sections.

1.3.3
Intent: ensure all users can gain access to instructions for using content even when they connot perceive shape or size or use of information about spatial location or orientation.

Benefits: Blind and low vision users may not understand info if conveyed by shape or location.

Example: an online multi page survey has a link as a green icon in the lower right hand corner. the arrow is cearly labled "next" with the instructions "move to the next section" the example uses both positioning, color and labeling to identify the icon.

Sunday, March 6, 2011

Blog Tasks Week 3 (Not Finished Yet)

Self study Questions
1) the difference between a tag and an element is the tag is the characteristics that will br applied to the content of the element.
2) the characters that are used around an attribute name is "<" or its the element name.
3)XHTML is case sensitive.
4)the <"hr" "/"> element is for the Horizontal rule
5)the terms 'strict', 'transitional', 'frameset' refer to different versions of the XHTML DTD
6)The special character for the copyright symbol is "& copy ;"
7)the two required attributes that are for the image element are src and alt.
8)The XHTML that displays a bullet list is:
<"ul">
<"li"> Blah <"li">
<"li"> Blah <"li">
<"ul">
9)the attributes that are use to make part of a table spread over multiple rows or columns are Colspan and rowspan.
10)The name of the element used to create hyperlinks is "a"

Sunday, February 27, 2011

Group Work: Use Cases

1)
Functional: Users log in, Users can view their details, Users can view their account balance, users can delete their account, users can send gift vouchers, users and visitors can browse the catalogue by genre - price or alphabetical, admin staff may log in to the administration area, admin staff may bpdate any catalogue information, users may apply for a refund.

Non-Functional: Attract new users, uses can view their purchase history, users can edit their details, users can purchase more credit, users and visitors can browse the entire catalogue, users may purchasr and download catalogue items, users and visitors may sign up for a weekly newsletter, admin staff may apply refunds to user accounts, the service should support PC and Mobile devices, the service should be online 24/7 and 365 days a year, the interface should contain groovy web 2.0 elements.

2)
Must Have: Users can login, users can view their details, Admin staff may log in to the admin area, admin staff may update any catalogue information, the service should be online 24/7 365 days a year.

Should Have: Attract new users, users can edit their details, usres and visitors can browse the entire catalogue, users and visitors can browse the catalogue by genre price or alphabetically, admin staff may apply refunds to user accounts, the service should support PC and Mobile devices, the interface should contain groovy web 2.0 elements.

Could Have: Users can view their purchase history, users can purchase more credit, users may purchase and dowload catalogue items, users and visitor may sign up for a weekly newsletter.

Want to Have: users can view their account balance, users can delete their account, users can send gift vouchers, Users may apply for a refund.

3)
Identify key concepts:
-Log in
-View Details
-Account balance
-purchase history
-edit details
-delete account
-purchase more credit
-gift vouchers
-browse catalogue
-browse genre, price or alphabetical
-purchase and dowload items
-weekly newsletter
-admin area
-update catalogue info
-apply refunds
-appling for refunds
- PC and mobile
-online 24/7 365 days
-web 2.0
Initial model:
4)
5)
Use case name: Buying an item online
Actors: Visitor
Start page: Home Page
Use case descritpion:
1. The actor clicks on browse catalogue
2. The actor browses by alphabetical
3. The actor chooses a product
4. The actor proceeds to purchase the item.
5. The site shows the result of his purchase.

Storyboarding 2

"Modify the previous storyboard to include the 'Client page' & 'Form page' icons as shown on page 39. These icons may be harvested from this week's powerpoint presentation."

Storyboarding 1

"Reverse engineering - Using the online shopping process you documented last week, create a storyboard for the process using the example on page 38"