Table of Contents

Page
Chapter Contents
No.
1. Introduction 4
1.1 Synopsis of the Project 4
1.1.1 About the Organization 4
1.1.2 About the Project 6

1.2 Objective & Scope of the Project 7

1.3Problem Definition 7
1.4 Theoretical Background 8
1.4.1 Overview of Front End 8
1.4.2 Overview of Back End 10
1.4.3 Overview of Reporting Tool 12

2. System Analysis 15
2.1 Feasibility Study 15
2.1.1 Technical 15
2.1.2 Operational 16
2.1.3 Resource 16
2.2 System Planning and Schedule 18
2.2.1 GANTT Chart 18

2.2.2 PERT Table 19

2.2.3 PERT Chart 19
2.2.4 Mind Map 20
2.2.5 Time Line 21
2.2.6 Work Break down Structure 22
2.2.7 Cause Effect Diagram

3. System Design 23
3.1 Software Requirement Specification 23

1
 3.1.1 Introduction 23
3.1.2 Selection of Technology/Specific Requirements 23
3.1.2.1 Hardware to be used 23
3.1.2.2 Software to be used 24
3.1.2.3 Tools to be used 24
3.2 Methodologies Adapted 30
3.3 Detailed life Cycle of the Project 34
3.3.1 Object Oriented Analysis & Design Diagrams 34
3.3.1.1 Use Case Diagram 34
3.3.1.2 Activity Diagram 35
3.3.1.3 Sequence Diagram 40
3.3.1.4 Component Diagram 41
3.3.1.5 Deployment Diagram 41
3.3.2 Flow Chart 42
3.3.3 Data flow diagram 46
3.3.4 Decision Tree 52
3.3.5 Decision Table 53
3.3.6 Database 54
3.3.6.1 Database Table 54
3.3.6.2 Data Dictionary 54
3.3.6.3 ER Diagram 63
3.3.7 I/0 Screen Layout 64
3.3.8 Processes Involved 81
3.3.9 Design Testing

4. Testing 86
4.1 Methodologies used for testing 86
4.2 Types of Testing 90
4.2.1 White Box Testing 90
4.2.2 Black Box Testing 91

2
 4.3 Test Report 93
4.3.1Testing & Result 93
4.4 Check List 94

5. System Implementation 67
5.1 Hardware required at Client Side 67
5.2 Software required at Client Side 67
5.3 Testing Done As End User

6. System Maintenance & Evaluation 68

6.1 Maintenance 68
6.2 Evaluation 79

7. User/Operational Manual 71
7.1 Security Aspects, Access Rights 71
7.2 Screen Shots 72

8. Future Enhancements 84

9. Limitations 85

10. Conclusion 86

11. Appendices 87

12. Bibliography 88

3
 1. Introduction

1.1 Synopsis of the Project

1.1.1 About the Organization

BLUE STAR INFOTECH LIMITED (BSIL):

Blue Star Infotech is an IT consulting firm and has been in operation for more than

30 years. It has offices in USA, UK, Europe, India, Singapore and Malaysia. Blue

Star Infotech is a public company listed on the Bombay Stock Exchange (BSE) and

National Stock Exchange (NSE) of India.

It is a part of the Blue Star Group, a USD 750 million conglomerate with a rich 70-

year history.

Blue Star Infotech helps global enterprises derive measurable business outcomes

through the efficient use and adoption of information technology. It works in the

space of Mobility, Cloud Computing, Analytics & Business Intelligence, Product

Engineering, Testing, Package Implementation and Applications Services.

It has a Global Delivery network that spans across India (Mumbai and Bangalore),

USA (Milwaukee, WI), and Singapore.

With access to a diverse pool of specialized talent and employee strength of about

1300, Blue Star Infotech has partnered with over 250 technology companies and

4
300 enterprises across the globe. The company has completed more than 800 major

IT projects and has delivered more than 1600 product releases for its technology

customers worldwide.

Its clients include business leaders in industries such as Manufacturing, Travel &

Hospitality, Media & Entertainment, Hi-Tech, and Healthcare. It is reputed for its

financial stability over the past 30 years and has yet been responding in a nimble

way to the changing global ecosystem.

Blue Star Infotech employees like the progressive work culture, our reimbursement

policy for certain certifications, a structured training calendar, a sabbatical leave

policy, flexible working hours, health check- ups/camps, upwards and peer

feedback through 360 degree surveys, medical insurance & accident insurance

policy and of course, discounts on Blue Star products like Air Conditioners.

5
1.1.2 About The Project

INTERVIEW TRACKING SYSTEM:

Existing System

Project managers generate project requirement. HR selects candidates as per

manager’s requirement by resume scanning, schedules interview and allots

interview panel. Candidate acts as an interviewee and participates in various

interview rounds. Panel acts as an interviewer and provides feedback.

This entire process is carried out manually and documented using paper (hard

copy) or electronic (soft copy) documents. Thus each participant has different copy

of document in case of miscommunication. Manual processing of information leads

to ambiguities, inconsistency and processing delays.

6
 Absence of central data store produces difficulties in data retrieval and storage.

Also it makes status tracking of process very difficult. That is managers, panel and

HR personals cannot find out current status of requirement or interview if there is

no online solution with central data store.

Proposed System

In the proposed system, Interview Tracking System, interview process gets

computerized. The key participants of this system are: Project Managers, HR

personal and Panel and Administration personals.

Project Manager submits his requirements using Requirement Module.

As per those requirements HR personal selects candidates and using Candidate

Module, enters their details and then schedules interview for each. An automatic

mail notification is sent to allotted panel and its manager to inform them about

Interview.

Panel Module contains panel details like their manager, mail and skills, which

allows HR for efficient panel allotment by comparing required skills and panel

skills.

Interview Panel takes interview and gives feedback using Candidate Module

Feedback page.

Based on this feedback HR and Manager decide the interview result, which can

be cleared, rejected or on hold. Cleared candidate is then scheduled for next round.

This process continues until final round.

7
1.2 Objective and Scope of the Project
Objective

● Main objective is to keep track of entire interview process and record all the

crucial details.

● Make data processing computerized which includes addition, updating,

deletion and retrieval of data as and when required.

● Make all the required details like details of candidate, interview panel, and

project requirements available online, so it can be accessed from anywhere

and at any time.

