TITLE

A mini-project Report

Submitted in partial fulfillment the requirements

For the award of degree of

BACHELOR OF TECHNOLOGY
in

Computer science and Engineering

By

V.MADHURIMA

13841A0544

D.GAYATRI

13841A0557

Under the guidance of

Department of computer science and Engineering

Aurora’s Technological and Research Institute

Parvathapur(Vill.),Uppal,Hyderabad-98

(2015-2016)
[onLetter Head]

CERTIFICATE

This is to certify that the Project work entitled “MRI(MNC’s recruitment information)” is
a bonafide work carried out by V.Madhurima(13841A0544),D.Gayatri(13841A0557) in
partial fulfilment of the requirements for the award of degree of B.Tech in COMPUTER
SCIENCE AND ENGINEERING by the JAWAHARLAL NEHRU
TECHNOLOGICAL UNIVERSITY, Hyderabad, during the academic year 2015-
2016.The results embodied in this report have not been submitted by any student to any
other university of institution for the award of any degree or diploma.
 DECLARATION

We hereby declare that the work contained in this report entitled “MRI(MNC’s recruitment
information)” is original and has been done by us under the guidance of ____________Guide
NAME[TNR,size 12],Designation[TNR, size12] Aurora’s Technological and Research Institute,
Jawaharlal Nehru Technological University Hyderabad. The work is original and has not been
submitted to any other institute for any degree or diploma. We have followed the guidelines
provided by the institute in preparing report. We have conformed to the norms and guidelines
given in the ethical code of Conduct of the Institute. Whenever we have used materials (data,
theoretical analysis, figures and text) from other resources, we have given due credit to them by
editing them in the text of the report and giving their details in the references.

Place:[TNR,SIZE,12]

Date:[TNR,SIZE,12]

V.Madhurima(CSE)

13841A0544

D.Gayatri(CSE)

13841A0557
 ACKNOWLEDGEMENT

This work has been done during project period, this present project work
method of education is really good opportunity to put theoretical knowledge into
planned exercise with an aim to solve a real time problem and also to develop a
confidence to face various practical situations

We would also like to express our gratitude to Mr.J.Srikanth[TNR, Bold.12],

Director, Aurora’s Technological and Research Institute for providing us/me
congenial atmosphere and encouragement.

We express our/my sincere thanks to Head of the Department Ms.

M.Nirmala[TNR, Bold.12], for giving us the support and her kind attention and
valuable guidance to me throughout this course

We express my sincere thanks to Project Coordinator____________ [TNR,

Bold.12], for helping us/ me to complete my/our project work by giving valuable
suggestions.

We convey thanks to our/my project guide Name of guide [TNR, Bold, 12] of
Department of CSE for providing encouragement, constant support and guidance
which was of a great help to complete this project successfully.

V.Madhurima(CSE)

13841A0544

D.Gayatri(CSE)

13841A0557
 ABSTRACT

MRI (MNC’s RECRUITMENT INFORMATION)

Description:
This is an android application where the user can know the recruitment information of various MNC’s.It
is important to know the interview process of the company before attending the recruitment. This MRI
application helps in such cases. The user can know the various levels of recruitment procedure followed
by different MNC’s. It also contains other information like the location of the company, images, contact
details etc. Once the user opens the application, he can know this information by selecting the company
from the list of MNC’s displayed.

Existing System: In android mobiles, there is no application which can describe the recruitment
procedure followed by various companies. It is very much important for the people who want to attend
the recruitment. In existing system, the user has to visit the sites of the companies to know the levels in
the recruitment procedure.

Proposed System:In this proposed system, the user can install this application in his mobile through
which he can know the details of recruitment procedure of various MNC’s. The user need not browse
through various sites. He can know the recruitment procedures of all the MNC’s by using this app. Also
he can know other information like location of the company, images etc.

Technologies used:

Language : Java ,android SDK 2.3

IDE : Eclipse

Operating System : Windows

Hardware Requirements:
Ram : 1GB Ram and above

Hard Disk : 50GB and above

Processor : Dual core and above

 TABLE OF CONTENTS

Chapter Title Page No.

No.

Certificate I

Declaration Ii

Acknowledgement Iii

Abstract Iv

Index v- vi

List of Figures Vii

List of Tables Viii

Acronyms Ix

1 INTRODUCTION 1

1
.
11.1Problem statement
1.2Proposed System

