STANDARDIZED TERMINOLOGY
When you're creating code comments, object names, help files, and system documentation, it's important to use terms that have an accepted and unambiguous meaning. You should build a list of standardized terms for your specific industry or application to ensure consistency. Table D.19 provides a short list of standardized terminology. These terms aren't required by LNC; they're only examples.
| Term | Description |
|---|---|
| Add | To create a new record. You should select one of Add, Create, Enter, and New to be consistent. |
| Beg | The start of a process. |
| Close | To close. |
| Comment | A more familiar term (than Remark or Notes) for text originating with a human. |
| Desc | A description, often a long text string. |
| Edit | To change or modify. |
| Editor | The last person to change a record. |
| End | The end of a process. |
| Flag | A programming item with fixed set of values, usually true/false (Boolean). |
| Key | An index used to find a record. |
| Max | The maximum, better than Most. |
| Min | The minimum, better than Least. |
| Open | To open. |
| Owner | The creator of a record, process, or object. |
| Save | To commit a record. |
| User | The person currently running an application. |
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.