● Central database to reduce data redundancy and ambiguity which can be

accessed through efficient GUI.

● To provide reminders of scheduled interview and pending feedbacks

● Another important objective is to develop responsive user interface that

adjust itself according to device.

● Create mobile friendly interface, so that all details can be accessed

seamlessly through any mobile.

Scope

● Interview process has 4 key participants’ viz. Project managers who

generate project requirement, HR who organizes interview, Panel who acts

8
 as an interviewer and Candidates who act as an interviewee. The produced

solution is only accessible to Managers, HR and Panel.

● Candidates will not have access to the produced solution

● Loosely coupled system for seamless future modifications.

1.3 Problem Definition

● Manual Process: Existing process is mostly manual with no computerized

processing

● Decentralized Data: All the data is stored and communicated using paper (hard
copy) or electrical (word, excel) documents (soft copy) and not on central database.
Hence each participant has different version of data.

● Repetition Of work: Lack of communication or miscommunications lead to

repetition of work.

● Low resource utilization: Decentralized data causes inefficient resource utilization

like inefficient panel allotment.

● Time consuming: Manual work leads to processing delays.

● Interview tracking impossible: Status tracking of individual interview is not

possible.

● Lack of security: The details and information’s about the vehicles are highly vital.
Since data are stored in a particular system, it is freely available to anyone. If the
information falls into the wrong hands, it can be processed in a wrong way.

● Inconsistency: Data might get misplaced during manual filling. So data won't be
preserved properly for future use.

9
1.4 Theoretical Background

1.4.1 Overview Of Front End

ASP.NET MVC4

ASP.NET MVC 4 is a framework for building scalable, standards-based

web applications using well-established design patterns and the power of

ASP.NET and the .NET Framework.

 Key Features

● ASP.net Web API

●  Enhancements to Default Project Templates

10
 ● Mobile Project Template

● Display Modes

● jQuery Mobile, the View Switcher, and Browser overriding

● Azure SDK

● Database Migrations

● Empty Project Template

● Add Controller to any project folder

● Bundling and Minification

● Enabling Logins from Facebook and Other Sites Using OAuth and OpenID

jQuery Plugins, Validations and jQuery Ajax

Metronic - Responsive Admin Dashboard Template

Metronic is a responsive and multipurpose admin and frontend

theme powered with Twitter Bootstrap 3.1.1 Framework.

11
 Metronic can be used for any type of web applications: custom admin

panels, admin dashboards, ecommerce back ends, CMS, CRM, SAAS and

websites: business, eCommerce.

Metronic has a sleek, clean and intuitive metro & flat balanced design

which makes project look awesome and yet user friendly. Metronic has a huge

collection of plugins and UI components and works seamlessly on all major

web browsers, tablets and phones.

Metronic comes with 8 complete themes: Metronic Admin, Metronic

Admin RTL Version, MetroniceCommerce Frontend, MetroniceCommerce

Frontend RTL Version, Metronic Corporate Frontend, Metronic Corporate

Frontend RTL Version, Metronic One Page Parallax Frontend and Metronic

One Page Parallax Frontend RTL Version.

CanvasJS HTML5 & JavaScript Charts

12
 CanvasJS is an easy to use HTML5 & JavaScript Charting library built on

Canvas element. Graphs can render across devices including iPhone, iPad,

Android, Windows Phone, Desktops, etc. This allows to create rich dashboards

that work on all devices without compromising on maintainability or

functionality of your web application. Charts include several good looking

themes and is over 10x faster than conventional Flash and SVG Charts –

resulting in lightweight, beautiful and responsive dashboards.

Key Features

● Very simple to use

● Works across all devices and browsers and good Performance

● Well Documented

● Support directly from developers

1.4.2 Overview Of Back End

13
 SQL Server 2008 R2

SQL Server is a relational database management system (RDBMS) from

Microsoft that's designed for the enterprise environment. SQL Server runs on

T-SQL (Transact -SQL), a set of programming extensions from Sybase and

Microsoft that add several features to standard SQL, including transaction

control, exception and error handling, row processing, and declared variables.

It is said to provide enhanced flexibility, scalability, reliability, and security

to database applications, and to make them easier to create and deploy, thus

reducing the complexity and tedium involved in database management.

Key features of SQL Server 2008 R2

● Scalability and Performance

● High Availability

● Replication

● Enterprise Security

● Application and Multi-Instance Management

14
 ● Management Tools

● Development Tools

● Programmability

● Complex Event Processing (Stream Insight)

● Integration Services

● Data Warehouse

● Analysis Services

● Data Mining

● Reporting

● Business Intelligence Clients

2. System Analysis

2.1 Feasibility Study

The Feasibility study is an analysis of possible alternative solutions to a

problem and a recommendation on the best alternative. It can decide whether a

process be carried out by a new system more efficiently than the existing one.

15
 Things to be studied in the feasibility study:

● The present organizational system

● Stakeholders, users, policies, functions, objectives...

● Problems with the present system

● Inconsistencies, inadequacies in functionality, performance…

● Possible solution alternatives

● Sticking with the current system” is always an alternative

● Different business processes for solving the problems

● Different levels/types of computerization for the solutions

● Advantages and disadvantages of the alternatives

2.1.1 Technical

The technical feasibility explores—if the project feasibility is within

the limits of current technology (hardware and software) and does the

technology exist at all, or if it is available within given resource constraints

(i.e., budget, schedule).

The proposed Application system is technical feasible because-

● The proposed solution is practical and workable.

● The necessary technology -H/W configuration and software

platform (Microsoft tools and license, Metronic License) is

already there.

● The necessary technical expertise is available.

● The H/W and S/W required are easy to install and handle

16
 ● The application supports interactivity with the user through GUI

● The required technology is available within necessary resource

constraints (i.e., budget, schedule) as it is internal project.

2.1.2 Operational

  Operational feasibility also performs the following tasks:

● Determines whether the problems anticipated in user requirements are

of high priority

● Determines whether the solution suggested by the software

development team is acceptable

● Analyses whether users will adapt to a new software

● Determines whether the organization is satisfied by the alternative

solutions proposed by the software development team.

The PIECES framework can help in performing operational

feasibility, by reviewing six factors –Performance/ Response Time,

Information, Economy, Control, Efficiency, Service

