Recruitment System SFS 1 0

Functional Specification DocumentFor

Recruitment SystemVersion 1.0

Friday, July 18, 2008

Document ID: FS_RecSys_1.0.doc

Proprietary and Confidential Information

Prepared By:Netrasoft Technologies (pvt) Ltd.

Recruitment System Software Functional Specification

Functional Specification Document

© Netrasoft Technologies (Pvt.) Ltd – Proprietary & ConfidentialFS_RecSys_1.0.doc Page 2 of 147


1. Document Control PageDescription Date

Description Name Designation

Document Contents and Graphics

Nouman Hameed SQA Analyst

Document Contents Hafiz Ahmad Shehzad SQA Engineer

Document Contents and revisions

Muhammad Usman Tipu SQA Manager

Project Contacts

Primary Point of Contact Mr. Shahid Maqsood Project Manager

Secondary Point of Contact Mr. Shahid Malook Team lead PHP

Note: The above table shows a detailed history of the latest revision of the document.



Table of Contents

RECRUITMENT SYSTEM..........................................................................................................................1

1. DOCUMENT CONTROL PAGE.................................................................................................................32. OVERVIEW OF RECRUITMENT SYSTEM.................................................................................................72.1. RECRUITMENT SYSTEM OBJECTIVES AND GOALS............................................................................72.2. SYSTEM FEATURES...........................................................................................................................72.3. FUNCTIONAL REQUIREMENTS...........................................................................................................72.4. QUALITY REQUIREMENTS.................................................................................................................92.4.1. USABILITY.....................................................................................................................................92.4.2. MAINTAINABILITY........................................................................................................................92.4.3. SYSTEM RESPONSE........................................................................................................................92.4.4. VALIDATION..................................................................................................................................93. HIGH LEVEL USE CASE DIAGRAM......................................................................................................103.1.1. ADMINISTRATOR MODULE..........................................................................................................104. ELABORATED USE CASES...................................................................................................................114.1. ADMINISTRATOR.............................................................................................................................114.1.1. COUNTRIES MANAGEMENT.........................................................................................................114.1.1.1. VIEW EXISTING COUNTRIES...................................................................................................114.1.1.2. ADD NEW COUNTRY...............................................................................................................124.1.1.3. EDIT COUNTRY.......................................................................................................................134.1.1.4. DELETE COUNTRY..................................................................................................................144.1.2. STATE MANAGEMENT.................................................................................................................154.1.2.1. VIEW EXISTING STATES..........................................................................................................154.1.2.2. ADD NEW STATE....................................................................................................................164.1.2.3. EDIT STATE.............................................................................................................................174.1.2.4. DELETE STATE........................................................................................................................184.1.3. CITY MANAGEMENT...................................................................................................................194.1.3.1. VIEW EXISTING CITIES...........................................................................................................194.1.3.2. ADD NEW CITY.......................................................................................................................204.1.3.3. EDIT CITY...............................................................................................................................214.1.3.4. DELETE CITY..........................................................................................................................224.1.4. INDUSTRY MANAGEMENT...........................................................................................................234.1.4.1. VIEW EXISTING INDUSTRIES...................................................................................................234.1.4.2. ADD NEW INDUSTRY..............................................................................................................244.1.4.3. EDIT INDUSTRY.......................................................................................................................254.1.4.4. DELETE INDUSTRY..................................................................................................................264.1.5. FORUM MANAGEMENT...............................................................................................................274.1.5.1. FORUM MANAGEMENT...........................................................................................................274.1.6. BLOG MANAGEMENT..................................................................................................................284.1.6.1. BLOG MANAGEMENT..............................................................................................................284.1.7. CONTENT MANAGEMENT............................................................................................................294.1.7.1. CONTENT MANAGEMENT........................................................................................................294.1.8. EMAIL CONTENT MANAGEMENT................................................................................................304.1.8.1. EMAIL CONTENT MANAGEMENT............................................................................................304.1.9. NEWSLETTER MANAGEMENT......................................................................................................314.1.9.1. NEWSLETTER MANAGEMENT..................................................................................................314.1.10. BANNER MANAGEMENT..............................................................................................................324.1.10.1. VIEW BANNERS.......................................................................................................................324.1.10.2. ADD BANNER..........................................................................................................................334.1.10.3. EDIT BANNER..........................................................................................................................354.1.10.4. DELETE BANNER.....................................................................................................................374.1.11. FAQ MANAGEMENT...................................................................................................................38



4.1.11.1. VIEW FAQS............................................................................................................................384.1.11.2. ADD FAQ................................................................................................................................394.1.11.3. EDIT FAQ...............................................................................................................................404.1.11.4. DELETE FAQ..........................................................................................................................414.1.12. PROFILE MANAGEMENT..............................................................................................................424.1.12.1. PROFILE MANAGEMENT..........................................................................................................424.1.12.2. PASSWORD MANAGEMENT.....................................................................................................434.1.13. ADMINISTRATION MANAGEMENT...............................................................................................444.1.13.1. VIEW ADMINISTRATORS.........................................................................................................444.1.13.2. ADD NEW ADMINISTRATOR....................................................................................................454.1.13.3. DELETE ADMINISTRATOR.......................................................................................................464.1.13.4. EDIT ADMINISTRATOR GROUP................................................................................................474.1.14. CANDIDATE MANAGEMENT........................................................................................................484.1.14.1. VIEW PENDING CANDIDATE REQUESTS..................................................................................484.1.14.2. APPROVE PENDING CANDIDATE REQUESTS............................................................................494.1.14.3. REJECT PENDING CANDIDATE REQUESTS...............................................................................504.1.14.4. VIEW INCOMPLETE CANDIDATE REQUESTS............................................................................514.1.14.5. DELETE INCOMPLETE CANDIDATE REQUESTS........................................................................524.1.14.6. VIEW APPROVED CANDIDATE.................................................................................................534.1.14.7. VIEW REJECTED CANDIDATE..................................................................................................544.1.14.8. ADD NEW CANDIDATE............................................................................................................554.1.14.9. EDIT CANDIDATE....................................................................................................................574.1.14.10. DELETE CANDIDATE...........................................................................................................594.1.14.11. VIEW VIDEOS OF CANDIDATE.............................................................................................604.1.14.12. UPLOAD VIDEOS OF CANDIDATE........................................................................................614.1.14.13. DELETE VIDEOS OF CANDIDATE.........................................................................................634.1.14.14. UPLOAD OWN INTERVIEW VIDEOS OF CANDIDATE............................................................644.1.14.15. EDIT OWN INTERVIEW VIDEOS OF CANDIDATE..................................................................664.1.14.16. DELETE OWN INTERVIEW VIDEOS OF CANDIDATE.............................................................674.1.14.17. VIEW JOB NEWSLETTER SUBSCRIBERS...............................................................................684.1.14.18. SEND JOB NEWSLETTER......................................................................................................694.1.15. EMPLOYER MANAGEMENT..........................................................................................................704.1.15.1. VIEW PENDING EMPLOYER REQUESTS...................................................................................704.1.15.2. APPROVE PENDING EMPLOYER REQUESTS.............................................................................714.1.15.3. REJECT PENDING EMPLOYER REQUESTS................................................................................724.1.15.4. VIEW INCOMPLETE EMPLOYER REQUESTS.............................................................................734.1.15.5. DELETE INCOMPLETE EMPLOYER REQUESTS.........................................................................744.1.15.6. VIEW APPROVED EMPLOYER..................................................................................................754.1.15.7. VIEW REJECTED EMPLOYER...................................................................................................764.1.15.8. ADD NEW EMPLOYER.............................................................................................................774.1.15.9. EDIT EMPLOYER......................................................................................................................794.1.15.10. DELETE EMPLOYER.............................................................................................................814.1.15.11. VIEW JOB NEWSLETTER SUBSCRIBERS...............................................................................824.1.15.12. SEND NEWSLETTER.............................................................................................................834.1.15.13. ADD NEW JOB.....................................................................................................................844.1.15.14. EDIT JOB.............................................................................................................................874.1.15.15. DELETE JOB........................................................................................................................894.1.15.16. VIEW PENDING JOB REQUEST.............................................................................................904.1.15.17. VIEW APPROVED JOB REQUEST..........................................................................................914.1.15.18. VIEW REJECTED JOB REQUEST...........................................................................................924.1.15.19. APPROVE JOB......................................................................................................................934.1.15.20. REJECT JOB.........................................................................................................................944.1.15.21. VIEW ACTIVE JOB REQUEST...............................................................................................954.1.15.22. VIEW INACTIVE JOB REQUEST............................................................................................964.1.15.23. ACTIVATE JOB.....................................................................................................................974.1.15.24. INACTIVATE JOB.................................................................................................................98



4.2. CANDIDATE.....................................................................................................................................994.2.1. CANDIDATE PROFILE...................................................................................................................994.2.1.1. ACCOUNT CREATION..............................................................................................................994.2.1.2. EDIT CANDIDATE PROFILE....................................................................................................1014.2.2. PHOTO MANAGEMENT..............................................................................................................1034.2.2.1. UPLOAD CANDIDATE PHOTO................................................................................................1034.2.2.2. EDIT CANDIDATE PHOTO......................................................................................................1044.2.2.3. DELETE CANDIDATE PHOTO.................................................................................................1054.2.3. RESUME MANAGEMENT............................................................................................................1064.2.3.1. UPLOAD RESUME..................................................................................................................1064.2.3.2. COPY OR PASTE RESUME......................................................................................................1074.2.4. VIDEO MANAGEMENT...............................................................................................................1084.2.4.1. UPLOAD CANDIDATE VIDEO.................................................................................................1084.2.4.2. EDIT CANDIDATE VIDEO.......................................................................................................1094.2.4.3. DELETE CANDIDATE VIDEO..................................................................................................1104.2.5. JOBS MANAGEMENT..................................................................................................................1114.2.5.1. SEARCH A JOB.......................................................................................................................1114.2.5.2. SET CUSTOMIZED SEARCHES FOR FUTURE JOBS..................................................................1124.2.5.3. APPLY FOR A JOB..................................................................................................................1144.2.5.4. VIEW JOB APPLICATION HISTORY........................................................................................1154.2.5.5. VIEW EMPLOYER INFORMATION...........................................................................................1164.2.6. SUBSCRIBE TO JOB NEWSLETTERS............................................................................................1174.2.7. INVITE A FRIEND.......................................................................................................................1184.3. EMPLOYER....................................................................................................................................1194.3.1. REGISTRATION AS EMPLOYER..................................................................................................1194.3.1.1. CREATE ACCOUNT................................................................................................................1194.3.1.2. EDIT PROFILE........................................................................................................................1214.3.2. JOB MANAGEMENT...................................................................................................................1234.3.2.1. PLACE A JOB.........................................................................................................................1234.3.2.2. EDIT A JOB............................................................................................................................1264.3.2.3. DELETE A JOB.......................................................................................................................1294.3.2.4. DEACTIVATE A JOB...............................................................................................................1314.3.2.5. ACTIVATE A JOB...................................................................................................................1334.3.3. VIEW CANDIDATES...................................................................................................................1344.3.3.1. VIEW CANDIDATES...............................................................................................................1344.3.3.2. VIEW RESUME.......................................................................................................................1364.3.3.3. VIEW HISTORY......................................................................................................................1384.3.3.4. VIEW COMMENTS..................................................................................................................1404.3.3.5. POST COMMENTS..................................................................................................................1414.3.3.6. VIEW VIDEO..........................................................................................................................1424.3.3.7. ADD VIDEO...........................................................................................................................1434.3.3.8. ADD TO FAVORITE................................................................................................................1454.3.4. Subscribe for News Letter........................................................................................................146



1. Overview of Recruitment SystemThe Application/Software to be developed for this project is a Web-based Information System

called Recruitment Website. This information system provides the services of recruiting the

resources for employers. Employers will be able to post the jobs and system will help them to hire

the right candidates for that particular job. Candidates will be able to upload their CVs and target

a job suitable for them. The system will provide the service to upload the feedback about a

candidate for all other employers in the form of comments or videos.

1.1.Recruitment System Objectives and GoalsThe primary objectives and goals of Recruitment Website include the following.

Job posting by employers

Search for CVs

Feedback about candidate, to and from employers

Interview videos of candidates

Job posting history

Job searching

Apply for a job

CV uploading

Video uploading

Applied job history

Invite the other friends

Newsletters for registered employers and candidates

Blog

Forum

1.2. System FeaturesFollowing is the list of high level features of Recruitment System.

Candidate Management System

Employee Management System.

Job Management System.

Videos Management System.

Blog Management System.

Forum Management System.

1.3.Functional Requirements1. System provides user friendly and efficient mechanism to deal with the applicants.

2. System provides form and button level security.



3. System provides facility to Administrators to manage all aspects of the website.

4. For Employers:

a. System provides facility to add, edit and view Employers and their information.

b. System provides facility to post a job.

c. System provides facility to activate/deactivate the job.

d. System provides facility to view applicants against posted jobs.

e. System provides facility to search CVs of Candidates

f. System provides facility to add Candidates to favorites

g. System provides facility to subscribe for Newsletter

h. System provides facility to receive or provide feedback to recruiters

i. System provides facility to view Videos of Candidates

j. System provides facility to receive alerts on their email addresses

