Jump to content

Haggis (programming language)

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by CS104G14 (talk | contribs) at 13:42, 30 November 2016 (Added Applications and Uses). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

HAGGIS is a high-level, dynamic, educational programming language used primarily to teach Computing Science to Scottish pupils taking SQA courses on the subject.[1]HAGGIS is used as a tool to bridge the gap between pseudocode and typical computer programming, allowing users to easily understand how the program is functioning.[2]

HAGGIS is not based on any one specific language but a mixture that provides easy to learn syntax. It has multiple programming paradigms of functional, imperative and object-oriented, to provide an adaptable learning environment for pupils.[3]

Online HAGGIS interpreters have been developed to provide a way for pupils to check their programmes run as expected.[4]Other third-party tools are available to download such as VisualHaggis which provides users with a visual interpretation of the programme running and the ability to translate the HAGGIS into other programming languages.[5]

History

HAGGIS was commissioned by the SQA in 2010 to provide a uniform syntax and form in which to present questions to pupils in assessments. It was developed primarily by Quintin Cutts of University of Glasgow (See 'External Links') in collaboration with Greg Michaelson (Heriot Watt University). The aim of developing HAGGIS was to emphasise the core idea of ensuring pupils could view various versions of code and then demonstrate their understanding to develop their computational thinking and programming skills.[1]

HAGGIS was first introduced into the Computing Science curriculum as part of the Scottish Government’s Curriculum for Excellence development programme in the 2013/2014 session in National 5 and new Higher courses[6]and into the new Advanced Higher curriculum in the 2015/2016 session.[7] HAGGIS was not introduced as a language to replace other languages already used in education, but to be taught in conjunction, enhancing the pupil’s understanding of mapping pseudocode like structures (HAGGIS) to other languages such as Visual Basic and Python.[6]

Features and Philosophy

Core Principles

HAGGIS was designed with 8 core principles in mind[8]:

  • Not to be inspired by any existent language.
  • Be adaptable to programming languages already taught in the Scottish Curriculum.
  • Provide enough complexity for Advanced Higher teaching whilst being appropriately useful for earlier teaching years.
  • Provide an instinctive element, eg variable types are self specified.
  • Be concise in use but open to interpretation of multiple ways to solve a problem.
  • Allow different constructs have different meanings when used in certain context.
  • Don’t visualise the non-useful elements such as Memory being allocated.

Use within Education

It was designed to be both functional/sequential and object-oriented based in order to be simple and complex for National 5 / Higher students and Advanced Higher students simultaneously.[8]

HAGGIS was designed to allow pupils across Scotland to enhance the learning and understanding of computer programming through reading examples, and aid the step of converting from pseudocode to full programming. It was not created with the intention of asking pupils to write it in assessments but provide a uniform language in which to present code examples to students, ensuring that all pupils have a fair understanding and is not hindered by learning a different programming language different to the one exemplified in the assessment.[2]

Category:Programming language.

Syntax

Syntax and structure in HAGGIS are very similar to other programming languages and can be easily learned.

An example of the HAGGIS programming language which prints all even numbers between 0 and 100.
A more complex example of some HAGGIS code

Reserved words

  • Reserved words are Capitalised.
  • SET, FOR, WHILE, etc.

Data types

(types do not necessarily need to be disclosed if it can be determined by context)

  • Character (As opposed to string)
  • Integer (Whole numbers)
  • Real (Whole numbers as well as decimal numbers)
  • Boolean (True or False)

Structure Types

  • Array: Sequence of same data types.
  • String: Array of Data Type Character.
  • Record: Collection of values and is labelled.
  • Class: Object Oriented Class Object with own defined structure.

Line Numbers

Each line should state its number at the beginning. For example: Line 1

Indentation

Code within other structures should be intended so it can be properly identified by the compiler and to make it easier to read for the developer and for anyone else of whom may be reading the code.

Comments

Comments can be made using the “#” character for every line of commented text, this can appear either at the beginning of a new line or after a piece of code. Large blocks of text can be specified using the “<(COMMENT TEXT>” format, this is primarily implemented for educational use to provide larger context for students.

Variable names

Variable names should be written in lowercase or, if the name is complex, in lower camelcase. Camelcase is when a name is concatenated together to form one long word, however the first letter of each word (apart from the first) is capitalised. For example variables could be called

  • number
  • meaningfulName

Assignment

Assignment allows the user to set values to variables. The syntax is as shown.

  • SET <variable’s name> TO <value>
  • If <value> is a string, it should be written within quotation marks, like this: SET phrase TO “maybe”
  • If <value> is an integer, it doesn’t need quotation marks, like this: SET number TO 23

Input

Input in HAGGIS is similar to pseudocode in that you state the data type of the input the program is receiving and also where the input is coming from, like so:

  • RECEIVE <variable that will store input> FROM () <INPUT DEVICE>

