The Name of the Page

A high-level description of the system

System Specifications


Key hardware information related to the system. For example:

Some examples:

  • Machine's name:
    • May be moved to another server in the winter term
  • Server's name:
    • Server1
    • Server2


Key software information related to the system. For example:

For example:

  • Server OS: Ubuntu 12.04 Server
  • Database type: SQLite Version
  • Tables: Users, Assignments, Courses

Authentication and Authorization Information

Many systems demand authentication before they can be managed. List the information required to gain access to the system. Please do not put passwords on this page. This page will be public and accessible by Google.


People that may need to be contacted when working with this system

  • Administrator: [Name]
  • Point of contact (expert): [Name]
  • Stakeholders:
    • CS 100
      • Requires system for use in assignments
      • Usually requires approximately user 200 accounts
      • Primary contact: Arthur Conan Doyle (ext. 22790)
    • CS 136
      • Requires system for assignments
      • ...


Unique terminology that might be required while performing tasks on this system. For example:

  • Definitum
    • In a definition the word being defined is the definitum
    • Is a fancy word that nobody ever really uses
  • MarkUs
    • A marking system in which students can submit their code and faculty can provide feedback and assign grades
    • Originates from the University of Toronto

Guides to the Completion of Scheduled Tasks

Some tasks must be completed on a regular basis. List the scheduled tasks from least frequently recurring to most frequently recurring. Each one must have a detailed guide on how to go about completing the task and how often/when the task must be completed. Try to be as detailed as possible.

For example:

Between Every Term

Empty the database

Keeps things clean and organized

  1. Log in to the database.
    • This is a secure connection
  2. Run the purge command
  3. log out
    • The logout button is at the top-right of the page
  4. Try to make a query to the database. If it returns an error, you are good to go.

Another Example, also completed between every term

This example will help you understand

  1. Do this
  2. Do that
  3. Now do something fancy

Guides to the Completion of Common Requests

This section outlines the guides to completing tasks that are commonly requested by stakeholders

Heading with a very high-level description of the request

  1. Description of step
    • Details and notes about how to complete the step
    • Details and notes about how to complete the step
  2. ...

Set Up an Exam

  1. Log into the system for setting up exams
  2. ...

Common Failures/Bugs & Troubleshooting

This section outlines some issues that have been known to occur with the system, along with details on how to fix them and when they occur.

Each section should be formatted like so:

A level-3 heading that identifies the issue

Paragraph text to explain the symptoms that would be observed when the issue exists.

Optional paragraph text that describes the potential causes of the issue.

A level-4 heading that says, "How to Fix the Issue"
  1. A series of steps to fix the issue
    • Formatted as an ordered list of steps
    • If the fix is really simple, describing it in a small paragraph will suffice instead of using the list format

Current Discussions Related to the System

Some systems have important long-term changes that are being discussed. If needed, a summary of each discussion may be included here.

See Also

Related material to learn more about the system.

Related ST Items

Related Twiki Pages

Formatted in a list.

For example:

Related EDocs

Formatted in a list.

For example:

  • EDoc 1
  • EDoc 2
  • ...

Related External Links

Formatted in a list.

For example:

Edit | Attach | Watch | Print version | History: r54 < r53 < r52 < r51 < r50 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r54 - 2013-07-17 - DrewPilcher
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback