Final answer:
Static Code Analysis is performed to catch flaws in the source code early, typically before a validate or release and usually between sprint and deployment, to refine the design and meet established criteria.
Step-by-step explanation:
Static Code Analysis identifies defects before you run a validate or a release. This process is crucial as it focuses on identifying potential issues in the code without having to execute the program. It involves evaluating the source code at various stages of the software development life cycle to ensure the code quality meets the established criteria and constraints.
Static Code Analysis is usually performed between sprint and deployment, allowing developers to refine the design of the software before it is released to production. This proactive approach helps to catch flaws early in the development process, thereby reducing the cost and time required to fix them later on. If testing and evaluation reveal weaknesses in the design, it may be necessary to refine the code or even go back to the drawing board for further concept generation.