Creating User Interfaces[Tutorials due.] Development cycle.

Standards. Communities. Work session.

Homework: For next Thursday: Finish HTML5 project: prepare to present.

Midterm guide posted.

Development cycle

• In organizations, generally formal, engineered process– Monitor existing systems to generate 'to do' lists

• Fix bugs. Add features. Sometimes debatable which something is.

– Design changes– Build– Test– Deploy

• Training, run parallel systems, …

Development cycle

• Interface design guidelines also serve to present common look – Maintain brand

Categories

• Cool and usable• Cool and confusing• Boring and usable• Boring and confusing

BUT recall Cooper, other remarks: in most cases, best interfaces do not dominate. You don't say: hey, that was a great interface. You say: I got the job done.

Levels of use?

• My phrase– Find a better one? Standard?

• Example– Registrar's office sets up system– Faculty/staff put in schedule information

• Actually, not directly, at least here at Purchase– Students register– Faculty views system to check counts, other

info, get class lists

Standards checklist• Does coding satisfy standards?• http://www.bukisa.com/articles/409738_a-web-

standards-checklist-how-to-make-a-proper-website

• Issues include valid code– Note: my examples don't have specified doctype, etc.– Proper XHTML: quoted attributes, proper nesting,

lowercase– broken links– help for Screen readers (e.g., alternate text for

images, headings for tables)

[my] check list / process• Identify users• Identify what

– System users want to do– What system owners want users to do & be

accomplished– Identify relevant expectations & experiences – Identify / make connections users may have with

other parts of the organization• Design & build

– Review vocabulary– Review with a user group

• Deploy– monitor

FACT!

• More time is spent maintaining (renewing, enhancing, updating) applications then in the initial design!

Second system syndrome

… derogatory term describing tendency to put every new feature into an application.

Could also imply tendency to 'fight the last war'

• Technologies have changed• Typical users may have changed

Content Management Systems

• Attempt to separate technical implementation from content

• Note: there also is split:– Content– Technical implementation– Design

• FaceBook, LinkedIn, blogs etc. provide ways to have a web presence in common formats

Content Management Systems

• http://en.wikipedia.org/wiki/List_of_content_management_systems

• http://php.opensourcecms.com/• Other?

Work session

• Time to work on project!

Homework• Next Thursday: Complete HTML5 project.

Prepare 1-pager– abstract (formal description, 100-200 words),

screen shot, sources used. PROOFREAD.– Come prepared to present and discuss objective,

users, and usability features.• Tutorials due!!!! Do put in summary together

with link on moodle forum.– Take/read/do tutorials and post comments on other

tutorials.