HIGHLIGHT Product Documentation
This documentation is for reference only. Original Highlight Product Documentation is available at https://doc.casthighlight.com/
- Ensure that your main SQL-related code artifacts are documented
- Operators and operands should use appropriate spacing to help readability
- Levels of logic complexity and conditions seem to be unbalanced
- Avoid using "this" unless it points to a newly created object (and tested)
- Wildcard imports should not be used too frequently
- Exceptions shouldn't be caught with system exception classes
- Avoid Implied Typecasting
- Using {curly braces} is less error-prone
- Too much commented out code can be counter-productive
- The vocabulary frequency is too low
- Bulky files are complex to work with
- A line of code shouldn't be too long (to help readability)
- Ensure the code contains enough block of comments
- Short code identifiers are harder to understand
- Software Maintenance Estimates
- Backfired Function Points
- Release Notes - Highlight June 2017
- Release Notes - Highlight March 2017
- Business Impact
- Release Notes - Highlight October 2016
- Release Notes - Highlight May 2016
- Automated Dependency Discovery & Supported Package Managers
- Software Elegance
- Software Agility
- ROAR Index
- Software Resiliency
- Release Notes - Highlight February 2016
- CAST Highlight primed for Cyber-secure Cloud Analytics with ISO/IEC 27001:2013 certification
- Release Notes - Highlight October 2015
- Release Notes - Highlight June 2015