Assoc. Prof. Ayman Taha, Eng. Mennat Allah Hassan, Eng. Heba Osama
3rd of Jan. 2022
Static analysis is a debugging approach that checks source code automatically before a program is run. However, Static Code Analysis is a debugging method that includes studying source code before running software. To achieve this, a collection of code is compared against a set of coding rules. Static analysis can help development teams who are under pressure. It was necessary to offer high-quality releases on schedule. Requirements for coding and compliance must be satisfied. These tools are mostly used by programmers to aid in the understanding of code structures. It’s frequently used before, and occasionally during, component and integration testing by developers. A compiler may also be called a static analysis tool because it produces a symbol table, points out erroneous usage, and tests for non-compliance with coding language rules or grammar.
1.1 Purpose of this document
The main purpose of this document is to illustrate and outline the requirements for our graduation project (Yotta Tool). The software implementation covers the functions and the diagrams that describe our project. This document shows the vulnerabilities and holes that “Yotta Tool” detect. The application will contain dataset from software developer code or stakeholder Web application.
1.2 Scope of this document
YOTTA static analysis tool aimed to help software developers free of bugs and holes. Help them in testing before release. Also stakeholders that have Web application to be insecure from any vulnerabilities and holes. They will get a report about their holes and bugs as a PDF by mail.
1.3 System Overview
The Yotta tool is a highly effective way for software engineers to find and show programming errors, bugs, and vulnerabilities. It helps developers to make sure that their project is safe to be released by detecting faults before run-time, and it detects the errors that the user could make during implementation, whether it’s a security issue, a refactoring issue, or a design issue. Our aim is to save users who search for security. As a result, we cover the greatest number of vulnerabilities in user files to help developers get the most out of our tool. An in-depth warning or feedback regarding the difficulty and a few answers to the hassle if found would be ideal.
1.4 System Scope
- Take any source code as input.
- Read and analyze input.
- Create a pdf report explaining mistakes found in input.
- A usable system that gives out a report that is easy for the user to understand their mistakes and their severity from.