Writing for the Internet (Fall 2008)

Term Project: Final Presentations

2008-12-08T15:00:00Z

In a brief informal presentation, demonstrate the changes you made after completing your beta testing (backed up with user-testing data).

Portfolio 4

2008-12-05T15:05:00Z

Project Workshop

2008-12-05T15:00:00Z

Term Project Progress Report (cancelled)

2008-12-03T15:10:00Z

I'm dropping this assignment.

Project Workshop

2008-12-03T15:00:00Z

Q4: Beta Reports

2008-12-03T15:00:00Z

Individual reports, revisiting findings discovered during alpha testing, and presenting your goals for the final release.

Upload to Turnitin.com.

About 500 words, starting with a bulleted list of your goals for the final release. (Place that list at the beginning of your submission, but you should probably write the list last, after you have thoroughly considered what you learned from the beta-testing.)

(Moved from Dec 1)

There used to be a "Term Progress Report" on the sylalbus... I've dropped that assignment.

Term Project: Beta Release

2008-12-01T15:05:00Z

This is the last submission we will have time to discuss in great detail, and our last chance to discuss big-picture changes. From here on, our focus should be on resolving trouble spots and fine-tuning.

Thanksgiving Break

2008-11-28T15:00:00Z

Term Project Workshop

2008-11-24T15:00:00Z

Focus on getting ready for your beta testing. After break, I will be shifting to trouble-shooting what you've already completed, and giving feedback on the big picture. So today will be a good time to ask me about how to do something you haven't yet learned to do.

Term Project Workshop

2008-11-21T15:00:00Z

G4: Alpha Reports

2008-11-19T15:05:00Z

Small teams test each other's projects and report results. This is not a contest - this is a practical, honest exploration of strengths and weaknesses.

Term Project Workshop

2008-11-19T15:00:00Z

Term Project: Alpha Release

2008-11-17T15:05:00Z

Delayed from Nov 14.

What is an Alpha Release?

A partial draft, with some sections more or less fully complete, but whole sections left unfinished.

So, if you plan a website with a home page, four supporting pages, and a "credits" page, your alpha release might have the home page, just one supporting page, and an
incomplete "credits" page.

If you plan a game in which the character explores a three-story house, your alpha release might include one more-or-less complete floor.

The basic idea is that you need some parts complete enough that your users can actually test them usefully, but you have to be willing to change your work based on what you learn from your test users.

(A beta release is an essentially finished product - your game should have an ending, your website should be written and proofread. Your beta-testers will identify improvements that you hadn't thought of -- synonyms you should implement in Inform 7, new sections or navigational features on web pages, etc.)

Alpha Testing Workshop

2008-11-17T15:00:00Z

Term Project Workshop

2008-11-15T02:40:21Z