SOFT6008 Class 05.3

Some students worked on the credit card check sum code, but other got ready for today's exam by reviewing code.

SOFT6008 The Google

I cannot stress enough the importance of trying to write code for yourself.  Googling for solutions is of limited value.  Students need to learn to write code from scratch.  That the the point of the programme they are enrolled on.  I've been doing this while now and in my experience obsessive Googlers tend not to be successful because they don't learn the skills they need.  Students are unlikely to learn much from other people's code.

If you try to write the code yourself I am happy to help you.  If your objective is to steal code and put all your efforts into covering your tracks, then you are wasting your time and mine.

No one is going to pay you Google code for a living.

SOFT6008 Class 05.2 & 05.3 W

Students continued working on the credit card validation.  Progress was slower than I had expected.  I think students are struggling with going from the problem definition to the algorithm.  The JavaScript code per se doesn't see to be an issue.

SOFT6008 Class 05.1 B

Stduenst worked on coding the Luhn algorithm in JavaScript

SOFT6007 Class 05.1

We looked at CSS. I stressed the importance of keeping the content and styling information separate and told students to never used embedded nor inline styles.

SOFT6008 Class 05.1 & 05.2 A

I asked students to write code for the Luhn checksum algorithm used for credit cards.

SOFT6008 Attendance

The attendance rate in Week 04 was 64%. That's a slight improvement on earlier weeks, but it's still low.

SOFT6008 Exam reminder

The exam will run from 1230 to 1400 in the Melbourne Exam Hall on next Wednesday 14 October.

It won't be a long exam but I booked a 2-hour slot just in case someone needs a bit of extra time.

This is a one-sheet exam. Student will be permitted to bring a single A4 sheet of notes (front-and-back).

This will be worth 20% of the final mark for the module. All students registered for the module need to attend in order to get full marks.

You should have received a sample by e-mail.

Please enter and leave quietly.

SOFT6007 Class 04.2 & 04.3 & 04.4

Students worked on coding up the form.

We had a brief introduction to CSS and students styled the timetables they completed in previously

SOFT6007 Class 04.2 & 04.3 W

Students worked on coding up the form. Most are done now or nearly done.

We may move on to something new in the next class.

SOFT6008 Class 04.2 & 04.3 B

I asked student to start coding up the Luhn algorithm for check sum calculations. It was slow going. But we will look at it again in the next lab.

SOFT6008 Class 04.4

I talked a little bit about the slot machine exercise and the exam next week.

We began our look at user input validation and checksums.

slides: 2015-JS04.pdf  (check notes page for most recent version)


code: Phone Number Checker


audio: SOFT6008-04-4-20151007.mp3

HTML5 Audio tag

MP3 

SOFT6008 Class 04.1 A

Students worked on the phone cost calculator. As with other lab groups it is the logic that is slowing people down and not the javascript as such.

SOFT6008 Feedback on exercise 1

Individual feedback is here:
2015-SOFT6008slot-feedback3.htm

I didn't  make note of any instances of copying. But I did have a word with some students.

For assessments worth marks I would investigate possible cheating more thoroughly.

SOFT6008 Call Cost Calculator Tips

Some students have struggled with the logic required to complete the call cost calculator exercise.

Once the first two price plans have been coded correctly the rest are easy.

The pre-pay plan is simple because each minute, text, or mb used is charged per unit.

If if mins were 8c, texts 6c, and data 2c per mb
the calculation looks something like:

total = mins * .08 + texts *.06 + mbs * .02

However where a plan comes with some free usage for a set minimum fee and this need to be accounted for.

Suppose a price plan costs €20 and comes with 50 free minutes and customers are charged 8c per extra minute.

It's tempting to say that
extramins = mins - 50

But wherever mins in less than 50, the phone company would be giving money back for unused minutes. It's only correct to say extramins = mins - 50 when mins is greater than 50. Furthermore, if mins is less than 50 then the number of extra minutes is zero.

So the code would look something like

if mins > 50 then
     extramins = mins - 50
else
     extramins = 0
end if

This is the pice of the puzzle that most students who had difficultly failed to figure out.

However the calculation of the extra minutes, texts, and data are independent of each other.

Eventually the final calculation might look something like:
totalcost = 20 + extramins * .08 + extratexts *.07 + extradata * .03

It doesn't make sense to check to see
if (mins > 50) && (texts > 100) && (data >100)

The extra minutes, extra texts, and extra data, must be calculated independently of each other.


The javascript part of the exercise didn't seem to pose any major problems for students.  Students who are weak in programming may want to revisit some of the exercises they did in first year.

SOFT6008 Class 04.1 & 04.2 W

Students worked on extending the phone cost calculator. That has taken much longer than I was expecting. I think some students are struggling with simple programming issues. The javascript portions of the problem don't seem to be giving rise to any of the difficulties.

Students who were finished with that exercise took a look at checksums and some started coding.

SOFT6008 Attendance

The attendance rate for the first three weeks of semester was 57%. This isn't good. Coming to class can have a big impact on a student's chances of passing this module.

SOFT6008 User Input Validation

Video on User Input Validation

SOFT6008 Class 04.1 B

Most students worked on the call cost calculator. I advised them to concentrate on getting the first two plans completed correctly before starting the others.

I asked students who were done to take a look at the video on User Input Validation

SOFT6007 Class 04.1

We looked at semantic tags and forms.

I mentioned that we will have an assessment soon.probably in Week 06. I will get back to students about this.