ScholaFly

CS06-08 Computer Science Watch

The IDE

Watch on YouTube

In this lesson

Integrated development environment (IDE): how to name the common tools of an integrated development environment. Edexcel 1CP2 and OCR J277 GCSE. Software and languages 8 of 8. Full Software and languages playlist: https://www.youtube.com/playlist?list=PLQW0s9-KegDg More at https://scholafly.com

By the end: Name the common tools of an integrated development environment - the editor and its features, error diagnostics, the run-time environment, translators, and debugging tools such as breakpoints, stepping and a variable watch - and describe how each one helps a programmer write, run, test and fix a program, without describing a tool by repeating its own name.

What it covers

  1. 0:00 Intro: the IDE
  2. 0:44 The IDE
  3. 2:05 The editor and error diagnostics
  4. 5:26 Debugging: finding and fixing errors
  5. 8:07 Name three IDE tools and describe

Key words

About this video

Integrated Development Environment (IDE) | GCSE Computer Science | CS06-08

Integrated development environment (IDE): how to name the common tools of an integrated development environment.
Edexcel 1CP2 and OCR J277 GCSE. Software and languages 8 of 8.
Full Software and languages playlist: https://www.youtube.com/playlist?list=PLQW0s9-KegDg
More at https://scholafly.com

Video code: CS06-08 (search "ScholaFly CS06-08")

#GCSEComputerScience #SoftwareAndLanguages #TheIDE

For teachers
This GCSE Computer Science lesson teaches the IDE. By the end, students should be able to name the common tools of an integrated development environment - the editor and its features, error diagnostics, the run-time environment, translators, and debugging tools such as breakpoints, stepping and a variable watch - and describe how each one helps a programmer write, run, test and fix a program, without describing a tool by repeating its own name. It works through four worked examples and the mistakes examiners report.

Exam board specification references:
OCR J277
- 2.5.2

Read the transcript

You type a line of code, and before you have run anything, one word gets a wavy red line under it. What spotted the mistake? Was it the programming language itself? The obvious guess is the language. It was not, because a language is only the words and rules you write in. The wavy line comes from a tool inside the program you are typing into, and that program holds a whole set of tools. That program has a name, and so does every tool in it.

The program you type code into is usually an IDE, short for integrated development environment. An integrated development environment is one program that brings together the tools a programmer needs to write, run, test and fix code. Integrated means those tools all sit in one place. Think of a workshop with every tool on one bench, so nobody walks to another building each time they need a clamp. An IDE does that for code. Not every exam board lists the IDE. Check your course, and if you program at all, these are the tools you will be using. Keep two things apart from the start. The language is what you write: its keywords, its variables, which are named stores for values, and its comments, which are notes for people reading the code. The IDE is where you write it. In an answer, every tool gets the same treatment: name the tool, then say what it does for the programmer.

Start with the editor. The editor is where code is typed and changed, and it helps in several ways at once. Line numbers let you find the exact line an error message points to. Syntax highlighting colours each part of the code by its job, so a mistyped keyword stands out because it comes up the wrong colour. Auto-indentation lines up blocks of code for you, and code completion offers to finish a keyword or a name you have started typing, which saves typing and spelling slips. The second tool is error diagnostics, tools that find and report errors. They underline a syntax error as you type, a syntax error being a break in the language's rules, such as a missing bracket. When the program runs and fails, error diagnostics give a message with the line number and the kind of problem. What each kind of error is gets a video of its own, on syntax, logic and runtime errors. Now a new question. A student types a line, and before running anything, part of it turns a different colour with a wavy line under it. Which two tools are at work, and what should the student do next? The editor's syntax highlighting and the error diagnostics, which have flagged a syntax error. The student should read the message, fix that line, and then run the code to check. One examiner's report, on a paper that is sat at the computer, advises running your code, and says the IDE will highlight syntax errors in the code editor or identify them with a runtime error during execution. The habit it points to is to run your code early and often, so the IDE can show you what is wrong while it is still small. The third tool is the run-time environment. It lets you run the program inside the IDE and see its output there, so you can test it without leaving the window. The fourth is the translator. The IDE includes a compiler or an interpreter, so pressing run translates your code and runs it in one step. The translator is one tool inside the IDE, and the video on compilers, interpreters and assemblers covers how it works. One examiner's report says candidates were mostly able to name and describe suitable IDE tools, such as an editor, error diagnostics, a run-time environment or a translator. If you can name those four, you are on solid ground.