1.3 Scope of the project

1
.
3
2 LITERATURE SURVEY

2.1 List of Articles Referred

2.1.1 Article 1 – Title , Author, source [Times new roman,
Size 12,Left,Bold]
Content [Times new roman, Size 11]

2.1.2 Article 2 – Title , Author, source [Times new roman,

Size 12,Left,Bold]
Content [Times new roman, Size 11]

2.1.3 Article 3 – Title , Author, source [Times new roman,

Size 12,Left,Bold]
Content [Times new roman, Size 11]

2.2 List of Text books Referred

2.2.1 Text book 1 – Title , Author, [Times new roman, Size
12,Left,Bold]
Content [Times new roman, Size 11]

2.2.2 Text book2 – Title , Author, [Times new roman, Size

12,Left,Bold]
Content [Times new roman, Size 11]

2.2.3Text book 3 – Title , Author, [Times new roman, Size

12,Left,Bold]
Content [Times new roman, Size 11]

3 SOFTWARE REQUIREMENTS SPECIFICATION

3.1 Overall Description
3.1.1 Product Functions
3.1.2 Operating Environment

3.2 External Interface Requirements

3.2.1 User Interfaces
3.2.2 Hardware Interfaces
3.2.3 Software Interfaces
3.2.4 Communication Interfaces
3.3 Functional Requirements
3.3.1 Module Name(each module of your project)
 3.4 Non-functional Requirements
3.4.1 Performance
3.4.2 Reliability
3.4.3 Availability
3.4.4 Security
3.4.5 Maintainability
3.4.6 Efficiency
4 DESIGN

4.1 UML Diagrams

4.1.1 Use Case Diagram
4.1.2 Class Diagram
4.1.3 Sequence Diagram
4.1.4 Activity Diagram
4.1.5 State Diagram
5
IMPLEMENTATION
5
.
5.1
1 Pseudo code
5.2 Results [ screen shots should be numbered]

SCREE

6 TESTING

6.1 Testing Methodologies[applied to your project]

7 CONCLUSION&FUTURE SCOPE

8 REFERENCES
 1.INTRODUCTION

1.1Problem statement:
This is an android application where the user can know the recruitment information of various MNC’s. It
is important to know the interview process of the company before attending the recruitment. This MRI
application helps in such cases. The user can know the various levels of recruitment procedure followed
by different MNC’s. It also contains other information like the location of the company, images, contact
details etc. Once the user opens the application, he can know this information by selecting the company
from the list of MNC’s displayed.

This MRI application helps in such cases. The user can know the various levels of recruitment procedure
followed by different MNC’s. It also contains other information like the location of the company, images,
contact details etc. This application supports the 2.3 and the later versions of the Android.

1.2Proposed System:
In this proposed system, the user can install this application in his mobile through which he can know the
details of recruitment procedure of various MNC’s. The user need not browse through various sites. He
can know the recruitment procedures of all the MNC’s by using this app. Also he can know other
information like location of the company, images etc.

1.3Scope of the project :

Our project aims to build this information system in a Mobile phone using the latest technology in the
market namely Google Android SDK . Music makes human to refresh their mood and control their
emotions. Our project recruitment information of various MNC’s.It is important to know the interview
process of the company before attending the recruitment. for Android users which makes a person
anxious.
 2. LITERATURE SURVEY

2.1List of Articles Referred

[Times new roman, Size 13,center,Bold]

 Title:[ Times new roman, Size 12,Left,Bold]

Description:[Times new roman, Size 11,Left,Bold]
Content [Times new roman, Size 11]
Content should not exceed more than 50 words

 Title:[ Times new roman, Size 12,Left,Bold]

Description:[Times new roman, Size 11,Left,Bold]
Content [Times new roman, Size 11]
Content should not exceed more than 50 words

 Title:[ Times new roman, Size 12,Left,Bold]

Description:[Times new roman, Size 11,Left,Bold]
Content [Times new roman, Size 11]
Content should not exceed more than 50 words

2.2List of Textbooks Referred

[Times new roman, Size 13,center,Bold]

 Title:[ Times new roman, Size 12,Left,Bold]

Description:[Times new roman, Size 11,Left,Bold]
Content [Times new roman, Size 11]
Content should not exceed more than 50 words

 Title:[ Times new roman, Size 12,Left,Bold]

