SOFTWARE REQUIREMENTS

1. Jdk 1.4.

2. ODBC Drivers installed

3. JDBC Drivers installed

4. Fully Functional Html Editor

5. Weblogic Server

1. Database (oracle or Sql server)

HARDWARE REQUIREMENTS

1. Personal computer with 80486 or higher processor

2. 40 GB hard disk space

1. 512 MB RAM
 ABSTRACT

ELIPS for Electronic Issue Processing Software is a tool enabling the user
to manage different kind of issues related to a project. Such a tool is usually
called Change management tool, or even defect/bug tracker.

Issue types

One distinguishes five types of requests in Elips:

• Requests for bug correction: this request type is carried out mainly by a
person of client profile when a defect occurs on the software.
• Requests for enhancement: this request can be carried out when
functionality misses or an ergonomic aspect can be improved for instance.

• Requests for task processing: this request is mainly for developers or

responsible to achieve a software task.. That allows for example a project
leader to plan complex tasks for his developers and to have a follow-up.
• Requests of work processing: this kind of request is generally sent by
another department or another team to carry out a job like of the
compilation, delivery, and so on.
• Requests for support: this kind of issue is generally used when a user
encounters a problem with a product and needs a help from the support
team

The Elips tool is structured in the following way. It is about a client-Server

application with light web client. The technology used is based on the JSP/Java
and JDBC as back-end. The Web server used to make run the Elips application
is Tomcat.

Elips handles primarily the notion of projects. A project is the first level of
access in Elips. The tool also guarantees the sealing between the projects. the
requests emitted in a project are invisible in another project.

A project can itself be subdivided in sub-projects which are called Domains in

the tool. The subdivision in sub-projects is optional. In this case, a project
without sub-projects will only own one sub-project by default named Default. In
the same way, a domain can also be subdivided in sub-systems.

The rights of Elips users will be given by the administrator. The same user could
participate in several projects with different profiles but in a project he only owns
one profile!!!
 OVERVIEW

Existing System:
The Software industry is increasing like anything. So every software
company getting no of projects to be developed with in the stipulated time with
better quality. In large companies some of their products are having more no
clients. So these companies should have separate divisions for tracking the
bugs, maintaining the issues, enhancements and Tasks World Each and every
department has to co-ordinate each other to increase the productivity. In this
process each and every client request has to record and plans how to process
that request. The Management people at the top level requires to schedule each
every task and assign it to different people to share the work and monitor the
status at each and every interval of time.
Everything is dome manually till now.

Proposed System:
Develop a software system that automates the maintenance of Bugs,
Enhancements, Tasks, Support and work. This increased the productivity for the
company. Top-level management people can visit this application to know the
status of each and every thing and ask the responsible person, the reasons for
the delay and then they can take the decision based on the statistics. This
application also provides high security at each and every level and provides
different functionalities based on the user profile. Finally
It provides an efficient mechanism to maintain above things and co-ordinate each
and every department.
Bug: A Bug is nothing but an error instead of the output when we run a project,
product or program.

Task: A Task is nothing some work which the programmer to has to do

to achieve some functionality.

Enhancement: An Enhancement is a functionality which needs to be

extended in current product or project. Generally this will be asked by
the client.

Support: Support is nothing providing some help to the client after the
development of the project and given to the client. This helps the
client t\to run the project at their environments with better
performance.

Elips
Before Elips

In the project development process the people at higher level has to divide
the modules into different tasks and assign to different programmers. These
people has to maintain task details, description and to whom the a particular task
is assigned and check whether that task is completed or not or check the status
and take the decisions based on the statistics. After development of the project
and given it to the client, that client may get some bugs when they deploy at their
environments. So the client requests the company to fix the bugs and release the
patch for that bug. The company has to maintain the all these bug details and
bug resolutions in the database.

Whenever we develop a project we need to provide some support to run

that project and use the project. Client may request the company to add some
enhancements to the same product. For doing that, the company has to store the
client requirements for enhancements and develop the extra features.

If the project manager assigns some tasks to the programmer he can say
the program that one of that task is very important and that is having high priority
in two ways. One way is to specify the priority at the time of assigning or else
mail the priority.
 After the completion of the bug, enhancement, task and work request the
user has to intimate the by directly contacting the team leaders and make a mail
then the team will prepare the report for his team and finally integrate all the
reports from different teams and calculate the final statistics.

After preparing the documents all the documents should be placed at a secured
location. On each and everyday all the reports should be stored like this. This is a time
taking process to prepare the documents rather than work. We can’t provide security at
different levels to some parts of the documents.
Maintaining all the above things manually in an Excel sheet or somewhere else is
not a better solution for the companies to improve the productivity or taking the
decisions, putting the deadlines and announce new releases.

After Elips
Elips is change management tool which allows creating, tracking update
and maintain the changes in Bug, Task, Enhancement and Support divisions. It is
very good application to improve the productivity of the company

It maintains different users and their profiles to provide security from top
level to bottom level different options. It also maintains the project where are
going in the company and the completed projects. It allows us to store the client
requests related to bug, enhancement, task and work and process the requests
by assigning them to different users and setting the priorities easily though the
application. Then the user can take up the high priority things and complete it. He
can also intimate the status the above things to the supervisors. The Higher level
can see the statistics and generate the reports. Based on their reports they can
take necessary action.

The user can see the tasks, bugs or enhancements or support requests
which are assigned to him only. He can also assign that these things to different
user if he is not able to do it.

Transaction:
We distinguish in Elips five user profiles, i.e.:

• Client: The client is the default user profile for a specific project. He can
send requests toward a given domain and consult all the requests/issues
done by all the clients of the project. I won't see on the other hand the
requests done by the other profiles of the project.
• Responsible: The user is responsible of the project with possibly other
users. He will receive requests emitted by a client and assign them to
developers for processing
• Developer: The developer is the person who processes the request after
assignment by the responsible. The developer can also consult all the
requests of the domain.
• Supervisor: he has the visibility on every request of a project.
• Administrator of the project: he can
- add / delete domains
- add / delete sub-systems
- assign / delete profile to a person
- assign / delete developer or a responsible to a domain
- define persons notified by emails in a domain
• Administrator of the Elips application: he can:
- add / delete projects
- add / delete profiles
- associate users to projects
- visualize current sessions + history
• Administrator of the company : he can: &
- add / delete application administrators
- add / delete users
- add / delete departments
- add / delete teams
A notification system by email is available in Elips. Whenever a major change is
made on an issue (publishing, assignment, resolution,), a mail is sent to the
person concerned after saving it in the database.

INTRODUCTION

The activity of change management constitutes traditionally of a piece of

the broader activity of configuration management. We point out that the purpose
of the activity of configuration management is to historize the changes on the
code, and documents of a project and to allow building at any time a given
version of software.

The purpose of the change management activity treats part of these problems
and is to manage the various defects being able to occur in the maintenance
phase of a project, as well as the enhancement requests on the tool.

One can summarize this activity in the following way:

• sending defect, enhancement, task, work processing requests(issues) by

the users, the production engineers, the developers
• archiving these issues and following-up them in a specific life cycle
(opening, processing, correction, closing) by the people responsible for
the issue processing and then the communication of found solutions