Populating List of Edits

Glenn posted a Google spreadsheet for accruing the edit updates. We need to update that list and review it in our meeting tomorrow.

Sbs 4.1.1 confusion in Step 8 & 9

Steps 8 & 9 repeat a screen shot that causes confusion.Old code needs to be inserted inside of a new ELSE. The way that is shown is causing some confusion.

Troubleshooting Class

Even though we have a Debugging class, we should have a troubleshooting class near the beginning of the quarter to alleviate a lot of the 'easy' questions...such as brackets (how to highlight and problem-solve), quotation-marks (whatever is in red is being written out in the GUI, should not be broken across the lines), organization of pages/folders), semicolons (do not need at the end of methods/if statements), format document (using that to check problem spots), etc.

With the sbss, you become very detail-focused, only looking at one-line of code but not the whole block and what it is supposed to do. I think it would be helpful whenever we are commenting code one line at a time, to step back and say, "ok, what does this whole section actually do?" Personally, it helps me to troubleshoot to know what the whole section does (it is easier to spot the mistakes in the line).

Also, since there is no class in Copeland 014 before Professor Luce's 400 class, I think I am going to add a help session in there when things start ramping up, since I was helping a whole bunch of students working on the homework before class. However, I'm going to warn them that it is right before class and they should not expect me to see everyone and get it fixed, so only as a last-ditch effort.

SbS 2.1 Addition

For the validators, we need to let the students know that they type in the "*" next to each textbox field. Also remind them to change the color to red.

There were some issues with this Winter 2011.

-Glenn

Midterm

Hi Everyone!

I have finally had the opportunity to open up the South Breeze Zip that Glenn sent, but I have some concerns about the instructions before I attempt the new midterm.

1. I think we really need to make these directions step by step clear.  For the most part the directions are easy to follow, but once I get to the fifth paragraph I begin to get a little confused on what is expected.  It does mention in the directions that the student does not need to use the GUI, but it does not specify that the student CANNOT use the GUI, which may cause many conflict if students that add a btn to the gridview on the products page rather than using only code want full credit.

2. For the first run through am I supposed to make the AddAProduct.aspx or is this provided somewhere.  If the students need to make the page, specific directions of what is needed on this page must be given so that all assignments do not vary too much and are easier to grade.

Sorry that I could not get this blog out any sooner, I will finish up with a draft of what I imagine the AddAProduct.aspx page should look like by sometime tomorrow!

See You All Tomorrow!

Dyan

Project Team Formation Process

This is a temporary placeholder.... We will put in the process used for making teams.

Include a link to a googledoc template for the teams!

Updated MIS 400 Midterm

Wanted to update the way that we do the midterm for MIS 400. We are going to talk about ideas for how to do this during the strategy meeting on 1/4/2011.

The changes will be based on Dr. Luce's MIS 220 hands on midterm and final from last quarter.

-Glenn