APPROACH TO THE PROBLEM

I initially approached the problem with some trepidation as I had not dealt with quadratic equations for a number of years. This difficulty was alleviated somewhat as I was required to teach quadratic equations to year 9 pupils at Kirkham. The media I used was Coypu so I had to learn the package to teach the subject. As part of my learning then I read up on the subject so as to know exactly what was happening when the equation appeared as a graph in the package.

This was of help when I came to consider the problem set. I was aware of the formula for solving the equation for given values of x and that the values of x and y are effectively co-ordinates and thus a range of values for x would be needed to plot a graph.

PRODUCING THE CALCULATOR PAGE

The first stage in solving the problem was to construct a layout of how the finished application would look when a User used it. Initially I considered that there should be three pages or sheets. One would show the graph, one would calculate the figures and may be hidden, the last would be the frontpage and would invite the user to insert values of x and an increment value. Having decided upon this I decided to produce a spread sheet that would calculate the figures and give a reasonable range of values. At this stage I thought that the page would be hidden so was not to concerned about the appearance of the sheet.

MACROS

I then created a sheet that would produce the graph. Initially I created a Macro to highlight the figures and plot a graph using the Graph function and this worked up to a point. I then created the GRAPH sheet, simply as a Chart sheet, rather than as an object, which was constantly replaced with a new object each time the program was run. The Chart sheet takes its range of values from the SOLUTION sheet which calculates the values. and is thus automatically updated each time the program is run. the Macros obviously run behind the command button.

I then created the frontpage. This was to be the first page that opened, using the auto_open function to ensure this. There would need to be two buttons on this page. A user form could have been used but I felt it necessary to use both macros and user forms in the teaching. The buttons navigate to the enter values userform1 or exit the application.

I then decided to create a fourth page being a short help page, both as an extension task for the more able to basically create another userform and link them all together and as a means of introducing the concept of a user manual in their projects. The remainder of the time wa devoted to creating the userforms as navigation tools around the program. Once the program was fully functional I decided to format the sheets, hide the tags and toolbars and protect all of the pages so that the code could not be tampered with by a user, again as an extension task to the main aim of using the graph function, and the use of macros in buttons and user forms. It was necessary to tinker around with the code in the user forms to get the logic correct. I found that this part of the task was more about programming skills than I.T. skills although felt that the distinction between the two blurred somewhat. It was sinply a question of getting the protect and select, hide and show commands in the right order so that the values of the caluclator or solution page could be changed when the program ran but could not be accesed when the user went to the chart or GRAPH sheet.

THE LESSON PLANNING

I formed the view that the best way to teach it was the same way that I had learned it. By effectively starting with a piece of paper and drawing out a solution and then working out how to implement it. I have assumed that the pupils will have a sufficient knowledge of spreadsheets so as to be able to create the calculator page if provided with the formula and a brief explanation of the $ symbol and it's relevance. Thereafter the use of the graph tool would be taught and the two initially linked with a macro. I would hope to cover most of the theory and demonstrate the use of macros behind buttons inlesson one. The homework would consist of them creating a front page with two buttons on it one to exit and the other to bring up the calculator page. It would be necessary for them to be told about the auto open function and the end keyword for obvious reasons.

The second lesson would be to consolidate the previous learning and to introduce the Userform as a tool. The main part of the solution is the input form and the use of text boxes to gather the data. The buttons navigate. The use of labels is fairly straightforward. The various VBA commands would need to be expalined, and how to use them and sequencing of instructions. Homework would be to create the user form to accept the values and to show the graph or solution pages.

The third lesson would be a consolidation and continuation of the second. The concept of using the buttons to navigate between each sheet would be taught with demonstrations as appropriate and handouts of the keywords and examples. The concept of hiding showing and selecting would already have been covered, however,the principles of security would be introduced protect and unprotect and the logic behind it. Homework would be to complete the userforms and to incorporate security into the documents. I have assumed they have the knowledge to format the worksheet appropriately (use of colour). As optional homwework a help page would be devised.