Professional Documents
Culture Documents
PROJECT REPORT ON
Mr. A SRINIVAS
CERTIFICATE
This is to certify that the project work entitled BUG TRACKING SYSTEM that is being submitted by I.V.SURRENDRA VARUN KUMAR (06861A0530), NAGIREDDY JANARDANA RAO (06861A0559), A.HARI PRASAD GUPTA (06861A0501), S.SRIKANTH (06861A0580), D.PRASHANTH (06861A0523).In partial fulfillment of the requirement for the award Degree Bachelor of Technology in COPMUTER SCIENCE & ENGINEERING in MOTHER THERESSA COLLEGE OF ENGINEERING & TECHNOLOGY affiliated to Jawaharlal Nehru Technical University is a record of Bonafide work carried out by them under my guidance and supervision . The results are embodied in this project work have not been submitted to any University or Institute for the award of any degree or diploma.
KNOWLEDGEMENT
We wish to take this opportunity to express our deep gratitude to all the people who have extended their cooperation in various ways during our project work .It is our pleasure to acknowledge the help of all those individuals. We would like to thank our project guide Mr. K.HAREESH, SHRIKAR & SUNIL for his guidance and help throughout the development of this project work by providing us required information .Without his guidance , cooperation and encouragement, we couldnt learn many new things during our projects tenure. We express our profound gratitude to our guide Mr. A.SRINIVAS Assistant Professor, Computers Department for his support and encouragement in completing our project. We would like to thank Mr. B. VEERAPRATHAP for his encouragement and valuable guidance in bringing shape to this dissertation.
DECLARATION
We hereby declare that the project report titled BUG TRACKING SYSTEM is an original work done at INFOCUS SOFTWARE SOLUTIONS, HYDERABAD, submitted in partial fulfillment of the requirements for the award of the degree of Bachelor of Technology in Computer Science and Engineering from MOTHER THERESSA COLLEGE OF ENGINEERING & TECHNOLOGY (Affiliated to JAWAHARLAL NEHRU TECHNOLOGICAL UNIVERSITY, Hyderabad). We assure you that this project has not been submitted by any degree anywhere in any college or university so far.
I.V. SURENDRA VARUN KUMAR NAGIREDDY JANARDANA RAO A.HARI PRASAD GUPTA S.SRIKANTH D.PRASHANTH
CONTENTS Page-No
1. Abstract 2. Introduction Profile 2.1. Introduction to BUG TRACKING SYSTEM 2.1.1 Scope 2.1.2 Existing system with limitations 2.1.3 Proposed System Features 2.2. Introduction to Environment. 2.3 Definitions 2.4 Overview 2.5 System Requirements 2.6 Feasibility Study 3. Software Development Methodology 3.1 Software Requirement Specification 3.2 Problem Frame 3.3 Interface Requirements 3.4 Functional Requirements 3.5 Nonfunctional Requirements 4. Software Development Environment 4.1 About HTML 4.2 about PHP 4.3 About JavaScript 4.4 About My sql 4.5 Pseudo Code 25-43 22-25 7-8 9-22
Project Report Bug Tracking System 5. Overall Description About modules 5.1 Admin module 5.2 Test Manager 5.3 Test Engineer 5.4 Develop Manager 5.5 Develop Engineer 6. Behavioral Description 6.1 Data Flow 6.1.1 Data Flow Diagrams 6.1.2 Use-Case Documentation 6.2 Process Flow 6.2.1 System flow Chart 6.2.2 Activity Diagrams 7. Design 7.1 Sequence Diagrams 7.2 Collaboration Diagrams 7.3 E-R Diagrams 8. Database tables Documentation 9. Screens 10. System Testing 11. Conclusion 12. Bibliography
44-48
48-74
75-83
1.Abstract
6
A bug tracking system is a software application that is designed to help quality assurance and programmers keep track of reported software bugs in their work. It may be regarded as a sort of issue tracking system. Many bug-tracking systems, such as those used by most open source software projects, allow users to enter bug reports directly. Other systems are used only internally in a company or organization doing software development. Typically bug tracking systems are integrated with other software project management applications. Having a bug tracking system is extremely valuable in software development, and they are used extensively by companies developing software products. A major component of a bug tracking system is a database that records facts about known bugs. Facts may include the time a bug was reported, its severity, the erroneous program behavior, and details on how to reproduce the bug; as well as the identity of the person who reported it and any programmers who may be working on fixing it. Typical bug tracking systems support the concept of the life cycle for a bug which is tracked through status assigned to the bug. A bug tracking system should allow administrators to configure permissions based on status, move the bug to another status, or delete the bug. The system should also allow administrators to configure the bug statuses and to what status a bug in a particular status can be moved. Our project BUG TRACKING SYSTEM provides services to the employees, managers as well as Administrator of that particular Software Company. The primary objective of this system is to help the quality assurance and keep track of reported bugs in their work. Mainly the BUG TRACKING SYSTEM acts as a bridge between the Test Team Professionals and Develop Team Professionals. Administrator is responsible of performing various tasks like adding, removing an Employee, viewing status of an Employee and requests from Employees.
In a corporate environment, a bug-tracking system may be used to generate reports on the productivity of programmers at fixing bugs. However, this may sometimes yield inaccurate results
In the olden days the communication between the employees would have been done through emails to over come this problem we are developing this kind of applications to help the software professionals. Due to this, report generation becomes accurate and fast. On the whole our System benefits Software departments /Organizations. .
Software Constraints:
Backend Front End : My SQL, PHP. : HTML, CSS, JAVA SCRIPT.
Hardware Constraints
1. 1GB RAM
2. 1.44 Floppy Disk Drive
This volume presents the manner in which the software was developed and how the various problems are tackled at the different levels to convince the user. We hope that this package would prove to be an excellent environment for managing web sites.
2. INTRODUTION PROFILE
Manual way of handling seems to be impossible in these modern days of high speed. Issue / bug finder, generator, specialist are all located in different places making the timely solutions difficult. Keeping track of all these issue related activities is another big area where maintenance is tougher.
10
The proposed solution contains a simple intranet or Internet based website, which will be accessible to all the programmers participating in the development project. All these personnel will have to authenticate themselves to report any kind of problem aroused in developing the specified project. These problems will be carried to the concerned developer for solution. It also makes the administrator to administer these issues or bugs centrally to ensure these issues or bugs are answered in time by the concerned programmers.
Related issue details, but at the same time proper security is incorporated into the software enabling only the related developers can go to in depth details. And only these people can respond to those unanswered issues or bugs.
The centrally managed database makes the administration easy. It provides summarized information about the issues, bugs, and problems. It also provides standard bookmarks to find out related bug issues that logged developer. Bug Issue Management application also incorporates rigorous search engine to find out any kind of bug issue for its details.
Finally, it is planned in such a way that administration of the Bug Issue Management Application itself is in very easy and intuitive way giving the administrators an easy walk over it.
11
2.2.A.1 ADD EMPLOYEE This service enables the Admin to add the new employee details. And he/she can generate an employee serial no, and it sends to that particular employee what ever is created by him. He/she can also add the employees on the bases of their department. And also Admin create the user_id and password of the each and every employee and it send to their mail address. He/she can also view the employee details according to their department.
2.2.A.2 DELETE EMPLOYEE This service enables the Admin to delete the employee. He/she can also delete the employee based on their department. 2.2.A.3 MODIFY EMPLOYEE This service enables to the Admin to modify the employee details. He/she can also modify the employee based on their department. By using this scenario he/she can change or modify the details like addresses, expertise details, user_id, parent position, password, status of an employees etc ..
12
By using this service the administrator enables the whole requests of the current working employees those who want to make changes in their profile and then the administrator can update their profiles. 2.2.A.7 LOGOUT This service enables the Administrator to exit from the software.
13
2.2.B.1.Assign module:
Test manager assigns module to the test engineer.
2.2.B.2Notified bugs:
In this test manager able to view the bugs which are reported by test engineer.
2.2.B.3.Request to admin:
A request to admin regarding any queries or updates in the profile.
2.2.B.4.Logout:
This service enables to exit from the application.
C.TEST ENGINEER:
Test engineer performs the different test methods on the given module and bug reports to the test manager if any and he also receives the tested module from the develop engineer to perform retest and if he find and bugs in the given module he is going to perform the retest on it else closes the module.
2.2.C.1.Report bugs:
Bug reporting is the main functionality of test engineer where he is going to report the bugs details to the test manager.
14
2.2.C.3.Request to admin:
A request to admin regarding any queries or updates in the profile.
2.2.C.4.Logout:
This service enables to exit from the application.
D.DEVELOP MANAGER:
The test manager assigns the notified bugs to develop manager and the work of the develop manager is assigns the particular module to develop engineer based on the priority of bugs.
2.2.D.1.Assign bugs:
Develop manager assigns the bugs based on the category of the bugs.For instance, if a bug is raised in design section then the develop manager assigns to design professional.
2.2.D.2.Request to admin:
A request to admin regarding any queries or updates in the profile.
2.2.D.3.Logout:
This service enables to exit from the application.
15
2.2.E.2.Request to admin:
A request to admin regarding any queries or updates in the profile.
2.2.E.3.Logout:
This service enables to exit from the application
16
2.3 Definitions:
Definition
BUG TRACKING SYSTEM By the name it self it can provide the services to software Professionals. By using this software we can develop a product with high quality. It is more useful in the present software organizations or companies. The main use of this particular software is to used for debugging purpose. Today most of the software companies using this kind of applications to develop a good quality products with less amount of money. BUG TRACKING SYSTEM is used to keep track of reported bug in their work. It also keep track of product development process to provide quality assurance. It act as bridge between Test Professionals & Development Professionals.
2.4 Overview
The Project BUG TRACKING SYSTEM over all deals with the tracking of bugs. The bug tracking system supports the concept of bug life cycle. The system has to manage the assignment of bug, submission of a bug and resolution of bug. Mainly the BUG TRACKING SYSTEM acts as a bridge between the test team and development team. Typically a bug tracking system begin when ever any vendor gives any project to the administrator then the admin is going to add the particular project in to their database and divides the project in to different type of modules and assign the modules to their respective team members to resolve the bugs. The privileges of administrator is adding, removing an Employee, view status of an Employee, Edit profile, View requests from employees and Add Project. The privileges of Test Manager is assign module and notified bugs. The privileges of Test Engineer is report bugs and re-test of bugs. 17
18
Server side
Minimum : 120GB Hard Disk Pentium : P-IV Processor RAM : 2GB Windows Operating System with Apache preloaded.
Client side
Minimum: 120GB Hard Disk Pentium: P-IV Processor RAM : 2GB
19
SOFTWARES
Software is a set of programs to do a particular task. Software is an essential requirement of computer systems. The kind of software used in this project is: Operating System: Language Database Network Type of server Browser : : : : Red Hat Linux9
20
21
User Interfaces
The constraints that the user interfaces must adhere here are:
22
Communication Interfaces
Server System should have a Web server, which supports PHP as server scripting language and My SQL as database. Explorer. There should be good Internet Connection. The Proposed System uses Hyper Text Transfer Protocol (HTTP) and File Client System can be of any system with normal Operating System and Internet
FUNCTIONAL REQUIREMENTS This section analyzes various angles of the functionality to be developed. You do not need to use each type of analysis for the entire system. Select only that analysis that best allow you to complete your understanding of the requirements. Feature Analysis Add (), View (), Update () functions are used in this system Add () function is used to add new information. View () function is used to view the existing details. Update () function is used to make any modifications on the existing target or incentive details. Formal Analysis In this section, logical analysis further refines the understanding of the features. The logic addresses properties of the use-cases or of the underlying databases. It can cover the pre- and the information,
23
Software Requirement Backend Requirement: MY SQL Front-end Requirement: PHP, HTML, JAVASCRIPT,CSS. Only the administration department uses this system.
To access this system, the user is provided with a login entry. If the employee is not present
others in the same department can access the system with the login entry provided and hence the system is safe and reliable. Security Requirements To access this system, the user is provided with a login entry. If the user is not present others in the same department can access the system with the login entry provided and hence the system is secure. Software Quality Attributes This system possess the quality characteristics that will be important to either the employee ,Administrator or Manager include adaptability, availability, accuracy, flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability
24
REFERENCES: For preparing the Software Requirement Specification the following documents are referred. Feasibility system study report for Collect rate department as prepared by IEG.
25
PHP's features
26
There are three main areas where PHP scripts are used. Server-side scripting
This is the most traditional and main target field for PHP. You need three things to make this work: The PHP parser (CGI or server module) A web server A web browser
You need to run the web server, with a connected PHP installation. You can access the PHP program output with a web browser, viewing the PHP page through the server.
27
Smarty
Smarty is a template engine for PHP. It facilitates a manageable way to separate application logic and content from its representation. This is best described in a situation where the programmer and the template designer play different roles. They are passed into Smarty by the application, and then the template designer edits the templates and uses a combination of HTML tags and template tags to format the presentation of these elements (HTML tables, background colors, font sizes, style sheets, etc.) If the programmer needs to change the way the article content is retrieved (a change in application logic.) This change does not affect the template designer; the content will still arrive in the template exactly the same. Likewise, if the template designer wants to completely redesign the templates, this requires no changes to the application logic. Therefore, the programmer can make changes to the application logic without the need to restructure templates, and the template designer can make changes to templates without breaking application logic.
28
Requirements
Smarty requires a web server running PHP 4.0.6 or later.
29
complex queries foreign keys triggers views transactional integrity multiversion concurrency control Additionally, My SQL can be extended by the user in many ways: data types functions operators aggregate functions index methods procedural languages
By adding new
31
Advantages
My SQL offers many advantages for your company or business over other database systems.
Immunity to over-deployment
Over-deployment is what some proprietary database vendors regard as their #1 license compliance problem. With My SQL, no-one can sue you for breaking licensing agreements, as there is no associated licensing cost for the software. This has several additional advantages: More profitable business models with wide-scale deployment. No possibility of being audited for license compliance at any stage. Flexibility to do concept research and trial deployments without needing to include additional licensing costs.
32
Cross platform
My SQL is available for almost every brand of Unix (34 platforms with the latest stable release), and Windows compatibility is available via the Cygwin framework. Native Windows compatibility is also available with version 8.0 and above.
33
echo
"<form
name=\"login\"
method=\"post\"
action=\"act_login.php\"
onSubmit=\"return login_validation();\"> <table width=\"500\" border=\"0\" id=\"tbl\"> <tr> <th colspan=\"2\">LOGIN</th> </tr> <tr> <td>Employee Id: </td> <td><input type=\"text\" name=\"emp_id\" /></td> </tr> <tr> <td>Password:</td> <td><input type=\"password\" name=\"pass\" /></td> </tr> <tr> <td> </td> <td> </td> </tr> <tr>
34
35
$FIRST_NAME=$_POST['f_name']; $LAST_NAME=$_POST['l_name']; $ADDRESS1=$_POST['add1']; $ADDRESS2=$_POST['add2']; $CITY=$_POST['city']; $STATE=$_POST['state']; $ZIP=$_POST['zip']; $MAIL=$_POST['e_mail']; $PHN0=$_POST['ph_no']; $JOIN_DATE=$_POST['join_date']; 36
into
employee_info
values('','$FIRST_NAME','$LAST_NAME','$ADDRESS1','$ADDRESS2','$CITY','$STATE','$Z $PHN0,'$JOIN_DATE','$STATUS','$EXPERTISE','$PARENT_POS','','$PASS','$POSITION','e mp','','','','','')"; $res=mysql_query($stmt); $data=mysql_insert_id(); $sql="select * from employee_info where emp_id=$data"; $res=mysql_query($sql); $row=mysql_fetch_array($res); echo "<table width=\"500\"> <tr> <th colspan=\"2\">Successfully Inserted</td> </tr> <tr class=\"red\"> <td width=\"250\">Employee Id:</td> <td width=\"250\">".$row['emp_id']."</td> </tr>
37
38
39
into
bug_track
values('',
$module_id,'$desc','$title','$priority','$raised_by','$raised_date','','$estimated_end_date','open','','',''
40
into
test_work_assign
values('$module_id','$module_name','$assigned_date','$estimated_end_date','','$assigned_to','ope
$stmt="select * from test_work_assign where module_id=$data"; $res=mysql_query($stmt); $row=mysql_fetch_array($res); echo "<table width=\"500\"> <tr> <th colspan=\"2\">Successfully Inserted</td> </tr> <tr class=\"red\"> <td width=\"250\">Project Id:</td> <td width=\"250\">".$row['project_id']."</td>
41
42
?>
43
5.1. ADMINISTRATOR
By using this Bug Tracking System facilitates to enroll the details of the newly joined employee into the database and maintains employees details up to date. The Administrator store and retrieve the Departmental details when required. Administrator can update the details if he wants to do so. He/she will do all these things. For this purpose he/she needs to login to the system by entering user_id and password. The employee can view all the details as per the requirement i.e., could generate reports of those details. And also he/she can do some various tasks. Some of those tasks are as shown below.
5.A.1 ADD EMPLOYEE This service enables the Admin to add the new employee details. And he/she can generate an employee serial no, and it sends to that particular employee what ever is created by him. He/she can also add the employees on the bases of their department. And also Admin create the user_id and password of the each and every employee and it send to their mail address. He/she can also view the employee details according to their department.
5.A.2 DELETE EMPLOYEE This service enables the Admin to delete the employee. He/she can also delete the employee based on their department. 5.A.3 MODIFY EMPLOYEE This service enables to the Admin to modify the employee details. He/she can also modify the employee based on their department. By using this scenario he/she can change or modify the
44
By using this service the administrator enables the whole requests of the current working employees those who want to make changes in their profile and then the administrator can update their profiles. 5.A.7 LOGOUT This service enables the Administrator to exit from the software.
45
5.B.1.Assign module:
Test manager assigns module to the test engineer.
5.B.2Notified bugs:
In this test manager able to view the bugs which are reported by test engineer
5.B.3.Request to admin:
A request to admin regarding any queries or updates in the profile.
5.B.4.Logout:
This service enables to exit from the application.
5.3.TEST ENGINEER:
Test engineer performs the different test methods on the given module and bug reports to the test manager if any and he also receives the tested module from the develop engineer to perform retest and if he find and bugs in the given module he is going to perform the retest on it else closes the module.
5.C.1.Report bugs:
Bug reporting is the main functionality of test engineer where he is going to report the bugs details to the test manager.
46
5.C.3.Request to admin:
A request to admin regarding any queries or updates in the profile.
5.C.4.Logout:
5.4.DEVELOP MANAGER:
The test manager assigns the notified bugs to develop manager and the work of the develop manager is assigns the particular module to develop engineer based on the priority of bugs.
5.D.1.Assign bugs:
Develop manager assigns the bugs based on the category of the bugs.For instance, if a bug is raised in design section then the develop manager assigns to design professional.
5.D.2.Request to admin:
A request to admin regarding any queries or updates in the profile.
5.D.3.Logout:
This service enables to exit from the application.
47
5.E.1.Assigned bugs:
In this section the develop engineer is able to view all the assigned bugs to him.
5.E.2.Request to admin:
A request to admin regarding any queries or updates in the profile.
5.E.3.Logout:
This service enables to exit from the application.
6.1.1 DATA FLOW DIAGRAMS A data flow diagram is graphical tool used to describe and analyze movement of data through a system. These are the central tool and the basis from which the other components are developed. The transformation of data from input to output, through processed, may be described logically and independently of physical components associated with the system. These are known as the logical data flow diagrams. The physical data flow diagrams show the actual implements and movement of data between people, departments and workstations. A full description of a system actually consists of a set of data flow diagrams. Using two familiar notations Yourdon, Gane and Sarson notation develops the data flow diagrams. Each component in a DFD is labeled with a descriptive name. Process is further identified with a number that will be used for identification purpose. The development of DFDs is done in several levels. Each process in lower level diagrams can be broken down into a more detailed DFD in the next level. The lop-level diagram is often called context diagram. It consists a single process bit, which plays vital role in studying the current system. The process in the context level diagram is exploded into other process at the first level DFD. The idea behind the explosion of a process into more process is that understanding at one level of detail is exploded into greater detail at the next level. This is done until further explosion is necessary and an adequate amount of detail is described for analyst to understand the process. Larry Constantine first developed the DFD as a way of expressing system requirements in a graphical from, this lead to the modular design. A DFD is also known as a bubble Chart has the purpose of clarifying system requirements and identifying major transformations that will become programs in system design. So it is the starting point of the design to the lowest level of detail. A DFD consists of a series of bubbles joined by data flows in the system. DFD SYMBOLS In the DFD, there are four symbols 1. A square defines a source (originator) or destination of system data
49
Data flow
Data Store
CONSTRUCTING A DFD Several rules of thumb are used in drawing DFDs: 1. Process should be named and numbered for an easy reference. representative of the process. 2. The direction of flow is from top to bottom and from left to right. Data traditionally flow from source to the destination although they may flow back to the source. One way to indicate this is to draw long flow line back to a source. An alternative way is to repeat the source symbol as a destination. Since it is used more than once in the DFD it is marked with a short diagonal. Each name should be
50
51
2. CURRENT LOGICAL The physical aspects at the system are removed as mush as possible so that the current system is reduced to its essence to the data and the processors that transforms them regardless of actual physical form. 3. NEW LOGICAL This is exactly like a current logical model if the user were completely happy with he user were completely happy with the functionality of the current system but had problems with how it was implemented typically through the new logical model will differ from current logical model while having additional functions, absolute function removal and inefficient flows recognized. 4. NEW PHYSICAL The new physical represents only the physical implementation of the new system.
RULES GOVERNING THE DFDS PROCESS 1) No process can have only outputs. 2) No process can have only inputs. If an object has only inputs than it must be a sink. 3) A process has a verb phrase label. DATA STORE 1) Data cannot move directly from one data store to another data store, a process must move data.
52
53
54
55
56
57
58
59
Use case activities done by the Test manager Login High Home Medium Assign modules Medium Notified bugs Medium Request to admin Medium View all Medium Log out High Use case activities done by the Test engineer Login High Home Medium Report bugs Medium Retest bugs Medium Request to admin Medium View all Medium Log out High
Use case activities done by the Develop Manager Login High Stable home Medium Stable Assign bugs Medium Stable Request to admin Medium Stable View all Medium Stable Logout High Stable
60
Use case activities done by the Develop Engineer 5.0 5.1 5.2 5.3 5.4 5.5 Login home Assigned bugs Request to admin View all Logout High Medium Medium Medium Medium High Stable Stable Stable Stable Stable Stable Verifiable Verifiable Verifiable Verifiable Verifiable Verifiable
Use-Cases Specifications:
Use-Case ID:1.0,2.0,3.0, Use Case Name: 4.0,5.0 Description: Preconditions:
Login
The user who enters the system is provided with a login id in order to access the services of the system. Not applicable. The administrator who is the user of the system logins into the system and monitors the details regarding employees and targets assigned to various district officers and also generates reports regarding these details. Admin can view, add and update the details of all the employees and target reports. All the updating made regarding the details of all the employees and the targets are to be updated and stored in the database. Whenever the user wants to access the services provided. 61
Post conditions:
Frequency of Use:
Use Case Name: Add Employee In this use-case the entire Employee should be added or created by the Administrator and he also maintained the reports. User-Id should be valid user-id. When adding new employee, System checks whether the admin login is having that provisions or not? ID should be unique. New work assignment details should be updated in the database. For every new Employee details will be added once and can be changed later. Adding new employee details No other alternative exists for this use-case. Login use-case. No additional Requirement is needed for managing Employee details.
Post conditions: Frequency of Use: Normal Course of Events: Alternative Courses: Includes: Associated Requirements:
62
63
Project Report Bug Tracking System Use-Case ID:1.3 Use Case Name: Edit Employee
Description: Preconditions: In this use-case the Employee Details should be Modified by the Admin and maintained the database. User-Id should be valid user. When editing employee details, System checks whether the user login is Post conditions: Frequency of Use: Normal Course of Events: Alternative Courses: Exceptions: Includes: Associated Requirements: having that admin are not? Changed details should be updated in the database. For every updated detail will be added once and can be changed later. Updated Details details are Forwarding to concern officer/employee. No other alternative exists for this use-case. Login use-case. No additional Requirement is needed for managing Editing Employee details. In this use-case all the Employee Details should be maintained.
65
Use case Documentation Regarding to the developers as shown in the following Use-Case ID: 2.4, 3.4, 4.3, 5.3 Description: Preconditions: Post conditions: Frequency of Use: Normal Course of Events: Alternative Courses: Includes: Associated Requirements:
66
Use-Case ID: 1.3 Description: Preconditions: Post conditions: Frequency of Use: Normal Course of Events:
67
68
Activity Diagram of the Test Manager in This System is as shown in the following following figure.
69
Activity Diagram of the Test Engineer in This System is as shown in the following figure
70
71
72
73
74
75
76
Sequence Diagram
following
78
Collaboration diagram
following
79
Collaboration Diagram
following
80
PROJECT_INFO
Project_id(PK) Project_name Start_date End_date Client_name Emp_id(FK) Atbt_02 Atbt_03 Atbt_04 Atbt_05 Atbt_06
BUG_TRACK TEST_WORK_ASSIGN
Bug_id(PK) Module_id(FK) Desc Title Priority Raised_by Raised_date Assigned_to Estimated_end_date Status End_date Atbt_01 Atbt_02 Atbt_03 Atbt_04 Atbt_05
REQUEST_DETAILS
Emp_id(FK) Last_name Description Atb_01 Atb_02 Atb_03 Atb_04 Atb_05
Module_id(PK) Module_name Assigned_date Estimated_end_date End_date Assigned_to Status Project_id(FK) Project_name Atbt_03 Atbt_04
82
DATABASE TABLES
85
86
9 screens
HOME PAGE
87
88
89
ADMIN PAGE
90
ADD PROJECT
91
ADD EMPLOYEE
92
DELETE EMPLOYEE
93
EDIT STATUS
94
EDIT PROFILE
95
TEAM MANAGER
96
ASSIGN MODULE
97
NOTIFED BUGS
98
TEST ENGINEER
99
REPORT BUGS
100
RETEST BUGS
101
DEVELOP MANAGER
102
ASSIGN BUGS
103
DEVELOP ENGINEER
104
ASSIGNED BUGS
10.PROJECT TESTING
1) COMPILATION TEST:
105
Project Report Bug Tracking System It was a good idea to do our stress testing early on, because it gave us time to fix some of the unexpected deadlocks and stability problems that only occurred when components were exposed to very high transaction volumes. 2) EXECUTION TEST:
This program was successfully loaded and executed. Because of good programming there were no execution error.
3) OUTPUT TEST:
The successful output screens are placed in the output screens section.
11.CONCLUSION
106
Project Report Bug Tracking System The project has been appreciated by all the users in the organization.
It is easy to use, since it uses the GUI provided in the user dialog.
User friendly screens are provided. The usage of software increases the efficiency, decreases the effort. It has been efficiently employed as a Site management mechanism. It has been thoroughly tested and implemented.
12. BIBLIOGRAPHY
SOFTWARE ENGINEERING
107
Project Report Bug Tracking System By Roger.S. Pressman SQL FOR PROFESSIONALS By Jain
108