CHANGE

REQUEST
TRACKER
ACKNOWLEDGEMENT
We the students Juveria Shaheen Syed (16L51A0564),
K Thaufiqa Banu (16L51A0566), Kubra Begum
(16L51A0568), Lubna Begum (16L51A0569) would like to
express our special thanks of gratitude to our guide Shahana
naaz madam and the head of department Srivani madam who
gave us the opportunity to do this wonderful project on the
topic Change request tracker which helped us doing a lot of
research and come to know about many things.
E X I S T I N G S YS T E M

• No secure
registration and
profile management
of users.
• No online help
provided for the
users.
• Security
breaching was
highly amended.
• This system also
not providing
help to
implement and
tune the system.
AND MORE DRAWBACKS ARE

• This manual system doesn’t

provide for saving data and leads
to mismanagement of data
storage.
• The system doesn’t provide
intranet email services for the
users.
• This system doesn’t provide automatic warning to managers and
management when change request crosses the buffer cost.
P R O P O S E D S YS T E M

• This system makes the

over all project
management much easier
and flexible.
• Various classes have been
used to maintain the
details of all users and
catalog.
• This system is giving the
user to track change
request made by user
online.
• This system maintains
user’s personal,
address and contact
details.
• This system is
providing more space
to maintain user’s data.
• This system is
providing accessibility
control to data with
respect to users.
• Authentication is
provided for this system
which only registered
users can access.
• Report generation
features is provided using
to generate different
kinds of requests.
• User friendliness is
provided in the
application with various
controls provided by
system rich user
interface.
FUTURE ENHANCEMENT
WORKING AND
DESIGN
(M OD UL E S AN D UM L DI AG RAM S)
MODULES INVOLVED
• Authentication ans Security
module
• Mail Admin module
• Manager module
• Engineer module
• Track change request
module
• Reports module
AUTHENTICATION AND SECURITY MODULE
• The user’s details are verified against the
details in the user tables and if they are
valid they should be entered into the
system.
• Once entered, based on the user type
access to the different modules to be
enabled/disabled and individual user can
change their default password or old
password.
Password can be changed based on user’s demand or requirements such as,
forgotten password, changing the password for securing the details etc.
MAIL ADMIN MODULE
• The Mail admin module consists
of three sub-modules.

1. Registration Module –
Here mail admin register new
employees and store their details
in database. Create their mail
account in intranet service, and
username, password to them.
2. User’s Management Module -

In User Management module, mail

admin can access any user related
information, for
example their hierarchy ,contact
details, login details...etc. He can also
view the current login password of a
user, and can block him from system
access if requirement comes .He can
also communicate with others using
mail service
3. POP3 Management Module -

In POP3 Management module

mail admin can start and stop
pop3 server. For automatic email
alert and intranet based mail
service pop3 server must be
started by mail admin.
 MANAGER MODULE
There are there sub-modules here,
1. Project Manager Module –
In this module new project registration,
viewing old project, updating buffer cost
with respect to requirement and deletion
of older project can be done.
2. Change Request Management
Module –
New change request of user can be
added and viewing them and if
requirement came to delete them can be
done.
3. Others –
A manager also can use the mail service
to communicate with other registered
users of the system.
ENGINEER MODULE
A engineer can view his managers
projects and user change requests with
respect to that project. He can also take
the advantages of mail service.

TRACK CHANGE REQUEST MODULE

Tracking of change request is done
automatically with respect to a project.
If the total change request cost exceeds
the buffer cost fixed, then an automatic
mail will be sent to respective manager
and management about it, so that they
can re-negotiates with the customer.
REPORTS MODULE
User and Administrator can
generate the different types of
Reports according to their
access.
 UML DIAGRAMS -
 The Unified Modeling Language allows the software engineer to express an analysis model
using the modeling notation that is governed by a set of syntactic semantic and pragmatic rules.
 A UML system is represented using five different views that describe the system from distinctly
different perspective.
User Model View - Structural Model view - Behavioral Model View -
This view represents the system In this model the data and It represents the dynamic of
from the users perspective. functionality are arrived from inside behavioral as parts of the system,
The analysis representation the system. depicting the interactions of
describes a usage scenario from This model view models the static collection between various
the end-users perspective. structures. structural elements described in
the user model and structural
model view.
Implementation Model Environmental Model View -
View - In this the structural and behavioral
In this the structural and aspects of the environment in which
behavioral as parts of the the system is to be implemented are
system are represented as represented.
they are to be built.
 C L A S S D I AG R A M
 The class diagram is the main building
