Page 1 of 17

InView System Specification Document

Date: 19 April 2012

Page 2 of 17

Table of Contents

Page 3 of 17

1 Document Properties 1.1 Revision History

Revision No. 1 Date Modified By Description of Change 22-Apr-2010 Sujay Mahajan Initial Draft including Introduction. Identified most externals and associated use cases/Activity diagrams, Screen specifications

1.2 Approval List

Approving officer Mr. S. Kannan Mr. Anurag Singh Remarks

1.3 Distribution List

Recipient Mr. S. Kannan Mr. Anurag Singh Mr. Anshul Gupta Mr. Abhishek Remarks

Page 4 of 17

2 Definition of Terms
Term / Acronym NA TBD Definition Not Applicable To be done

Page 5 of 17

3 Purpose and Audience 3.1 Purpose

The purposes of this specification of the InView are to: Provide a system overview of the InView including definition, overviews, objectives and major capabilities. To formally specify its associated: - System specifications - Screen/functions involved - Data and other requirement in each screen - Assumptions and Constraints

3.2 Audience
The audiences of stakeholders for this specification of the InView include: InView Employees: - Managers - Representative, who must approve it BMS Employees: - Project Manager - Architects, whose overall architecture must meet the requirement specified in the SRS. - Programmers, whose software components must implement the requirement specified in the SRS. - Testers, who must ensure that the requirements are validatable and whose test must validate the requirement. Users, who are any 3rd party recruiters and corporations that take part in the InView. - Buyers, who will use the InView to manage their hiring process. - Client, Who will use the Inview to review the candidates - Client Administrator - Recruiter -

Page 6 of 17

4 System Overview 4.1 Background

Provide a brief background of the system

4.2

Brief overview of the system

InView is the leading video-enabled talent acquisition solution that 3rd party recruiters and corporations rely on for fast and complete management of their hiring process. This unique web-based system automates much of the administrative hassle by bringing together applicant tracking, best practices, and video giving recruiters the opportunity to focus on their key value add: evaluating and matching applicants to positions.

4.3 System Processes

4.3.1 Client and Client Administrator Capabilities
The InView will provide the following capabilities for the Client and Client Administrator. There is no difference in the application functionalities between client and client administrator. Review Candidates Manage Profile

4.3.1.1 Summary Use Case Diagrams

The following use case diagrams summarize the functional requirement for the recruiter capabilities. TBD Review candidates Activity Diagram:

Review Candidate
Candidate associated with any job? Yes No

Select Job

Select Candidates

Review Candidate

Page 7 of 17

Profile Management Activity Diagram

Manage Profile

Modify Profile

4.3.2 Recruiter Capabilities

The InView will enable recruiter to: - Provides Dashboard which shows recent jobs, candidates, Recruiters schedules. - Setup - Update Profile - Insert, Edit, Remove and review their Schedules - Subscriber Settings Summary Update subscriber setting Insert, Edit, Remove and review company contact details Send email to company contact details Equipments Insert, Edit, Remove and review Rooms Insert, Edit, Remove and review Web Cameras details Agreement Review and setup display settings of agreement - Update Email Templates - Insert, Edit, Remove and review candidates properties - Insert, Edit, Remove and review Reference Questions - Insert, Edit, Remove and review Recruiter Questions/Notes - Search Activity - Manage Question Templates Manage Clients: Insert, Edit, Remove and search clients. Review Activities, Events by client. Manage Client documents, contact summary, jobs and placements. Manage Jobs: Insert, Edit, Remove and search jobs. Review Activities, Events, Job details and Candidates by jobs. Manage Clients: Insert, Edit, Remove, forward candidates. Manage candidates information like videos, documents, reference information, candidate related activities, events, candidate history, Recruiter notes. Schedule candidate interview, Manage self edit and recording request to candidates which are not registered in Inview.

Page 8 of 17

4.3.2.1 Summary Use Case Diagrams

The following use case diagrams summarize the functional requirement for the recruiter capabilities. TBD

Page 9 of 17

System Specifications
This section will describe each screen/function of the InView system. It will cover each screen along with the input/output values, validations associated for the screen controls, Classes associated etc

5.1 Client Dashboard Screen

5.1.1 Overview
The main aim of the client is to review the candidates forwarded to a given jobs and record his interest for the candidates. This page explains that how the user will search for the forwarded candidates. User can search for the forwarded candidates for the particular job and also the candidates which are not associates with any job with or without using the search operation. This page also provide link to my profile which allows users to update their profile information.

5.1.2 Input conditions/Parameters

Input Conditions: The InView has identified and authenticated the client account on login screen. Parameters: --NA--

5.1.3 Associated classes/Objects

Project Name EMS.Checklist.UI Classes/Objects 1. Home2\ClientDashboard.xaml 2. Controls2\HeaderNew.xaml 3. Controls2\MainMenuNew.xaml 4. Controls2\FooterNew.xaml 1. ForwardCandidate.cs 2. Interview.cs

EMS.Checklist.DataAccess

Page 10 of 17

5.1.4 Screen

5.1.5 Field Information

Field name Search within Data type Alphanumeric Action Job Search Field Property Editable Source Validation No Validation Remarks Search text box for Job search

