Pick up where you left off on this computer



Learn KnowledgeKube Course 1 > Chapter 5: Starting to build your first KnowledgeKube Application > Naming Conventions – Getting Things Right from the Start


Skip Navigation Links.

Naming Conventions – Getting Things Right from the Start

When you start to create your KnowledgeKube project, you may be tempted to just add everything quickly without giving much thought to the names you use to identify content. After all, you created it, so you should be able to remember what a particular question, attribute or variable is used for, right?

This may be true while your project is small and relatively uncomplicated, but as you begin to expand its functionality you will soon find keeping track of various parts of your project a lot more difficult.

Additionally, if someone else is asked to make changes to your project, having a naming convention for identifying content will make their job considerably easier.

It is good practice to be consistent with your naming throughout. For example, if you are using a date of birth element of some kind across three projects, instead of using different names: DOB, DateOfBirth and CustomerDOB it would be better to use one term for all three.

Naming things consistently allows you to re-use calculations and other content across several projects - you won't need to significantly change how calculations refer to content if it's called the same thing (or similar) each time.

In computer science and software engineering, Reusability is the use of existing assets in some form within the software product development process. The ability to reuse relies in an essential way on the ability to build larger things from smaller parts.


Found a problem or something unclear? Get help or provide feedback on this page by completing this form.

Is seven = two ? (true/false)