A Project Report

On
Mind Tech Bug Component System Organization

Submitted in partial fulfillment of the requirements for award of the degree Of

MASTER OF TECHNOLOGY
IN
SOFTWARE ENGINEERING (INTEGRATED)
By
G.Archana (167Z1A0540)

B.Sahithi(167Z1A0521)

K.Rahul Reddy(167Z1A0554)

Under the guidance

of
VISHAL
Incharge
PRABHU RAJ A B

NSIC- NATIONAL
SMALL
INDUSTRIES
CORPORATION
(A Government of India Enterprise)
DEPARTMENT OF COMPUTER SCIENCE AND
ENGINEERING

NALLA NARSIMHA REDDY GROUP OF INSTITUTIONS,HYDERABAD

 ACKNOWLEDGEMENT

At every outset I express my gratitude to almighty lord for showering his grace and
blessings upon me to complete this project.

Although our name appears on the cover of this book, many people had
contributed in some form or the other form to this project Development. We could
not done this project without the assistance or support of each of the following we
thank you all.

I wish to place on my record my deep sense of gratitude to my project guide,

Mr.VISHAL , NATIONAL SMALL INDUSTRIES CORPORATION for his
constant motivation and valuable help through the project work. Express my
gratitude to Mr.V.Chandra Sekhar Reddy, Principal of Krishna Murthy
Institute of Technology and Engineering for his valuable suggestions and
advices throughout the course. I also extend my thanks to other Faculties for their
Cooperation during my Course.

Finally I would like to thank my friends for their cooperation to complete this
project.

G.Archana(167Z1A
0540) B.sahithi(167Z1A0521)

K.Rahul Reddy(167Z1A0554)

ABSTRACT
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 “Mind Tech 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.

MODULE DESCRIPTION

In the Project titled “Mind Tech 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.

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 anyone find out a bug in a
module of that application can report that bug to us using this
Bug System. Thus our Mind Tech 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 Android-based
application.
UNIFIED MODELING LANGUAGE (UML)

The unified modeling is a standard language for

specifying, visualizing, constructing and documenting the
system and its components is a graphical language which
provides a vocabulary and set of semantics and rules. The
UML focuses on the conceptual and physical representation
of the system. It captures the decisions and understandings
about systems that must be constructed. It is used to
understand, design, configure and control information
about the systems.

Depending on the development culture, some of

these artifacts are treated more or less formally than others.
Such artifacts are not only the deliverables of a project;
they are also critical in controlling, measuring, and
communicating about a system during its development and
after its deployment.
The UML addresses the documentation of a
system's architecture and all of its details. The UML also
provides a language for expressing requirements and for
 tests. Finally, the UML provides a language for modeling
the activities of project planning and release management.

. BUILINDING BLOCKS OF UML

The vocabulary of the UML encompasses three kinds of
building blocks:
1. Things
2. Relationships
3. Diagrams
Things are the abstractions that are first-class citizens
in a model, relationships tie these things together and
diagrams group interesting collections of things.

THINGS IN THE UML

There are four kinds of things in the UML:
1. Structural things

2. Behavioral things

3. Grouping things

4. Annotational things
1. STUCTURALTHINGS: are the nouns of UML models.
The structural things used in the project design are:

First, a class is a description of a set of objects that

share the same attributes, operations, relationships and
semantics.

Window
Origin

Size
open()

close()

move()

display()

Fig: Classes
 Second, a use case is a description of set of sequence
of actions that a system performs that yields an observable
result of value to particular actor.

Fig: Use Cases

Third, a node is a physical element that exists at

runtime and represents a computational resource, generally
having at least some memory and often processing
capability.

Fig: Nodes
 2.BEHAVIORAL THINGS :are the dynamic parts of
UML models. The behavioral thing used is:

INTERACTION:

An interaction is a behavior that comprises a set

