3. Introduction
Requirement Analysis
Vision And Scope Of The Project
System Design
System Implementation
Test Cases
Conclusion And Future Scope
5. Hardware requiremnts:
PROCESSOR : Intel Pentium II or above
PROCESSOR speed : 1.76 GHZ or above
RAM : 32 MB or above
HDD : 40 MB
Software Requirements:
PLATFORM : WINDOWS XP
FRONT END : C, C# .NET
BACK END : MS ACCESS
6. For the users of antivirus products who would like to
know the simulation of an antivirus the Virus
Detection System is an application which shows the
way of approaching a generic antivirus product.
Unlike to some antivirus products which binds
themselves to specific signatures of some particular
viruses, this simulation provides a generic approach by
which we are able to detect more than a single virus
with a common virus code in the database.
7. DATABASE UPDATION
s1.1-Adding new code to the database.
s1.2-Deleting the existing old code.
SCANNING FILES
s2.1-Scanning the selected file or folder
s2.3-A report is generated with status of scanned files.
s2.4-Provides the option to delete the files which is infected
s2.5-Provides an alternate option to record the infected file location.
SCANNING REPORT
s3.1-Shows the infected files after scanning is completed.
s3.2- Provides the options like moving to vault and delete now.
VIRUS VAULT
s4.1-View the affected files.
s4.2-Delete the selected files.
10. Data Dictionary :-
1. Scode table
2. Report table
3. Vault table
Database Logical Design :-
1. Normal forms
2. First Normal Form (1NF)
3. Second Normal Form (2NF)
4. Third Normal Form (3NF)
5. Boyce-Codd Normal Form
6. Fourth Normal Form (4NF)
7. Fifth Normal Form
UML Diagrams
11. User
Use Case Diagram
Scanning Files
Updating Database
Storing the infected Files.
18. The “virus tracking system” is a generic antivirus
approach that will detect the suspicious behaviors
of the files that are scanned and it avoids the
pitfalls of the signature scanning method and
provides a full security to the user.
19.
20. At present in our system only the files that were
scanned and reported as affected can be deleted or
can be moved to vault to delete in future. So the
only option provided for the user is to delete the
affected file. More over the affected file can be
repaired by deleting the virus code that was
matched from the disassembled code and restoring
the new file from the repaired code.