Description:[Times new roman, Size 11,Left,Bold]
Content [Times new roman, Size 11]
Content should not exceed more than 50 words

 Title:[ Times new roman, Size 12,Left,Bold]

Description:[Times new roman, Size 11,Left,Bold]
Content [Times new roman, Size 11]
Content should not exceed more than 50 words
 SOFTWARE
REQUIREMENT
SPECIFICATIONS
3:SOFTWARE REQUIREMENT SPECIFICATION:

3.1:Overall Description:
. The user can know the various levels of recruitment procedure followed by different
MNC’s. It also contains other information like the location of the company, images, contact
details etc.Once the user opens the application, he can know this information by selecting the
company from the list of MNC’s displayed.

3.2:Product perspective:
Existing System:In android mobiles, there is no application which can describe the recruitment
procedure followed by various companies. It is very much important for the people who want to
attend the recruitment. In existing system, the user has to visit the sites of the companies to know
the levels in the recruitment procedure.

Proposed System:In this proposed system, the user can install this application in his mobile
through which he can know the details of recruitment procedure of various MNC’s. The user
need not browse through various sites. He can know the recruitment procedures of all the MNC’s
by using this app. Also he can know other information like location of the company, images etc.

3.3.Modules in our application:

Modules:
 View mnc companies information
 Add mnc companies information

3.4.Business Scenario:
This application can be used my all android users because even a budget mobile device has a
SD card with some music files on it. All smartphones from lower end to higher end devices
can use this app.

3.5. Requirements:

3.5.1.Software Requirements:
Java(jdk 1.8)
Android SDK
Eclipse Ganymede IDE
Operating System –Windows XP, Windows 7

3.5.2.Hardware Requirements:
Ram : 1 GB Ram & above
Hard Disk : 50 GB & above
Processor :Dual Core & above

3.6. FEASIBILITY STUDY

3.6.FEASIBILITY STUDY:

The next step in analysis is to verify the feasibility of the proposed system. “All projects are feasible
given unlimited resources and infinite time“. But in reality both resources and time are scarce. Project
should confirm to time bounce and should be optimal in their consumption of resources.

 Technical feasibility
 Operational feasibility
 Economical feasibility

3.6.1.TECHNICAL FEASIBILITY:

As we are developing this Application on Java 2 platform edition which is an open source and
free of cost. Once we started developing this application in Java 2 platform edition then there is no need
of purchasing any special software or application software for support.

3.6.2.OPERATIONAL FEASIBILITY:

To determine the operational feasibility of the system we should take into consideration
the awareness level of the users. Users who are using this Application don’t require much
knowledge of how to use. Everything will be understood by user once he sees the application.
3.6.3.ECONOMIC FEASIBILITY

To decide whether a project is economically feasible, or not we have to consider various factors as:

 Cost benefit analysis

 Long-term returns
 Maintenance costs
SYSTEM DESIGN
4.SYSTEM DESIGN

System design is transition from a user oriented document to programmers or data base
personnel. The design is a solution, how to approach to the creation of a new system. This is
composed of several steps. It provides the understanding and procedural details necessary for
implementing the system recommended in the feasibility study. Designing goes through logical
and physical stages of development, logical design reviews the present physical system, prepare
input and output specification, details of implementation plan and prepare a logical design
walkthrough.

The database tables are designed by analyzing functions involved in the system and format of
the fields is also designed. The fields in the database tables should define their role in the system. The
unnecessary fields should be avoided because it affects the storage areas of the system. Then in the
input and output screen design, the design should be made user friendly. The menu should be precise
and compact.

4.1.SOFTWARE DESIGN

In designing the software following principles are followed:

1. Modularity and partitioning: software is designed such that, each system should consists of hierarchy
of modules and serve to partition into separate function.

2. Coupling: modules should have little dependence on other modules of a system.

3. Cohesion: modules should carry out in a single processing function.

4. Shared use: avoid duplication by allowing a single module is called by other that need the function it
provides
4.2.INPUT/OUTPUT DESIGNS

4.2.1.Input design:

Considering the requirements, procedures to collect the necessary input data in most efficiently
designed. The input design has been done keeping in view that, the interaction of the user with the
system being the most effective and simplified way.

Also the measures are taken for the following

 Controlling the amount of input

 Avoid unauthorized access to the Universal Dossier
 Eliminating extra steps
 Keeping the process simple
 At this stage the input forms and screens are designed.

