First review Part-A Identification and Statement of the Problem Bug tracking is a methodology used by software developers to collect

reports of defects or "bugs" in software programs. This allows developers to further refine their software design by making continual changes or upgrades to the product in order to better serve the customer base. Programmers who author software often invite the public to help identify problems. If the program has a nominal following, finding bugs might be accomplished by simply asking users to report any difficulties via email. Bug tracking reports typically include an explanation of the exact nature of the problem, the version of the software in question, and the operating system. While developers of programs with modest popularity can accomplish "manual" bug tracking via email, it would be a logistical nightmare for developers of more popular or ubiquitous software to attempt this approach. This is where developers can benefit most from using a special reporting software. To facilitate reporting, some highly popular software programs and operating systems incorporate built-in bug reporting. If the program crashes, it will attempt to connect to the Internet to relay an error log to an automated bug tracking system. As this feature might be considered a breech of privacy, it can normally be disabled if the users chooses to do so. PART-B Literature Survey( data Collection / Information Retrieval)

SOLUTION STRATEGIES
Analysis is a process of breaking the problems in to the successively manageable parts for individual study. System analysis is the study of various operations that has to be done to solve the problems. One aspects of the system analysis is defining the boundaries of the system and determining whether or not the proposed system should

consider other related system. During the

analysis, data are collected on the available

files, decision points and transaction handled by the existing system. Various tools are available to perform the system analysis. Some of the tools are data flow diagram, interviews, onsite observation and questionnaires regarding the proposed system, interviews and DFD are the commonly used tools in analysis. The interview is the face-to-face interpersonal role situations in which the designed questions are asked to gather information about the personal area. The interviews are the oldest and most often used device for gathering information in system analysis. The two main purposes of interviews are, Used exploratory devices to identify relations or verify information. To capture the information as it exists. Interviews are efficient techniques for eliciting the information about the complex subject and offers better opportunity. Data Flow Diagram are used to analyze the transactions involved in the proposed system, processing the Test case and bug tracking and so on. In developing a system, bias in the data collection may be a problem. Thus the area of the problem should be analyze properly and clearly to develop a successful system. FEASIBILITY ANALYSIS All Projects Are Feasible-given unlimited resources and infinite time. Unfortunately, the development of a computer-based system or product is more likely plagued by a scarcity of resources and difficult delivery dates. it is both necessary and prudent to evaluate the feasibility of the project at the earliest possible time. Feasibility and risk analysis are related in many ways. If project risk is great, the feasibility of producing the quality software is reduced. Feasibility analysis not warranted for system in which economic justification is obvious, technical risk is low, few legal problems are expected, and no reasonable alternatives exist. TECHNICAL ANALYSIS A Study of function performance and constraints that may affect the ability to achieve an acceptable system during technical analysis, the analyst evaluates the

technical merits of the system concept at the same time collecting additional information about performance, reliability, maintainability and product ability. Technical analysis begins with an assessment of the technical viability of the proposed system. The tools available for technical analysis are derived from mathematical modeling and optimization techniques, probability and statistics, queuing theory and control theory to name a few. ECONOMICAL ANALYSIS Economic analysis is the most frequently used method for evaluating the effectiveness of the proposed system. More commonly known as cost-benefit analysis, the procedure the costs for a proposed system and weights them against the tangible and intangible benefits of a system. If the benefits outweigh costs, then the system is designed and implemented. Otherwise further justification and alterations in the proposed system will have to be made if it is to have a chance of being approved.

PART-C MODULES :
Admin Module Testing Bug Tracking Report ADMIN MODULE

This Admin module is divided into two sub modules Login Module User Registration The login module is used for authenticating the existing user and the user registration module is used to take information like personal details, educational details, and technical skills and work experience from the users. After the user has registered

him he will be given a login name and password using which he can enter into his work space. It is helpful to set the security for the project. TESTING The Testing module is divided into three parts Project description module Test plan Test case THE PROJECT DESCRIPTION MODULE The information regarding the process of the project like, concept description, environment and the dead line are retrieved from the client along with the company details are stored into the database with the help of this module. TEST PLAN It is used to store the over all testing approaches like test plan identifier, scope, feature to be tested, environmental needs, schedule, test deliverables and approvals into the data base. TEST CASE It is made up of two modules Writing Test cases. Executing Test cases. Test case is a set of inputs, execution preconditions and expected outcome developed for a particular objective such as to exercise a particular program path or to verify compliance with a specific requirement. BUG TRACKING

By using this module we can maintain and track information regarding the bug, assigned to, status, priority, severity, detected by and detected date etc. REPORT It consists of two modules Total test report Total bug report By using the Total bug report we can get Daily bug report Weekly bug report Total bug report

PART-D HARDWARE CONFIGURATION Processor RAM Hard disk : : : Pentium IV 256 MB 40 GB

SOFTWARE CONFIGURATION Operating system Front End Tool Back End Tool Servers : : : : MS-Windows XP PHP MS SQL 2000 WAMP SERVER