Compliance with Design
Compliance Testing is performed to maintain and validate the compliant state for the life of the software. Every industry has a regulatory and compliance board that protects the end users.
Software compliance refers to how well an application obeys the rules in a standard. To achieve software compliance, you might also have to, for example, produce certain types of documentation or add security testing at more points in your software development life cycle.
Checklists:
- Professionals, who are knowledgeable and experienced, who understand the compliance must be retained.
- Understanding the risks and impacts of being non-compliant
- Document the processes and follow them
- Perform an internal audit and follow with an action plan to fix the issues
Coding Standards
Coding:
- The objective of the coding phase is to transform the design of a system into code in a high-level language and then to unit test this code.
- Good software development organizations normally require their programmers to adhere to some well-defined and standard style of coding called coding standards.
Coding Standards:
- A coding standard gives a uniform appearance to the codes written by different engineers.
- It enhances code understanding
- It encourages good programming practice
- Agree upon standards for coding styles
- Promotes ease of understanding and uniformity
- No idiosyncratic quirks that could complicate understanding and refactoring by the entire team.
Coding Guidelines:
- Line length
- Spacing
- Code is well documented
- Length not exceed 10 source lines
- Don’t use goto statement
- Inline comments
- Error messages
0 Comments