k. System provides facility to see interview with a candidate.

5. For Candidates:

a. System provides facility to manage profiles

b. System provides facility to upload/edit/delete their photos

c. System provides facility to upload or copy and paste their resume

d. System provides facility to edit/delete their resume

e. System provides facility to upload/edit/delete their video for employers

f. System provides facility to search jobs

g. System provides facility to view employer information

h. System provides facility to apply for jobs

i. System provides facility to view/manage History of their applications for jobs

j. System provides facility to set customized searches for future job

k. System provides facility to Subscribe to Job Newsletter

l. System provides facility to Invite a friend



1.4.Quality Requirements

1.4.1. UsabilityUsability means the look and feel and about the smooth interaction of an end-user of the

website. Website usability will be considered as high priority requirement while development

and testing the application. This will ensure the attractive and user friendly interface of the

application. Testing will be performed in order to meet the usability standards.

1.4.2. MaintainabilityEntire Application will be deployed, tested and supported for the duration of one year which

includes any other dependent component, support and training as a part of contract. The

system shall be monitored closely by the Netrasoft team through the contract period and

necessary changes shall be made to the system to ensure its scalability and enhance its

performance. Moreover the Design Document, Deployment Document shall be provided to

the stake holder if required.

1.4.3. System ResponseResponse time of the application will be calculated separately. It will help to measure the

stability and performance of the website. During testing process, different tools will be used

by QA department for this calculation. The report can be provided to the stake holder if

required.

1.4.4. ValidationCSS/HTML validation will be performed to make sure that website is up to the standards for

CSS and HTML.



2. High Level Use Case DiagramAfter the study of current business procedures and user requirements, a use case diagram

represents the understanding which as follows:

2.1.1. Administrator Module



3. Elaborated Use Cases

3.1.Administrator

3.1.1. Countries Management

3.1.1.1. View Existing Countries

<UC-001: View Existing Countries >Actor: AdministratorFeature: This use case will provide the functionality of viewing the existing countries. Actor can see the list of existing countries in the database.Pre-condition(s) 1. Actor is login

2. Some countries are already defined.Scenarios

Step# Action Software Reaction

1. Actor will open the Country page. System will open the country page by list down all the existing countries.

2. Actor will press Close button System will close the country page and will redirect the user to the main page.

Alternate Scenarios

Post Conditions

Concurrent User: ‘n’ number of users.

Graphical User Interface

Country Name (Read only)Add New (button)

Edit (button)Delete (button)

Business Rules

1. Countries will be listed alphabetically.



3.1.1.2. Add New Country

<UC-002: Add New Country >Actor: AdministratorFeature: This use case will provide the functionality of adding a new country. Actor can add a new record of country. The list of existing countries will be available throughout the system where required.Pre-condition(s) 1. Actor is loginScenarios


1. Actor will open the Country page. System will open the country page by list down all the existing records.

2. Actor will press Add New button System will open the page to add new record with all fields blank.

3. Actor will fill the form along with all mandatory fields

System will allow.

4. Actor will press Save button System will save the record, redirect the user to the listing page and display a relevant message

Alternate Scenarios

Step# Description

1.Actor will miss any mandatory field while filling the formSystem will not save the record and display a proper message.

2.Actor will press Cancel button after filling the formSystem will not save the record and redirect to the listing page

Post Conditions

Step# Description

1. Actor will be able to edit the record

2. Actor will be able to delete the record3. Record will be listed where it will be requiredConcurrent User: ‘n’ number of users.


Country Name* (Textbox)Save (button)

Cancel (button)Business Rules

1. Duplicated country name is not allowed.



3.1.1.3. Edit Country

<UC-001: Edit Country >Actor: AdministratorFeature: This use case will provide the functionality of editing a country record. Actor can edit the existing country record.Pre-condition(s) 1. Actor is login

2. At least one country record already exists.Scenarios



2. Actor will press Edit button System will open the page to edit the record with all fields having previous values.

3. Actor will edit the form along with all mandatory fields

System will allow.


Alternate Scenarios

Step# Description



Post Conditions

Step# Description



Country Name* (Textbox)Save (button)


1. Duplicated country name is not allowed.



3.1.1.4. Delete Country

<UC-001: Delete Country >Actor: AdministratorFeature: This use case will provide the functionality of deleting a country record. Actor can delete the existing country record.Pre-condition(s) 1. Actor is login




2. Actor will press Delete button against any record

System will open the confirmation window about deletion of record.

3. Actor will press OK button System will allow and delete the record from repository, update the listings and display the proper message.

Alternate Scenarios

Step# Description

1.Actor will press Cancel button on the confirmation windowSystem will not delete the record.

Post Conditions

Step# Description

1. Record will not be available in the country list where required.Concurrent User: ‘n’ number of users.


OK (button)Cancel (button)

Business Rules



3.1.2. State Management

3.1.2.1. View Existing States

<UC-001: View Existing States >Actor: AdministratorFeature: This use case will provide the functionality of viewing the existing states. Actor can see the list of existing states in the database.Pre-condition(s) 1. Actor is login

2. Some countries are already defined.Scenarios


1. Actor will open the State page. System will open the State page by list down all the existing State.

2. Actor will select the country from dropdown

System will list down all the relevant states under the selected country.

3. Actor will press Close button System will close the State page and will redirect the user to the main page.

Alternate Scenarios

Post Conditions



State Name (Read only)Country Name (Dropdown)

Add New (button)Edit (button)

Delete (button)Business Rules

1. States will be listed alphabetically.

2. Actor can see the relevant states under the selected country from dropdown.

3. By Default, country will not be selected and all the states will be listed down.



3.1.2.2. Add New State

<UC-002: Add New State >Actor: AdministratorFeature: This use case will provide the functionality of adding a new state. Actor can add a new record of state. The list of existing states will be available under the specific country throughout the system where required.Pre-condition(s) 1. Actor is login

2. At least one country record already exits.Scenarios


1. Actor will open the State page. System will open the state page by list down all the existing records.



System will allow.


Alternate Scenarios

Step# Description



Post Conditions

Step# Description




Country Name* (Dropdown)State Name* (Textbox)

Save (button) Cancel (button)

Business Rules

1. Duplicated state name is not allowed.

2. There can be many states under a single country



3.1.2.3. Edit State

<UC-001: Edit State>Actor: AdministratorFeature: This use case will provide the functionality of editing a state record. Actor can edit the existing state record.Pre-condition(s) 1. Actor is login

2. At least one country record already exists.3. At least one state record already exists.

Scenarios


1. Actor will open the State page. System will open the state page by list down all the existing records.



System will allow.


Alternate Scenarios

Step# Description



Post Conditions

Step# Description



Country Name* (Dropdown)State Name* (Textbox)


Business Rules

1. Duplicated state name is not allowed.

2. There can be many states under a single country



3.1.2.4. Delete State

<UC-001: Delete State>Actor: AdministratorFeature: This use case will provide the functionality of deleting a state record. Actor can delete the existing state record.Pre-condition(s) 1. Actor is login

2. At least one state record already exists.Scenarios


1. Actor will open the State page. System will open the State page by list down all the existing records.




Alternate Scenarios

Step# Description


Post Conditions

Step# Description

1. Record will not be available in the State list where required.Concurrent User: ‘n’ number of users.



Business Rules



3.1.3. City Management

3.1.3.1. View Existing Cities

<UC-001: View Existing Cities>Actor: AdministratorFeature: This use case will provide the functionality of viewing the existing Cities. Actor can see the list of existing cities in the database.Pre-condition(s) 1. Actor is login

2. Some countries are already defined.3. Some cities are already defined.

Scenarios


1. Actor will open the City page. System will open the City page by list down all the existing Cities.

2. Actor will select the Country from dropdown

System will populate the second dropdown of states and list down all the cities exists under the selected Country.

3. Actor will press Close button System will close the City page and will redirect the user to the main page.

Alternate Scenarios

Post Conditions



City Name (Read only)State Name (Read only)

Country Name (Dropdown)Add New (button)


Business Rules

1. Cities will be listed alphabetically.

2. Actor can see the relevant cities under the selected country from dropdown.

3. By Default, country and state will not be selected and all the cities will be listed down.



3.1.3.2. Add New City

<UC-002: Add New City>Actor: AdministratorFeature: This use case will provide the functionality of adding a new city. Actor can add a new record of city. The list of existing cities will be available under the specific country throughout the system where required.Pre-condition(s) 1. Actor is login



1. Actor will open the City page. System will open the City page by list down all the existing records.



System will allow.


Alternate Scenarios

Step# Description



Post Conditions

Step# Description




Country Name* (Dropdown)State Name (Textbox)City Name* (Textbox)


Business Rules

1. Duplicated city name is not allowed.

2. There can be many cities under a single country



3.1.3.3. Edit City

<UC-001: Edit City>Actor: AdministratorFeature: This use case will provide the functionality of editing a city record. Actor can edit the existing city record.Pre-condition(s) 1. Actor is login

2. At least one country record already exists.3. At least one city record already exists.

Scenarios


1. Actor will open the City page. System will open the city page by list down all the existing records.



System will allow.


Alternate Scenarios

Step# Description



Post Conditions

Step# Description



Country Name* (Dropdown)State Name (Textbox)City Name* (Text box)


Business Rules

1. Duplicated city name is not allowed.

2. There can be many cities under a single country



3.1.3.4. Delete City

<UC-001: Delete City>Actor: AdministratorFeature: This use case will provide the functionality of deleting a city record. Actor can delete the existing city record.Pre-condition(s) 1. Actor is login

2. At least one city record already exists.Scenarios


1. Actor will open the City page. System will open the City page by list down all the existing records.




Alternate Scenarios

Step# Description


Post Conditions

Step# Description

1. Record will not be available in the City list where required.Concurrent User: ‘n’ number of users.



Business Rules



3.1.4. Industry Management

3.1.4.1. View Existing Industries

<UC-001: View Existing Industries>Actor: AdministratorFeature: This use case will provide the functionality of viewing the existing Industries. Actor can see the list of existing Industries in the database.Pre-condition(s) 1. Actor is login

2. Some Industries are already defined.Scenarios


1. Actor will open the Industry page. System will open the Industry page by list down all the existing Industries.

2. Actor will press Close button System will close the Industry page and will redirect the user to the main page.

Alternate Scenarios

Post Conditions



Industry Name (Read only)Add New (button)


Business Rules

1. Industries will be listed alphabetically.



3.1.4.2. Add New Industry

<UC-002: Add New Industry>Actor: AdministratorFeature: This use case will provide the functionality of adding a new Industry. Actor can add a new record of Industry. The list of existing Industries will be available throughout the system where required.Pre-condition(s) 1. Actor is loginScenarios


1. Actor will open the Industry page. System will open the Industry page by list down all the existing records.



System will allow.


Alternate Scenarios

Step# Description



Post Conditions

Step# Description




Industry Name* (Textbox)Save (button)


1. Duplicated Industry name is not allowed.



3.1.4.3. Edit Industry

<UC-001: Edit Industry>Actor: AdministratorFeature: This use case will provide the functionality of editing an Industry record. Actor can edit the existing industry record.Pre-condition(s) 1. Actor is login

2. At least one Industry record already exists.Scenarios





System will allow.


Alternate Scenarios

Step# Description



Post Conditions

Step# Description



Industry Name* (Text box)Save (button)


1. Duplicated Industry name is not allowed.



3.1.4.4. Delete Industry

<UC-001: Delete Industry>Actor: AdministratorFeature: This use case will provide the functionality of deleting an Industry record. Actor can delete the existing Industry record.Pre-condition(s) 1. Actor is login

2. At least one Industry record already exists.Scenarios






Alternate Scenarios

Step# Description


Post Conditions

Step# Description

1. Record will not be available in the Industry list where required.Concurrent User: ‘n’ number of users.



Business Rules



3.1.5. Forum Management

3.1.5.1. Forum Management

<UC-001: Forum Management>Actor: AdministratorFeature: In the system, we will use the PHPBB embedding forum functionality. It will be a third party control.Pre-condition(s)Scenarios


Alternate Scenarios

Post Conditions

Concurrent User:


Business Rules



3.1.6. Blog Management

3.1.6.1. Blog Management

<UC-001: Blog Management>Actor: AdministratorFeature: In the system, we will use the WordPress embedding Blog functionality. It will be a third party control.Pre-condition(s)Scenarios


Alternate Scenarios

Post Conditions

Concurrent User:


Business Rules



3.1.7. Content Management

3.1.7.1. Content Management

<UC-001: Content Management>Actor: AdministratorFeature: This use case will provide the functionality of managing the contents of the website pages. Actor can edit and manage the contents of the website pages for front end.Pre-condition(s) 1. Actor is login

2. All Pages are definedScenarios


1. Actor will open the Content Management page.

System will open the Content Management page by list down all the existing pages.

2. Actor will chose Edit option to edit the contents against any page.

System will open the record in edit mode, by showing the previous values.

3. Actor will edit the contents of the page.

System will allow.

4. Actor will press Save button System will save the updated contents for that page and will redirect the user to the main page by showing a proper message.

Alternate Scenarios

Step# Description

1.Actor will press Cancel button.System will not save the contents of the pages.

Post Conditions

Step# Description

1. The edited contents are visible on that particular page on the public side (front end)