4.2.2.Output design:

All the screens of the system are designed with a view to provide the user with easy operations
in simpler and efficient way, minimum key strokes possible. Instructions and important information is
emphasized on the screen. Almost every screen is provided with no error and important messages and
option selection facilitates. Emphasis is given for speedy processing and speedy transaction between
the screens. Each screen assigned to make it as much user friendly as possible by using interactive
procedures. So to say user can operate the system without much help from the operating manual.
4.3.SYSTEMARCHITECTUREDESIGN

SQLite

Database

APPLICATION ARCHITECTURE DESIGN

BUSINESS ACCESS LAYER

PRESENTATION DATABASE DATA ACCESS LAYER

LAYER
4.4.UML DIAGRAMS:

4.4.1UML Concepts

The Unified Modelling Language (UML) is a standard language for writing software blue prints.
The UML is a language for

 Visualizing
 Specifying
 Constructing
 Documenting the artefacts of a software intensive system.
The UML is a language which provides vocabulary and the rules for combining words in that vocabulary
for the purpose of communication. A modelling language is a language whose vocabulary and the rules
focus on the conceptual and physical representation of a system. Modelling yields an understanding of a
system.

4.4.2Building Blocks of the UML:

The vocabulary of the UML encompasses three kinds of building blocks:

 Things
 Relationships
 Diagrams
Things are the abstractions that are first-class citizens in a model; relationships tie these things together;
diagrams group interesting collections of things.
4.4.3.Things in the UML:

There are four kinds of things in the UML:

 Structural things
 Behavioral things
 Grouping things
 Annotational things

Structural things 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

Behavioural things are the dynamic parts of UML models. The behavioural thing used is:

Interaction:

An interaction is a behaviour 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 behaviour invoked by a message, and links (the
connection between objects).

Fig: Messages
4.4.4.Relationships 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

4.4.5.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 behaviour 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)

Separator

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

4.4.5.1.Sequence Diagram Body Elements

Action

Represents an action taken by an actor, object or unit

Asynchronous 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 being treated as a functional block. Similar to a procedure or function
call that abstracts functionality or details not shown at this level. Can optionally be linked 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

4.4.6.Use Case Diagram

A use case diagram is a graph of actors set of use cases enclosed by a system boundary, communication
associations between the actors and users and generalization among use cases. The use case model
defines the outside(actors) and inside(use case) of the system’s behavior.

use case diagram is quite simple in nature and depicts two types of elements: one representing the
business roles and the other representing the business processes.

Figure 3.1: an actor in a use case diagram

To identify an actor, search in the problem statement for business terms that portray roles in the
system. For example, in the statement "patients visit the doctor in the clinic for medical tests," "doctor"
and "patients" are the business roles and can be easily identified as actors in the system.

Use case: A use case in a use case diagram is a visual representation of a distinct business functionality
in a system. The key term here is "distinct business functionality." To choose a business process as a
likely candidate for modelling as a use case, you need to ensure that the business process is discrete in
nature.
As the first step in identifying use cases, you should list the discrete business functions in your problem
statement. Each of these business functions can be classified as a potential use case. Remember that
identifying use cases is a discovery rather than a creation. As business functionality becomes clearer, the
underlying use cases become more easily evident. A use case is shown as an ellipse in a use case
diagram (see Figure 3.2).

Figure 3.2: use cases in a use case diagram

Figure 3.2 shows two uses cases: "Make appointment" and "Perform medical tests" in the use case
diagram of a clinic system. As another example, consider that a business process such as "manage
patient records" can in turn have sub-processes like "manage patient's personal information" and
"manage patient's medical information." Discovering such implicit use cases is possible only with a
thorough understanding of all the business processes of the system through discussions with potential
users of the system and relevant domain knowledge.

//////////////////////////////////////////////////////////////////////////////////////////////////////////////

Case diagram:
4.4.7.Activity Diagram

Activity diagrams represent the business and operational workflows of a system. An Activity diagram is a
dynamic diagram that shows the activity and the event that causes the object to be in the particular
state.

So, what is the importance of an Activity diagram, as opposed to a State diagram? A State diagram
shows the different states an object is in during the lifecycle of its existence in the system, and the
transitions in the states of the objects. These transitions depict the activities causing these transitions,
shown by arrows.

