0 of 12 lessons complete (0%)
Conventions

Naming conventions and naming schemes

You don’t have access to this lesson
Please register or sign in to access the course content.

File management and naming is absolutely essential to the success of any project[1].

Files should be saved in logical locations with appropriate file names.

For example doc1.docx does not tell the user anything about the file. Cover Letter.docx is more appropriate.

This shoud be stored in a folder called Letters or similar.

If using a database to store documents metadata needs to be completed for each file as well so that it can be easily searched for and found.

Different outcome[2] types will require different naming conventions.

For example a static[3] website will usually require the home / main page to be saved as index.html. If this was a php based website this would be index.php

Find out more below:

Terms definitions
2. outcome. Products and systems developed through Technological Practice[4] for a specific purpose. A technological outcome is evaluated in terms of its fitness for purpose[5], and can be described by their physical and functional nature.
3. static. In relation to computing static usually means that something is unable to change. In relation to Object Orientated Programming[6] (OOP) static is used to refer to a variable[7] or method that is used for multiple different objects. They can be called directly and do not need[8] an object to be instantiated (created) using a class.
Terms definitions
1. project. File management and naming is absolutely essential to the success of any project. Files should be saved in logical locations with appropriate file names. For example doc1.docx does not tell the user anything about the file. Cover Letter.docx is more appropriate. This shoud be stored in a folder called Letters or similar. If using a […]
2. outcome. File management and naming is absolutely essential to the success of any project. Files should be saved in logical locations with appropriate file names. For example doc1.docx does not tell the user anything about the file. Cover Letter.docx is more appropriate. This shoud be stored in a folder called Letters or similar. If using a […]
3. static. File management and naming is absolutely essential to the success of any project. Files should be saved in logical locations with appropriate file names. For example doc1.docx does not tell the user anything about the file. Cover Letter.docx is more appropriate. This shoud be stored in a folder called Letters or similar. If using a […]
4. Technological Practice. File management and naming is absolutely essential to the success of any project. Files should be saved in logical locations with appropriate file names. For example doc1.docx does not tell the user anything about the file. Cover Letter.docx is more appropriate. This shoud be stored in a folder called Letters or similar. If using a […]
5. fitness for purpose. File management and naming is absolutely essential to the success of any project. Files should be saved in logical locations with appropriate file names. For example doc1.docx does not tell the user anything about the file. Cover Letter.docx is more appropriate. This shoud be stored in a folder called Letters or similar. If using a […]