Sample report

1
LIST OF FIGURES
Name of Diagrams indexing
1: BTS-TOP LEVEL DIAGRAM 14
2: LOW LEVEL DIAGRAM-LOGIN 15
3: LOW LEVEL DIAGRAM-PRODUCTS 15
4: LOW LEVEL DIAGRAM-BUGS 16
5: LOW LEVEL DIAGRAM-TRACKING 17
6: LOW LEVEL DIAGRAM-VIEW 18
7: LOW LEVEL DIAGRAM-SEARCH 18
8: LOW LEVEL DIAGRAM-LOGOUT 19
9: E-R DIAGRAM 21

2
Table of Contents
TOPIC Page no
DECLARATION i
COMPANY CERTIFICATE iii
ACKNOWLEDGEMENT iv
ABSTRACT v
CHAPTER-1 INTRODUCTION 4
1.1Objective of Industrial Training Program 4
1.2 Scope of Industrial Training Program 4
1.3 Duration 4
1.4 Importance of Industrial Training 4
1.5 Benefits Derived from Training 4
1.6 Role in Industrial Training 4
1.7 Objective of the Report 5
CHAPTER-2 THE TRAINING ORGANIZATION 6
2.1 The Training Organization 6
2.2 The Training Environment 6
CHAPTER-3 FORMAL TRAINING 7
3.1 Classroom Training Environment 7
CHAPTER-4 INDUSTRIAL TRAINING 8
4.1 Objective 8
4.2 Analysis 8
4.2.1 Product Functions 9
4.2.2 SDLC Model Used 10
4.2.3 System study and Problem Formulation 10

3
4.2.4 Feasibility Study 11
4.2.4.1 Need for Feasibility Study 11
4.2.5 Software Requirements Specification 12
4.3 Designing 13
4.3.1Data Flow Diagram 13
4.3.2 ER DIAGRAMS 20
4.4 Testing 22
4.4.1 Introduction 22
4.5 Highlights of Training Exposure 24
4.5.1 Outcome-Screenshots 24
CHAPTER-5 CONCLUSION 31
5.1 Training Report Conclusion 31
5.2 Learning and frequently asked questions 31
CHAPTER-6 LIMITATIONS AND FUTURE ENHANCEMENTS 32
6.1Limitations of the system: 32
6.2Future Enhancements: 32
BIBLIOGRAPHY 33

4
CHAPTER-1
INTRODUCTION
1.1Objective of Industrial Training Program
The purpose of Bug Tracking for improving software reliability is to provide better
service to the administrator or useful for applications developed in an organization.
1.2 Scope of Industrial Training Program
The Bug Tracking for Improving Software Reliability is a web based application that
can be accessed throughout the organization. This system can be used for logging
bugs against an application/module, assigning bugs to team members and tracking the
bugs to resolution. There are features like email notifications, user maintenance, user
access control, report generators etc in this system.
1.3 Duration
The duration of the training was 4 weeks from 22/06/2015 to 22/07/2015.
1.4 Importance of Industrial Training
The importance of this training program is immense for me as a BTech student, as it
helped me to give a real life experience of applying the knowledge learnt and
develops web application.
1.5 Benefits Derived from Training
This program honed my skills in the area of web development and helped learn how
to use java language, HTML, collectively to develop web based applications and how
to implement database connectivity in java applications.
1.6 Role in Industrial Training
My role in this training program was to develop a website on ‘Technical Bug
Detecting System’ which involved: analyzing the system to be designed, designing
the diagrams and database schema, designing of web pages using HTML making
database using ORACLE doing database connectivity.

5
1.7 Objective of the Report
The objective of the report is to briefly describe the various aspects of the Industrial
Training Program.