block of object oriented modelling.

 It is used both for general conceptual

modeling of the systematics of the
application, and for detailed modelling
translating the models into programming
code.

 Class diagrams can also be used for data

modeling. The classes in a class diagram
represent both the main objects,
interactions in the application and the
classes to be programmed.

A class with three sections -

• Upper part holds class name.

• Middle part contains attributes of class.

• Bottom part contains methods or

operations class can hold.
USE CASE DIAGRAM
 USE CASE FOR ADMIN
 A use case diagram at its simplest is a
representation of a user's interaction
with the system and depicting the
specifications of a use case. A use case
diagram can portray the different types
of users of a system and the various
ways that they interact with the system.
This type of diagram is typically used in
conjunction with the textual use case
and will often be accompanied by other
types of diagrams as well.
 USE CA SE FOR M A NA G ER  USE CA SE FO R ENG I NEER
SEQUENCE DIAGRAM
A sequence diagram is a kind of interaction diagram that shows how
processes operate with one another and in what order.
A sequence diagram shows object interactions arranged in time sequence. It
depicts the objects and classes involved in the scenario and the sequence of
messages exchanged between the objects needed to carry out the functionality
of the scenario.
Sequence diagrams are typically associated with use case realizations in the
Logical View of the system under development.
Sequence diagrams are sometimes called event diagrams, event scenarios,
and timing diagrams.
SEQUENCE DIA G R AM FO R A DM I N
SEQUENCE DIA G R AM FO R M A NA G ER
SEQUENCE DIA G R AM FO R ENG I NEER
C O L L A B O R AT IV E D I AG R A M
 A collaboration diagram
• COLLABORATIVE DIAGRAM FOR ADMIN – describes interactions
among objects in terms of
sequenced messages.
Collaboration diagrams
represent a combination
of information taken from
class, sequence, and use
case diagrams describing
both the static structure
and dynamic behavior of a
system.
• COL L A BORAT IVE DI A G RAM FO R M A NA G ER • CO L L A B ORAT IVE DI A G RAM FO R ENG I NEER
COMPONENT DIAGRAM
In the Unified Modeling Language, a
• COMPONENT DIAGRAM FOR ADMIN component diagram depicts how
components are wired together to
form larger components and or
software systems. They are used to
illustrate the structure of arbitrarily
complex systems
Components are wired together by
using an assembly connector to connect
the required interface of one
component with the provided
interface of another component. This
illustrates the service consumer - service
provider relationship between the two
components.
• C OM P ON E NT D I AG RAM O F • C O M P ON E NT D I AG RAM O F
M AN AG E R E N G I NE E R
 D E P L OY M E N T M O D E L

• DEPLOYMENT MODEL FOR ADMIN A deployment diagram in the Unified

Modeling Language models the physical
deployment of artifacts on nodes. To describe a
web site, for example, a deployment diagram
would show what hardware components
("nodes") exist (e.g., a web server, an application
server, and a database server), what software
components ("artifacts") run on each node (e.g.,
web application, database), and how the different
pieces are connected (e.g. JDBC, REST, RMI).

The nodes appear as boxes, and the

artifacts allocated to each node appear as
rectangles within the boxes. Nodes may
have subnodes, which appear as nested
boxes. A single node in a deployment
diagram may conceptually represent
multiple physical nodes, such as a cluster of
database servers.
• DEP LOY MENT M O DEL FO R M A NA G ER • DEP LO Y MENT M O DEL FO R ENG I NEER
ACTIVITY MODEL
• ACTIVITY DIAGRAM FOR ADMIN AND MANAGER
• Activity diagram is another
important diagram in UML to
describe dynamic aspects of the
system. It is basically a flow
chart to represent the flow
form one activity to another
activity. The activity can be
described as an operation of the
system.
• So the control flow is drawn
from one operation to another.
This flow can be sequential,
branched or concurrent.
• ACT I V I T Y D I AG R A M FOR E NG I NEER