Compiled Messages: ------------------------------------------------------------- Message no. 222: posted by Robin Canaday (robincanaday78) on Sun Nov 04, 2001 01:10 Subject: Desk Checking I am getting rather frustrated with all this desk checking. Yes, I understand that is it necessary to understand how to do it. But I am spending more time desk checking than I am writing the algorithm. Does the desk check diagram have to be so inclusive and elaborate? (It seems like the putting anything other than variables and counters on the horizontal part of the diagram is redundant, and even if it isn't, it's too big!) I can't make the table fit on a word document EVEN when I set the font to 8, and change the page setup to landscape. It's just too big. Isn't there a better way to represent a desk check? ------------------------------------------------------------- Message no. 223: [Branch from no. 222] posted by Melvin Magnusson (melvinmagnusson68) on Sun Nov 04, 2001 01:46 Subject: re: Desk Checking In reference to what Robin? To assignment 6 Simple Program design or VB 4.1? I was just going over the assignment in VB and just got the picture of sub procedures and their purpose. But when it came down trying to figure out how to create the pseudocode for the assignment, I was frustrated, the desk check for a quotation seems stupid to do. I mean, to test your algorithm with the desk check, for the quotation, it would have to be the quotation for the desk check and not some other quote you know of, The defining diagram was useful for me to get my thoughts in focus for the assignment, trying to figure out how I'm going to arrange my pseudocode. Then, I went back to the instructions to go over it once again and the statement Laura made" I want pseudocode only" might be a possible quote to use for the desk check. But then it occured to me, if I read the instruction correctly, pseudocode only? Yippee!!!!I do not see desk check as part of the instruction, no do I see defining diagram and flow chart. All I see is pseudocode. The earliest chance I had this week to get to assignment 6 was this morning after work at 3:30 am. Then a friend of mine called long distance and talked with me for 4 hours solid so I can walk him through the installation of Partition Magic 7 on his computer. We had to deal with some complications which rendered his computer useless, but with much trials, we go his computer up and running with two partitions of Win98SE one squeeky clean and the original install stinkingly slow. By nine o'clock this morning I was able to focus on this assignment. I have not got off this desk and now it's almost 2am. with a meal or two in between and small chores to take care of in the process of doing this assignment. I haven't been to bed yet, and I aim to finish this assignment so I can devote Sunday to another course that's due Monday, that's equally frustrating, making ERD's and Normalization of databases. Ugh. So, if I have understood the instruction correctly, all we need to do is turn in the pseudocoe for the VB part of the assignment. If so, then I am almost done. Any input from anyone else? Dean ------------------------------------------------------------- Message no. 224: [Branch from no. 223] posted by Robin Canaday (robincanaday78) on Sun Nov 04, 2001 08:28 Subject: re: Desk Checking Huh.. I didn't realize she wanted psuedocode for the VB assignment. I just did the exercises like the book said to do them. Nah, I'm just annoyed by the desk checking for Simple Program Design Chap 6 assignment. It just seems like there could be a better way to do it. ------------------------------------------------------------- Message no. 225: [Branch from no. 224] posted by Dawn Baur (dawnbaur91) on Sun Nov 04, 2001 12:05 Subject: re: Desk Checking Yes, all Laura wants for the VB portion of the assignment is the pseudocode. As for the deskcheck portion, mine isn't that complicated. I only have 8 columns. Hopefully, I didn't oversimplify the problem. I don't think I did. I agree with you that I find the deskcheck portion to be the most tedius portion of the design process, but it really does make you think through the process and check the logical flow of the code. That doesn't mean that I have to like it, though. :) Sincerely, Dawn Baur -------------------------------------------------------------