6
CHAPTER-2
THE TRAINING ORGANIZATION
2.1 The Training Organization
Imperial impact assists blue chip companies globally in their look out for IT
professionals to join them and seamlessly integrate with their objectives in least time
and efforts. Imperial Impact offers its premium services, as it firmly believes that
1. Client barters fees for the saving of their time, efforts and resource.
2. Candidate barters information for better career prospects.
2.2 The Training Environment
Since now, there has been advancement in the way of studying, IMPERIAL IMPACT
provides online content, assessments with virtual labs which in turn allow the student
to learn at his own pace and time.

7
CHAPTER-3
FORMAL TRAINING
3.1 Classroom Training Environment
The classroom at IMPERIAL IMPACT is equipped with computers for every student
and every concept is taught with the help of projector thus helping the students to
learn through demo programs in a better way.
Technologies learnt:
1) Servlet
2) JSP
3) HTML
4) JDBC
Connecting java application with ORACLE database
1) Servlet: The servlet is a Java programming language class used to extend the
capabilities of a server. Although servlets can respond to any types of requests, they
are commonly used to extend the applications hosted by web servers.
2) JSP: Java Server Pages (JSP) is a technology that helps software developers create
dynamically generated web pages based on HTML, XML, or other document types.
It was released in 1999 by Sun Microsystems.
3) HTML: HTML or Hypertext Markup Language is the standard markup language
used to create web pages.

8
CHAPTER-4
INDUSTRIAL TRAINING
4.1 Objective
To develop a web based application on Technical Bug Detection System.The purpose
of Bug Tracking for improving software reliability is to provide better service to the
administrator or useful for applications developed in an organization.
4.2 Analysis
Definition, Acronyms, Abbreviations
Bug - A software bug (or just "bug") is an error, flaw, mistake, failure, or fault in a
computer program that prevents it from behaving as intended (e.g., producing an
incorrect result). Most bugs arise from mistakes and errors made by people in either a
program's source code or its design, and a few are caused by compilers producing
incorrect code.
Overview
Bug tracking is the process of reporting and tracking the progress of bugs from
discovery through to resolution, where a bug is defined as a deviation from
requirements. Other terminology frequently used to describe this process include
 problem tracking
 change management
 fault management
 trouble tickets
Bug tracking systems are most commonly used in the coding and testing phases of the
software development process. However, tracking systems can in fact be used for
many other purposes such as general issue tracking, simple task lists, help desk
situations or contact management, where the focus is on the tracking aspect rather
than what is being tracked. Even in software development, tracking systems are quite
often not limited to simply tracking bugs, but extended to track feature requests or
enhancements as well as enquiries.

9
4.2.1 Product Functions
It has following modules:
Admin: This module has the entire access to all other modules, admin creates the
project and assigning the projects to the created manager, adding members to the
managers, assigning bugs based on the priority. Can update the manager, members
and access to the particular project data. Generating reports based on the managers
report submission.
Manager: Manager has the full access to the particular project assigned by the admin
and controls the team members’ access to the bugs assigned. Has the permission to
generate the reports and update the information of team members and adding
members to the project.
Developer: Can access the task or bug assigned by the manager, view assigned
projects and resolving the assigned bug. Developer can view the bugs list assigned by
the manager.
Tester: Tester can access to the projects or bugs assigned by the manager, can view
the assigned projects and can add a new bug to the list and send the bug back to the
manager. Tester can login to the system and access the assigned projects list.
Reports: Both Admin and Manager can access this module and generate the reports
based on the requirements.
Functions
 Admin
 Manger
 Developer
 Tester
 Reports

10
4.2.2 SDLC Model Used
The Software Development Life Cycle Model used for this project is The
“ITERATIVE WATERFALL MODEL”. The Waterfall Model is used because:
1) It provides systematic & sequential Approach.
2) It is well suited for routine type of projects like ‘online banking’ where
requirements are well understood.
3) Explicit recognition of phases is there while using this model.
4.2.3 System study and Problem Formulation
4.2.3.1 Existing System
The existing system consists of entering the details in the Microsoft Excel Sheets for
the storing of the data. When a manager needs information of the employee he
searches for the specified file in the file system. He opens the file and takes the
information. Report Generation done manually by copying the content of the different
files into another file. The Manually generated report was then printed.
Limitations in Existing System
 Information retrieval is a very big process.
 Lack of organization of the files may porn to information loss due to
