Final Deadline Monday 18th November 2013 - update

Due to unfortunate server issues today I have decided to extend the unit 8 deadline to the end of Monday.

Your final folder needs to be handed in before 4pm on Friday 15th Monday 18th November.

The last lesson you have with me is on Thursday, you can hand the folder in then if it is finished.

I will then mark these and give you an estimated score (this has to be an estimate because I still have to mark two more classes of work before scores can be finalised). I will also give you some corrections, if I feel there is more you can do to improve your work.

You will need to resubmit any sections that you correct. e.g. if you need to make a change to the subroutine part of the your report for program two, you will need to give me the complete report for program two so I can swap out the old one for the new one. I cannot allow you to have your folders back at this stage.

Once you have re-submitted I will see how this affects the mark I gave you and update the estimated score appropriately.

All these details will be placed on your Nilpit for Unit 8, which can be found at the top of your dashboard when you are viewing the IT Intranet site.

Python Evaluation (tips)

For the evaluation after your Python report, you only really need to cover the following things

• identify things that ought to be changed to make the program more readable and maintainable (names of variables/functions). Maybe some re-structuring. You will need to give specific examples of changes.
• Think of improvements and features you could add to the program to make it more usable and work better (what issues does it have and how what might improve them). You don't have to say how you'd do it but just what you would do.
• Finally improvements to the way you went about commenting and understanding the Python code. What would you do if faced with a Python program that used features of python that you had never seen before.

Homework: Evaluation of Exam question One

You need to complete and hand in your evaluation for the first program you wrote by:

Thursday 10th October 2013

You can look at the exam booklet for information about the evaluation, but look at the sheet I have given you which is a print of this blog entry

Writing your report key points to explain

Refer back to this blog post I wrote Tips on how to write the report before looking at this as it covers all the elements of the report, what you need to show and what you need to write.

I'll be more specific in these examples:

Subroutines (& Functions)
You must state the names of the subroutines and what specific module they are in

You must mention any parameters that a subroutine uses, explain why they are a certain type and what they are used for in the subroutine.

'This subroutine requires a parameter value
'of type string which is referred to using the name data
'this value is processed by the subroutine
Public Sub ReactToInput(data As String)

End Sub

Functions are subroutines that return a value, you need to explain what information is returned and what type it is.

You need to explain where the return value of a function is used, whether it is stored in a variable or whether it is used directly as part of some calculation or string manipulation.

'function returns an integer value back to the caller
Function GenerateNumber() As Integer

    ' do some code

    Return 45

End Function

'call the GenerateNumber subroutine and store
'the return value in the variable saveMe
saveMe = GenerateNumber()

'combine the text with the return value from the function GenerateNumber
s = "I generated " & GenerateNumber() & " for you"

String manipulation
You should remember that & joins text together in visual basic

SubString(), ToLower() are both examples of string manipulation and you should describe how they work and how they are used.

Selection
You need to explain the test being performed for the IF and what code runs when the condition is true and what code runs when the condition is false.

If saveMe < 105 Then
    'code if condition is true (saveMe is less than 105)
Else
    'code if condition is false (saveMe is 105 or more)
End If

Make sure you explain nested if structures carefully, highlighting the chain of tests that get you to certain parts of the nesting.

If saveMe > 0 Then
    'code if condition is true (saveMe is greater than 0)
Else
    'saveMe is not greater than 0
    If saveMe = 0 Then
        'code if condition is true (saveMe is 0)
    Else
        'saveMe must be less than 0 (not greater than or equal to 0)
    End If
End If

With select case, you need to explain what value is being tested for a match and then explain each of the possible matches and the code that is executed when each match is found.

'examine lowercase version of choice
Select Case choice.ToLower()
    Case "open"
        'code if choice is open
    Case "close"
        'code if choice is close
    Case "delete"
        'code if choice is delete
End Select

Iteration (Loops)

In for loops you need to state the loop variable, it's starting value and its stop value (the value it will have during the last run of the loop).

'loop variable called clock starts at 1
'increases each time by 1, stops at 12
For clock = 1 To 12

Next

You need to explain how the loop variable is used inside the loop, whether it is just a counter or whether it's value is used to perform some other task like accessing an individual character in a string.

For count = 1 To 10
    'add current value of count to the total so far
    total = total + count
Next

In While loops make sure you explain the general purpose of the loop what does it do. You need to explain the condition that is tested at the start of the loop, explaining that the loop only keeps working if this condition is true. Make sure you explain where the end of the loop is and that the code jumps back to the start of the loop to test the condition at the end of each run through.

total = 45
'loop happens if total is less than 100
Do While (total < 100)

    'add 7 to the total
    'this will eventually cause loop to stop
    total = total + 7

    'end of loop must go back to Do While to test condition again
Loop

Tips on how to write the evaluation

You can refer to the Exam Booklet (U8 section of the ICT/Computing Intranet) for other details of the evaluation. When writing your evaluation you need to cover two strands:

Evaluation of the solution(s)

Strengths
Look at the strengths of your best program (these are some of the things you could write about if they are actually well done)

• sensible clear comments
• meaningful variable names
• meaningful subroutine names
• Using camelCasing for variables, Pascal casing for subroutine and function names and CAPS_CASING for contsants
• careful use of comments
• clear solution
• Appropriate use of modules
• Use of constants where appropriate to make the program more meaningful
• Clear User interface
• Meaningful messages to user

