Project Ideas

“ Web Issue-manager for distributed teams “

Issue Manager is a web-based application designed to help a workgroup keep track of issues and tasks via a shared central resource. The data is stored centrally on the server, which make it specially suitable for distributed teams who can use just the web browser to access it. No local software needs to be installed on the client and all web browsers are supported.

Strategic issue management is the responsibility of the entire organization. That responsibility crosses all units and all reporting lines. It is the external component of strategic management.

This issue management framework involves three functions:

• Gathering/Monitoring intelligence and information
• Analyzing the information and classifying the issue
• Taking action and evaluating the results

Issues are events that occur outside the control of an organization and that may require the organization to take action.

For effective strategic management , issues need to be classified and ranked.

Classification determines whether the problem is internal pr external and routes it accordingly

Ranking determines the priority order for dealing with and expending resources on an issue.

The purpose of the issue resolution process is to provide a mechanism for organizing ,maintaining and tracking the resolution of issues that cannot be resolved at the “individual” level. The approach consists of issue control mechanism and a well definied Process that enables the project team to identify ,address and prioritize problems and issues. All action items will be tracked until they are resolved.

The issue Manager will report on all open issues at the weekly status meetings. If the list of issues is too long only the new issues will be discussed. At times, it may be advisable to pre-distribute issues information so that the project status group can review the material before the meeting.When the issue of problem has been resolved and verified , the actual date problem was resolved and an approval signature complete the issue resolution process, and the issue is Closed.

Platform:- Windows

• IIS
• Microsoft access
• .NET Framework SDK Beta2/ASP.NET Premium Edition Beta2
• Winzip or similar program

• Local area network configuration

Our goal is to introduce a Package Manager for Source Code Installation in Linux distributions. This Package Manager would itself take care of maintenance of complete system, which so far has been a very cumbersome job for any administrator. This LPM along with a Registry would provide an alternative back-end for various text configuration files.

Thus, instead of each application having its own text-configuration files, our application provides a universal, hierarchical, fast & consistent namespace & infrastructure to access configuration parameters through a key-value pair mechanism.

This would include creation of separate entities:-

• local database for local machine administration & maintenance.
• registry for local as well as remote administration of the machine configuration.

• I386 Architecture Machines.
• Red Hat Linux 9.0 Operating System.

The project has some hardware & software requirements that are described as follows:-

• Red Hat Linux 9.0 with kernel(2.4.23)
• Linux GUI builder package – QT
• A C/C++ IDE for Linux – Anjuta
• Elektra API’s

• Two PC’s with usual configurations (128/256RAM P4 Processors etc.)
• LAN connection b/w the machines.

It has been long desired to have some kind of Package Management system in existing Linux environment. Due to the pre-existing feature of being Open Source, any package can be installed & used, almost anywhere in a Linux system (be it Personal/Server configuration).

Today’s GNU/Linux systems are a sum of independent components collected from Open Source Community. Each of them already has a working, but selfish configuration system.

One of the system (maintained by an administrator X) has an Apache package (say version 1.4) installed from source (instead of RPM distribution).After some time a new administrator (say Y) starts maintaining that system. Suppose he comes to know that Apache (version 1.4) has a serious security flaw and he installs a newer version (2.0). Now to clean the system more efficiently he has to effectively delete all the files (main files as well as support files) from various locations which become a very tedious task itself.

Thus we realize that the overall maintenance of complete Linux system is a highly cumbersome process which any administrator has difficulty in carrying out, both efficiently & effectively.

Now that the problem at hand is very much clear, the next & foremost step is as to how the information about various packages, getting installed on the system, needs to be track down & stored. One of the most important design issues that needs utmost attention is:-

The existing system should not change. It means that we cannot go about changing the entire installation methodology, just for the sake of obtaining the desired information. The reason is if the existing system changes, there is a high probability that the newer system is not at all welcomed by the existing developer & user society.

Thus after considering various other issues, the solution that has been finalized is as follows:-

We need to trap the information when & where it is getting created & moved into the existing system.

This information then has to be stored & later on retrieved in an efficient & effective way that would suite our project requirements.

Thus the complete project now gets divided into 4 different stages. They are:-

• Collection of all the data.
• Extraction of Information.
• Efficient storage of the information.
• Effective retrieval of this information.

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