Proposed system is operation feasible because of the following

reasons:-

Performance: System will provide adequate throughput and response time.

Information: System will provide end users and managers with timely,

accurate and usefully formatted information.

Economy: New System will provide cost-effective information by reducing

manual paper work.

17
 Control: It will offer effective controls to protect against fraud and to

guarantee accuracy and security of data and information through

authentication.

Efficiency: It will make maximum use of available resources, including

people, time.

Services: Expandability will be maintained in the new system as New

modules can be added later on the application, if required in the

future. Also the application will have User-friendly Forms and Screens.

2.1.3 Resource
This involves questions such as how much time is available to

build the new system, when it can be built, whether it interferes with

normal business operations, type and amount of resources required,

dependencies.

Proposed system is resource feasible because the necessary

technology -H/W configuration and software platform (Microsoft tools and

license, Metronic License) is already there within given resource constraints

(i.e., budget, schedule).

2.2 System Planning And Schedule

2.2.1 GANTT Chart

18
 Figure: 2.1: Gantt chart

2.2.2 PERT Table

19
 Figure 2.2: Pert Table

2.2.3 PERT Chart

Figure 2.3: Pert chart

2.2.4 Mind Map

20
 Figure2.4: Mind Map

2.2.5 Timeline

21
 Figure2.5: Timeline

2.2.6 Work Breakdown Structure

22
 Figure2.6: Work Breakdown Structure

2.2.7 Cause Effect Diagram

23
 Figure 2.7: Cause Effect

24
 3. System Design

3.1 Software Requirement Specification

3.1.1 Introduction
After the all the required information about the project to be developed is

gathered and the inconsistencies, incompleteness and anomalies in them have

been removed, a formal specification that systematically states the requirements

using which the project will be developed is drafted. This specification is called

Software Requirement Specification Document. Different people need SRS for

different purposes. Following are few categories to which SRS can be essential:

Users, Customers: Having an SRS to them are means to ensure that the system

as described will meet their needs.

Software Developers: They need this document to make sure that they are

developing exactly what is required by their customer.

SRS was constantly referred to while developing Interview Tracking System

to keep track of requirements being completed. Using the information drafted in

25
 this document the schedule involved in development of this project was decided

and finalized. It was referred during the design of test cases. SRS has come

handy in case of any doubts that rose during the development phase.

SRS is used as a reference document which can also serve as a contract

between the customer and the developer. In case of any disagreements SRS is

referred to solve the disputes. One can even consider it to a legal document.

3.1.2 Selection Of technology/Specific Requirements

3.1.2.1 Hardware To Be Used

● AMD or Intel Pentium Processor or Higher (1.6 GHz or faster

processor)

● Minimum 2GB Ram or higher

● Minimum 40GB Hard disk

3.1.2.2 Software To Be Used

● Operating system: Windows 7 Service Pack 1

3.1.2.3 Tools To Be Used

● Microsoft Visual Studio Express 2012 for Web

Microsoft Visual Studio is an integrated development

environment (IDE) from Microsoft. It is a complete set of

development tools for building ASP.NET Web applications, XML

Web Services, desktop applications, and mobile applications. Visual

Basic, Visual C#, and Visual C++ all use the same integrated

development environment (IDE), which enables tool sharing and

eases the creation of mixed-language solutions. In addition, these

26
 languages use the functionality of the .NET Framework, which

provides access to key technologies that simplify the development of

ASP Web applications and XML Web Services.

Visual Studio includes a code editor supporting IntelliSense as

well as code refactoring. The integrated debugger works both as a

source-level debugger and a machine-level debugger. Other built-in

tools include a forms designer for building GUI applications, web

designer, class designer, and database schema designer. It accepts

plug-ins that enhance the functionality at almost every level—

including adding support for source-control systems (like

Subversion) and adding new toolsets like editors and visual

designers for domain-specific languages or toolsets for other aspects

of the software development lifecycle (like the Team Foundation

Server client: Team Explorer).

Visual Studio Express 2012 for Web provides the core tools for

web development. You can use the full-featured code editors,

design-time tooling, rich language support, and other tools in Visual

Studio Express 2012 for Web to create innovative and compelling

ASP.NET apps and services for the web.

● SQL Server 2008 R2

SQL Server is a relational database management system

(RDBMS) from Microsoft that's designed for the enterprise

environment. SQL Server runs on T-SQL (Transact -SQL), a set of

programming extensions from Sybase and Microsoft that add several

27
 features to standard SQL, including transaction control, exception

and error handling, row processing, and declared variables.

It is said to provide enhanced flexibility, scalability, reliability,

and security to database applications, and to make them easier to

create and deploy, thus reducing the complexity and tedium involved

in database management.

Key features of SQL Server 2008 R2

● Scalability and Performance

● High Availability

● Replication

● Enterprise Security

● Application and Multi-Instance Management

● Management Tools

● Development Tools

● Programmability

● Complex Event Processing (Stream Insight)

● Integration Services

● Data Warehouse

● Analysis Services

● Data Mining

● Reporting

● Business Intelligence Clients

● Metronic - Responsive Admin Dashboard Template

28
 ● Metronic is a responsive and multipurpose admin and

frontend theme powered with Twitter Bootstrap 3.1.1

Framework.

● Metronic can be used for any type of web applications:

custom admin panels, admin dashboards, ecommerce back

ends, CMS, CRM, SAAS and websites: business,

eCommerce.

● Metronic has a sleek, clean and intuitive metro & flat

balanced design which makes project look awesome and yet

user friendly. Metronic has a huge collection of plugins and

UI components and works seamlessly on all major web

browsers, tablets and phones.

● Metronic comes with 8 complete themes: Metronic Admin,

Metronic Admin RTL Version, MetroniceCommerce

Frontend, MetroniceCommerce Frontend RTL Version,

Metronic Corporate Frontend, Metronic Corporate Frontend

RTL Version, Metronic One Page Parallax Frontend and

Metronic One Page Parallax Frontend RTL Version.

29
3.2 Methodologies Adapted

3.2.1 Agile Model

● Agile methodology is an alternative to traditional project management,

typically used in software development

● Agile methodologies are an alternative to waterfall, or traditional sequential

development.

30
 Figure 3.1: Agile model

Agile development methodology provides opportunities to assess the

direction of a project throughout the development lifecycle.