Weaknesses and Improvements
Weakness can cover any of the bullets above that could be strengths, but in the opposite way e.g poor naming of variables and interface elements.

If you have specific issues with either your first program (or even in the finished improved program), then explain them here (make sure you use a separate paragraph for each) list those issues with direct reference to the program code.

Looking at your improved program, for each improvement explain why they way you did it is better than the way you did it in the original program, this may be better for the user of the program or it may be better for another programmer (easier to maintain / better structure [modules, subroutines] / naming of variables/subs/functions).

This could be accompanied with screenshots from the code to illustrate the differences. It is important that this is clear, use a separate paragraph for each improvement

Future improvements
If you did not do an improved version you need to look at the program and identify anything that you could do to improve it (these should of already been mentioned in the weakness), make sure you identify more than one improvement (you don't have to do it just explain it what the improvement could be and why it would be better)

if you did an improved program then you need to also think of any other ways in which you could improve it, explain them clearly making sure you have explained why it would be an improvement. This is more likely to be extending the features of the program (unless you identified a weakness in the improved one)

Evaluation of your performance

Strengths
Try to identify what you feel your strengths were/are during the VB programming task. This is really asking you to talk about what you did well when you approached the task:

• Preparation, prior learning
• Commenting as you went along
• How you tackled the task (e.g. did you put the interface elements together first?, then storage etc...)
• Clear testing

Weaknesses and Improvements
It is not wrong to have weaknesses with the way you approached the work, it gives you something to address for improvements  Make sure you also discuss any areas in which you feel you have weaknesses and how you could improve them, these may be issues you had with the bullet points above or something else entirely.

For each weakness you identify you need to explain what you do on a future task to reduce the weakness, what would you do differently and explain why this would make a difference to the program produced.

Future improvements
If there is anything else you could do on top of what you did well, then explain those items here.Think about approaches to programming (you may need to look up some methods of program design), user feedback etc...

Programming language report

You need to complete the report by Monday 30th September 2013

Programming language report can be found here

This report is worth 6 marks of the total for the programming unit. You need to make sure you carefully proof read this report so it doesn't not have obvious mistakes in the English spelling or the grammar.

Basics of software development report Unit 4

The final report you write needs to briefly talk about 4 considerations used when writing software. Create a report with the following 4 headings. Under each discuss the topics in the bullet points, don't use the bullet points as sub headings it's not necessary, just use a separate paragraph for each sub topic.

Data Input and Output

• Gather user requirements (investigation, Data Flow Diagrams etc...)
• Identify methods of data capture (keyboard, scanner, barcode etc...)
• Validate input data (range checks, presence check, drop down lists etc...)
• Types of out required (on screen, print outs)

Data storage

• Individual files (text files, ini files etc...)
• Database requirements (ERD and normalisation, data dictionaries)
• Use of variables (data types integer, real, boolean, character, string)
• Use of lists/arrays and other data structures (lists of strings, records etc...)

Processing of data

• Use of flowcharts, pseudo code to design algorithms
• Sequence (identifying tasks to be performed in order)
• Selection (If, Select Case)
• Iteration (For next, Repeat Until and While loops)
• Subroutines and Functions

Efficiency of program

• Programming language to use
• User interface to adopt (console/forms/web etc...)
• writing maintainable/readable code (comments, sensible names, indentation etc...)
• Carrying out testing (white box, black box, alpha testing, beta testing, end user testing)

Unit 4 final deadline

The final deadline for Unit 4 is Monday 29th April.

Your completed folder must:

• Have the dividers present
• Be in the same order as the dividers
• Have as many of the corrections completed as possible if you hope to achieve reasonable marks

If you do not hand in your folder this will be taken as a non submission

Unit 6 Final Deadline

The final deadline for Unit 6 is Wednesday 24th April.

Your completed folder must:

• Have the dividers present
• Be in the same order as the dividers
• Have as many of the corrections completed as possible if you hope to achieve reasonable marks

If you do not hand in your folder this will be taken as a non submission

Unit 4 deadline

The deadline for this unit is Friday 26th April 2013

I will mark the folders and give you a mark and final referral.

You need to be working on this over Easter if you are too meet this tight deadline.

Unit 6 Deadline

The deadline for unit 6 is Thursday 28th March.

I don't teach you on Thursday, so you need to either:

Hand in the folder on Wednesday afternoon
Find me on Thursday and give me the folder

Make sure that you have gone through all the corrections I have given you (which can be found on the nilpit) and completed the Evaluation. You need to check carefully against the portfolio guide if you are unsure what you are supposed to include in any particular section.

Work to do Monday 4th March 2013

Unfortunately I will not be in on Monday.

I need you to make a start/finish tasks 3A, 2A and 1A (hardware, software and operating systems specifications)

We also need to produce the evaluations for these 3 sections, (3B, 2B and 1B), exactly what you need to write in this section is described in the portfolio guide, make sure you read it.

Could you also all sign into workshop (click the Workshop Sign link in the Actions section of the Dashboard on the ICT intranet page)

DO NOT GO OFF AND WORK IN ANOTHER ROOM.

Hopefully I'll be in Tuesday and we can make a start on the PC setup.