accidental deletion of files.
 No security because the files are visible to the users.
 Report generation will be a big task.
4.2.3.2 Proposed System
The Proposed system is a browser which is completely related to online system,
which provides the centralized database. It stores bugs data and description of the
particular bug data. It can also create Excel reports and PDF documents based on the
information in its database.
Advantages over Existing System
 The performance is increased due to well designed database.
 Security is increased
 Time saving in report generation
 Easy to update the details

11
4.2.4 Feasibility Study
4.2.4.1 Need for Feasibility Study
Feasibility study is mandatory for every project & is carried out to know if the system
proposed is:
1) Possible 2) Affordable 3) Acceptable
By the end of feasibility study, the team furnishes a document that holds the different
specific recommendations for the candidate system.
4.2.4.2Economic Feasibility
Economic feasibility attempts 2 weigh the costs of developing and implementing a
new system, against the benefits that would accrue from having the new system in
place. This feasibility study gives the top management the economic justification for
the new system.
A simple economic analysis which gives the actual comparison of costs and benare
much more meaningful in this case. In addition, this proves to be a useful point of
reference to compare actual costs as the project progresses. There could be various
types of intangible benefits on account of automation. These could include increased
customer satisfaction, improvement in product quality better decision making
timeliness of information, expediting activities, improved accuracy of operations,
better documentation and record keeping, faster retrieval of information, better
employee morale.
4.2.4.3 Operational Feasibility
Proposed project is beneficial only if it can be turned into information systems that
will meet the organizations operating requirements. Simply stated, this test of
feasibility asks if the system will work when it is developed and installed. Are there
major barriers to Implementation? Here are questions that will help test the
operational feasibility of a project:
Is there sufficient support for the project from management from users? If the current
system is well liked and used to the extent that persons will not be able to see reasons
for change, there may be resistance.

12
Are the current business methods acceptable to the user? If they are not, Users may
welcome a change that will bring about a more operational and useful systems.
Have the user been involved in the planning and development of the project?
Early involvement reduces the chances of resistance to the system and in general and
increases the likelihood of successful project.
Since the proposed system was to help reduce the hardships encountered. In the
existing manual system, the new system was considered to be operational feasible.
4.2.4.4 Technical Feasibility
Evaluating the technical feasibility is the trickiest part of a feasibility study. This is
because, .at this point in time, not too many detailed design of the system, making it
difficult to access issues like performance, costs on (on account of the kind of
technology to be deployed) etc. A number of issues have to be considered while doing
a technical analysis.
Understand the different technologies involved in the proposed system before
commencing the project we have to be very clear about what are the technologies that
are to be required for the development of the new system. Find out whether the
organization currently possesses the required technologies. Is the required technology
available with the organization?
4.2.5 Software Requirements Specification
Front End
The front end is an interface between the user and the back end. The front is an
abstraction, simplifying the underlying component by providing a user-friendly
interface.
Front End: . HTML, Javascript
Back End
A "back-end" application or program serves indirectly in support of the front-end
services, usually by being closer to the required resource or having the capability to

13
communicate with the required resource. A typical setup for a backend is a web
server, an application and a database.
Database: ORACLE
Technology: JSP
4.2.5.1 Hardware Requirements
Processor : Intel Core i3
Hard Disk : 500 GB
RAM : 2 GB
4.2.5.2 Software tools used:
Operating System : Windows 7/8
User Interface : HTML, CSS
Client-side Scripting : JavaScript
Programming Language : Java
Web Applications : JDBC, Servlet, JSP
Database : Oracle-10g
4.3 Designing
4.3.1Data Flow Diagram
Data Flow Diagramming is a means of representing a system at any level of
detail with a graphic network of symbols showing data flows, data stores,
data processes, and data sources/destination.
The data flow diagram is analogous to a road map. It is a network model of all
possibilities with different detail shown on different hierarchical levels.
This processes of representing different details level is called “levelling” or
“Partitioning” by some data flow diagram advocates. Like a road map, there
is no starting point or stop point, no time or timing, or steps to get
somewhere.

