2.1.2 Thinking ahead

Maximise code efficiencies Minimise errors

Start with the output and from there find out what you need and the processes to get that output

Inputs: length: real / float Width: real / float Height: real / float Process: Length x width x height Output: Volume: real/ float Process

Conditions that already exist and could affect how you devise a solution to a problem

Time Cost The overall quality of the solution

Quicker than retrieving items from secondary storage Improves efficiency Takes less time One live of code can be used multiple times Use of functions Use of classes Use of external libraries

Complicated to implement If the cache contains outdated or incorrect data, the wrong data is often retrieved and needs to be removed/ flushed Maintaining the correct sequencing of instructions or data items can be problematic

Data being requested before it is actually needed

The process of temporarily storing copies of frequently used data or instructions in small, fast memory This is quicker and more easily accessed than main memory This increases speed and efficiency of the system Eg. A CPU can store recently used instructions from RAM so the processor can use them faster net time

Shortens developing time Saves system resources Lowers development costs Reduces redundant code Pointless to write more- potentially flawed- code when perfectly good code already exists

Libraries Allow developers to use code that has been prewritten and tested code Methods/ subroutines In our code we use methods and subroutines — like functions and procedures — that we call instead of writing the same code multiple times.

Reselling components to a third party Eg. Facebook offers integration with other programs and software platforms May also use google, x, or facebook to log into other platforms

Developers can pull in contacts from friends lists The systems being linked also allows certain procedures and functions to be available to other developers via API