CSc 498/499
Capstone Design Project

Example of a good report

Journal Entry #4
October 25, 2002

Goals from last week:

I have begun to tackle the first prototype design. This has turned out to be harder then I thought. So far it looks really bland, and I have no idea what to do with it. I've told myself to keep it simple, but at the same time, I need to make it interesting enough to keep a user's attention. For now, a Cascading Style Sheet will have to do.

I'll need to brainstorm some non-obtrusive graphics later on. From what I have gleamed from the paper on making tutorials, I need to chop up my lessons into 15-minute chunks for easy consumption by the user. Each chunk needs to be summarized in the beginning and again at the end. The beginning summary is meant to prepare the user for what's coming and to let him decide whether or not he wants to continue on with the section. The closing summary is to let the user review what he has learned one last time before either quitting for a time or moving onto the next section. There should be button that will bring the user back to the beginning of that lesson if he doesn't feel confident with the information presented in the lesson. A "Save Progress" button would also be a good idea so the user has the option to save the location where he left off and later recall that location.

The email sent to was replied to. Here is what was said in a nutshell:

The way I read this email is that I should start brainstorming other ways of going about this, because it's going to be really hard to program Linux in Java.

Brainstorm: What if, instead of an active Linux window, after a user entered the correct information, a screenshot of what should be displayed appeared onscreen and the user continues on with the next question referring to that screenshot, and another screenshot replaces it after the next question is answered correctly. This eliminates any security hazards and any need for a working Linux window. (This is a big change in the project and will need to be discussed with Chris. But it is a good graphical + feasible way to interact with the user.) End Brainstorm.

Goals for next week:

  1. Brainstorm some non-obtrusive graphical work
  2. Add "ls command" tutorial section to the interface
  3. Discuss with Chris the feasibility of the Linux window, and introduction of the screenshot idea
  4. Abstract for the poster fair

What makes this good?

Back to CSc 498/499 homepage