home | email  


Proofing throughout the Development Process

Content Creation

[Teams--content, design]
1. Establish course objectives and content to be covered.
Establish course objectives, including consideration of standards and grade level
Prepare Proposal and submit to NDE for review.
Prepare Prospectus (detailed outline of content).

[Teams--content, design, permissions, graphics if needed]
2. Make decisions about material needing permissions that will be included.
Start permissions process for literature or other written material.
Begin the permissions process on special requests for graphics that may have permission issues.

[Content team]
3. Begin content creation.
Outside author (or internal content team member) begins writing first draft.

4. Review of first draft by member of content team (other than author).
Read through for completeness of material (based on standards, readability, and grade level).
Make notes for revisions by author.

5. Full edit of second draft by member of content team (other than author).
Full edit for accuracy and completeness of coverage of the topic--primarily based on standards (national and state)
Full edit for grammar, structure, readability, and grade-level.
Make notes for revisions by author or content team.
Include notes for desirable graphic or image considerations.

6. Write additional content for clarity or standards requirements.
Rewrite material as needed, based on number 5 above. (Content team members and/or author may do this, at the discretion of the content team.)

7. Edit rewritten material for grammar, structure, readability, grade-level, and standards (by member of content team). Make corrections/changes as necessary.

[Other reviewers]
8. Review of third draft by ISHS teacher(s) and/or other subject matter experts (which may include designers) to insure that the content is accurate. Final proofing by a designated editor for grammar, structure, readability, and grade level.


[Content team]
9. Final script preparation.
Format final draft for entry into html, including separating and file-naming pages.
Create and edit (in Microsoft Word) glossary, notebooks, discussion groups, self-checks, and exams as needed.
Create and edit Page-of-Links in Word for web sites related to specific course material.
Work with design team for images and graphics to complete overall tone of the course.
Establish final deadline for ongoing permissions for selections and images as requested.
Record all images in graphics organizer--image identification, page in the script, and correct copyright lines.

Design and Web Development

[Design team]
Designers will QA their courses at all stages of development. They will check the following:

  1. graphics--to make sure graphics are in the right places
  2. copyrights--to make sure all elements are copyrighted correctly, either on the page or on the Credits Page.
  3. links--to make sure all back/forward, web, exam, notebook, etc. links go where they are supposed to go.
  4. text--free of content, typing, and political correctness errors.
  5. headers--to make sure they give the correct unit, lesson, etc. information
  6. checklist--to make sure they haven't forgotten any pieces to the course!


After the courses have been put in the frameset, designers should make sure the links and the glossary are still working. They should specifically check forward and back buttons to see that they go where they should--especially at the ends of lessons and units.

[Content team]
After the course is deemed "ready for final QA testing," the content team will conduct a final read-through to make sure that all appropriate changes were made in the final draft and that nothing was lost during the design and web development processes.


Quality Assurance

[QA Lab]
QA testing includes:

  • Checking the course against the original script
  • Reading through the course for editorial changes
  • Consulting with course designers about changes and corrections
  • Verifying corrections
  • Testing the Installation Program
  • Checking all external and internal links within the course
  • Checking the courses with various operating systems, platforms, and browsers
  • Documenting bugs in spreadsheet form for fixes
  • Documenting bugs for QA files Routing bugs to NET or to the designer for corrections
  • Tracking the progress of bug fixes
  • Retesting when the course or install is revised
  • Scheduling regular web link checks
  • Scheduling regular course update checks
  • Investigating any reported course errors and problems
  • Tracking global QA issues

Copyright 2004 - University of Nebraska Board of Regents - All Rights Reserved

[ home ] [ contact ]