Final Year Projects

The purpose of this document is to collect, analyze and define high-level needs and features of the Source Code Analyzer. It focuses on the capabilities needed by the stakeholders, and the target users, and why these needs exist. 

Input to this source code analyzer will be a windows code and as an output it’ll give us graphical view of amount of portable source code, non-portable source code.

Purpose of Source Code Analyzer

In order to comply with this kinda working knowledge of different operating systems is must because one just can’t simply use the same program for different operating systems. One has to again write that program taking into consideration compatibility issues. This is not always possible. Here idea of porting comes into the picture.

We’ve discovered that there are no tools available to check the compatibility issues; ergo we’ve decided to design software that will analyze a program and give us an information regarding parameters needed to be considered while going for porting. This software is called source code analyzer.

Summary of Capabilities

SCA will be providing a launch pad for a porting project. It will indicate the comparative study of the existing code. SCA will assist management to identify problem areas and gauge staff workload. The reports generated by SCA allow high level review of problem status.

SCA will assist the programmers too as it provides the readymade reverse engineered documents of existing code as well as special guidelines for porting that code on the other platform.

Objectives

Manual analyzing of source code is a very time consuming and tedious. SCA attempts to reduce this process of analyzing the existing code, provides various reports, graphs, suggestions, which are extremely useful not only for developers but for management personnel also to decide the deadline, and number of employees to be assigned.

Platform:

 

• Jdk 1.4
• Software requirements:
• Gel IDE

 

Hardware requirements:

 

• PROCESSOR: PENTIUM III/IV.
• MEMORY: 256MB onwards

Source code analyzer final year project for cse

Project Statement To reinforce the discretionary access control mechanism on Windows 2000 through the creation of secure Virtual Drives.

Motivation and Objectives Windows 2000 has two forms of access control over objects. The first form—discretionary access control—is the protection mechanism that most people think of when they think of protection under Windows 2000. It’s the method by which owners of objects (such as files or printers) grant or deny access to others. When users log in, they are given a set of security credentials, or a security context. When they attempt to access objects, their security context is compared to the access control list on the object they are trying to access to determine whether they have permission to perform the requested operation.

Privileged access control is necessary for those times when discretionary access control isn’t enough. It’s a method of ensuring that someone can get to protected objects if the owner isn’t available. For example, if an employee leaves a company, the administrator needs a way to gain access to files that might have been accessible only to that employee. In that case, under Windows 2000, the administrator can take ownership of the file so that you can manage its rights as necessary.

With a privileged access control over objects, a user with administrative privileges can tamper with the files of other users, make changes in them or even delete them. There are situations where this privileged access of a user over objects is not only undesirable but can also cause heavy damage to the organization (consider a user modifying a tender document). An organization prefers to rely on the system than trusting those with administrative privileges.

We are trying to reinforce the discretionary access in WINDOWS 2000, which enables a user to protect his/her data from being tampered by users with privileged access to the system. Our project is driven by the concept of polyinstantiation of common resources leading to strong separation of users.

The easiest solution that comes to the mind is to provide the user with encryption software. Whatever documents the user wants to protect he simply encrypts it. Even the administrator cannot decrypt this document.

But if one looks carefully at the issue one finds that the administrator can still corrupt or delete the user’s data. Also the existence of the data can be known. Then also if we look from the point of view of the user’s convenience he has to explicitly specify which files need to be encrypted.

Our aim is to provide the user with a convenient mechanism to protect his data. We are providing every user his/her own secure virtual disk drive inaccessible and invisible to every other user, even the system administrator. The secure virtual drive is like a safe or a vault, what is inside it is known and accessible only to the owner.

• Win-2000 Operating System
• Driver Development Kit(DDK)
• Softice Debugger
• OSR Loader
• DBGView

Final year projects for cse

 

 

 

DOWNLOAD SYNOPSIS