3.2.5 - Writing Maintainable Programs

AndrewZV
Mind Map by AndrewZV, updated more than 1 year ago
AndrewZV
Created by AndrewZV about 6 years ago
46
2

Description

A Level Computing (F452) Mind Map on 3.2.5 - Writing Maintainable Programs, created by AndrewZV on 04/02/2014.
Tags

Resource summary

3.2.5 - Writing Maintainable Programs
1 Key Terms
1.1 Variable
1.1.1 Name associated with a particular memory location used to store data.
1.1.2 By using the variable name, the programmer can:
1.1.2.1 Store data
1.1.2.2 Retrieve data
1.1.2.3 Manipulate data
1.1.3 The value of the data is not know when the program is written.
1.1.4 Scope
1.1.4.1 Local variable
1.1.4.1.1 Declared and used inside:
1.1.4.1.1.1 Modules
1.1.4.1.1.2 Functions
1.1.4.1.1.3 Procedures
1.1.4.1.1.4 Subroutines
1.1.4.1.2 Only available inside their specified module, procedure etc...
1.1.4.1.3 Created when the subroutine is called.
1.1.4.1.4 Destroyed when the subroutine exits.
1.1.4.2 Global variable
1.1.4.2.1 Declared at the beginning of the code.
1.1.4.2.2 Available throughout the code.
1.1.5 Can change while the program is running.
1.2 Constant
1.2.1 A data item with a fixed value.
1.2.2 Assigned to a variable that cannot be changed when the program is executed.
1.3 Identifier
1.3.1 A name representing an object within a program.
1.3.1.1 Variables
1.3.1.2 Functions
1.3.1.3 Procedures
1.3.1.4 Data Types
1.3.2 Given meaningful names.
1.4 Reserved Word / Keyword
1.4.1 Vocabulary of a programming language.
1.4.2 Variables or other identifiers cannot use keywords.
1.4.3 Can only have the meaning which is defined in the language.
2 Coding Practices
2.1 Modularisation
2.1.1 Series of small routines.
2.1.2 Can quickly be seen to be performing one function.
2.1.3 Complex operations should be broken up into subroutines.
2.1.3.1 Defined separately and called from the main program.
2.1.4 Easier way to achieve if the program has been designed using top-down techniques.
2.2 Commenting Code
2.2.1 Comments are read by the programmer and ignored by the computer.
2.2.2 Should be written while the code is written and not after.
2.2.3 Comments should be used for:
2.2.3.1 Program headers
2.2.3.2 Subroutines
2.2.3.3 Declaring variables
2.2.3.4 Inline comments
2.3 Indentation
2.3.1 Improves readability.
Show full summary Hide full summary

Similar

A level Computing Quiz
Zacchaeus Snape
Types and Components of Computer Systems
Jess Peason
Input Devices
Jess Peason
Output Devices
Jess Peason
Computing
Kwame Oteng-Adusei
Pack of playing cards answer
Karl Taylor
Code Challenge Flow Chart
Charlotte Hilton
3.2.6 - Testing and Running a Solution
AndrewZV
Computing Hardware - CPU and Memory
Shantal K Green
Computing Hardware - CPU and Memory
Shantal K Green
Computing Hardware - CPU and Memory
ollietablet123