2010 Journal    54-894 Senior Seminar in Software Engineering

Your "journal" will contain several required components and a general weekly submission detailing what you have done relative to the course and your reactions to the material covered during the week.

January 14 Client
January 21  
January 28  2010-01-28nameJournal_2  (.doc  .docx  or .rtf)
February 4  2010-01-28nameJournal_3  (.doc  .docx  or .rtf)
February 11  2010-01-28nameJournal_4  (.doc  .docx  or .rtf)
February 18  2010-01-28nameJournal_5  (.doc  .docx  or .rtf)
February 25  2010-01-28nameJournal_6  (.doc  .docx  or .rtf)
March 4  2010-01-28nameJournal_7  (.doc  .docx  or .rtf)
March 23    2010-01-28nameJournal_8  (.doc  .docx  or .rtf)
April 1  2010-01-28nameJournal_9  (.doc  .docx  or .rtf)
April 8  2010-01-28nameJournal_10  (.doc  .docx  or .rtf)
April 15  2010-01-28nameJournal_11  (.doc  .docx  or .rtf)
 

• Required component pre journal Due January 14
• Required Component #1 Due January 21

1. Personal information
full name
name by which you prefer to be called
email addresses
preferred email address
other email addresses by which you can be reached
telephone contact information (these will not be published!)
schedule (make this as complete as possible!!)
give both school and work schedule
describe your other obligations as well (this will be very important information when we determine your team composition, since having compatible meeting times is vital to a project's prospects for success)
2. Brief resume: Describe your experience relevant to this class. Use the following headings:
Computing related employment experience
Computing related academic experience (beyond the CS core)
Other relevant experience (e.g. working with youth or project planning)
Special skills and strengths (e.g. language skills, HTML, Java, C++)
3. Report on meeting with client
4. Report on outside reading including reference

Required Component #2  Due January 28

 1. Your version of who is doing what.
2.  Your detailed description of your personal task on the pilot project
3.  A report on what you have done so far on your task.
4.  The title and reference of the article you read for this week.

 
Required Component #3 Due February 4

Book review title due: Each student will choose a book from  the list to read and evaluate for the class.  I will require that each student choose a different book, so inform me when you have chosen the book you will review.  A paper of your review and evaluation or editorial will be submitted as part of the week's journal, as well as a printout, and a class presentation will be given. This review should be about 800 words and include relevant publishing information, a synopsis and the import of the book to computer science in general and to you in particular. 

1.  Your detailed description of your personal task on the pilot project
2.  A report on what you have done so far on your task.
3.  The title and reference of the article you read for this week.

Required Component #4 Due February 11
1.  Your detailed description of your personal task on the pilot project
2.  A report on what you contributed to the  task.
3.  The title and reference of the article you read for this week.

Required Component #5 Due February 18
1.  Your detailed description of your personal task on the pilot project
2.  A report on what you contributed to the  task.
3.  The title and reference of the article you read for this week.

Required Component #6 Due February 25
1.  Your detailed description of your personal task on the SRS
2.  A report on what you contributed to the  task.
3.  The title and reference of the article you read for this week.

Required Component #7 Due March 4
1.  Your detailed description of your personal task on the SRS
2.  A report on what you contributed to the  task.
3.  The title and reference of the article you read for this week.
4.  Abstract for Research and Creative Works Symposium due today and included.

Required Component #8 Due March 23
2. Report on customer reaction to your specification and any changes
3. The title and reference of the article you read for this week.
4. Book review due.

Required Component #9 Due April 1
1.  Your detailed description of your personal task on the SDS
2.  A report on what you contributed to the  task.
3.  The title and reference of the article you read for this week.

Required Component #10 Due April 8
1.  Your detailed description of your personal task on the VV Plan
2.  A report on what you contributed to the  task.
3.  The title and reference of the article you read for this week.
4.   Report on outside reading -- including reference

Required Component #11 Due April 15
1.  Book review of Killer Robot
2.  A report on what you contributed to the  project.
3.  The title and reference of the article you read for this week.

Style

Use complete sentences where appropriate. Spell check your memo before you submit it. Pay attention to issues of grammar. In general, do not use abbreviations or contractions. Use the proper capitalization on standards acronyms (such as HTML) and language or product names (such as Java).

The appearance of your journal entry is also important.

• Ensure that you do not send your journal entry as an attachment.
• Do not send messages with embedded HTML tags.
• Do not give a lengthy prelude to your message. As long as the "To:" field of your email header is set properly, we will know that your message came from you.
• Watch spacing, since this dramatically affects readability.
• Do not make your message double spaced.
• Make sure that lines are not "too long", since this gives rise to an irritating alternating line length problem. A good rule of thumb is that lines should be no more than 72 characters in length.
• Organize the journal entry to make it easy for us to find the parts. Break the entire journal entry into labeled sections, using the numbers and headers suggested below.
• Think about typefaces and font:
• Printing an ASCII file in the default Courier typeface is acceptable.
• Select a typeface designed for easy reading, such as a Times or Schoolbook typeface. Do not use sans serif typefaces or 'cute' comic book style typefaces.
• Do not reduce the size of your font or the size of your pages. Small type is difficult to read in large quantities, and it does not leave us room
• to write in our corrections and feedback. Using small type may also leave you thinking you need to write more than necessary to meet the suggested length for the assignment.
• Use a 10 to 12 point font, and do not print your pages 2-up. (However, feel free to use duplex if you want to save paper.)
• Avoid quoting: the journal entries are intended to give us your personal thoughts on the subject matter. If quoting does prove to be necessary for some reason, be sure to delimit the quoted material with quotation marks and
• give a proper source citation.
• In general, do not use abbreviations or contractions.
• Use proper capitalization on standard acronyms (such as HTML) and language or product names (such as Java).