Page Title* (Textbox)Browser Title* (Textbox)

Keywords (Textbox)Description (Textbox)

Contents* (Editor)Save (button)


1. Editor should be handle the special characters in the contents, like &, %, @, $ etc.

2. All options of the editors should work properly like image insertion, table insertion etc.



3.1.8. Email Content Management

3.1.8.1. Email Content Management

<UC-001: Email Content Management>Actor: AdministratorFeature: This use case will provide the functionality of managing the email contents of the website. Actor can edit and manage the contents of all emails send by the system.Pre-condition(s) 1. Actor is login

2. All emails types should be definedScenarios


1. Actor will open the Email Content Management page.

System will open the Email Content Management page by list down all the existing email pages.

2. Actor will chose Edit option to edit the contents against any page.

System will open the record in edit mode, by showing the previous values.

3. Actor will edit the contents of the page.

System will allow.

4. Actor will press Save button System will save the updated contents for that page and will redirect the user to the main page by showing a proper message.

Alternate Scenarios

Step# Description


Post Conditions

Step# Description

1. The edited contents are visible in the body of email send by the system.Concurrent User: ‘n’ number of users.


To Name* (Textbox)To Email* (Textbox)Subject* (Textbox)

From Name (Readonly Variable)From Email (Readonly Variable)

Subject (Readonly Variable)Message (Readonly Variable)

Contents* (Editor)Save (button)




3. Email should be valid



3.1.9. Newsletter Management

3.1.9.1. Newsletter Management

<UC-001: Newsletter Management>Actor: AdministratorFeature: This use case will provide the functionality of managing the Newsletters. Actor can send and manage the Newsletters.Pre-condition(s) 1. Actor is login

2. At least one member is subscribed for the Newsletter.Scenarios


1. Actor will open the Newsletter Management page.

System will open the Newsletter Management page by list down all the subscribed members.

2. Actor will fill the form and chose the members as per requirement

System should allow.

4. Actor will press Send button System will sent the newsletter email to the selected members and display a proper message.

Alternate Scenarios

Step# Description


2.Actor will miss the mandatory fieldSystem will not allow sending the newsletter.

Post Conditions

Step# Description

1. The newsletter email will be sent to the selected members.Concurrent User: ‘n’ number of users.


From Name* (Textbox)From Email* (Textbox)

Subject* (Textbox)Subscribed Members* (Checkbox)

Contents* (Editor)Send (button)




3. From Email should be valid

4. At least one subscribed member must be selected to send the newsletter.



3.1.10. Banner Management

3.1.10.1. View Banners

<UC-001: View Banners>Actor: AdministratorFeature: This use case will provide the functionality of view the Banners. Actor can view the existing banners on the fixed locations on either side of the webpage.Pre-condition(s) 1. Actor is login

2. Banner locations are defined3. At least one banner has been uploaded

Scenarios


1. Actor will open the Banner Management page.

System will open the Banner Management page by list down Left and Right side options.

2. Actor will select either Left or Right hand side as per requirement.

System will open that particular side by list down 4 banner locations.

3. Actor will press Manage Banner button against a particular location

System will open the page by list down all the previous banners.

4. Actor will press Cancel button System will close the form and redirect the user to the previous page.

Alternate Scenarios

Step# Description

1.Actor will press Cancel button.System will not save the banner

2.Actor will miss the mandatory fieldSystem will not allow saving the banner.

Post Conditions

Step# Description

1. The banner will be display on the selected page, side and location.Concurrent User: ‘n’ number of users.


Image Name (Read only)Description (Read only)

Image (Thumbnail)Close (button)

Business Rules



3.1.10.2. Add Banner

<UC-001: Add Banner>Actor: AdministratorFeature: This use case will provide the functionality of managing the Banners. Actor can add multiple banners on the fixed locations on either side of the webpage.Pre-condition(s) 1. Actor is login

2. Banner locations are definedScenarios




2. Actor will select either Left or Right hand side




4. Actor will press Add Banner button System will open the form to upload new banner.

5. Actor will fill the form System will allow6. Actor will press Save button System will save the banner on that

particular location, display a proper message and redirect the user to the previous page.

Alternate Scenarios

Step# Description



Post Conditions

Step# Description

1. The banner will be display on the selected page, side and location.Concurrent User: ‘n’ number of users.


Image Name* (Textbox)Description (Textbox)

Image* (browse)Save (button)


1. Only specific type of images should be uploaded as banners. E.g. JPEG, BMP, GIF, JPG.

2. System should accept the image having a specific resolution as per instruction on the page.

3. System should automatically rotate the banners images periodically on the specified location of the page.

4. Actor can place multiple banners on a single location.



5. There will be 2 sided (Left and Right) having 4 locations for every page to post the banner.



3.1.10.3. Edit Banner

<UC-001: Edit Banner>Actor: AdministratorFeature: This use case will provide the functionality of managing the Banners. Actor can edit the banners successfully by replacing them or changing their name/description.Pre-condition(s) 1. Actor is login









4. Actor will press Edit button System will open that record in edit mode.5. Actor will change the record System will allow6. Actor will press Save button System will save the banner on that

particular location, display a proper message and redirect the user to the previous page.

Alternate Scenarios

Step# Description



3.Actor will visit the previous imageSystem will open the previous image file separately.

Post Conditions

Step# Description

1. The updated banner will be display on the selected page, side and location.Concurrent User: ‘n’ number of users.


Image Name* (Textbox)Description (Textbox)

Image* (browse)Save (button)


1. Only specific type of images should be uploaded as banners. E.g. JPEG, BMP, GIF, JPG.

2. System should accept the image having a specific resolution as per instruction on the page.

3. System should automatically rotate the banners images periodically on the specified location of the page.

4. Actor can place multiple banners on a single location.



5. There will be 2 sided (Left and Right) having 4 locations for every page to post the banner.



3.1.10.4. Delete Banner

<UC-001: Delete Banner>Actor: AdministratorFeature: This use case will provide the functionality of Deleting the Banners. Actor can delete the banners as per requirement.Pre-condition(s) 1. Actor is login









4. Actor will press Delete button System will open a confirmation message to the user.

5. Actor will press OK button System will delete the respective image, update the list and display a proper message.

Alternate Scenarios

Step# Description

1.Actor will press Cancel button.System will not Delete the banner

Post Conditions

Step# Description

1. The deleted banner will not be visible on the selected page, side and location.Concurrent User: ‘n’ number of users.



Business Rules



3.1.11. FAQ Management

3.1.11.1. View FAQs

<UC-001: View FAQs>Actor: AdministratorFeature: This use case will provide the functionality of view the FAQs. Actor can view the existing FAQs successfully.Pre-condition(s) 1. Actor is login

2. At least one FAQ has been defined.Scenarios


1. Actor will open the FAQ Management page.

System will open the FAQ Management page by list down all the existing records.

4. Actor will press Close button System will close the form and redirect the user to the main page.

Alternate Scenarios

Step# Description

Post Conditions

Step# Description



Question (Read only)Answer (Read only)Add New (button)

Edit (button)Delete (button)Close (button)

Business Rules

1. FAQs will be listed down alphabetically.



3.1.11.2. Add FAQ

<UC-001: Add FAQ>Actor: AdministratorFeature: This use case will provide the functionality of add the FAQ. Actor can add the new FAQ record successfully for the proper guidance and help of the visiting user.Pre-condition(s) 1. Actor is loginScenarios




4. Actor will press Add New button System will open the form with all blank fields.


System should allow

4. Actor will press Save button. System should save the record, redirect the user to the listing page and display a proper message

Alternate Scenarios

Step# Description

1. Actor will press Cancel buttonSystem will not save the record.

2. Actor will miss the mandatory fieldSystem will not save the record and display proper message.

Post Conditions

Step# Description

1. The newly added record will be available on the front end on FAQ page.



Question* (Textbox)Answer* (Textbox)

Save (button)Close (button)

Business Rules



3.1.11.3. Edit FAQ

<UC-001: Edit FAQ>Actor: AdministratorFeature: This use case will provide the functionality of edit the FAQ. Actor can edit the FAQ record successfully for the proper guidance and help of the visiting user.Pre-condition(s) 1. Actor is login

2. At least one record already exists.Scenarios




4. Actor will press Edit FAQ button System will open that record in edit mode by showing the previous values.

3. Actor will change the record System should allow4. Actor will press Save button. System should save the record, redirect

the user to the listing page and display a proper message

Alternate Scenarios

Step# Description


2. Actor will miss the mandatory fieldSystem will not save the record and display proper message.

Post Conditions

Step# Description

1. The updated record will be available on the front end on FAQ page.



Question* (Textbox)Answer* (Textbox)

Save (button)Close (button)

Business Rules



3.1.11.4. Delete FAQ

<UC-001: Delete FAQ>Actor: AdministratorFeature: This use case will provide the functionality of Delete the FAQ. Actor can Delete the FAQ record successfullyPre-condition(s) 1. Actor is login





4. Actor will press Delete FAQ button System will open the confirmation message for deletion.

3. Actor will press OK button System should delete the record, update the listing and display proper message.

Alternate Scenarios

Step# Description


Post Conditions

Step# Description

1. The deleted record will not be available on the front end on FAQ page.



OK (button)Close (button)

Business Rules



3.1.12. Profile Management

3.1.12.1. Profile Management

<UC-001: Profile Management>Actor: AdministratorFeature: This use case will provide the functionality of managing the profile. Actor can manage, edit or change his profile information successfully.Pre-condition(s) 1. Actor is loginScenarios


1. Actor will open the Profile Management page.

System will open the Profile Management page by list down all the field of profile page having old values.

2. Actor will edits the information System will allow.3. Actor will press Save button System will save the information and

redirect the user to the main page.

Alternate Scenarios

Step# Description

1. Actor will miss any mandatory fieldSystem will not save the changes and display a proper message.

2. Actor will press cancel buttonSystem will not save the changes

Post Conditions

Step# Description

1. Admin profile is updated



Title* (Textbox)First Name* (Textbox)Last Name* (Textbox)

Email* (Textbox)Address* (Textbox)Country* (Textbox)

City* (Textbox)Phone Number (Textbox)Mobile Number (Textbox)

Fax Number (Textbox)Save (button)


1. Email address should be valid



3.1.12.2. Password Management

<UC-001: Password Management>Actor: AdministratorFeature: This use case will provide the functionality of managing the password. Actor can change his password successfully as per requirement.Pre-condition(s) 1. Actor is loginScenarios


1. Actor will open the Profile Management page.

System will open the Profile Management page by list down all the field of profile page having old values.

2. Actor clicks on Change Password button

System will open the Change password form by showing the fields having old values in New password and Confirm Password fields.

3. Actor fills the form System will allow the user to type the password in encrypted form.

4. Actor will press Save button System will save the information and redirect the user to the main page.

Alternate Scenarios

Step# Description



Post Conditions

Step# Description

1. Admin password is updated



Old Password* (Textbox, encrypted)New Password* (Textbox, encrypted)

Confirm New Password* (Textbox, encrypted)Save (button)


1. Old password must match the existing password

2. New password and confirm new password must match.

3. Password length cannot be less than 5 characters.



3.1.13. Administration Management

3.1.13.1. View Administrators

<UC-001: View Administrators>Actor: AdministratorFeature: This use case will provide the functionality of viewing the accounts of administrator. Actor can add new account of administrator successfully.Pre-condition(s) 1. Actor is loginScenarios


1. Actor will open the Administration Management page.

System will open the Administration Management page by list down all the existing records.

2. Actor will press Close button System will close the form and redirect the user to the main page.

Alternate Scenarios

Step# Description

Post Conditions

Step# Description



First Name (Read only)Last Name (Read only)Username (Read only)

Email (Read only)Add New (button)

Edit (button)Delete (button)Cancel (button)

Business Rules




3.1.13.2. Add New Administrator

<UC-001: Add New Administrator>Actor: AdministratorFeature: This use case will provide the functionality of adding new account of administrator. Actor can add new account of administrator successfully.Pre-condition(s) 1. Actor is loginScenarios



System will open the Administration Management page by list down all the records.

2. Actor press Add New button System will open the form with all fields blank.

3. Actor fills the form System will allow.4. Actor will press Save button System will save the information, redirect

the user to the previous page and display a proper message.

Alternate Scenarios

Step# Description



Post Conditions

Step# Description

1. Admin profile is updated



Title* (Textbox)First Name* (Textbox)Last Name* (Textbox)Username* (Textbox)

Email* (Textbox)Address* (Textbox)Country* (Textbox)

City* (Textbox)Phone Number (Textbox)Mobile Number (Textbox)

Fax Number (Textbox)Save (button)



2. Username cannot be duplicated.



3.1.13.3. Delete Administrator

<UC-001: Delete Administrator>Actor: AdministratorFeature: This use case will provide the functionality of deleting the account of administrator. Actor can delete any account of administrator successfully.Pre-condition(s) 1. Actor is loginScenarios



System will open the Administration Management page by list down all the records.

2. Actor press Delete button System will open the confirmation message for deletion.

3. Actor press OK button System will delete that record, update the listing and display a proper message

Alternate Scenarios

Step# Description


Post Conditions

Step# Description

1. Admin is deleted successfully.



Ok (button)Cancel (button)

Business Rules



3.1.13.4. Edit Administrator Group