This is achieved through regular cadences of work, known as sprints or

iterations, at the end of which teams must present a potentially shippable product

increment.

By focusing on the repetition of abbreviated work cycles as well as the

functional product they yield, agile methodology is described as “iterative” and

“incremental.”

In waterfall, development teams only have one chance to get each aspect of a

project right. In an agile paradigm, every aspect of development — requirements,

design, etc. — is continually revisited throughout the lifecycle.

When a team stops and re-evaluates the direction of a project every two

weeks, there’s always time to steer it in another direction.

The results of this “inspect-and-adapt” approach to development greatly

reduce both development costs and time to market.

Because teams can develop software at the same time they’re gathering

requirements, the phenomenon known as “analysis paralysis” is less likely to

impede a team from making progress.

31
 ● Requirements phase: Requirements for the software are gathered and

analysed. Iteration should eventually result in a requirements phase that

produces a complete and final specification of requirements.

● Design phase: Software solution to meet the requirements is designed. This

may be a new design, or an extension of an earlier design.

● Testing phase: Software is integrated and tested.

● Review phase: Software is evaluated, the current requirements are

reviewed, and changes and additions to requirements proposed.

● Acceptance and Deployment phase: Software is deployed to the customer

and starts accomplishing the desired work.

Advantages of Agile model:

● Customer satisfaction by rapid, continuous delivery of useful software.

● People and interactions are emphasized rather than process and tools.

Customers, developers and testers constantly interact with each other.

● Working software is delivered frequently (weeks rather than months).

● Face-to-face conversation is the best form of communication.

● Close daily cooperation between business people and developers.

● Continuous attention to technical excellence and good design.

● Regular adaptation to changing circumstances.

● Even late changes in requirements are welcomed.

32
 Disadvantages of Agile model:

● In case of some software deliverables, especially the large ones, it is

difficult to assess the effort required at the beginning of the software

development life cycle.

● There is lack of emphasis on necessary designing and documentation.

● The project can easily get taken off track if the customer representative is

not clear what final outcome that they want.

● Only senior programmers are capable of taking the kind of decisions

required during the development process. Hence it has no place for newbie

programmers, unless combined with experienced resources.

33
3.3 Detailed Lifecycle Of The Project

3.3.1 Modules
● Master Module:
It includes following master forms -

1) Skill Set: Deals with Add, Edit, Delete of skills [C#, .Net, MVC]

2) Location: Deals with Add, Edit, Delete of Branches [Mumbai,

Bangalore]

3) Candidate Preference: Deals with Add, Edit, Delete of candidate type

[Intern, Employee]

4) Interview Status: Deals with Add, Edit, Delete of interview status

[Cleared, Rejected]

5) Interview Type: Deals with Add, Edit, Delete of interview type

[Telephonic, Scan]

6) Round: Deals with Add, Edit, Delete of interview rounds [HR,

Managerial]

7) Required Status: Deals with Add, Edit, Delete of requirement status

[Open, Close]

● Candidate Module:

1) View, Add, Update, Delete and Search candidate information which

includes candidate name, candidate resume [upload and download],

received date, source.

2) Each candidate has Interview Schedule link, which allows to View, Add,

Update, Delete and Search schedule information which includes project

name, interview type, interview round, interview date and time, interview

34
 panel and interview status for that particular candidate. An automatic

email notification will be sent to a panel for every schedule interview.

3) Each schedule has Feedback link, which allows giving feedback using

star rating control against require skill [like C#, MVC etc.] and textual

remarks.

● Requirement Module:

1) Allows to View, Add, Update, Delete and Search project requirement

information which includes candidate preference, location, impact,

project name, requester’s name and requestor date, required date,

experience, status of this requirement, closed date.

2) Every requirement has Required Skillset link, which allows to View,

Add, Update, Delete and Search skills required.

● Panel Module:

1) Allows to View, Add, Update, Delete and Search panel information

which includes panel name, grade and email, supervisor name and email.

2) Each panel has Panel Skillset link, which allows to View, Add, Update,

Delete and Search skills of that particular panel.

● Dashboard:

1) Interview Schedules for logged in Panel

2) Pending feedbacks of logged in Panel

3) Candidate interview status chart and details

4) Top requirements chart and details based on interviews scheduled for

them.

35
 3.3.2 Object Oriented Analysis And Design Diagrams
3.3.2.1 Use Case Diagrams

Project Manager

Figure 3.2: Use-Case Diagram for Project Manager

36
 HR Manager

Figure 3.3: Use-Case Diagram for HR Manager

37
 Panel

Figure 3.4: Use-Case Diagram for Panel

38
 3.3.2.2 Activity Diagrams

39
 Figure 3.5: Activity Diagram of system

3.3.2.3 Sequence Diagrams

Figure 3.6: Sequence Diagram of System

40
 3.3.2.4 Component Diagram

Figure 3.7: Component Diagram for Interview Tracking

41
 3.3.2.5 Deployment Diagram

Figure 3.8: Deployment Diagram for Interview Tracking

42
 3.3.3 Flow Chart

43
 Figure3.9: FLOW CHART FOR LOGIN

44
 Figure 3.10: FLOW CHART FOR MASTER MODULE

45
 Figure 3.11: Flow Chart for Requirement Module

46
 Figure 3.12: Flow Chart for Panel Module

47
 Figure 3.13: Flow Chart for Candidate Module

48
 3.3.4 Data Flow Diagram

Context Level

Figure 3.14: Context Level DFD

49
 First Level

Figure 3.15: First Level DFD

50
 Second Level

51
 Figure 3.16: Second Level DFD

Third Level

Figure 3.17: Third Level DFD

52
 3.3.5 Decision Tree

53
Figure 3.18: DECISION TREE FOR INTERVIEW TRACKING SYSTEM

3.3.6 Decision Table

54
 Table 3.1: DECISION TABLE

Conditi Rules
ons/
Course
Of 1 2 3 4
Actions
Dashboard data and
Y - - -
charts not displayed
Selected form’s / page’s
Y Y - -
data not available
Conditions
Addition/Updating not
Y - Y -
occurring
Delete not occurring Y - - Y
Database empty , insert
X X
required data
Validation errors, enter
X
valid data
Actions Database server down,
X X X X
check connection
Check if being
X
referenced
Check login credentials X