14
We just know that the data path must exist because at some point it will be needed. A
road map shows all existing or planned roads because the road is needed. Data Flow
Diagram (DFD) uses a number of symbols to represent the systems. Data Flow
Diagram also known as ‘Bubble Chart’ is used to clarify system requirements and
identifying the major transformations that will become programs in system design. So
it is the starting point of the design phase that functionally decomposes the
requirements specifications down to the level of details.
1: BTS-TOP LEVEL DIAGRAM
BTS - TOP LEVEL DIAGRAM
Bug Tracking
System
Programmer
Administrator
Database

15
2: LOW LEVEL DIAGRAM-LOGIN
3: LOW LEVEL DIAGRAM-PRODUCTS
LOW LEVEL DIAGRAM - LOGIN
User
1.1
User Details
1.2
Validate
Admin User
Programmer
tbl_Authentication
LOW LEVEL DIAGRAM - PRODUCTS
User
tbl_Product_Details
2.1
Product List
2.2
Details
2.3
Version
2.6
Users
tbl_Product_Users
2.4
Add / Modify
2.5
Delete
2.7
Add/ Modify
2.8
Delete
tbl_Product_Details
tbl_Product_Users

16
4: LOW LEVEL DIAGRAM-BUGS
LOW LEVEL DIAGRAM - BUGS
User
2
Product List
tbl_Product_Details
3.1
Bugs List
3.2
Bug History
3.2
Bug Assigned
3.3
File
Attatchments
tbl_Bug_Details
3.4
Add/Modiy
3.5
Delete
3.6
Add/Modiy
3.7
Delete
3.8
Add/Modiy
3.9
Delete
tbl_Bug_History tbl_Bug_Assign tbl_File_Attatchment

17
5: LOW LEVEL DIAGRAM-TRACKING
LOW LEVEL DIAGRAM - TRACKING
User
4.1
Bug Details
tbl_Bug_Details
4.2
Track
Hierarchy
4.2
Track
Resources
4.3
Track
Resolution
4.4
Add / Modiy
4.5
Delete
4.6
Add / Modiy
4.7
Delete
4.8
Add / Modiy
4.9
Delete
tbl_Bug_Resources tbl_Bug_Resolution
tbl_Bug_Hierarchy

18
6: LOW LEVEL DIAGRAM-VIEW
7: LOW LEVEL DIAGRAM-SEARCH
User
LOW LEVEL DIAGRAM - VIEW
5.1
Products
5.3
Bug Hierarchy
5.2
Product User
Hierarchy
tbl_Product_Details
tbl_Product_Users tbl_Bug_Details
LOW LEVEL DIAGRAM - SEARCH
User
6.1
Search Criteria
6.2
Build Query
6.3
Execute Query Results

19
8: LOW LEVEL DIAGRAM-LOGOUT
LOW LEVEL DIAGRAM - LOGOUT
User
8.1
Close Session
8.2
Redirect Home
Page

20
4.3.2 ER DIAGRAMS
4.3.2.1 Definition
An entity-relationship(ER) diagram is a specialized graphic that
illustrates the interrelationships between entities in a database. ER diagram
often use symbols to represent three types of information. Boxes are
commonly used to represent entities. Diamonds are normally used to
represent relationships and ovals are used to represent attributes.
4.3.2.2 Entity Relationship Diagram
This diagramming technique is used to visually present a database schema or
data model and original proposed by Chen in 1970. There are many different
data modelling notations, some are very similar to UML class diagrams.
However, the notation used here is slightly different.
The database schema for this system is shown. The table object has been left out of
the diagram because the table management feature set had been dropped from the
requirement before this stage of the design process.