<UC-001: Edit Administrator Group>Actor: AdministratorFeature: This use case will provide the functionality of editing the administrator group.Pre-condition(s) 1. Actor is loginScenarios


Alternate Scenarios

Step# Description

Post Conditions

Step# Description



Business Rules



3.1.14. Candidate Management

3.1.14.1. View Pending Candidate Requests<UC-001: View Pending Candidate Requests>

Actor: AdministratorFeature: This use case will provide the functionality of viewing Pending requests of candidates. Actor can see the list of those requests of candidates, which are in pending status for registration.Pre-condition(s) 3. Actor is login

4. At least one pending request existsScenarios


1. Actor goes to Candidate Management link.

System will allow and show the link for Pending Candidate Requests.

2. Actor opens the Pending Candidate Requests page.

System will open the page and list down all the existing records.

3. Actor press Close button System will close the form and redirect the user to the main page.

Alternate Scenarios

Post Conditions



Username (Read only)First Name (Read only)Last Name(Read only)

Email (Read only)Approve (button)Reject (button)

Business Rules



3.1.14.2. Approve Pending Candidate Requests<UC-001: Approve Pending Candidate Requests>

Actor: AdministratorFeature: This use case will provide the functionality of approval the Pending requests of candidates. Actor can approve the pending requests from candidates in order to confirm their registration with the system.Pre-condition(s) 1. Actor is login







3. Actor clicks on the Approve button System will allow and display a confirmation message

4. Actor clicks on Ok button System will update the status of that candidate, update the listing and display a proper message.


Alternate Scenarios

Post Conditions





Business Rules



3.1.14.3. Reject Pending Candidate Requests<UC-001: Reject Pending Candidate Requests>

Actor: AdministratorFeature: This use case will provide the functionality of Rejecting the Pending requests of candidates. Actor can reject the pending requests from candidates for their registration with the system.Pre-condition(s) 1. Actor is login







3. Actor clicks on the Reject button System will allow and display a confirmation message

4. Actor clicks on Ok button System will update the status of that candidate, update the listing and display a proper message.


Alternate Scenarios

Post Conditions





Business Rules



3.1.14.4. View Incomplete Candidate Requests<UC-001: View Incomplete Candidate Requests>

Actor: AdministratorFeature: This use case will provide the functionality of viewing the incomplete requests of candidates. Actor can see the list of those requests of candidates, which are incomplete for registration.Pre-condition(s) 1. Actor is login

2. At least one incomplete request existsScenarios



System will allow and show the link for Incomplete Candidate Requests.

2. Actor opens the Incomplete Candidate Requests page.



Alternate Scenarios

Post Conditions




Email (Read only)Delete (button)

Business Rules



3.1.14.5. Delete Incomplete Candidate Requests<UC-001: Delete Incomplete Candidate Requests>

Actor: AdministratorFeature: This use case will provide the functionality of Deletion of incomplete requests of candidates. Actor can delete the incomplete requests from candidates for their registration with the system.Pre-condition(s) 1. Actor is login




System will allow and show the link for Incomplete Candidate Requests.

2. Actor opens the Incomplete Candidate Requests page.


3. Actor clicks on the Delete button System will allow and display a confirmation message

4. Actor clicks on Ok button System will delete that request, update the listing and display a proper message.


Alternate Scenarios

Post Conditions





Business Rules



3.1.14.6. View Approved Candidate<UC-001: View Approved Candidate>

Actor: AdministratorFeature: This use case will provide the functionality of viewing the Approved requests of candidates. Actor can see the list of those requests of candidates, which are Approved and active for registration.Pre-condition(s) 1. Actor is login

2. At least one approved request existsScenarios



System will allow and show the link for Approved Candidate Requests.

2. Actor opens the Approved Candidate Requests page.



Alternate Scenarios

Post Conditions





Edit (button)Delete (button)Close (button)

Business Rules

1. Only Approved candidates must be visible on this page.



3.1.14.7. View Rejected Candidate<UC-001: View Rejected Candidate>

Actor: AdministratorFeature: This use case will provide the functionality of viewing the Rejected requests of candidates. Actor can see the list of those requests of candidates, which are Rejected.Pre-condition(s) 1. Actor is login

2. At least one rejected request existsScenarios



System will allow and show the link for Rejected Candidate Requests.

2. Actor opens the Rejected Candidate Requests page.



Alternate Scenarios

Post Conditions




Email (Read only)Delete (button)Close (button)

Business Rules

1. Only Rejected candidates must be visible on this page.



3.1.14.8. Add New Candidate<UC-002: Add New Candidate>

Actor: AdministratorFeature: This use case will provide the functionality of adding a new candidate. Actor can add a new record of candidate.Pre-condition(s) 2. Actor is loginScenarios






3. Actor press Add New button System will open the page with all fields blank.

4. Actor fills the form along with all mandatory fields

System will allow


Alternate Scenarios

Step# Description



Post Conditions

Step# Description






Email* (text box)Username* (text box)Password* (textbox)

Confirm Password* (textbox)First Name* (text box)Last Name* (text box)

Gender* (Drop down menu)Date of Birth* (Drop down menu)

Country* (Drop down menu) State* (Drop down menu)City* (Drop down menu)

Home Phone (text box menu)Mobile Phone* (text boxes)Degree* (Drop down menu)

Degree Title* (text box)Degree Completion Year* (dropdown)

Institution* (text box)Profession Industry* (Drop down menu)

Total Professional Experience* (Drop down menu) Latest Job Title* (text box)

Job Duration* (Drop down menu)Company* (text box)CV upload (browse)

Sign Up* (button)

Business Rules

1. Duplicated Email is not allowed.

2. Email must be valid

3. Date of Birth cannot be future date

4. Only valid formats of CV can be uploaded.

5. Duplicated Username is not allowed



3.1.14.9. Edit Candidate<UC-001: Edit Candidate>

Actor: AdministratorFeature: This use case will provide the functionality of editing a Candidate record. Actor can edit the existing candidate record.Pre-condition(s) 3. Actor is login

4. At least one candidate record already exists.Scenarios






3. Actor clicks on edit button System will open that record in edit mode by showing all the previous values.


System will allow.


Alternate Scenarios

Step# Description



Post Conditions

Step# Description














Save (button)Cancel (button)

Business Rules








3.1.14.10.Delete Candidate<UC-001: Delete Candidate>

Actor: AdministratorFeature: This use case will provide the functionality of deleting a candidate record. Actor can delete the existing candidate record.Pre-condition(s) 3. Actor is login

4. At least one candidate record already exists.Scenarios









Alternate Scenarios

Step# Description


Post Conditions

Step# Description




Business Rules



3.1.14.11.View Videos of Candidate<UC-001: View Videos of Candidate>

Actor: AdministratorFeature: This use case will provide the functionality of viewing the Videos of candidates. Actor can see the list of videos uploaded by the candidates.Pre-condition(s) 1. Actor is login

2. At least one record existsScenarios






3. Actor clicks on the Video button against any candidate record.

System will open the page of Videos uploaded by that candidate by showing all the video records.

3. Actor press Close button System will close the form and redirect the user to the previous page.

Alternate Scenarios

Post Conditions



Username (Read only)Video Name (Read only)

Size (Read only)View (button)


Delete (button)Close (button)

Business Rules



3.1.14.12.Upload Videos of Candidate<UC-001: Upload Videos of Candidate>

Actor: AdministratorFeature: This use case will provide the functionality of uploading the new Videos against candidates. Actor can add new video against any candidate, which will be visible in the account of candidate on front end.Pre-condition(s) 1. Actor is loginScenarios








4. Actor clicks on Add New button System will open the form to add new video with all fields blank.


System will allow.

6. Actor press Save button System will save the record, redirect the user to the previous page, display a proper message and update the listing.

Alternate Scenarios

Step# Description

1.Actor will press Cancel button on the confirmation windowSystem will not saving the record

2.Mandatory field is not filled by actor.System will not allow saving the record.

Post Conditions

Step# Description

1. Videos will be available in the candidates account.

2. Actor can edit the video

3. Actor can delete the video



Video Title* (Textbox)Video file* (Browse)

Description (Textbox)Save (button)

Add New (button)Close (button)

Business Rules

1. Video file format must be valid



2. Video file size should be according to the mentioned size on the page.



3.1.14.13.Delete Videos of Candidate<UC-001: Delete Videos of Candidate>

Actor: AdministratorFeature: This use case will provide the functionality of Deleting the Videos against candidates. Actor can delete the videos against any candidate.Pre-condition(s) 1. Actor is login

2. At least one record must existsScenarios








4. Actor clicks on Delete button System will show the confirmation message.

5. Actor press Ok button System will delete that record, update the listing and display a proper message.

Alternate Scenarios

Step# Description


Post Conditions

Step# Description

1. Video will not be available in the candidates account.



Ok (button)Close (button)

Business Rules



3.1.14.14.Upload own Interview Videos of Candidate<UC-001: Upload own Interview Videos of Candidate>

Actor: AdministratorFeature: This use case will provide the functionality of uploading the new Interview videos against candidates. Actor can add new interview video against any candidate, which will be for all other employers where that candidate will apply, but this video will not be visible to the candidate.Pre-condition(s) 1. Actor is loginScenarios






3. Actor clicks on the Interview Video button against any candidate record.

System will open the page of Interview videos by showing the previous values

5. Actor uploads a new video along with all mandatory fields

System will allow.


Alternate Scenarios

Step# Description



Post Conditions

Step# Description

1.Videos will be available for other employers if that particular candidate apply against their posted jobs.

2. Actor can edit the video







Business Rules





3. Interview video is not visible to the candidate



3.1.14.15.Edit own Interview Videos of Candidate<UC-001: Edit own Interview Videos of Candidate>

Actor: AdministratorFeature: This use case will provide the functionality of editing the Interview videos against candidates. Actor can edit interview video against any candidate, which will be for all other employers where that candidate will apply, but this video will not be visible to the candidate.Pre-condition(s) 1. Actor is login








System will open the page of Interview videos by showing the previous values.

4. Actor edits the record along with all mandatory fields

System will allow.


Alternate Scenarios

Step# Description



Post Conditions

Step# Description

1.Videos will be available for other employers if that particular candidate applies against their posted jobs.







Business Rules






3.1.14.16.Delete own Interview Videos of Candidate<UC-001: Delete own Interview Videos of Candidate>

Actor: AdministratorFeature: This use case will provide the functionality of deleting the Interview videos against candidates. Actor can delete the interview video against any candidate.Pre-condition(s) 1. Actor is login








System will open the page of Interview videos by showing the previous values.

4. Actor clicks on Delete button System will show a confirmation message5. Actor clicks on Ok button System will delete that record, redirect the

user to the previous page, display a proper message and update the listing.

Alternate Scenarios

Step# Description


Post Conditions

Step# Description

1. Videos will not be available for other employers



Ok (button)Close (button)

Business Rules






3.1.14.17.View Job Newsletter Subscribers<UC-001: View Job Newsletter Subscribers>

Actor: AdministratorFeature: This use case will provide the functionality of viewing job newsletter subscribers. Actor will be able to view those candidates who are subscribed for the job newsletter.Pre-condition(s) 1. Actor is login

2. At least one subscriber must exist.Scenarios



System will allow and show the link for Newsletter Subscribers.

2. Actor opens the Newsletter Subscribers page.


Alternate Scenarios

Step# Description

Post Conditions

Step# Description



From Email (Textbox)From Name (Textbox)

Subject (Textbox)Details (Editor)

Check All (button)Clear All (button)