3.3.7 Database
3.3.7.1 Database Table

3.3.7.2 Data Dictionary

55
 3.3.7.3 ER Diagram

Figure 3.19: ENTITY RELATIONSHIP DIAGRAM FOR INTERVIEW

TRACKING SYSTEM

56
Architectural Design

Figure 3.20: Architectural Design for Interview Tracking

57
 3.3.8 I/O Screen Layout

Figure 3.21: Login Page Design

58
 Figure 3.22: Dashboard Design

59
 Figure3.23: General Page Layout

3.3.9 Processes Involved

60
 MODULE: MASTER
Table 3.2: MASTER MODULE PROCESSES

PROCESS
PROCESS DESCRIPTION
NO.

The user can save the entered

details about Skills, Candidate
Preferences, Interview Types,
1 Save
Interview Rounds, Locations,
Interview Statuses, and Required
Statuses.

User can enter multiple entries in

2 Save and Continue
one go.

The user can view the details about

Skills, Candidate Preferences,
3 Display Interview Types, Interview
Rounds, Locations, Interview
Statuses, and Required Statuses.

The user can modify the name of

Skills, Candidate Preferences,
4 Update Interview Types, Interview
Rounds, Locations, Interview
Statuses, and Required Statuses.

The user can delete specific

records of Skills, Candidate
Preferences, Interview Types,
5 Delete
Interview Rounds, Locations,
Interview Statuses, and Required
Statuses.

User can search specific entry

6 Search
using search bar.

61
 MODULE: CANDIDATE
Table 3.3: CANDIDATE MODULE PROCESSES

PROCESS
PROCESS DESCRIPTION
NO.

The user can save the entered

1 Save
details about Candidate.

The user can upload, download

2 Upload and Download
candidate resume.

The user can view the details about

3 Display
Candidate.

The user can modify the details of

4 Update
Candidate.

The user can delete specific

5 Delete Candidate, provided there is no
Interview Schedule associated.

The user can Schedule selected

6 Schedule
Candidate for an interview.

The user can save the entered

7 Save [Schedule]
details about Candidate Schedule.

The user can view the details about

8 Display [Schedule]
Candidate Schedule.

The user can modify the details of

9 Update [Schedule]
Candidate Schedule.

The user can delete specific

10 Delete [Schedule] Candidate, provided there is no
Interview Feedback associated.

62
 The user can provide feedback for
11 Feedback
selected Interview Schedule.

Every time an interview is

schedule an automatic schedule
12 Email
notification is sent to selected
interview panel through email

The user can save the entered

13 Save [Feedback]
details about InterviewFeedback.

The user can view the details about

14 Display [Feedback]
Interview Feedback.

The user can modify the details of

15 Update [Feedback]
Interview Feedback.

The user can enter, view and

16 Remarks
modify remarks for interview.

User can search specific entry

17 Search
using search bar.

MODULE: Requirement
Table 3.4: REQUIREMENT MODULE PROCESSES

PROCESS
PROCESS DESCRIPTION
NO.

The user can save the entered

1 Save
details about Project Requirement.

User can enter multiple entries in

2 Save and Continue
one go.

The user can view the details about

3 Display
Project Requirements.

63
 The user can modify the Project
4 Update
Requirement.

The user can delete specific Project

5 Delete
Requirement.

It allows user to crate copy of

existing requirement along with its
6 Copy
required skills but different
requirement name.

The user can add required skillset

7 Skillset for a particular Project
Requirement.

The user can save the entered

8 Save [skills]
details about Required Skills.

The user can view the details about

9 Display [skills]
Required Skills.

The user can modify the details of

10 Update [skills]
Required Skills.

The user can delete specific

11 Delete [skills]
Required Skill.

User can search specific entry

12 Search
using search bar.

MODULE: Panel
Table 3.5: PANEL MODULE PROCESSES

PROCESS
PROCESS DESCRIPTION
NO.

The user can save the entered

1 Save
details about Interview Panel.

64
 User can enter multiple entries in
2 Save and Continue
one go.

The user can view the details about

3 Display
Interview Panel.

The user can modify the Interview

4 Update
Panel.

The user can delete specific

5 Delete
Interview Panel.

The user can add required skillset

6 Skillset
for a particular Interview Panel.

The user can save the entered

7 Save [skills]
details about Panel Skills.

The user can view the details about

8 Display [skills]
Panel Skills.

The user can modify the details of

9 Update [skills]
Panel Skills.

The user can delete specific Panel

10 Delete [skills]
Skill.

User can search specific entry

11 Search
using search bar.

65
 4. Testing

4.1 Methodologies Used For Testing

Software testing is an investigation conducted to provide stakeholders with

information about the quality of the product or service under test. Software testing

also provides an objective, independent view of the software to allow the business

to appreciate and understand the risks of software implementation. Test techniques

include, but are not limited to, the process of executing a program or application

with the intent of finding software bugs (errors or other defects).

Software testing can also be stated as the process of validating and verifying

that a software program/application/product:

● Meets the business and technical requirements that guided its design and

development

● Works as expected; and

● Can be implemented with the same characteristics.

Primary purpose:

Testing is to detect software failures so that defects may be discovered and

corrected. This is a non-trivial pursuit. Testing cannot establish that a product

functions properly under all conditions but can only establish that it does not

function properly under specific conditions.

66
 Scope:

The scope of software testing often includes examination of code as well as

execution of that code in various environments and conditions as well as examining

the aspects of code: does it do what it is supposed to do and do what it needs to do.

In the current culture of software development, a testing organization may be

separate from the development team.

Implementation:

Software testing, depending on the testing method employed, can be

implemented at any time in the development process. However, most of the test

effort occurs after the requirements have been defined and the coding process has

been completed. As such, the methodology of the test is governed by the software

development methodology adopted.

67
 SOFTWARE TESTING MODEL

Figure 4.1: Structure of V-Model

The V-model involves building a logical V shape sequence where the

testing techniques associated with the design are reflected as descending and are

68
 applied for the “verification” and connected to the requirements or specifications

parts are reflected as ascending and are applied for “validation”.

The V-model ordains that the code testing documentation is written in

tandem with the development phases that means, for instance, the integration tests

should be documented as and when the high level design is finalized and the unit

tests should be ready as and when the detailed specifications are laid down.