An Activity diagram talks more about these transitions and activities causing the changes in the object
states.

Activity Diagram:

Select Level

Give Answers

View Score
4.4.7.1.Defining an Activity diagram

Let us take a look at the building blocks of an Activity diagram.

4.4.7.2.Elements of an Activity diagram

An Activity diagram consists of the following behavioural elements:

Initial Activity: This shows the starting point or first activity of the flow. Denoted by a solid circle. This is
similar to the notation used for Initial State.

Activity: Represented by a rectangle with rounded (almost oval) edges.

.
Decisions: Similar to flowcharts, a logic where a decision is to be made is depicted by a diamond, with
the options written on either sides of the arrows emerging from the diamond, within box brackets.

Signal: When an activity sends or receives a message, that activity is called a signal. Signals are of two
types: Input signal (Message receiving activity) shown by a concave polygon and Output signal (Message
sending activity) shown by a convex polygon.

Concurrent Activities: Some activities occur simultaneously or in parallel. Such activities are called
concurrent activities. For example, listening to the lecturer and looking at the blackboard is a parallel
activity. This is represented by a horizontal split (thick dark line) and the two concurrent activities next
to each other, and the horizontal line again to show the end of the parallel activity.
Final Activity: The end of the Activity diagram is shown by a bull's eye symbol, also called as a final
activity.
4.4.8.Class Diagram

An object is any person, place, thing, concept, event, screen, or report applicable to your
system. Objects both know things (they have attributes) and they do things (they have methods).A class
is a representation of an object and, in many ways; it is simply a template from which objects are
created. Classes form the main building blocks of an object-oriented application. Although thousands of
students attend the university, you would only model one class, called Student, which would represent
the entire collection of students.

4.4.8.1.Responsibilities

Classes are typically modeled as rectangles with three sections: the top section for the name of
the class, the middle section for the attributes of the class, and the bottom section for the methods
of the class. Attributes are the information stored about an object, while methods are the things
an object or class do. For example, students have student numbers, names, addresses, and phone
numbers. Those are all examples of the attributes of a student. Students also enroll in courses,
drop courses, and request transcripts. Those are all examples of the things a student does, which
get implemented (coded) as methods. You should think of methods as the object-oriented
equivalent of functions and procedures.

Class diagram:
4.4.9.object diagram

An object diagram in the Unified Modeling Language (UML), is a diagram that shows a
complete or partial view of the structure of a modeled system at a specific time.

An Object diagram focuses on some particular set of object instances and attributes, and
the links between the instances. A correlated set of object diagrams provides insight into how an
arbitrary view of a system is expected to evolve over time. Object diagrams are more concrete
than class diagrams, and are often used to provide examples, or act as test cases for the class
diagrams. Only those aspects of a model that are of current interest need be shown on an object
diagram. State chart diagram

State chart diagram is used to describe the states of different objects in its life cycle. So the
emphasis is given on the state changes upon some internal or external events. These states of
objects are important to analyze and implement them accurately.State chart diagrams are very
important for describing the states. States can be identified as the condition of objects when a
particular event occurs.

Before drawing a State chart diagram we must have clarified the following points:

 Identify important objects to be analyzed.

 Identify the states.
 Identify the events.
4.4.10.Deployment Diagram

Deployment diagrams are used to visualize the topology of the physical components of a system
where the software components are deployed.

So deployment diagrams are used to describe the static deployment view of a system.
Deployment diagrams consist of nodes and their relationships.

The purpose of deployment diagrams can be described as:

The name Deployment itself describes the purpose of the diagram. Deployment diagrams are
used for describing the hardware components where software components are deployed.

 Visualize hardware topology of a system.

 Describe the hardware components used to deploy software components.
 Describe runtime processing nodes.
SYSTEM CODING &
IMPLEMENTATION
 5.SYSTEM CODING & IMPLEMENTATION

5.1.PSEUDO CODE:
package com.example.mri;

import java.util.ArrayList;

import android.app.Activity;
import android.content.Intent;
import android.os.Bundle;
import android.view.View;
import android.widget.AdapterView;
import android.widget.AdapterView.OnItemClickListener;
import android.widget.ArrayAdapter;
import android.widget.GridView;
import android.widget.TextView;