21
9:E-R DIAGRAM
hasTbl_bug_details Tbl_product_details
contains
has
maintains
Tbl_bug_resourcesTbl_file_attachments
Tbl_bug_histor
y
historyid
fieldid
productid
1
m
1 m
m
m
1 1
bugid

22
4.4 Testing
Software Testing is the process used to help identify the correctness, completeness,
security, and quality of developed computer software. Testing is a process of technical
investigation, performed on behalf of stakeholders, that is intended to reveal quality-
related information about the product with respect to the context in which it is
intended to operate. This includes, but is not limited to, the process of executing a
program or application with the intent of finding errors. Quality is not an absolute; it
is value to some person. With that in mind, testing can never completely establish the
correctness of arbitrary computer software; testing furnishes a criticism or comparison
that compares the state and behavior of the product against a specification. An
important point is that software testing should be distinguished from the separate
discipline of Software Quality Assurance (SQA), which encompasses all business
process areas, not just testing.
There are many approaches to software testing, but effective testing of complex
products is essentially a process of investigation, not merely a matter of creating and
following routine procedure. One definition of testing is "the process of questioning a
product in order to evaluate it", where the "questions" are operations the tester
attempts to execute with the product, and the product answers with its behavior in
reaction to the probing of the tester[citation needed]. Although most of the intellectual
processes of testing are nearly identical to that of review or inspection, the word
testing is connoted to mean the dynamic analysis of the product—putting the product
through its paces. Some of the common quality attributes include capability,
reliability, efficiency, portability, maintainability, compatibility and usability. A good
test is sometimes described as one which reveals an error; however, more recent
thinking suggests that a good test is one which reveals information of interest to
someone who matters within the project community.
4.4.1 Introduction
In general, software engineers distinguish software faults from software failures. In
case of a failure, the software does not do what the user expects. A fault is a
programming error that may or may not actually manifest as a failure. A fault can also
be described as an error in the correctness of the semantic of a computer program. A
fault will become a failure if the exact computation conditions are met, one of them

23
being that the faulty portion of computer software executes on the CPU. A fault can
also turn into a failure when the software is ported to a different hardware platform or
a different compiler, or when the software gets extended. Software testing is the
technical investigation of the product under test to provide stakeholders with quality
related information.
Software testing may be viewed as a sub-field of Software Quality Assurance but
typically exists independently (and there may be no SQA areas in some companies).
In SQA, software process specialists and auditors take a broader view on software and
its development. They examine and change the software engineering process itself to
reduce the amount of faults that end up in the code or deliver faster.
Regardless of the methods used or level of formality involved the desired result of
testing is a level of confidence in the software so that the organization is confident
that the software has an acceptable defect rate. What constitutes an acceptable defect
rate depends on the nature of the software. An arcade video game designed to
simulate flying an airplane would presumably have a much higher tolerance for
defects than software used to control an actual airliner.
A problem with software testing is that the number of defects in a software product
can be very large, and the number of configurations of the product larger still. Bugs
that occur infrequently are difficult to find in testing. A rule of thumb is that a system
that is expected to function without faults for a certain length of time must have
already been tested for at least that length of time. This has severe consequences for
projects to write long-lived reliable software.
A common practice of software testing is that it is performed by an independent group
of testers after the functionality is developed but before it is shipped to the customer.
This practice often results in the testing phase being used as project buffer to
compensate for project delays. Another practice is to start software testing at the same
moment the project starts and it is a continuous process until the project finishes.
Another common practice is for test suites to be developed during technical support
escalation procedures. Such tests are then maintained in regression testing suites to
ensure that future updates to the software don't repeat any of the known mistakes.
It is commonly believed that the earlier a defect is found the cheaper it is to fix it.