The idea of the V-model is to have a implementation plan for the software

testing at each level namely component, interface, system, acceptance and release

of the software project which need to be adhered to eliminate discrepancies in the

software simultaneously rather than waiting for the software development process

to complete before handling it to the software testing professionals.

4.2 Types Of Testing

69
 4.2.1 White Box Testing
White box testing is performed based on the knowledge of how the system

is implemented. White box testing includes analyzing data flow, control flow,

information flow, coding practices, and exception and error handling within the

system, to test the intended and unintended software behaviour. White box testing

can be performed to validate whether code implementation follows intended

design, to validate implemented security functionality, and to uncover exploitable

vulnerabilities.

White box testing is used to test areas that cannot be reached from a black

box level. White box testing uses an internal perspective of the system to design

test cases based on internal structure. It requires programming skills to identify all

paths through the software. The tester chooses test case inputs to exercise paths

through the code and determines the appropriate outputs.

Branch coverage

Branch coverage exclusively considers the logical value of the result of a

condition (true or false). ‘Social Networking App’ contains many conditions which

has effect on overall working of the application. Selection of date range, category

has overall effect on expense. Such cases are tested in branch coverage.

Path coverage

Path coverage requires the execution of all different paths through the test

object. This is important with respect to mobile application. Application should

execute all the paths and should not crash in between.

4.2.2 Black Box Testing

70
 Black-box testing is a method of software testing that tests the functionality

of an application as opposed to its internal structures or workings. Specific

knowledge of the application's code/internal structure and programming knowledge

in general is not required.

Test cases are built around specifications and requirements, i.e. what the

application is supposed to do. It uses external descriptions of the software,

including specifications, requirements, and designs to derive test cases. These tests

can be functional or non-functional, though usually functional. The test designer

selects valid and invalid inputs and determines the correct output. There is no

knowledge of the test object's internal structure. This method of test can be applied

to all levels of software testing: unit, integration, functional, system and

acceptance.

Black-Box testing helps to find errors such as-

● Incorrect or missing functions

● Interface errors

● Errors in data structures

Equivalence class partitioning

Test case for input fields such as username, password, etc. are prepared and

tested. Equivalence class partitioning helps to reduce total time in testing by

dividing valid and invalid test cases.

Boundary value analysis

71
 Faults often occur at the boundary of equivalence classes, because

boundaries are not often defined clearly or misunderstood by programmers.

Application having range fields such as date ranges are tested using this technique.

State transition testing

In many cases, not only current input, but also the history of execution or

events or inputs, influences the outputs. Application has many fields such as date,

category which has different effects on overall application. Minor change in each of

them triggers changes in lot of input methods. These fields are tested under state

transition testing.

72
4.3 Test Report

4.3.1 Testing And Result

Sr. Expected
Test Case Actual Output Pass/Fail
No Output
1 Invalid Login Show Invalid Displayed Invalid Pass
Credentials Credentials Credentials
Message Message
2 Valid Login Redirect to Redirected to Pass
Credentials Dashboard Dashboard
3 No Records in Show ‘No Displayed ‘No Pass
Database Records’ Records’ Message
Message
4 No text in Show ‘Required Displayed Pass
Mandatory Fields Field’ Message ‘Required Field’
Message
5 No Value Selected Show ‘Select Displayed ‘Select Pass
for ‘Auto complete Field’ Message Field Message’
Textbox’
6 No File Selected For Show ‘Select Displayed ‘Select Pass
Resume File’ Message File’ Message

7 File other than Show ‘Select Displayed ‘Select Pass

Word format is Word File Only’ Word File Only’
selected Message Message

8 Interview Schedule Show ‘Invalid Displayed ‘Invalid Pass

Date and Time is Schedule Date Schedule Date’
Less than Current Message’ Message
Time
9 Master Records Show ‘Fill Displayed ‘Fill Pass
Empty Master’ Message Master’ Message

10 Duplicate Entry Show ‘Already Displayed Pass

Given’ Message ‘Already Given’
Message
11 Server Error Show ‘Server Displayed ‘Server Pass
Error’ Message Error’ Message
12 Ajax Error while Show ‘Server Displayed ‘Server Pass
fetching data Error’ Message Error’ Message
13 Record being Disabled link Disabled link Pass
referenced
14 Search a particular Display searched Displayed Pass
record using search record Searched record
bar
15 Add new entry using New entry in New entry in Pass
New button database and in database and in

73
 table on page table on page
16 Edit a record using Corresponding Corresponding Pass
edit link changes should changes gets
get reflected reflected
17 Delete a record Record gets Record gets Pass
deleted deleted
18 Experience of Display error Displays error Pass
candidate is less message message
than zero or greater
than 60
19 Score of panel skill Display error Displays error Pass
or required skill is message message
greater than 5 or less
than zero
20 Error occurs Highlight input Highlights input Pass
with error icon with error icon
and display error and displays error
message message
21 Wrong email entry Display error Display error Pass
message message
22 Upload resume in Display error Displays error Pass
format other than message ‘Only message ‘Only
MS-word word format word format
allowed’ allowed’
23 New interview is Send email to Sends email to Pass
scheduled or allotted interview allotted interview
Schedule is edited panel which panel which
contains contains schedule
schedule details details
24 Click on download Prompt for login Prompts for login Pass
link from email and download and downloads
resume of resume of
scheduled scheduled
candidate candidate
25 Page content Page content Page contents Pass
responsiveness adjust according adjust according
to screen to screen
resolution resolution
26 Modal Popup Modal popup Modal popup Pass
responsiveness adjust according adjusts according
to screen to screen
resolution resolution
27 Grid responsiveness Table content Table content Pass
flips to show flips to show
responsive grid responsive grid
28 Chart Chart size Chart size adjusts Pass
responsiveness adjusts as per as per screen
screen resolution resolution

74
 5. System Implementation

5.1 Hardware Required At Client Side

● For User

This Web Application only needs a device (desktop or tablet or smart

phone) which has web browser with net connection, due to its Responsive

Web Design. Thus system requirements of a browser will serve as system

requirement of this application. For instance

For machine having Firefox 28.0 and Windows Operating System recommended

hardware:

▪ Pentium 4 or newer processor that supports SSE2

▪ 512MB of RAM

▪ 200MB of hard drive space