public class first extends Activity{

ArrayList<String> al =new ArrayList<String>();

@Override
protected void onCreate(Bundle savedInstanceState) {
// TODO Auto-generated method stub
 super.onCreate(savedInstanceState);
setContentView(R.layout.first);
final TextView
tv=(TextView)findViewById(R.id.textView1);
final GridView
gv=(GridView)findViewById(R.id.gridView1);
al.add("ACCENTURE");
al.add("COGNIZANT");
al.add("DELOITTE");
al.add("HCL");
al.add("IBM");

al.add("MPHASIS");
al.add("ORACLE");
al.add("IGATE PATNI");
al.add("TECH MAHINDRA");
al.add("TCS");
al.add("UST GLOBAL");
al.add("WIPRO");

gv.setAdapter(new
ArrayAdapter<String>(getApplicationContext(),
android.R.layout.simple_list_item_1, al));
 gv.setOnItemClickListener(new OnItemClickListener() {

@Override
public void onItemClick(AdapterView<?> arg0,
View arg1, int arg2,
long arg3) {
// TODO Auto-generated method stub
String
s1=gv.getItemAtPosition(arg2).toString();
if(s1.equalsIgnoreCase("tcs"))
{
Intent it=new
Intent(first.this,second.class);
startActivity(it);
}
else if(s1.equalsIgnoreCase("accenture"))
{
Intent it1=new
Intent(first.this,accent.class);
startActivity(it1);
}
if(s1.equalsIgnoreCase("cognizant"))
{
 Intent it2=new
Intent(first.this,cogni.class);
startActivity(it2);
}
if(s1.equalsIgnoreCase("deloitte"))
{
Intent it3=new
Intent(first.this,deloit.class);
startActivity(it3);
}
if(s1.equalsIgnoreCase("hcl"))
{
Intent it4=new Intent(first.this,hcl.class);
startActivity(it4);
}

if(s1.equalsIgnoreCase("ibm"))
{
Intent it6=new Intent(first.this,ibm.class);
startActivity(it6);
}
if(s1.equalsIgnoreCase("micro"))
{
 Intent it7=new
Intent(first.this,micro.class);
startActivity(it7);
}
if(s1.equalsIgnoreCase("mphasis"))
{
Intent it8=new
Intent(first.this,mphasis.class);
startActivity(it8);
}
if(s1.equalsIgnoreCase("oracle"))
{
Intent it9=new
Intent(first.this,oracle.class);
startActivity(it9);
}
if(s1.equalsIgnoreCase("Igate patni"))
{
Intent it10=new
Intent(first.this,patni.class);
startActivity(it10);
}
if(s1.equalsIgnoreCase("tech mahindra"))
 {
Intent it11=new
Intent(first.this,mahindra.class);
startActivity(it11);
}
if(s1.equalsIgnoreCase("ust global"))
{
Intent it12=new Intent(first.this,ust.class);
startActivity(it12);
}
if(s1.equalsIgnoreCase("wipro"))
{
Intent it13=new
Intent(first.this,wipro.class);
startActivity(it13);
}

}
});

}
};
5.2.Splash UI:-
import java.io.InputStream;
import android.app.Activity;
import android.content.Intent;
import android.database.Cursor;
import android.database.sqlite.SQLiteDatabase;
import android.os.Bundle;

public class MainScreen extends Activity{

@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);

setContentView(R.layout.mainscreen);

@Override
protected void onResume() {
// TODO Auto-generated method stub
super.onResume();

Thread runnerlog=new Thread()

{
public void run()
 {
try
{
int logoTimer=0;
while(logoTimer<2000)
{
sleep(100);
logoTimer=logoTimer+100;
}
startActivity(new Intent("com.lalitha.musicpuzzle.MAINACTIVITY"));
}catch (Exception e) {
// TODO: handle exception
e.printStackTrace();
}
}

};

runnerlog.start();
}
}
package com.example.mri;

import android.os.Bundle;
import android.app.Activity;
import android.content.Intent;
import android.view.Menu;
import android.view.View;
import android.view.View.OnClickListener;
import android.widget.Button;
import android.widget.ImageButton;
import android.widget.RelativeLayout;

public class MainActivity extends Activity {

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
ImageButton bt=(ImageButton)findViewById(R.id.imageButton1);
bt.setOnClickListener(new OnClickListener() {

@Override
public void onClick(View v) {
// TODO Auto-generated method stub
Intent it=new Intent(MainActivity.this,first.class);
startActivity(it);

}
});
}