24
Time Detected
Time
Introduced
Requirements Architecture Construction
System
Test
Post-
Release
Requirements 1 3 5-10 10 10-100
Architecture - 1 10 15 25-100
Construction - - 1 10 10-25
In counterpoint, some emerging software disciplines such as extreme programming
and the agile software development movement, adhere to a "test-driven software
development" model. In this process unit tests are written first, by the programmers
(often with pair programming in the extreme programming methodology). Of course
these tests fail initially; as they are expected to. Then as code is written it passes
incrementally larger portions of the test suites. The test suites are continuously
updated as new failure conditions and corner cases are discovered, and they are
integrated with any regression tests that are developed.
Unit tests are maintained along with the rest of the software source code and generally
integrated into the build process (with inherently interactive tests being relegated to a
partially manual build acceptance process).
The software, tools, samples of data input and output, and configurations are all
referred to collectively as a test harness.
4.5 Highlights of Training Exposure
The training provided exposure to concepts of OOPS, Core and Advanced Java and
helped immensely to learn to develop web applications using Advanced Java
concepts.
4.5.1 Outcome-Screenshots
The outcome of this training is the web based project on shipping system developed
using the software Net Beans IDE 6.5

25
4.5.1.1 Screenshot of website:
LOGIN FORM:
PRODUCT DETAILS:

26
PRODUCT VERSION:
PRODUCT USERS:

27
BUG DETAILS:
FILE ATTACHMENT:

28
TRACKING HIERARCHY:
VIEWS PRODUCT USER HIERARCHY:

31
CHAPTER-5
CONCLUSION
5.1 Training Report Conclusion
The given project “Technical Bug Detecting System” was successfully completed and
the required reports are generated. The project has been designed to fulfill the needs
of the customer and company. The system is extremely user friendly. The system is
flexible so that there is a lot of scope to update the system. As the system is flexible
the system can be changed if any changes come in future. The developed system is
portable. The developed system has been completed which is customized for the
satisfaction of the user. The system that is developed satisfies the needs of the clients.
It has achieved the required output as described by the system. This can effectively
replace the manual control process, which is followed and reduce the work of
organizations. Thus the system functions with the maximum effort ruling out the
constraints that were faced previously.
The conclusion that can be thus drawn from the above mentioned Industrial Training
Program is that given proper training Java is an immensely useful computer language
in the IT field and holds immense potential for use in further development of IT field.
It’s one of the languages that form the basis of web based application development.
5.2 Learning and frequently askedquestions
The training program was aimed at making students skilled in developing web
applications using concepts of java. It enhanced my skills as a web developer. I also
learned connecting a web application to MS Access database as well as ORACLE
database. I also learned what thin driver is and how to do database connectivity using
thin driver i.e. pure java driver.

32
CHAPTER-6
LIMITATIONS AND FUTURE ENHANCEMENT
6.1Limitations of the system:
 Only the permanent employees can access the system.
 System works with windows’98 and its compatible environments.
 Advanced techniques are not used to check the authorization.
 Once the employee is registered to a course cannot drop, without
completing.
6.2Future Enhancements:
It is not possible to develop a system that makes all the requirements of the user. User
requirements keep changing as the system is being used. Some of the future
enhancements that can be done to this system are:
 As the technology emerges, it is possible to upgrade the system and can be
adaptable to desired environment.
 Because it is based on object-oriented design, any further changes can be
easily adaptable.
 Based on the future security issues, security can be improved using emerging
technologies.
 Attendance module can be added
 sub admin module can be added

33
BIBLIOGRAPHY
[1] http://csis.pace.edu/~marchese/CS389/L9/Use%20Case%20Diagrams.pdf
[2] http://css-tricks.com/perfect-full-page-background-image/
[3] http://www.dhl.co.in/en.html
[4]http://www.roseindia.net/jsp/jsp-login-logout-example.shtml
[5] http://www.onlinetuting.com/website-layout-in-html5-and-css3/

Sample report

Recommended

Recommended

More Related Content

What's hot

What's hot (18)

Viewers also liked

Viewers also liked (10)

Similar to Sample report

Similar to Sample report (20)

Recently uploaded

Recently uploaded (20)

Sample report