of messages exchanged among a set of objects within
a particular context to accomplish a specific purpose.
An interaction involves a number of other elements,
including messages, action sequences (the behavior
invoked by a message, and links (the connection
between objects).

Fig: Messages

. RELATIONAL IN THE UML

There are four kinds of relationships in the UML:

  Dependency
 Association
 Generalization
 Realization
A dependency is a semantic relationship between two
things in which a change to one thing may affect the
semantics of the other thing (the dependent thing).

Fig: Dependencies

An association is a structural relationship that

describes a set links, a link being a connection among
objects. Aggregation is a special kind of association,
representing a structural relationship between a whole and
its parts.

Fig: Association
 A generalization is a specialization/ generalization
relationship in which objects of the specialized element (the
child) are substitutable for objects of the generalized
element (the parent).

Fig: Generalization

A realization is a semantic relationship between

classifiers, where in one classifier specifies a contract that
another classifier guarantees to carry out.

Fig: Realization

.SEQUENCE DIAGRAMS

UML sequence diagrams are used to represent the

flow of messages, events and actions between the objects or
components of a system. Time is represented in the vertical
direction showing the sequence of interactions of the
header elements, which are displayed horizontally at the
top of the diagram.

Sequence Diagrams are used primarily to design,

document and validate the architecture, interfaces and logic
of the system by describing the sequence of actions that
need to be performed to complete a task or scenario. UML
sequence diagrams are useful design tools because they
provide a dynamic view of the system behavior which can
be difficult to extract from static diagrams or specifications.

ACTOR
Represents an external person or entity that interacts
with the system

OBJECT
Represents an object in the system or one of its
components
UNIT
Represents a subsystem, component, unit, or other
logical entity in the system (may or may not be
implemented by objects)

SEPERATOR
Represents an interface or boundary between
subsystems, components or units (e.g., air interface,
Internet, network)

GROUP
Groups related header elements into subsystems or
components
SEQUENCE DIAGRAM BODY ELEMENTS

ACTION
Represents an action taken by an actor, object or
unit

ASYNCHRONUS MESSAGE
An asynchronous message between header
elements

BLOCK
 A block representing a loop or conditional for a
particular header element

CALL MESSAGE
A call (procedure) message between header
elements

CREATE MESSAGE
A "create" message that creates a header element
(represented by lifeline going from dashed to solid
pattern)

DIAGRAM LINK
Represents a portion of a diagram treated as a
functional block. Similar to a procedure or function
call that abstracts functionality or details not shown at
this level and can be an optional link to another
diagram for elaboration.

Else Block Represents an "else" block portion of

a diagram block

MESSAGE

A simple message between header elements

RETURN MESSAGE

A return message between header elements

USE-CASE DIAGRAM

System

Login

Bug

Projects

Developer

Profile

Logout
 Login

Add project

Bug status

Super user

Profile

Logout
 System

Login

Bug status

Tester

Profile

Logout
SEQUENCEDIAGRAM
COMPONENT DIAGRAM
Deployment Diagram

server

Application
INTRODUCTION

Implementation is the most crucial stage in

achieving a successful system and giving the user’s
confidence that the new system is workable and effective.
Implementation of the modified application to replace an
existing one. This type of conversation is relatively easy to
handle, provide there are no major changes in the system.

Each program is tested individually at the time of

development using the data and has verified that this
program linked together in the way specified in the
programs specification, the computer system and its
environment is tested to the satisfaction of the user. The
system that has been developed is accepted and proved to
be satisfactory for the user. And so the system is going to
be implemented very soon. A simple operating procedure is
included so that the user can understand the different
functions clearly and quickly.

Initially as a first step the executable form of the

application is to be created and loaded in the common
server machine which is accessible to all the user and the
 server is to be connected to a network. The final stage is to
document the entire system which provides components
and the operating procedures of the system.

5.2. DESIGN AND IMPLEMENTATION CONSTRAINTS

All modules are coded thoroughly based on

requirements from software organization. The software is
designed in such a way that the user can easily interact with
the screen. Software is designed in such a way that it can be
extended to the real time business.

SCREENSHOTS