@Override
public boolean onCreateOptionsMenu(Menu menu) {
// Inflate the menu; this adds items to the action bar if it is present.
getMenuInflater().inflate(R.menu.activity_main, menu);
return true;
}

}
Screen Shots
SCREEN 1:
SCREEN 2:
SCREEN 3:
SCREEN 4:
SCREEN 5:
SCREEN 6:
SCREEN 7:
SCREEN 8:
SCREEN 9:
SCREEN 10:
SCREEN 11:
SCREEN 12:
SCREEN 13:
SCREEN 14:
SCREEN 15:
SCREEN 16:
 6. TESTING AND VALIDATION
The development of software systems involves of a series of production activities where
opportunities for injection of human fallibilities are enormous. Errors may begin to occur at the
very inception of the process where the objectives may be erroneously or imperfectly specified,
as well as in later design and development stages. Because of human inability to perform and
communicate with perfection, software development is accompanied by a quality assurance
activity.

6.1.TESTING TECHNIQUES

Testing is the process of executing a program with the intention of finding errors. The various
test strategies used for testing the software are as follows.

6.1.1. Unit Testing

Unit testing focuses on verification effort on the smallest unit of the software design module. The
main goal is to make sure that every source statement and logic path has been executed correctly
at least once. The output of this stage is the source code.

6.1.2. Integration Testing

In Integration testing, we find errors that have occurred during the integration. After testing each
module, which is then integrated into subsystems and then to form the entire system on which
integration testing is performed. The goal of testing is to detect the design errors, while focusing
on the testing the interconnection between modules.

6.1.3. Validation Testing

This testing concentrates on confirming that the software is error-free in all respects. All the
specified validations are verified and the software is subjected to hard-core testing. It also aims at
determining the degree of deviation that exists in the software designed from the specification;
they are listed out and are corrected.
6.1.4. System Testing

In this testing, the system is tested for the errors after coupling all the modules together The
system is tested against the specified requirements to see if all the requirements are met and the
system performs as specified by the requirements.

6.1.5.Test cases

Test case 1: Database creation and updating. Priority (H, L): High
Test Objective: For database creation.
Test Description: User selects book name
Requirements Verified: Yes
Test Environment: Application must be deployed in android mobile phone or emulator.
Test Setup/Pre-Conditions:

Actions Expected Results

The user will select book with details Stores the book details in
database
Pass: Yes Conditions pass: Yes Fail: No
Problems / Issues: NIL
Notes: Successfully Executed

A test case is a software testing document, which consists of event, action, input, output,
expected result and actual result. Larger test cases may also contain prerequisite states or steps,
and descriptions. A test case should also contain a place for the actual result. These steps can be
stored in a word processor document, spreadsheet, database or other common repository.

Test case 2: Searching for books Priority (H, L): High

Test Objective: For database creation.
Test Description: User enters book name
Requirements Verified: Yes
Test Environment: Application must be deployed in android mobile phone or emulator.
Test Setup/Pre-Conditions:
Actions Expected Results
The user enter book name Searches books based on
pattern matching.
Pass: Yes Conditions pass: Yes Fail: No
Problems / Issues: NIL
Notes: Successfully Executed

Test case 2: Adding books into internal database Priority (H, L): High
Test Objective: For database creation.
Test Description: User enters book name
Requirements Verified: Yes
Test Environment: Application must be deployed in android mobile phone or emulator.
Test Setup/Pre-Conditions:
Actions Expected Results
The user selects required book among the list of Add the book into database
books
Pass: Yes Conditions pass: Yes Fail: No
Problems / Issues: NIL
Notes: Successfully Executed
 CONCLUSION
7.Conclusion:

This application is used for The user can know the various levels of recruitment procedure followed
by different MNC’s. It also contains other information like the location of the company, images,
contact details etc.Once the user opens the application, he can know this information by selecting
the company from the list of MNC’s displayed.
 REFERENCES

8. REFERENCES

1. Herbert Schildt.2008 ,”Java Complete Reference”, Tata McGraw-Hill ,

7th Edition, pp.177-180 .

2. Grady Booch, James Rambaugh.1998,“UnifiedModeling Language User Guide”,

Addison Wesley Publishing, chapter 8-31.

WEBSITES: REFERRED URLS:

www.android.com http://developer.android.com/index.html

www.google.com http://en.wikipedia.org/wiki/SQLite