5.1.6 Processing
Client logged in to the InView and is presented with this screen with the summary of Jobs, Job Description and candidates forwarded to these jobs. User can search for a particular job using Search text box and by clicking on search button icon. User can select a job to view the job description and candidates forwarded for the selected jobs. User can also view the candidates which is not associated with any job but they are forwarded by using a checkbox Show candidates not associated with any job. If the user selects the candidate in the list by selecting a row, then the screen displays the Candidates summary. User can also select multiple candidates by selecting checkbox in the list and click on Review Selected Candidates button, then the screen displays candidates summary by showing summary of first candidates by default, here user can select the user image icon to view summary of a particular candidate. User can Click on My Profile button to go to profile screen, here user can update their profile information.

Page 11 of 17

5.1.7 Validation
1. Page displays message if user didnt selected the candidate and clicked on Review Selected Candidates button.

5.1.8 Information Sources

Following are the table names from where this screen is fetching data: Interview, Profile, Forward_Profile, Candidate_Forward, Forwarded_Candidate, Interview_Candidate

5.1.9 Information Sinks

None

5.1.10 Output condition/parameters

None

5.1.11 Other application dependencies

None

5.2 Client Review Candidate Screen

5.2.1 Overview
This page allow user to review the summary and profile of the selected candidates and update the interview candidates as interested or not interested. This page explains that how the user will review the forwarded candidates in two ways, user can review a single candidate or multiple candidates using this page. In case of multiple candidates, page displays the list of user icons and user can view candidates summary and review by selecting these user icons.

5.2.2 Input conditions/Parameters

Input Conditions: Client has selected candidate for review on Client Dash board. Parameters: Object of Collection of type Submission, Forwardid

5.2.3 Associated classes/Objects

Project Name EMS.Checklist.UI Classes/Objects 1. Submission2\Controls\CandidateProfileNew.xaml 2. Controls2\HeaderNew.xaml 3. Controls2\MainMenuNew.xaml 4. Controls2\FooterNew.xaml 5. Submission2\Controls\ImageSlider.xaml 6. Submission2\Controls\ctrlCandidateReviewSummary.xaml 7. Submission2\Controls\ctrlCandidateReviewReferences.xaml 1. InterviewCandidate.cs 2. Generic.cs 3. InterviewCandidateDocument.cs 4. InterviewCandidateReference.cs 5. InterviewCandidateVerification.cs

EMS.Checklist.DataAccess

Page 12 of 17

5.2.4 Screen
Review page is divided in two ways: 1. Single candidate selected:

2. Multiple candidates selected:

Page 13 of 17

5.2.5 Field Information

Field name Data type Action Field Property Source Validation Remarks

5.2.6 Processing
Client has been selected Candidates for review and is presented with this screen with summary of the forwarded candidates. In case user has selected multiple candidate, page will display a image slider with candidate icons for all the candidates selected. Page will display first candidate selected by default and will display summary of that candidate. User will record their interest by clicking on Yes or No button.

5.2.7 Validation 5.2.8 Information Sources

Following are the table names from where this screen is fetching data: Interview_Candidate, Question, Interview_Candidate_Document, Document_Category, Interview_Candidate_Reference, Interview_Candidate_Verification

5.2.9 Information Sinks

Following are the table names in which the information is get updated when user record their interest. Activity

Page 14 of 17

5.2.10 Output condition/parameters

None

5.2.11 Other application dependencies

None

5.3 Client My Profile Screen

5.3.1 Overview
This page allow user to review and update their profile. User can update their profile information, also page explains how user will change their profile picture.

5.3.2 Input conditions/Parameters

Input Conditions: Client has selected My Profile on Client Dash board. Parameters: --NA--

5.3.3 Associated classes/Objects

Project Name EMS.Checklist Classes/Objects 1. Home2\MyProfile.xaml 2. Home2\CtrlProfile.xaml 3. 1. Profiles.cs

EMS.Checklist.DataAccess

5.3.4 Screen

Page 15 of 17

5.3.5 Field Information

Field name Company Name First Name Middle Initial Last Name Email Confirm Email Zip State City Address Country Phone Data type Varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar varchar Action Field Property Non Editable Editable Editable Editable Editable Editable Editable Editable Editable Editable Editable Editable Mandatory Field Mandatory Field Mandatory Field Source Validation Remarks Company full name Contact First Name Contact Middle Initial Contact Last Name Contact Email Contact Email Contact zip code Contact State Contact City Contact Addresss Contact Contry Contact Phone Number Contac Fax Number Contact Mobile Number Contact Password

Mandatory Field

Fax Mobile

varchar varchar

Editable Editable

Password

varchar

Editable

Mandatory Field

5.3.6 Processing
Client has been selected My Profile and is presented with this screen with all the profile information. Client can update their profile information and click on save to record the same in the database. Client can also update their profile picture. User can select a new profile picture by selecting browse button, Page will save this picture on the location configured in the web.config file. Page will create a folder structure to upload this picture, the criteria to create the folder structure is: folder name as Subscriber id and CandidatesImages under the basic folder path configured in the web.config file.

5.3.7 Validation
1. Page will validate Email and Confirm Email field and if both are not same, page will display message. 2. Page will validate password and Confirm Password fields and if both are not same, page will display message.

5.3.8 Information Sources

Following are the table names from where this screen is fetching data: Profile

Page 16 of 17

5.3.9 Information Sinks

Following are the table names in which the information is get updated when user record their interest. Profile

5.3.10 Output condition/parameters

None

5.3.11 Other application dependencies

None

Page 17 of 17

Assumptions and Constraints