Now the debugging tools, for finding and fixing errors in a program that runs but does the wrong thing. That same examiner's report says other sensible tools were credited too, such as a variable watch window and stepping. A breakpoint is a marker on a chosen line. The program pauses when it reaches that line, so you can look at what has happened so far. Stepping runs the program one line at a time, so you can follow the path it takes and see the line where it goes wrong. A variable watch, sometimes called a variable inspector, shows the value of each variable as the program runs, so you can see the moment a value goes wrong. Error diagnostics catch a broken rule. A program that runs and gives a wrong answer breaks no rule, so it is the programmer, with these debugging tools, who finds the problem. Now a testing question. A program runs, but it prints the wrong total. Name two IDE features that would help find where the total goes wrong, and say how each one helps. Have a go on paper: two tools, and a sentence for each. First, a breakpoint on the adding line. Execution pauses there each time, so you can check what has happened up to that point. Second, the variable watch. It shows the total's value after each addition, so you can spot the exact step where it goes wrong. Stepping through the lines would also do. One examiner's report on a question like this says less successful responses tended to be descriptions that simply repeated the name of the feature given. An answer such as, debugging tools allow debugging, names a tool and then says nothing new about it. The fix is to name it, then say what it does for you. A breakpoint pauses the program at a chosen line, so you can inspect the values so far.

Now put the naming rule to work. A question asks you to name three IDE tools and describe each one without repeating its name. Two of them arrive done. The editor lets you write and change your program, and numbers the lines so an error message can be traced to the right one. The run-time environment lets you try the program inside the IDE and see its output. Now yours. How would you describe error diagnostics without using the word error? They find mistakes in the code and report them, underlining a broken rule as you type and giving the line number and the kind of problem. Now sort these. Which of these is not a tool of an IDE: a breakpoint, a comment, a run-time environment, or a variable watch window? The comment. The other three are tools the IDE gives you. Now the reason behind it. You type a comment in the editor, so why is it not an IDE tool? Because a comment belongs to the language. It is a note you write in the code, and it would be there whatever program you typed it into. One examiner's report says a small number of candidates mistakenly described tools contained within programming languages, such as commenting or use of variables. The fix is to ask whether the IDE gives it to you, or you write it in the code.

To finish, put the tools to work on four questions.

First, what does the word integrated mean in integrated development environment? That the tools a programmer needs to write, run, test and fix code are all together in one program.

Now a fresh case. A program stops with a message about line twelve. Which tool produced the message, and which editor feature takes you to line twelve? Error diagnostics produced the message, and the editor's line numbers let you find the line it names.

Now a loop that should count to five, but the count ends at four. Which tool shows the count changing, and which lets you go through one line at a time? The variable watch shows the count's value as it changes. Stepping moves through the code one line at a time.

Now the last. How would you describe the run-time environment, without the word run or the word environment? It lets you try the program inside the IDE and see its output in the same window, so you can test it without leaving.

So what spotted the mistake under that wavy red line was the IDE, its editor and its error diagnostics, and not the language. The language is what you write, and the IDE is where you write it.

If there is no need to see this twice, give it a thumbs-up. If it is still settling, it comes with time at the keyboard: open an IDE and find each tool once.

That completes Software, systems and languages. The next chapter is Networks. Hopefully that's next in your feed, but if not, search for ScholaFly C S oh seven, oh oh.

Every other video is on scholafly.com too, easy to search by video code or by keyword. Whatever you're revising, go there and have a look, or, watch the next video.

Related terms

For: OCR GCSE J277, Edexcel GCSE 1CP2

On the specification

BoardSpecStatement
OCR GCSE J2772.5.2Describe the tools an IDE provides (editors, error diagnostics, run-time environment, translators) and how each helps a programmer.
Edexcel GCSE 1CP2missingthe plan names no spec point for this board
For teachers

This GCSE Computer Science lesson teaches the IDE. By the end, students should be able to name the common tools of an integrated development environment - the editor and its features, error diagnostics, the run-time environment, translators, and debugging tools such as breakpoints, stepping and a variable watch - and describe how each one helps a programmer write, run, test and fix a program, without describing a tool by repeating its own name. It works through four worked examples and the mistakes examiners report.