Guidelines
Security
This category includes chapter contains guidelines that are essential for concerned specifically with ensuring security of Java-based applications.
They are concerned with issues such as:
- dealing with sensitive data;
- avoiding common injection attacks;
- language features that can be misused to compromise security; and
- details of Java's fine-grained security mechanism.
| Content by Label | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
This chapter contains guidelines for defensive programming. Defensive programming is carefully guarded programming that helps you construct reliable software by designing each component so it protects itself as much as possible, for example, by checking that undocumented assumptions remain valid [Goodliffe 2006]. These guidelines look at areas of the Java language that can help to constrain the effect of an error or help recover from an error.
| Content by Label | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Best Practices
This category chapter includes guidelines that are:
- Essential for ensuring correctness of Java code;
- Specific, implementation-level java coding advice;
- Have a higher normative requirement than defensive programming category.
The guidelines deal with generally low-level Java language features that can easily be misused by the unwary.
| Content by Label | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Program understandability is the ease with which the program can be understood, that . That is, the ability to determine what a program does and how it works by reading its source code and accompanying documentation [Grubb 2013]. Another term used to describe this property of source code is readability. Understandable code is easier to maintain because software maintainers are less likely to introduce defects if the code is clear and comprehensible. Understandability helps in manual analysis of source code because it allows the auditor to more easily spot defects and vulnerabilities.
The guidelines in this chapter are mainly stylistic in nature, and will help a Java programmer to write code that it clearer and more readable.
| Content by Label | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Programmer Misconceptions
This category includes chapter contains guidelines that address:
- Misconceptions about Java APIs and language features;
- Assumptions and ambiguity-laced programs;
- Situations in which the programmer wanted to do x but ended up doing y.
They deal with areas where developers often make unwarranted assumptions about how Java works, or where ambiguities can easily be introduced.
| Content by Label | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...