MIS 400 Exam collection

Please copy paste as comments, your versions of MIS 400 Exam finals.
I have copied in the  MIS 400 final exam that was used in Spring 2011.

Meeting on Wed Oct 19

Error on pg 183, step 2 the semi colon in the if needs to go
The session varable needs a ToString and the paprameter needs to be NVarChar

Concept Quiz 5 has a question the discusses SCRIPT tags
In SbS 5.2 and SbS 6.2 should redirect to the custome rregistration page is session variable is null.
also, in SbS 5.2 add a response.redirect should be in the TRY block.
InsertChecker should become NumRowsAfected

Wiki of common errors
How d we enforce debugging.
1. if people ask for help, check if they debugged

MIDTERM EXAM ISSUES
One problem is that people have not thought out program logic
Solution:
develop flow diagram
then develop pseudo code
use sandbox approach

FINAL EXAM IDEAS
web services, database, inserts,
connection string
insert/update
creating of a webservice
NorthwindEasy
is session variable is null.

Students did ot do well in becaues they don't pay attention to Sbs
use psuedo code the second time around
use a review based exam.

SbS 5.2
week 6 needs 40+ hours

MIS400 meeting - midterm and status check

Issues with class in Week 5:

1. Students are not using Debugging
2. Some students are making strategic decisions.
3. <Script> tags in the lecture
4. Sbs 4.2.1 image is different from the code

Midterm:

1. Students may not know how bitdata types can be updated
2. We will use a modified version of the College database, that the students will need to download and copy to SBG folder.

Documentation

In our class, during Agile modules, documentation of feedback is suggested, but not reinforced. Since it is not an actual deliverable, it rarely gets done well. What do you think of making this one of the deliverables of the report, as a checklist or something along those lines? In their final feedback essays a few of students mentioned being better prepared (in hindsight). I believe our feedback during Agile feedback notes get forgotten, and should perhaps become a checklist.

Desired Features for MIS400

1. Paramtetrizing SQL statements with different data types: the first time parameters are used for the customer registration page in SbS 4.1. It should have at least one numeric piece of data to demonstrate how parameters of different data types are set up.
2. Using Try-Catch recovering from inserting duplicate records (Primary Keys)

Introduce SbS Concepts before HW is assigned

Light bulb going off ....  draw project on the board
Conduct pre and post Sbs

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