The web application can also be accessed easily from any mobile device having
system specification to support internet.

5.2 Software Required At Client Side

For User

● Web Browser(Java Enabled)

● Better Performance On

● IE9, Chrome V.34, Firefox V.27 And Above

For Deployment Server

● .Net framework 4.0

● IIS

● SQL Server R2 2008

75
5.3 Testing Done As End User

Acceptance Testing:Acceptance testing is performed after system testing is done

and all or most of the major defects have been fixed. The goal of acceptance testing

is to ensure the end user/customer that software/system that has been developed

meets their requirements.Acceptance testing is done in production kind of

environment.

Thus we tested the developed application, Interview Tracking System, in various

devices like HTC smartphone, Apple’s iPad2 (safari browser),and client machines.

Beta Testing:Beta testing is also known as field testing, it is done by potential or

existing users/customers at an external site without developers involvement, this

test is done to determine that the software satisfies the end user’s needs.

Thus Interview Tracking System was tested by various end users

From these we found out various positioning issues, which were very serious from

client’s point of view as Responsiveness of web site was important requirement.

These issues were resolved immediately.

76
 6. System Maintenance And Evaluation

6.1 Maintenance
Maintenance is an enigma of the system development. It holds the software

industry captive. Analysts spend more time in maintaining programs than coding

them. Software maintenance denotes any changes made to the software product

after it has been delivered to the customer. Most products need maintenance due to

the wear and tear of the product. Software Maintenance can be divided into

following types:

▪ Corrective Maintenance: It is necessary to rectify the bugs observed while the

system is in use. Interview Tracking System needs this maintenance for any

removing flaws that can arise while sending the data or for correcting the logical

bugs that might have been left unchecked as they appear only in real time like

empty database.

▪ Perfective Maintenance: Software product might need maintenance to support the

new features that users want it to support, to change different functionalities of the

system according to the customer demands, or to enhance the performance of the

system. Interview Tracking Systemneeds this maintenance for removing the short

falls of its current features.

Software Maintenance is essential as initial stages of any software developed

are always unstable. Over the time it achieves stability as bugs are fixed and faults

are removed to make the system accurate.

77
 System Maintenance is often termed as the task of doing repairs to the

developed system. When websites are inaccessible due to attacks from hackers,

server problems or for updating and repair, the administrators of the website will

often display an image apologizing for System Maintenance and Website

downtime. This allows the user to understand that the website cannot be used and

that the administrators are aware of the issue.

6.2 Evaluation
System Evaluation is termed as the task of evaluating the success and failure

of the system. It is performed with the help of following two V’s:

Verification:

Verification determines whether the system is built correctly and does not

contain technical errors. It also involves the review of the requirements, to verify

that the right problem is being solved. Verification also ensures that the system is

syntactically and logically correct and performs functionally as being specified. It is

a static practice of verifying documents, design, code and program.

As verification relates to the humanized effort of checking the documents and

files, we have taken utmost care to see to it that the application conforms to

specifications. Reviews and inspections were carried out periodically. The web

based application has been put through the process of Verification successfully.

Validation:

Validation on the other hand is a difficult task of insuring the meaning and

content of the rules meet some carefully defined criteria of adequacy. Defining such

78
criteria is the key to successfully conduct Validation procedure and demonstrating

the level of acceptability of the system.

As Validation is a dynamic mechanism of validating and testing the actual

product; we have implemented the process of validation by executing the code

thoroughly. By performing White Box as well as Black Box testing; along with

Acceptance Testing, we have made sure that the application adheres to customer’s

expectation and requirements.

The target for validation was actual product-a unit, a module, a bent of

integrated modules, and effective final product.

Verification process describes whether the outputs are according to inputs

or not. Validation process describes whether the software is accepted by the user or

not.

79
 7. User/Operational Manual

7.1 Security Aspects

What is Authentication?

Authentication is the process of identifying who users are when they visit a
Web site.

When to use Windows Authentication?

In intranet applications inside your corporate domain, you typically use

Windows authentication. Windows authentication enables Web applications in a

Windows domain to take advantage of the domain infrastructure for authenticating

users. However, do not use Windows authentication if users who must be

authenticated access your Web site from behind firewalls and proxy servers.

The web application uses windows based authentication because it is an

intranet application. Thus only company employees can only access this web

application using their assigned credentials.

What is Authorization?

Authentication is typically used in combination with authorization.

Authorization is the process of determining whether a user has permissions to

access a particular resource or to perform some action. For example, when an end

user accesses a URL using a browser, ASP.NET can authenticate the user and then

80
 examine the authorization rules for the requested resource to determine whether the

user has permission to access it.

The Web application does not use any authorization currently, but it will in

the future. Thus allowing role based view to every user.

7.2 Screen Shots

Login

Figure 7.1: Login Screen

This is Login page, which allows only company employees within company
domain (bsil) to access the web application using their credentials because of Windows
Authentication.

81
Dashboard

Figure 7.2: Dashboard Screen

This is home page/ dashboard, which provides following:

● Details of Scheduled Interview for logged in panel.

● Details of Pending interview feedbacks which were taken by logged in panel.

● Candidate interview status chart showing candidate count for each interview status.

82
● Top requirement chart showing candidate count for top requirements.

Figure 7.3: Dashboard Screen with interview status

83
 Figure7.4: Dashboard Screen with top requirements

Master

Figure 7.5: Skill Master