For example:

  • RECEIVE number FROM (integer) KEYBOARD

Output

Outputs in HAGGIS can be written similarly to inputs.

  • SEND <variable, value or text> TO <OUTPUT DEVICE>

For example:

  • SEND meaningfulName to DISPLAY

Arithmetic Calculations

"SET" is used to assign the result of calculation. For example:

  • SET number TO 32*6

This is another form of Assignment.

Procedures / Functions

A procedure is a kind of sub-program within a program. It allows the sectioning of code to make it more readable and easier to work with. You must remember to end the procedure as shown below. PROCEDURE <Procedure ID/Name>( <Variable>, <Variable>...) HAGGIS Commands END PROCEDURE

Operations

HAGGIS includes all the operations you would expect from a programming language to be able to carry out calculations and logical operations alike. For INTEGER and REAL data typed, the following operations are possible.

  • “-” is subtract
  • “+” is add
  • “*” is multiply
  • “/” is divide
  • “^” is exponent

For INTEGER data types alone, the modulo is possible which is written as “MOD”.

Comparison Operators:

  • “=” is equals
  • “≠” is inequals
  • “<” is less than
  • “>” is greater than
  • “≤” is less than or equal
  • “>” is greater than or equal

Logical Operations:

  • “AND” is Conjuction
  • “OR” is Disjunction
  • “NOT” is Negation

Defining a Class

Defining a class in HAGGIS is as follows. [CLASS <Class Name>()] There are various methods you can declare in HAGGIS such as:

   CONSTRUCTOR( [Data Type][Data Name], [Data Type][Data Name]...)
       The users' HAGGIS code will then go here.
   END CONSTRUCTOR
   FUNCTION <Function Name>() RETURN 
       The users' HAGGIS code will then go here.
       RETURN THIS <Class Property>
   END FUNCTION
   “THIS” is used to reference the current object invoking the method.
   PROCEDURE <Procedure Name> ()
       The users' HAGGIS code will then go here.
   END PROCEDURE

Application and Uses

HAGGIS was originally implemented and then expected to be used in the following ways. The students would be taught how to code in a programming language that the teacher has selected. The students would then make plans in a pseudocode format in a higher level of language than the code itself. Once the students felt comfortable with writing pseudocode they would then be introduced to HAGGIS as it is the language used in exam texts [2]. HAGGIS was implemented in this way because research has shown the ability to understand programs is essential to developing further programming skills [2]. Courses run by the SQA (National 5 and Higher) both include outcomes that require students to have this ability. Because HAGGIS is so easy to understand and pick up, it has been used in exam texts. It is noted that students were and never will be asked to write any code in HAGGIS during an exam, they are only required to be able to read and understand it.

Problems

There have only ever been a very small number of problems with HAGGIS. None are to do with the language itself but more to do with the way students view it. The first is that students had no idea why they were being taught to write a completed computer program in two languages. The other is that they were mixing up the two languages that they had been taught and were often getting syntax wrong because they were being taught the two languages at the same time which was causing some minor confusion [2].

Observation

HAGGIS was observed by the creator and was found to be used in the following ways [2]. HAGGIS was being used as a planning language for the computer programs that students were being asked to create. After students had been asked to refine their code through several planning stages, a final plan was made using HAGGIS. After this final plan is made, the HAGGIS code would then be transferred into a real programming language that is specified by the teacher. This method is effective in increasing students skills as mentioned earlier to give them as much preperation as possible for the exam for when they will see HAGGIS applied in a context.

References

  1. ^ a b Cutts, Quintin. "Computing Science Education in Schools". Glasgow University. Retrieved 8 November 2016.
  2. ^ a b c d e f Tennant, Mark, J. "Haggis – what should it be used for?". CompEdNet. Retrieved 8 November 2016.{{cite web}}: CS1 maint: multiple names: authors list (link)
  3. ^ Michaelson, Greg. "Object Oriented Programming from Procedural Programming with a little Computational Thinking" (PDF). Herriot Watt University - Mathematical Computing Science. Retrieved 8 November 2016.
  4. ^ Connor, Richard. "Haggis Parser". appspot. Retrieved 8 November 2016.
  5. ^ Ferguson, David. "VisualHaggis". Retrieved 8 November 2016.
  6. ^ a b "Reference language for Higher Computing Science Question Papers" (PDF). SQA. Retrieved 8 November 2016.
  7. ^ "Reference language for Advanced Higher Computing Science Question Papers" (PDF). SQA. Retrieved 8 November 2016.
  8. ^ a b "HAGGIS Working Document". Page 4. Retrieved 8 November 2016. {{cite web}}: Unknown parameter |authors= ignored (help)

HAGGIS (Programming Language)