Send (buttonCancel (button)

Business Rules



3.1.14.18.Send Job Newsletter<UC-001: Send Job Newsletter >

Actor: AdministratorFeature: This use case will provide the functionality of sending job newsletter. Actor will be able to send the job newsletter to the candidatesPre-condition(s) 1. Actor is login







3. Actor selects the candidates System will allow4. Actor compose the newsletter along

with all mandatory fieldsSystem will allow

5. Actor sends the newsletter System will allow, send the newsletter to the selected candidates and display a proper message.

Alternate Scenarios

Step# Description

1. Actor press cancel buttonSystem will not send the newsletter

2. Mandatory field is missed by the actorSystem will not send the newsletter and display a proper message

Post Conditions

Step# Description

1. Newsletter email will be sent to all subscribed members.



From Email* (Textbox)From Name* (Textbox)

Subject* (Textbox)Details* (Editor)



Business Rules

1. From Email must be valid.

2. At least one member must be selected for sending the newsletter.



3.1.15. Employer Management

3.1.15.1. View Pending Employer Requests<UC-001: View Pending Employer Requests>

Actor: AdministratorFeature: This use case will provide the functionality of viewing Pending requests of Employers. Actor can see the list of those requests of Employers, which are in pending status for registration.Pre-condition(s) 5. Actor is login



1. Actor goes to Employer Management link.

System will allow and show the link for Pending Employer Requests.

2. Actor opens the Pending Employer Requests page.



Alternate Scenarios

Post Conditions





Business Rules



3.1.15.2. Approve Pending Employer Requests<UC-001: Approve Pending Employer Requests>

Actor: AdministratorFeature: This use case will provide the functionality of approval the Pending requests of Employers. Actor can approve the pending requests from Employers in order to confirm their registration with the system.Pre-condition(s) 3. Actor is login







3. Actor clicks on the Approve button System will allow and display a confirmation message

4. Actor clicks on Ok button System will update the status of that Employer, update the listing and display a proper message.


Alternate Scenarios

Post Conditions





Business Rules



3.1.15.3. Reject Pending Employer Requests<UC-001: Reject Pending Employer Requests>

Actor: AdministratorFeature: This use case will provide the functionality of Rejecting the Pending requests of Employers. Actor can reject the pending requests from Employers for their registration with the system.Pre-condition(s) 3. Actor is login







3. Actor clicks on the Reject button System will allow and display a confirmation message

4. Actor clicks on Ok button System will update the status of that Employer, update the listing and display a proper message.


Alternate Scenarios

Post Conditions





Business Rules



3.1.15.4. View Incomplete Employer Requests<UC-001: View Incomplete Employer Requests>

Actor: AdministratorFeature: This use case will provide the functionality of viewing the incomplete requests of Employers. Actor can see the list of those requests of Employers, which are incomplete for registration.Pre-condition(s) 3. Actor is login




System will allow and show the link for Incomplete Employer Requests.

2. Actor opens the Incomplete Employer Requests page.



Alternate Scenarios

Post Conditions





Business Rules



3.1.15.5. Delete Incomplete Employer Requests<UC-001: Delete Incomplete Employer Requests>

Actor: AdministratorFeature: This use case will provide the functionality of Deletion of incomplete requests of Employers. Actor can delete the incomplete requests from Employers for their registration with the system.Pre-condition(s) 3. Actor is login




System will allow and show the link for Incomplete Employer Requests.

2. Actor opens the Incomplete Employer Requests page.


3. Actor clicks on the Delete button System will allow and display a confirmation message

4. Actor clicks on Ok button System will delete that request, update the listing and display a proper message.


Alternate Scenarios

Post Conditions





Business Rules



3.1.15.6. View Approved Employer<UC-001: View Approved Employer>

Actor: AdministratorFeature: This use case will provide the functionality of viewing the Approved requests of Employers. Actor can see the list of those requests of Employers, which are Approved and active for registration.Pre-condition(s) 3. Actor is login




System will allow and show the link for Approved Employer Requests.

2. Actor opens the Approved Employer Requests page.



Alternate Scenarios

Post Conditions






Job details(button)Close (button)

Business Rules

1. Only Approved Employers must be visible on this page.



3.1.15.7. View Rejected Employer<UC-001: View Rejected Employer>

Actor: AdministratorFeature: This use case will provide the functionality of viewing the Rejected requests of Employers. Actor can see the list of those requests of Employers, which are Rejected.Pre-condition(s) 3. Actor is login




System will allow and show the link for Rejected Employer Requests.

2. Actor opens the Rejected Employer Requests page.



Alternate Scenarios

Post Conditions




Email (Read only)Delete (button)Close (button)

Business Rules

1. Only Rejected Employers must be visible on this page.



3.1.15.8. Add New Employer<UC-002: Add New Employer>

Actor: AdministratorFeature: This use case will provide the functionality of adding a new Employer. Actor can add a new record of Employer.Pre-condition(s) 3. Actor is loginScenarios






3. Actor press Add New button System will open the page with all fields blank.


System will allow


Alternate Scenarios

Step# Description



Post Conditions

Step# Description
















Business Rules








3.1.15.9. Edit Employer<UC-001: Edit Employer>

Actor: AdministratorFeature: This use case will provide the functionality of editing a Employer record. Actor can edit the existing Employer record.Pre-condition(s) 5. Actor is login

6. At least one Employer record already exists.Scenarios






3. Actor clicks on edit button System will open that record in edit mode by showing all the previous values.


System will allow.


Alternate Scenarios

Step# Description



Post Conditions

Step# Description















Business Rules








3.1.15.10.Delete Employer<UC-001: Delete Employer>

Actor: AdministratorFeature: This use case will provide the functionality of deleting a Employer record. Actor can delete the existing Employer record.Pre-condition(s) 5. Actor is login

6. At least one Employer record already exists.Scenarios









Alternate Scenarios

Step# Description


Post Conditions

Step# Description




Business Rules



3.1.15.11.View Job Newsletter Subscribers<UC-001: View Job Newsletter Subscribers>

Actor: AdministratorFeature: This use case will provide the functionality of viewing job newsletter subscribers. Actor will be able to view those employers who are subscribed for the newsletter.Pre-condition(s) 3. Actor is login







Alternate Scenarios

Step# Description

Post Conditions

Step# Description



From Email (Textbox)From Name (Textbox)

Subject (Textbox)Details (Editor)



Business Rules



3.1.15.12.Send Newsletter<UC-001: Send Newsletter >

Actor: AdministratorFeature: This use case will provide the functionality of sending newsletter. Actor will be able to send the newsletter to the employersPre-condition(s) 3. Actor is login







3. Actor selects the employers System will allow4. Actor compose the newsletter along

with all mandatory fieldsSystem will allow

5. Actor sends the newsletter System will allow, send the newsletter to the selected employers and display a proper message.

Alternate Scenarios

Step# Description

1. Actor press cancel buttonSystem will not send the newsletter

2. Mandatory field is missed by the actorSystem will not send the newsletter and display a proper message

Post Conditions

Step# Description

1. Newsletter email will be sent to all subscribed members.



From Email* (Textbox)From Name* (Textbox)

Subject* (Textbox)Details* (Editor)



Business Rules

1. From Email must be valid.

2. At least one member must be selected for sending the newsletter.



3.1.15.13.Add New Job<UC-002: Add New Job>

Actor: AdministratorFeature: This use case will provide the functionality of adding a new Job. Actor can add a new job against employers.Pre-condition(s) 1. Actor is loginScenarios






3. Actor press Job Details button System will open the page of job details by listing down all the active jobs.

4. Actor Press Add New button System will open the page with all fields blank.


System will allow


Alternate Scenarios

Step# Description



Post Conditions

Step# Description






Job Title* (Text box)No. of Positions (Drop down)

Industry* (Drop down )Department (Text box)

Job Type* (Drop down )Job Shift (Drop down )

Job Location* - Country*/State/City (Drop down)Gender* (Drop down )

Age From (Drop down ) - Age To (Drop down)Degree Level* - Min/Max (Radio button), Degree (Drop Down )

Degree Title (Text box)Career Level* (Drop down )

Experience* - Min/Max (Radio button), Years (Drop Down )Work Permit (Drop down )

Require Travel (Drop down )Salary Range – From (Text box) To (Text box), Salary Per(dropdown)

Currency (Drop Down )Apply By – Day/Month/Year (Drop down )

Deactivate this job after Apply By date (Check box)Job Description* (Rich text editor)

Required Skills (Text box)Email resume? (Check box)Email resume to (Text box)

Cancel (Button)Post Job (Button)

Business Rules

1. Age from cannot be greater than Age to.

2. Salary Range From cannot be greater then To.

3. Apply By date cannot be past date

4. Email Resume to must be a valid email address

5. No. of Positions dropdown will have the value from 1 to 20+.

6. Industry dropdown will have the values updated by the administrator.

7. Job type dropdown will have the values as:PermanentFull timePart timeContractInternship

8. Job shift dropdown will have the values as:First shift (Day)Second shift (Afternoon)Third shift (Night)Rotating

9. Job Location dropdown will have the values updated by the administrator

10. Gender dropdown will have the values as Male and Female.

11. Age From and Age To dropdowns will have the values from 10-40+



12. Degree dropdown will have the values as:Non-matriculationMatriculation/O-LevelIntermediate/A-LevelBachelor DegreeMaster DegreeDoctorate

13. Career level dropdown will have the values as:Student (undergraduate/graduate)Entry LevelExperience (Non-Manager)

14. Year dropdown will have the digits values from 0 to 20+

15. Work permit will have the values of countries as updated by administrator.

16. Require Travel dropdown will have the values as:Not required25%50%75%100%

17. Salary Per dropdown will have the values:Per HourPer WeekPer MonthPer YearCurrency dropdown will have the values from all countries. e.g. Pakistani Rupees.



3.1.15.14.Edit Job<UC-002: Edit Job>

Actor: AdministratorFeature: This use case will provide the functionality of editing a Job. Actor can edit an existing job against employers.Pre-condition(s) 1. Actor is login








4. Actor Press Edit button System will open the page with all fields having old values.

4. Actor changes the information along with all mandatory fields

System will allow


Alternate Scenarios

Step# Description



Post Conditions

Step# Description

1. Actor will be able to delete the record2. Updated record will be listed where it will be requiredConcurrent User: ‘n’ number of users.




Job Title* (Text box)No. of Positions (Drop down)

Industry* (Drop down )Department (Text box)

Job Type* (Drop down )Job Shift (Drop down )

Job Location* - Country*/State/City (Drop down)Gender* (Drop down )

Age From (Drop down ) - Age To (Drop down)Degree Level* - Min/Max (Radio button), Degree (Drop Down )

Degree Title (Text box)Career Level* (Drop down )

Experience* - Min/Max (Radio button), Years (Drop Down )Work Permit (Drop down )

Require Travel (Drop down )Salary Range – From (Text box) To (Text box), Salary Per(dropdown)

Currency (Drop Down )Apply By – Day/Month/Year (Drop down )


Required Skills (Text box)Email resume? (Check box)Email resume to (Text box)

Cancel (Button)Post Job (Button)

Business Rules

1. Age from cannot be greater than Age to.

2. Salary Range From cannot be greater then To.

3. Apply By date cannot be past date

4. Email Resume to must be a valid email address



3.1.15.15.Delete Job<UC-002: Delete Job>

Actor: AdministratorFeature: This use case will provide the functionality of Deleting a Job. Actor can delete an existing job against employers.Pre-condition(s) 1. Actor is login








4. Actor Press delete button System will open the confirmation message.

4. Actor press OK button System will delete the job, update the listing and display a proper message.

5. Actor will press Close button System will close the form and redirect the user to the previous page.

Alternate Scenarios

Step# Description


Post Conditions

Step# Description

1. Record will not be listed where it will be requiredConcurrent User: ‘n’ number of users.


OK (Button)Cancel (Button)

Business Rules



3.1.15.16.View Pending Job Request<UC-001: View Pending Job requests>

Actor: AdministratorFeature: This use case will provide the functionality of viewing the pending requests of job. Actor can see the list of those job requests of Employers, which are pending.Pre-condition(s) 1. Actor is loginScenarios






3. Actor opens the Job details button System will open the job page and list down the entire Pending job requests.


Alternate Scenarios

Post Conditions



Username (Read only)Job title (Read only)Location (Read only)Apply By (Read only)

Delete (button)Approve (button)Reject (button)

Job details(button)View Approved jobs (button)View Rejected jobs (button)

Close (button)Business Rules

1. Only Pending Jobs must be visible on this page.



3.1.15.17.View Approved Job Request<UC-001: View Approved Job requests>

Actor: AdministratorFeature: This use case will provide the functionality of viewing the Approved requests of job. Actor can see the list of those job requests of Employers, which are Approved.Pre-condition(s) 1. Actor is login








4. Actor clicks on View Approved Jobs button

System will open the Approved job page and list down the entire Approved job requests.

Alternate Scenarios

Post Conditions





Reject (button)Delete (button)

Activate (button)Inactivate (button)

View Rejected Jobs (button)View Active Jobs (button)

View Inactive Jobs (button)Close (button)

Business Rules

1. Only Approved Jobs must be visible on this page.



3.1.15.18.View Rejected Job Request<UC-001: View Rejected Job requests>

Actor: AdministratorFeature: This use case will provide the functionality of viewing the Rejected requests of job. Actor can see the list of those job requests of Employers, which are Rejected.Pre-condition(s) 1. Actor is login








4. Actor clicks on View Rejected Jobs button

System will open the Rejected job page and list down the entire Rejected job requests.

Alternate Scenarios

Post Conditions




Delete (button)Job details(button)

View Approved jobs (button)Close (button)

Business Rules

1. Only Rejected Jobs must be visible on this page.



3.1.15.19.Approve Job<UC-001: Approve Job>

Actor: AdministratorFeature: This use case will provide the functionality of Approving the pending requests of job. Actor can approve those job requests of Employers, which are pending.Pre-condition(s) 1. Actor is login

2. At least one pending request must exist.Scenarios







4. Actor clicks on Approve button System will show the confirmation message.

5. Actor press OK button System will approve the job, update the listing and display the proper message.


Alternate Scenarios

Step# Description


Post Conditions

Step# Description

1. The record will be available on the front end for CV posting.

2. The record will be available on Approved jobs page.




Business Rules

1. All approved jobs will be active by default.



3.1.15.20.Reject Job<UC-001: Reject Job>

Actor: AdministratorFeature: This use case will provide the functionality of Rejecting the pending requests of job. Actor can reject those job requests of Employers, which are pending.Pre-condition(s) 1. Actor is login

2. At least one pending request must exist.Scenarios







4. Actor clicks on Reject button System will show the confirmation message.

5. Actor press OK button System will approve the job, update the listing and display the proper message.


Alternate Scenarios

Step# Description


Post Conditions

Step# Description

1. The record will not be available on the front end for CV posting.

2. The record will be available on the Rejected Jobs page.




Business Rules



3.1.15.21.View Active Job Request<UC-001: View Active Job requests>

Actor: AdministratorFeature: This use case will provide the functionality of viewing the active requests of job. Actor can see the list of those job requests of Employers, which are active.Pre-condition(s) 1. Actor is login

2. At least one approved request exists3. At least one active request exists.

Scenarios







4. Actor clicks on View Active Jobs button

System will open the Active job page and list down the entire Active job requests.

Alternate Scenarios

Post Conditions





Inactive (button)Delete (button)


Business Rules




3.1.15.22.View Inactive Job Request<UC-001: View Inactive Job requests>

Actor: AdministratorFeature: This use case will provide the functionality of viewing the inactive requests of job. Actor can see the list of those job requests of Employers, which are inactive.Pre-condition(s) 1. Actor is login

2. At least one approved request exists3. At least one inactive request exists.

Scenarios







4. Actor clicks on View Inactive Jobs button

System will open the Inactive job page and list down the entire Inactive job requests.

Alternate Scenarios

Post Conditions




Delete (button)Active (button

View Active Jobs (button)Close (button)

Business Rules




3.1.15.23.Activate Job<UC-001: Activate Job>

Actor: AdministratorFeature: This use case will provide the functionality of activation of job. Actor can activate the job successfully.Pre-condition(s) 1. Actor is login









System will open the Approved job page and list down the entire approved job requests.

5. Actor clicks on active button against any job

System will show a confirmation message.

6. Actor clicks on OK button System will activate the job and display a proper message.

Alternate Scenarios

Step# Description

1.Actor will press Cancel button after filling the formSystem will not activate the inactive job

Post Conditions

Step# Description

1.Active job will be available on front end and candidate will be able to post his CV for that job.




Delete (button)Active/Inactivate (button)View Active Jobs (button)


Business Rules




3.1.15.24.Inactivate Job<UC-001: Inactivate Job>

Actor: AdministratorFeature: This use case will provide the functionality of inactivation of job. Actor can inactivate the job successfully.Pre-condition(s) 1. Actor is login









System will open the Approved job page and list down the entire approved job requests.

5. Actor clicks on inactive button against any job

System will show a confirmation message.

6. Actor clicks on OK button System will inactivate the job and display a proper message.

Alternate Scenarios

Step# Description

1.Actor will press Cancel button after filling the formSystem will not inactivate the active job

Post Conditions

Step# Description

1.Inactive job will not be available on front end, so the candidate will not be able to post his CV for that job.




Delete (button)Active/Inactivate (button)View Active Jobs (button)


Business Rules




3.2.Candidate

3.2.1. Candidate Profile

3.2.1.1. Account Creation

<UC-001: User Registration as Candidate>Actor: CandidateFeature: This use case will provide the functionality of candidate registration. Candidate will fill the registration form in order to complete the registration process to use the complete services of the system.Pre-condition(s) 7. Webpage will be opened.Scenarios


1. Actor will open the relevant webpage System will open the webpage against the correct URL.

2. Actor press “Sign Up” link System will open the registration form with all fields blank.


System will allow

4. Actor press Register button System will allow and save the information, register the user and login the candidate by entering correct username and password.

Alternate Scenarios

1. Actor types incorrect URL to open the page.System will not open the page

2. Actor doesn’t fill all the mandatory fields and press Register buttonSystem will not allow the registration and will display a relevant message.

Post Conditions

Step# Description

1. Actor will be able to manage profiles

2. Actor will be able to upload/edit/delete their photos

3. Actor will be able to upload or copy and paste their resume

4. Actor will be able to edit/delete their resume

5. Actor will be able to upload/edit/delete their video for employers

6. Actor will be able to search jobs

7 Actor will be able to view employer information

8 Actor will be able to apply for jobs

9 Actor will be able to view/manage History of their applications for jobs

10 Actor will be able to set customized searches for future job

11 Actor will be able to Subscribe to Job Newsletter







Gender* (Drop down menu)Date of Birth* (Drop down menus)

Address* (text box)Country* (Drop down menu)

State* (Drop down menu)City* (Drop down menu)Home Phone (text box)

Mobile Phone* (text box)Degree* (Drop down menu)

Degree Title* (text box)Degree Completion Year* (drop down menu)




Terms and Conditions* (check box)How did You here about us* (Drop down menu)

Image verification box* (text box)Register* (button)

Business Rules

1. Email should be entered in a valid format

2. Actor cannot enter duplicate email address

3. Username cannot be duplicated

4. In password fields only * should be visible

6. Password and confirm password should match

7. Date of birth should be less than the current date

8. By default, no country will be selected

9. Country cannot be duplicated

10. By selecting a particular country, its states will only be visible

11. By default, no state will be selected

12. State cannot be duplicated

13. By selecting a particular State, only its cities will be visible

14. By default, no city will be selected

15. City cannot be duplicated

16. Phone fields will only accept numeric values

17. From date in Job duration should be less than to date

18. Only specified format file can be uploaded



3.2.1.2. Edit Candidate Profile

<UC-001: Edit Candidate Profile>Actor: CandidateFeature: This use case will provide the functionality of candidate profile edition. Candidate will edit the form in order to complete the updation process.Pre-condition(s) 1. The actor must be logged in.

2. Webpage will be opened.Scenarios


1. Actor press “Edit Profile” link System will open the candidate profile form showing all fields values.

2. Actor edits the form System will allow3. Actor press Update button System will allow and save the information

in the system.

Alternate Scenarios

1. Actor doesn’t fill any mandatory field and press Update buttonSystem will not allow the updation and will display a relevant message.

Post Conditions

Step# Description


2. Actor will be able to upload/edit/delete their photos

3. Actor will be able to upload or copy and paste their resume

4. Actor will be able to edit/delete their resume

5. Actor will be able to upload/edit/delete their video for employers

6. Actor will be able to search jobs

7 Actor will be able to view employer information

8 Actor will be able to apply for jobs

9 Actor will be able to view/manage History of their applications for jobs

10 Actor will be able to set customized searches for future job

11 Actor will be able to Subscribe to Job Newsletter





Email* (text box)Username* (text box)

Old Password* (textbox)New Password* (text box)

Confirm New Password* (textbox)First Name* (text box)Last Name* (text box)Gender* (Drop down)

Date of Birth* (Drop down menus)Address* (text box)

Country* (Drop down menu)State* (Drop down menu)City* (Drop down menu)Home Phone (text box)

Mobile Phone* (text box)Degree* (Drop down menu)

Degree Title* (text box)Degree Completion Year* (drop down menu)


Total Professional Experience* (drop down menu) Latest Job Title* (text box)

Job Duration* (Drop down menu)Company* (text box)

Update (button)

Business Rules


2. Username field should be read-only

3. Old password should be correct

4. In password fields only * should be visible

5. New password and confirm new password should match

6. Date of birth should be less than the current date

7. By default, previous country will be selected


9. By selecting a particular country, its states will only be visible

10. By default, previous state will be selected

11. State cannot be duplicated

12. By selecting a particular State, only its cities will be visible

13. By default, previous city will be selected


15. Phone fields will only accept numeric values

16. From date in Job duration should be less than to date



3.2.2. Photo Management

3.2.2.1. Upload Candidate Photo

<UC-001: Upload Candidate Photo>Actor: CandidateFeature: This use case will provide the functionality of uploading candidate photo.Pre-condition(s) 1. The actor must be logged in.



1. Actor press “Upload Photo” link System will open the upload photo window.

2. Actor press browse button System will open the browse window3. Actor selects photo to be uploaded System will allow and display the photo

path in the field4. Actor press “Upload” button System will upload the photo and display a

relevant message.

Alternate Scenarios

1. Actor press “cancel” button during photo uploading processSystem will not upload the photo and return to upload photo window

2. Actor upload photo with invalid formatSystem will not upload the photo

3. Actor doesn’t fill the mandatory field and press upload buttonSystem will not allow uploading photo and will display a relevant message.

Post Conditions

Step#

Description

1. Actor will be able to activate the uploaded photo

2. Actor will be able to view the uploaded photo

3. Actor will be able to apply for a job with the uploaded photo



Upload photo* (text box)Browse (button)

Upload photo (button)Business Rules

1. Photo should be uploaded in a valid format

2. Photo size should be less than the specified size

3. Multiple photos can be uploaded



3.2.2.2. Edit Candidate Photo

<UC-001: Edit Candidate Photo>Actor: CandidateFeature: This use case will provide the functionality of editing existing candidate photo.Pre-condition(s) 1. The actor must be logged in.

2. At least one photo must exist3. Webpage will be opened.

Scenarios


1. Actor press “Edit Photo” link System will open the Edit photo window.2. Actor press browse button System will open the browse window3. Actor selects photo to be uploaded System will allow and display the photo

path in the text field4. Actor press “Update” button System will update the photo and display

a relevant message.

Alternate Scenarios

1. Actor press “cancel” button during photo updation processSystem will not upload the photo and return to edit photo window

2. Actor upload photo with invalid formatSystem will not upload the photo

3. Actor doesn’t fill the mandatory field and press update buttonSystem will not allow uploading photo and will display a relevant message.

Post Conditions

Step# Description

1. Actor will be able to activate the updated photo

2. Actor will be able to view the updated photo

3. Actor will be able to apply for a job with the updated photo



Upload photo* (text box)Browse (button)

Update photo (button)

Business Rules

1. Photo should be uploaded in a valid format

2. Photo size should be less than the specified size



3.2.2.3. Delete Candidate Photo

<UC-001: Delete Candidate Photo>Actor: CandidateFeature: This use case will provide the functionality of deleting existing candidate photo.Pre-condition(s) 1. The actor must be logged in.

2. Al least one photo must exist 3. Webpage will be opened.

Scenarios


1. Actor selects the photo to be deleted and checks its corresponding checkbox

System will allow

2. Actor press “Delete” button System will Delete the photo and display a relevant message.

Alternate Scenarios

1. Actor press “Delete” button without checking the checkboxSystem will not delete any photo and display a relevant message

2. Actor press “Cancel” buttonSystem will not delete the selected photo

Post Conditions

Step# Description

1. Actor will not be able to view the deleted photo



Uploaded photos (read only)Remove photo (check boxes)

Delete (button)

Business Rules

1. Multiple photos can be deleted at a time



3.2.3. Resume Management

3.2.3.1. Upload Resume

<UC-001: Upload Resume>Actor: CandidateFeature: This use case will provide the functionality of uploading candidate Resume.Pre-condition(s) 1. The actor must be logged in.



1. Actor press “Upload Resume” link System will open the upload resume window.

2. Actor Enters resume title System will allow3.. Actor press browse button System will open the browse window4. Actor selects resume to be uploaded System will allow and display the resume

path in the field5.. Actor press “Upload” button System will upload the resume and display

a relevant message.

Alternate Scenarios

1. Actor press “cancel” button during resume uploading processSystem will not upload the resume and return to upload resume window

2. Actor upload resume with invalid formatSystem will not upload the resume

3. Actor doesn’t fill the mandatory field and press upload buttonSystem will not allow uploading resume and will display a relevant message.

Post Conditions

Step# Description

1. Actor will be able to view the uploaded resume

2. Actor will be able to apply for a job with uploaded resume

3. Actor will be able to download the uploaded resume

4. Actor will be able to remove the uploaded resume



Resume Upload (radio box selected)Resume Title* (textbox)

Upload Resume* (text box)Browse (button)

Resume Upload (button)

Business Rules

1. Resume should be uploaded in a valid format

2. Resume file size should be less than the specified size

3. Multiple resumes can be uploaded



3.2.3.2. Copy or Paste Resume

<UC-001: Copy or Paste Resume>Actor: CandidateFeature: This use case will provide the functionality of copy and paste candidate Resume.Pre-condition(s) 1. The actor must be logged in.



1. Actor selects “Copy and Paste Resume” option

System will display the copy and paste resume window and upload option will be non functional.

2. Actor Enters resume information in the editor

System will allow

3. Actor press “Save” button System will save the resume and display a relevant message.

Alternate Scenarios

1. Actor press “cancel” button during resume copy and paste processSystem will not save the resume

Post Conditions

Step# Description

1. Actor will be able to view the copy and paste resume

2. Actor will be able to apply for a job with copy and paste resume

3. Actor will be able to download the copy and paste resume



Copy and Paste Resume (radio box)Resume Writing Editor* (text area)

Save (button)

Business Rules

1. None



3.2.4. Video Management

3.2.4.1. Upload candidate Video

<UC-001: Upload Candidate Video>Actor: CandidateFeature: This use case will provide the functionality of uploading candidate video.Pre-condition(s) 1. The actor must be logged in.



1. Actor press “Upload video” link System will open the upload video window.

2. Actor press browse button System will open the browse windowActor selects video to be uploaded and press open button

System will allow and display the video path in the field

3. Actor press “Upload” button System will upload the video and display a relevant message.

Alternate Scenarios

1. Actor press “cancel” button during video uploading processSystem will not upload the video and return to upload video window

2. Actor upload video with invalid formatSystem will not upload the video and display a relevant message

3. Actor doesn’t fill the mandatory fields and press upload buttonSystem will not allow uploading video and will display a relevant message.

Post Conditions

Step# Description

1. Actor will be able to activate the uploaded video

2. Actor will be able to view the uploaded video

3. Actor will be able to apply for a job with the uploaded video



Upload video* (text box)Browse (button)

Upload Video (button)

Business Rules

1. Video should be uploaded in a valid format

2. Video size should be less than the specified size



3.2.4.2. Edit Candidate Video

<UC-001: Edit Candidate video>Actor: CandidateFeature: This use case will provide the functionality of editing existing candidate videos.Pre-condition(s) 1. The actor must be logged in.

2. At least one video must exist3. Webpage will be opened.

Scenarios


1. Actor press “Edit video” link System will open the Edit video window.2. Actor press browse button System will open the browse window

Actor selects video to be uploaded System will allow and display the video path in the text field

3. Actor press “Update” button System will update the video and display a relevant message.

Alternate Scenarios

1. Actor press “cancel” button during video updation processSystem will not upload the video and return to edit video window

2. Actor upload video with invalid formatSystem will not upload the video

3. Actor doesn’t fill the mandatory fields and press upload buttonSystem will not allow uploading video and will display a relevant message.

Post Conditions

Step# Description

1. Actor will be able to activate the updated video

2. Actor will be able to view the uploaded video

3. Actor will be able to apply for a job with the uploaded video



Upload Video* (text box)Browse (button)Update (button)

Business Rules

1. Video should be uploaded in a valid format

2. Video size should be less than the specified size



3.2.4.3. Delete Candidate Video

<UC-001: Delete Candidate Video>Actor: CandidateFeature: This use case will provide the functionality of deleting existing candidate video.Pre-condition(s) 1. The actor must be logged in.

2. Al least one video must exist 3. Webpage will be opened.

Scenarios


1. Actor selects the video to be deleted and checks its corresponding checkbox

System will allow

2. Actor press “Delete” button System will Delete the video and display a relevant message.

Alternate Scenarios

1. Actor press “Delete” button without checking the checkboxSystem will not delete any video and display a relevant message

2. Actor press “Cancel” buttonSystem will not delete the selected video

Post Conditions

Step# Description

1. Actor will not be able to view the deleted video



Uploaded video (visible)Remove video (check box)

Delete (button)

Business Rules

1. None



3.2.5. Jobs Management

3.2.5.1. Search a Job

<UC-001: Search a Job>Actor: CandidateFeature: This use case will provide the functionality of searching jobs. Candidate will fill the search criteria in order to complete and search jobs.Pre-condition(s) 1. Webpage will be opened.Scenarios


1. Actor will open the relevant webpage System will open the webpage 2. Actor press “Search Jobs” link System will open the search page3. Actor enters the search criteria or

leaves itSystem will allow

4. Actor press search button System will search and display all relevant job results against given search criteria.

Alternate Scenarios


Post Conditions

Step# Description

1. Actor will be able to view jobs details

2. Actor will be able to apply for jobs

3. Actor will be able to save the jobs search

4. Actor will be able to view companies information



Keywords (text box)Country (drop down menu)

City (drop down menu)Job Type(drop down menu)

Job Industry (drop down menu)Search (button)

Business Rules

1. By default, all countries will be visible on the field


3. By selecting a particular country, its cities will only be visible

4. By default, all cities will be visible on the field


6. By default, ‘doesn’t matter’ will be visible on all drop down fields



3.2.5.2. Set Customized Searches for Future Jobs

<UC-001: Set Customized Searches for Future Jobs>Actor: CandidateFeature: This use case will provide the functionality to set customized searches for future jobs. Candidate will enter the search criteria in order to set customize searches for future jobs.Pre-condition(s) 1. Webpage will be opened.

2. Actor must be login Scenarios


1. Actor will open the relevant webpage System will open the webpage 2. Actor press “Search Jobs” link System will open the search page3. Actor enters the search criteria or

leaves itSystem will allow

4. Actor press search button System will search and display all relevant job results against given search criteria.

5. Actor enters the search title System will allow6. Actor checks the check box System will allow7. Actor press “Save” button System will save the search and will

display a relevant message

Alternate Scenarios


2. Actor press save button without entering mandatory fileSystem will not save the search and display a relevant message

Post Conditions

Step# Description

1. Actor will be able to view jobs details

2. Actor will be able to apply for jobs

3. Actor will be able to view job status

4. Actor will be able to view companies information



Keywords (text box)Country (drop down menu)

City (drop down menu)Job Type(drop down menu)

Job Industry (drop down menu)Search (button)

Search Title* (text box)Enable Email Alerts (check box)

Save (button)

Business Rules

1. By default, ‘all countries’ will be visible on the field




3. By selecting a particular country, its cities will only be visible

4. By default, all cities will be visible on the field


6. By default, ‘doesn’t matter’ will be visible on all fields



3.2.5.3. Apply for a Job

<UC-001: Apply for a Job>Actor: CandidateFeature: This use case will provide the functionality of applying for a job. Pre-condition(s) 1. Actor must be login

2. Jobs listing page will be opened.Scenarios


1. Actor will select a job form the list System will open the job detail page2. Actor press “Apply for this Job”

buttonSystem will open the apply for this job page

3. Actor enters information in the cover letter

System will allow

4. Actor selects a cv from drop down menu

System will allow

5. Actor press “Submit” button System will submit the candidate application and display a relevant message

Alternate Scenarios

1. Actor press submit button without mandatory fieldSystem will not submit the application and display a relevant message

2. Actor press cancel button without sending applicationSystem will close the apply for a job window

Post Conditions

Step# Description

1. Actor will be able to get response from employer

2. Actor information will be available to employer

3. Actor application information will be available in jobs history

4. Actor will be able to manage the application



Cover Letter (text area)Select Cv* (drop down menu)Submit Application (button)

Business Rules

1. By default, some text will be written in cover letter

2. By default, ‘select’ cv will be visible on select drop down field



3.2.5.4. View Job Application History

<UC-001: View Job Application History>Actor: CandidateFeature: This use case will provide the functionality of viewing job applications history. Pre-condition(s) 1. Actor must be login

2. At least one job history must exist.Scenarios


1. Actor will open the relevant webpage System will open the webpage 2. Actor press “My Jobs” link System will open the My jobs page and

display all jobs with related information 3. Actor selects a particular job System will display details of the job

Alternate Scenarios

1. None

Post Conditions

Step# Description

1. Actor will be able to view all employers Information

2. Actor will be able to manage the jobs



My Jobs (job link)Company(read only)

Application Status (read only)Date Applied(read only)Delete all Jobs (button)

Business Rules

1. None



3.2.5.5. View Employer Information

<UC-001: View Employer Information>Actor: CandidateFeature: This use case will provide the functionality of viewing Employer Information from the system. Pre-condition(s) 1. Actor must be login

2. At least one employer information must exist3. Webpage will be open

Scenarios


1. Actor press Employer List link System will open the Employer List page and display all employers’ information alphabetically.

2. Actor selects a particular employer System will open the requested employer information in a pop up window

Alternate Scenarios

1. None

Post Conditions

Step# Description

1. None



Company Name (Read Only)Location (read only)

Company Description (read only)Close Window (button)

Business Rules

1. None



3.2.6. Subscribe to Job Newsletters

<UC-001: Subscribe to Job Newsletters>Actor: CandidateFeature: This use case will provide the functionality to subscribing job newsletters. Candidate will receive job newsletters at his email address.Pre-condition(s) 1. Actor must be login Scenarios


1. Actor press “My Account” link System will open the my account page and display candidate profile

2. Actor checks the job newsletter checkbox

System will allow

3. Actor press “Save Changes” button System will save and display a relevant message

Alternate Scenarios

1. Actor press save button without checking the check boxSystem will not save the information about job newsletter

Post Conditions

Step# Description

1. Actor will be able to receive job newsletters



Job Newsletter(check box)Save Changes (button)

Business Rules

1. By default, all countries will be visible on the field



3.2.7. Invite a Friend

<UC-001: Invite a Friend>Actor: CandidateFeature: This use case will provide the functionality to invite a friends by their email addresses. Pre-condition(s) 1. Actor must be login Scenarios


1. Actor press “Invite a Friend” link System will open invite a friend form with all fields blanks

2. Actor fills the form System will allow3. Actor press “submit” button System will send email to friends and

display a relevant message

Alternate Scenarios

1. Actor press save button without checking the check boxSystem will not save the information about job newsletter

2. Actor press submit button without filling mandatory fieldSystem will not send email and display a relevant message

Post Conditions

Step# Description

1. Actor friends will be able to receive emails



Your Name* (text box) Your Email* (text box)

Friends Emails* (text box)Message (text area)

Submit (button)

Business Rules


2. Actor cannot enter same email twice

3. Multiple emails must be separate with commas



3.3.Employer

3.3.1. Registration as Employer

3.3.1.1. Create Account

<UC-001: Create Account>Actor: EmployerFeature: This use case will provide the functionality of Actor registration. Actor will fill the registration form in order to complete the registration process to use the complete services of the system.Pre-condition(s) 8. Webpage will be opened.Scenarios


1. Actor will click Employer button System will open the Employer page2. Actor will click Sign Up button System will open registration form3. Actor fills the form along with all

mandatory fieldsSystem will allow


System will allow

5. Actor press Register button System will allow and save the information, register the actor and login the actor automatically by opening the confirmation page.

Alternate Scenarios

1. Actor clicks the search button with certain search criteria.System will show listing according to the search criteria.


3. Actor fill all the mandatory fields and press Cancel buttonSystem will not register the actor will redirect the actor to the Employer’s main page.

Post Conditions

Step# Description


1. Actor will be able to post a job

2. Actor can Edit/Delete jobs

3. Actor can activate / deactivate jobs

4. Actor will be able to view resumes against posted jobs

5. Actor will be able to view interview videos

6. Actor can add candidates to favorites

7. Actor can receive/ provide feedback

8. Actor will be able to manage message board

9. Actor will be able to receive alerts on his/her email address.



10.9

Actor will be able to view/manage History of applications for their posted jobs

11.1

Actor will be able to Subscribe to Job Newsletter

Concurrent Actor: ‘n’ number of Actors.


Email* (Text box)User Name* (Text box)Password* (password)

Confirm password* (password)Title* (Drop down menu)First Name* (Text box)Last Name* (Text box)

Company Name* (Text box)Logo (Browse button)

Industry* (Drop down menu)Country* (Drop down menu)

State* (Drop down menu)City* (Drop down menu)

Address of Company* (Text box)Work Phone (Text box)

Mobile Phone (Text box)Fax (Text box)

I accept agreement* (Check box)Image validation* (Text box)

Register (Button)Cancel (Button)

Business Rules

1.1

Email should be provided with valid format

2.2

Email can not be duplicated

3.3

Actor must choose a Title

4. Actor must provide a unique Company Name

5. Actor must provide the accurate Image Validation Code

6. Actor must provide unique username

7. Actor must provide password

8. Password provided in Confirm Password must be identical

9. Actor must provide valid picture format in Logo

10. State should be active only in case of country is selected as USA



3.3.1.2. Edit Profile

<UC-002: Edit Profile>Actor: EmployerFeature: This use case will provide the functionality of editing profile. Actor will fill the registration form in order to edit his/her profile.Pre-condition(s) Actor must be logged in successfullyScenarios


1. Actor will click My Profile button System will open the Profile page in edit mode.

2. Actor will edit the profile System will allow5. Actor will Save button System will allow and save the changes.

Alternate Scenarios

1. Actor edits the profile with invalid information.System will not allow the registration and will display a relevant message.


Post Conditions

Step# Description






Email* (Text box)Password* (password)








Subscribe for News Letter (Check box)Save (Button)

Cancel (Button)Business Rules

1.1

Email should be provided with valid format

2.2

Email can not be duplicated









3.3.2. Job Management

3.3.2.1. Place a Job

<UC-003: Place a Job>Actor: EmployerFeature: This use case will provide the functionality of placing a new job. That new job will be available to candidates for posting their CVs if the job is active.Pre-condition(s) Actor must be logged in successfullyScenarios


1. Actor will click Place a Job button System will open the Job placement form

2. Actor will fill the form including mandatory fields.

System will allow

3. Actor will click Post Job button System will allow and will post the job by opening confirmation page.

Alternate Scenarios

1. Actor fills the form with invalid information.System will not allow the job posting and will display a relevant message.

2. Actor doesn’t fill all the mandatory fields and press Post Job buttonSystem will not allow the job posting and will display a relevant message.

3. Actor clicks Cancel button.System will redirect the actor to Employer page without posting any job.

Post Conditions

Step# Description

1. Actor will be able to Activate / Deactivate the job

2. Actor will be able to Edit / Delete the job







9 Actor will be able to view/manage History of applications for their posted jobs





Job Title* (Text box)No. of Positions (Drop down menu)

Industry* (Drop down menu)Department (Text box)

Job Type* (Drop down menu)Job Shift (Drop down menu)

Job Location Country* (Drop down menu)

State (Drop down menu)City (Drop down menu)

Gender* (Drop down menu)Age From (Drop down menu)

Age To (Drop down menu)Degree Level*

Min (Radio button)Max (Radio button)

Selection (Drop Down Menu)Degree Title (Text box)

Career Level* (Drop down menu)Experience*


Selection (Drop Down Menu)Work Permit (Drop down menu)

Require Travel (Drop down menu)Salary Range

From (Text box)To (Text box)

Selection [per month / per annum] (Drop Down Menu)Currency (Drop Down Menu)

Apply ByDay (Drop down menu)

Month (Drop down menu)Year (Drop down menu)


Required Skills (Text box)I would like the resumes of the applicants to be delivered in my inbox (Check box)

Email resume to (Text box)Cancel (Button)

Post Job (Button)

Business Rules

1. No. of positions dropdown will have the value between 1 to 20+

2.1

Age From should not be greater than Age To

3.2

Salary Range From should not be greater than Salary Range To

4.3

Apply By Date should not be less than current date.



5. Actor should provide the valid email address in Email resume to.




3.3.2.2. Edit a Job

<UC-004: Edit a Job>Actor: EmployerFeature: This use case will provide the functionality of editing a placed job.Pre-condition(s) 1. Actor must be logged in successfully

2. Job must already be posted Scenarios


1. Actor will click on Edit button against specific job in listing.

System will open the Job Descriptions form in edit mode.

2. Actor will fill the form including mandatory fields.

System will allow

5. Actor will click Save button System will allow and will save the changes by opening confirmation page.

Alternate Scenarios

4. Actor fills the form with invalid information.System will not allow the job posting and will display a relevant message.

5. Actor doesn’t fill all the mandatory fields and press Post Job buttonSystem will not allow the job posting and will display a relevant message.

6. Actor clicks Cancel button.System will redirect the actor to Employer page without posting any job.

Post Conditions

Step# Description

1. Actor will be able to Activate / Deactivate the job













Job Title* (Text box)No. of Positions (Drop down menu)Job Category* (Drop down menu)

Department (Text box)Job Type* (Drop down menu)Job Shift (Drop down menu)

Job Location Country* (Drop down menu)

State (Drop down menu)City (Drop down menu)

Gender* (Drop down menu)Age From (Drop down menu)

Age To (Drop down menu)Degree Level*


Selection (Drop Down Menu)Degree Title (Text box)

Career Level* (Drop down menu)Experience*


Selection (Drop Down Menu)Work Permit (Drop down menu)

Require Travel (Drop down menu)Salary Range

From (Text box)To (Text box)

Selection [per month / per annum] (Drop Down Menu)Currency (Drop Down Menu)

Apply ByDay (Drop down menu)

Month (Drop down menu)Year (Drop down menu)


Required Skills (Text box)I would like the resumes of the applicants to be delivered in my inbox (Check box)

Email resume to (Text box)Cancel (Button)Save (Button)

Business Rules

No. of positions can not be less than 1

1.

Age From should not be greater than Age To

2.

Salary Range From should not be greater than Salary Range To

3.

Apply By Date should not be less than current date.

Actor should provide the valid email address in Email resume to.

State should be active only in case of country is selected as USA





3.3.2.3. Delete a Job

<UC-005: Delete a Job>Actor: EmployerFeature: This use case will provide the functionality of deleting a placed job.Pre-condition(s) Actor must be logged in successfully

Job must already be posted Scenarios


1. Actor will click on Delete button against specific job in listing.

System will open confirmation window

2. Actor will click Yes button System will delete the job along with all data related to that job.

Alternate Scenarios

1. Actor will click on Delete button against specific job in listing.System will open confirmation window

2. Actor will click No button.System will not delete the job and will redirect the actor to the listing.

Post Conditions

Step# Description

1. Actor will not be able to perform any functionality related to that job



Job Title (Link)Activate/Deactivate (Button)

Edit (Button)View Applicants (Button)

Delete (Button)Business Rules

1. All data related to deleted job should be updated accordingly.





3.3.2.4. Deactivate a Job

<UC-006: Deactivate a Job>Actor: EmployerFeature: This use case will provide the functionality of deactivating an active job.Pre-condition(s) Actor must be logged in successfully

Job must already be posted Job’s status must be inactive

Scenarios


4. Actor will click on Deactivate button against specific job in listing.


5. Actor will click Yes button System will deactivate the job and update the referred effects accordingly.

Alternate Scenarios

7. Actor will click on Deactivate button against specific job in listing.System will open confirmation window

8. Actor will click No button.System will not deactivate the job and will redirect the actor to the listing.

Post Conditions

Step# Description

1. Actor will be able to Deactivate the job









10. Actor will be able to Subscribe to Job Newsletter








2. Deactivated Jobs should not be viewable to any other actor except then that Employer who posted that job.

3. If the resume of any candidate is automatically posted though some candidate in response of availing Future Job Search facility; and job is now deactivated then if the candidate tries to update any status against that job, system will inform the candidate that this job is now deactivated and not applicable.



3.3.2.5. Activate a Job

<UC-007: Activate a Job>Actor: EmployerFeature: This use case will provide the functionality of placing a new job.Pre-condition(s) Actor must be logged in successfully

Job must already be posted Job’s status must be active

Scenarios


1. Actor will click on Activate button against specific job in listing.


2. Actor will click Yes button System will Activate the job and update the referred effects accordingly.

Alternate Scenarios

1. Actor will click on Activate button against specific job in listing.System will open confirmation window

2. Actor will click No button.System will not Activate the job and will redirect the actor to the listing.

Post Conditions

Step# Description

1. Actor will be able to Activate the job




Actor will be able to view/manage History of applications for that job






Deactivated Jobs should not be viewable to any other actor except then that Employer who posted that job.If the resume of any candidate is automatically posted though some candidate in response of availing Future Job Search facility; and job is now deactivated then if the candidate tries to update any status against that job, system will inform the candidate that this job is now deactivated and not applicable.



3.3.3. View Candidates

3.3.3.1. View Candidates

<UC-009: View Candidates>Actor: EmployerFeature: This use case will provide the functionality of placing a new job.Pre-condition(s) Actor must be logged in successfully



6. On Job listing page Actor will click Job Title link against any specific job.Actor will click on Candidates button against specific job in listing.

System will open Candidates listing page against that specific job.System will open candidates listing against that job with default sorting.

Alternate Scenarios

1.

Post Conditions

Step# Description

Actor will be able to view listing as per his/her desired sorting criteria.



Actor will be able to view/manage History of applications for that job

Actor will be able to view comments against applicants

Actor will be able to post comments/feed back against applicants



Resume (Button)History (Button)

Comments (Button)Videos (Button)Delete (Button)

Add to Favorites (Button)Business Rules

4. Listing should be displayed in default sorted order.





3.3.3.2. View Resume

<UC-010: View Resume>Actor: EmployerFeature: This use case will provide the functionality of placing a new job.Pre-condition(s) Actor must be logged in successfully



7. On Job listing page Actor will click Job Title link against any specific job.Actor will click on Candidates button against specific job in listing.Actor will click on Resume button against any specific candidate

System will open Candidates listing page against that specific job.

System will open candidates listing against that job with default sorting.System will open the resume of that candidate.

Alternate Scenarios

1.

Post Conditions

Step# Description

Actor will be able to save resumes on his machine.



Actor will be able to add the candidate to his favorites list.








5. Employer can not edit the resume of any candidate.



3.3.3.3. View History

<UC-011: View History>Actor: EmployerFeature: This use case will provide the functionality of placing a new job.Pre-condition(s) Actor must be logged in successfully



8. On Job listing page Actor will click Job Title link against any specific job.Actor will click on Candidates button against specific job in listing.Actor will click on History button against any specific candidate


System will open candidates listing against that job with default sorting.System will open the History page of that candidate.

Alternate Scenarios

1.

Post Conditions

Step# Description







6. Employer can not edit the comments of any other employer against any candidate.





3.3.3.4. View Comments

<UC-012: View Comments>Actor: EmployerFeature: This use case will provide the functionality of placing a new job.Pre-condition(s) Actor must be logged in successfully



9. On Job listing page Actor will click Job Title link against any specific job.Actor will click on Candidates button against specific job in listing.Actor will click on Comments button against any specific candidate.


System will open candidates listing against that job with default sorting.System will show the comments provided by any employer against that candidate.

Alternate Scenarios

1.

Post Conditions

Step# Description








7.



3.3.3.5. Post Comments

<UC-013: Post Comments>Actor: EmployerFeature: This use case will provide the functionality of posting comments against any candidate.Pre-condition(s) Actor must be logged in successfully



10.1.

On Job listing page Actor will click Job Title link against any specific job.Actor will click on Candidates button against specific job in listing.Actor will click on Comments button against any specific candidate.Actor will write his/her comments in Post your comments text box.Actor will click on Submit button.


System will open candidates listing against that job with default sorting.System will open the comments page against that candidate. System will allow.

System will add comments to the comments list

Alternate Scenarios

1. On Job listing page Actor will click Job Title link against any specific job.System will open Candidates listing page against that specific job.Actor will click on Candidates button against specific job in listing.System will open candidates listing against that job with default sorting.Actor will click on Comments button against any specific candidate.System will open the comments page against that candidate. Actor will write his/her comments in Post your comments text box.System will allow.Actor will click on Cancel button.System will not add comments to the comments list

Post Conditions

Step# Description





Comments (Read only)Add your comments (Text box)

Submit (Button)Cancel (Button)

Business Rules

8. Actor can not edit any posted comment.



3.3.3.6. View Video

<UC-014: View Video>Actor: EmployerFeature: This use case will provide the functionality of viewing an interview video of some

candidate.Pre-condition(s) Actor must be logged in successfully



11.1.

On Job listing page Actor will click Job Title link against any specific job.Actor will click on Candidates button against specific job in listing.Actor will click on Video button against any specific candidate.Actor will click on the desired video icon.


System will open candidates listing against that job with default sorting.System will show the interview video list provided against that candidate. System will play that video with FLP on screen.

Alternate Scenarios

1.

Post Conditions

Step# Description





Videos (icons)Add a video (Button)

Video player (Flash Player)Business Rules

9. Actor can not Edit any video.



3.3.3.7. Add Video

<UC-015: Add Video>Actor: EmployerFeature: This use case will provide the functionality of adding an interview video of some

candidate.Pre-condition(s) Actor must be logged in successfully

Job must already be posted Candidate must have applied for that job

Scenarios


12.1.

On Job listing page Actor will click Job Title link against any specific job.Actor will click on Candidates button against specific job in listing.Actor will click on Video button against any specific candidate.Actor will click on the Add Video button.User will provide Video TitleUser will provide DescriptionUser will click on Browse buttonUser will select the desired video

User will click on Add Button


System will open candidates listing against that job with default sorting.System will show the interview video list provided against that candidate. System will open Add Video page.

System will allow.System will allow.System will open browse window.System will show the selected video icon on Add Video page.System will post the video.

Alternate Scenarios

1. Actor will click on the Add Video button.System will open Add Video page.Actor fills the form without providing mandatory fieldsSystem will allow.User will click on Cancel ButtonSystem will clear the form and will redirect the actor to Add video page.

Post Conditions

Step# Description





Videos (Icons)Video Title* (Text box)

Video Description (Text box)Add a Video (Button)

Browse (Browse button)Add (Button)


10. Video must be of valid format.

11. Video should not exceed the described video size.



12. Actor can add only one video against any candidate at one time.

13. If Actor adds videos more than once against a specific candidate, each time previously posted video will be replaced with the newer one.

14. Actor can’t edit or delete any posted video directly.

15. Actor must provide a proper Video Title.



3.3.3.8. Add to Favorite

<UC-016: Add to Favorite>Actor: EmployerFeature: This use case will provide the functionality of adding some candidate to actor’s favorites list.Pre-condition(s) Actor must be logged in successfully



1. On Job listing page Actor will click Job Title link against any specific job.Actor will click on Candidates button against specific job in listing.Actor will click on Add to Favorite button against any specific candidate.


System will open candidates listing against that job with default sorting.System will add the candidate to actor’s favorites list.

Alternate Scenarios

1.

Post Conditions

Step# Description

1. Actor will be able to view comments against applicants

2. Actor will be able to post comments/feed back against applicants

3. Actor will be able to view video of candidates






1. Actor can not Edit any video.

2. Actor can not Delete any video



3.3.4. Subscribe for News Letter

<UC-017: Subscribe for News Letter>Actor: EmployerFeature: This use case will provide the functionality of subscription for news letter.Pre-condition(s) Actor must be logged in successfullyScenarios


1. Actor will click My Profile button System will open the Profile page in edit mode.

2. Actor will edit the profile by checking the Subscribe me for News Letters check box.

System will allow

3. Actor will Save button System will allow and save the changes.

Alternate Scenarios

1. Actor edits the profile with invalid information.System will not allow the registration and will display a relevant message.

2. Actor edits the profile with invalid information.System will not save the changes and will display a relevant message.

3. Actor doesn’t fill all the mandatory fields and press Cancel buttonSystem will not subscribe the actor for news letters and redirect actor to profile.

Post Conditions

Step# Description

1. Actor will be able to receive news letters alerts on his/her email address.


3. Actor will be able to post a job

4. Actor can Edit/Delete jobs

5. Actor can activate / deactivate jobs







12. Actor will be able to view/manage History of applications for their posted jobs

13. Actor will be able to Subscribe to Job Newsletter





Email* (Text box)Password* (password)








Subscribe for News Letter (Check box)Save (Button)


1. Email should be provided with valid format

2. Email can not be duplicated

3. Actor must choose a Title

4. Actor must provide First Name

5. Actor must provide Last Name


7. Actor must check the I accept agreement check box







Documents

Recruitment System SFS 1 0