This is a skill master page which deals with various skills Like [C#, .Net, MVC] required
for project. Also allows user to add new skills using New button and edit existing skills
using edit link under Action. Searching is provided using search bar.

84
 Figure 7.6: Location Master

This is a Location master which deals with various branches Like [Mumbai, Bangalore] of
organization. Allows user to add new location using New button, edit and delete specific
location using edit and delete link under Action and search functionality.

85
 Figure 7.7: Candidate Preference Master

This is Candidate Preference master which deals with candidate type Like [Intern,
Employee]. Provides user to add, edit delete and search Preferences.

86
 Figure 7.8: Required Status Master

This is Required Status master which deals with Requirement status Like [Open, Close].
Provides user to add, edit delete and search Required Statuses.

87
 Figure 7.9: Interview Type Master

This is Interview Type master which deals with Interview types Like [Telephonic, In
person]. Provides user to add, edit delete and search Interview Types.

Simillarly Rounds master which deals with interview rounds like [HR, Managerial]
andInterview Status master which deals with Interview status Like [Cleared, Rejected]
provide Add, edit, delete and search functionality.

88
 Figure 7.10: Round Master

89
 Figure 7.12: Interview Status Master

Requirement

Figure 7.13: Requirement

This is Requirement page where project managers can write their requirements to notify
HR. Here project managers can add new requirement using New button. Each rows Action
Column provides four links – edit, delete, required skillset and copy.

After project manager identifies need of resources, entry will be made to this module
which includes: candidate preference, location, impact, project name, requester’s name and
requestor date, required date, experience, status of this requirement, closed date.

90
 Figure 7.14: New Requirement

This page shows modal popup which opens on click of a New button. It accepts details of

new project requirement from user and inserts into database on click of save button. Save

& Continue allows user to make multiple entries in one go.

91
 Figure 7.15: Edit Requirement

This page shows modal popup which opens on click of a edit link. It accepts details to be

edited for a specific project requirement from user and inserts into database on click of

save button.

92
 Figure 7.16: Copy Requirement

This page shows modal popup which opens on click of a copy link. It accepts name of new

project requirement copy.Copy link will allow user to insert copy of existing project

requirement with new name, which saves time in case there is a requirement having same

requirement details

93
 Figure 7.17: Requirement Skillset

With every requirement there are certain skills associated. For this, each requirement has
Required Skillset link, along with edit, delete and copy link which will navigate to
Required Skillset where we can manage skills of that requirement.

94
Panel

Figure 7.18: Panel

For taking interview there is need of panel. This module deals with panel details like panel
name, grade, panel email, supervisor name and supervisor email.

Here user can add new panels using New button. Each rows Action Column provides three
links – edit, delete, required skillset.

95
 Figure 7.19: New Panel with Validation Message

This page show modal popup with error messages. Whenever user enters invalid data,
respective input field highlights and shows corresponding error message as tooltip for icon.

96
 Figure 7.20: Panel Skillset

Every panel has certain skills. For this, each panel has Panel Skillset link, along with edit

and delete link; which will navigate to Panel Skillset page where we can manage skills of

panel.

This also provides add, edit, delete and search functionality.

97
Candidate

Figure 7.21: Candidate

This module deals with candidate information which includes candidate name, candidate
resume [upload and download], received date, source.

It also provides Addition of new candidate through New button. Each record has three
links which are: edit, delete, Interview Schedule.

98
 Figure 7.22: Delete Candidate

99
 Figure 7.23: Candidate Interview Schedule

Each candidate has Interview Schedule link, which navigates you to schedule page and

allows you to manage schedule information which includes project name, interview type,

interview round, interview date and time, interview panel and interview status for that

particular candidate.Like other it provides add, edit, delete and search functionality. It has

an extra link –Feedback.

100
 Figure 7.24: New Candidate InterviewSchedule

This is modal popup that shows when user clicks on New button to add interview schedue.

101
 Figure 7.25: Interview Feedback

Each schedule has Feedback link, which navigates you to feedback page and allows to give
feedback using star rating control against required skill [like C#, MVC etc.] and textual
remarks.

Figure 7.26: Interview Remarks

102
 Figure 7.27: Interview Schedule Mail

This is email message that is sent to alloted interview panel , evry time a new interview is

scheduled for him or any changes are madhe to his interview schedule.

103
 Figure 7.28: Responsive Dashboard and Navbar

104
 Figure3.29: Responsive Dashboard with Responsive Charts

105
 Figure 3.30: Responsive Page Content

106
 Figure 3.31:Responsive Table wth flip scroll

107
 Figure 3.32:Responsive Modal Popup and its elements

108
 8. Future Enhancements

Future Enhancements are features that can be added into project in future.

Interview Tracking System has future enhancements in order to make it a more

efficient system.

The future enhancements of the project include the following:

● Import data via MS-Excel Files to support bulk recruitment drive.

● Export data to MS-Excel, MS-Word and PDF for evaluation.

● Role specific View and Access permissions.

● Integration with other systems.

● Include candidate screening process.

109
 9. Limitations

The limitations of Interview Tracking System are as follows:

● This system only tracks interview process not candidate screening which
is done manually.

● Not efficient for bulk recruitment drive.

● Escalation of schedule is not possible.

● More suitable for technical background.

● Web Page is not responsive to changes until it being reloaded manually.

● It is mandatory for user to access site within company domain.

● Net Connection is must

110
 10. Conclusions

Interview Tracking System will help the HR Department, Project Manager

and Panels to check the information about Candidates, Interview Status, Panels and

Project Requirements whenever needed.

After identifying need of resources, Project Manager add information about

requirement through Requirement Module.

HR Department can see the information about requirement which is generated

by project manager. So according to requirement hr can schedule interview of

suitable candidate and to take interview, assign panel through Candidate

Module.Schedule notification sent through mail will act as a interview reminder.

Panel can see the information about requirement and candidate. So he can

take interview according to that perspective and provide feedback through

schedules feedback link.

All the users can also access site using any mobile device because of its

Responsive Web Design( RWD).

System will efficiently track interview process and store data on central

database, thus providing consistent data. Also site will provide 24*7 access and

improved performance.

111
 11. Appendices
Acronyms Used In This Document

Acronym Stands For Context

‘Interview Tracking System’ or
Interview ‘IntreviewTrack’ is an intranet web
ITS
Tracking System application for recording and improving
existing manual interview process .

Blue Star Infotech is an IT Consulting

firm, which works in the space of
Mobility, Cloud Computing, Analytics &
Blue Star Infotech
BSIL Business Intelligence, Product
Ltd.
Engineering, Testing, Package
Implementation and Applications Services
for which the system is developed.

The Model-View-Controller (MVC) is an

architectural pattern which separates the
Model View modeling of the domain (behavior and
MVC
Controller data), the presentation (user interface), and
the actions based on user input

Responsive Web design is the approach

that suggests that design and development
should respond to the user’s behavior and
Responsive Web
RWD environment based on screen size,
Design
platform and orientation.

112
 12. Bibliography
Web Site Referred

● https://www.msdn.com

● https://www.codeproject.com

● https://learn.jquery.com

● https://github.com

● https://www.jqueryrain.com

● https://stackoverflow.com

113
114