Contact at mumbai.academics@gmail.com or 8097636691
Responsive Ads Here

Friday, 2 February 2018

Mind Tech Bug Component System


Mind Tech Bug Component System


Problem Specification:
In every organization, every product that needs to be tested before making it available to the society. So, we have to maintain the details of test process. In the present project “MindTech Bug Component System” we are able to keep track all the testing details of bugs occurred in different projects. In the standalone system, it is some more difficult to maintain different databases on every system. So in every branch we have to install the software and maintain a database individually for tracking the bugs occurred in that branch. At final it is very difficult to keep track of all bugs occurred around all the branches. Totally is very time taking and risky process to collect all the bugs from every branch and controlling them and taking the decisions on those collected data about the bugs.
Project Scope:
One more motive to develop this new system is when we developed an application and it is in beta version and is being tested by different peoples around the earth. If any one find out a bug in a module of that application can report that bug to us using this Bug System. Thus our MindTech Bug Component System collects all the bugs related one/more projects and maintain them in a proper manner which helps us to take a decision and to know quickly the status of bug in each project.
Project Objectives:
Ø  MindTech Bug and Component System is a tool is used to keep track of the bugs occurred among the several projects. Lot of effort was put to make it user friendly.
Ø    Optimum utilization of tool is possible. All basic features are provided.
Ø    Reduces the user interaction work.
Ø    The wastage of time is reduced.
Ø  It also helps in optimum distribution of funds by the management among user groups for procurement of new equipment.
Ø  More flexible it means user (administrator) can add his own number of filters if he interested easily.
Ø  All the bugs are stored and controlled centrally. So no need to maintain separate database in every branch.
Existing System:
The existing system is also computerized one. But it is standalone computer system application. So in every branch we have to install the software and maintain a database individually for tracking the bugs occurred in that branch. At final it is very difficult to keep track of all bugs occurred around all the branches. Totally is very time taking and risky process to collect all the bugs from every branch and controlling them and taking the decisions on those collected data about the bugs.
One more motive to develop this new system is when we developed an application and it is in beta version and is being tested by different peoples around the earth. If any one find out a bug in a module of that application can report that bug to us using this Bug System. Thus our MindTech Bug and Component System collects all the bugs related one/more projects and maintain them in a proper manner which helps us to take a decision and to know quickly the status of bug in each project.
Proposed System:
The first step of analysis process involves the identification of need. The success of a system depends largely on how accurately a problem is defined, thoroughly investigated and properly carried out through the choice of solution.
This application has been developed in order to overcome the difficulties encountered while using the existing system. This is web-based distributed JSPBug. An integration of JSP/Java-Servlets,and relational database.
MODULE DESCRIPTION
In the Project titled “MindTech Bug Component System”, the modules are
1.      Super User
2.      Administrator
3.      Developer
4.      Tester
Super User: The Application is designed to keep track of bugs that are raised during the Life Cycle of Software development. The Super User maintains the details of Employees along with department, Projects with Components and Versions. Super user can add Employees for different projects. After logon the SuperUser, he can enter the SuperUser homepage and from there he can do the activities like adding users in the organization.   
Administrator: Administrators can add Projects to this application. The Bugs raised will be reported to the Administrator or Super User. The Bug will be assigned to different Users. The Bugs will be maintained under different conditions with different priorities and Status. Nearly administrator is also having same rights like SuperUser except addition of users. 
Developer: Developer can see the bugs in his project. Others cannot view the Bugs assigned to a particular employee. This application allows adding Solution also. After finding the solution for a bug, it will be forwarded to Admin people.
Tester: The tester can report the bugs to the administrators. He can send the bugs severity, priority of bugs, and the bug description to the administrator either through the interface provided or through mail.
At every stage it is possible to get the bug reports by all the members that are interacting with the system.
SOFTWARE REQUIREMENTS
Operating System                      :  WindowsXP or Mail server
Web Server                               :  Tomcat 5.0
Web Browser                            :  Internet Explorer 5
Database                                    : Oracle 8i
Other Technologies                  :  JSPs/Servlets, JDBC.
HARDWARE REQUIREMENTS
Pentium Processor                   :           Pentium
RAM                                         :           128MB
Hard Disk                                 :           20 GB
CD/ROM Drive                        :           52 Bit

No comments:

Post a Comment