ISDS Recruiting Services · Web viewISDS Recruiting Services Project Plan and Analysis Alexson...

ISDS Recruiting ServicesProject Plan and Analysis

Alexson Andrus, Katherine Barrios, Phillip Nelson, Alexandra Tolbert

ABSTRACT

This document contains the Phase 4 - Implementation for ISDS 4125 Recruiting Services Project.

Table of Contents

Executive Summary.................................................................................................................6

Description of Interface...........................................................................................................7

Test Plan................................................................................................................................11Form Test Plans..............................................................................................................................11Test Scenario Plans........................................................................................................................19

Migration Plan.......................................................................................................................22

Training Plan.........................................................................................................................23

User Documentation..............................................................................................................24On-Line Help..................................................................................................................................24

Sitemap.................................................................................................................................25

Requirements Analysis..........................................................................................................26Functional Requirements...............................................................................................................26Nonfunctional Requirements.........................................................................................................26

Use Case Diagram..................................................................................................................27

Use Case Narratives...............................................................................................................28

Data Flow Diagrams...............................................................................................................33Context Level.................................................................................................................................33Level-0...........................................................................................................................................34Level-1...........................................................................................................................................35

Entity Relationship Diagram..................................................................................................36

Project Assessment................................................................................................................37Project Team Review......................................................................................................................37System Review...............................................................................................................................37

Timecards..............................................................................................................................38Alexson Andrus..............................................................................................................................38Katherine Barrios...........................................................................................................................39Phillip Nelson.................................................................................................................................40Alexandra Tolbert..........................................................................................................................41

Executive Summary

The ISDS Recruiter program is a web-based program that will be used by the LSU Department of Information Systems and Decision Sciences (ISDS) faculty, students, and active

company recruiters to view, update, organize and display a list of current and future companies actively seeking to recruit students for employment and/or internships. The program is currently stored in Microsoft Excel. As internet and technology software continues to become the primary means of viewing and storing information; this program will utilize the accessibility of the internet, advanced database tools and combine the two to create a more efficient means to store and display recruiting information to staff and students. The goal is to keep better records of our recruiters in hopes to increase the number of students that get job offers and internships as the number of students increase in the ISDS major.

The target audience for this program is the project sponsor, students in the ISDS major and the companies participating in LSU recruiting services. This application is designed to connect the students and recruiters, keep up to date information on available internships and job opportunities, and display this information on a secure university web page. Students will benefit from the program by the availability of up to date job opportunities and a means to directly connect with active recruiters; in which can increase their professional experience and advance their career opportunities. Company recruiters will benefit from the program by having secured access to modify and update their individual profiles and communicate career opportunities directly to a targeted pool of qualified students. The project sponsor will benefit from the program as it will be a more efficient, organized and easier method of storing and displaying the necessary data on the programs web page.

The main business problems our application is designed to address are: improving the current system of storing and organizing recruiters information, enhancing the display of information by including filter selections, increase the availability and awareness of career opportunities to the growing number of students in the ISDS major and implement security features that will protect the project sponsor and company recruiters private information as well as ensure private login capabilities for the project sponsor and guest accounts. This project is expected to be completed and fully functional by the end of the semester, May 2013. Implementing a database structure, using Microsoft Access, will simplify the process of storing, organizing, updating and displaying company information. Creating an intuitive interface will give users the ability to sort and filter the information stored inside the database. The user can filter the data on selections such as: by company, or by job title or keyword, which produces relevant information that is particular to their individual needs about a company or career opportunities. This program will be better suited to handle the growing number of students accessing this information within the ISDS major. With an increase in traffic, security measures will be implemented to protect the data and control measures.

Description of Interface

Form: User Login/Register Homepage Users: Administrator, Guest

Task: Allows user to log into their account in order to access other feature of the website. User is required to log into account prior to accessing other pages. Environment: Standard Web Browser

See Access the System Use Case

Form: Query Database InformationUsers: Administrator, GuestTask: Allows the user (Administrator or Guest) to select from a list of premade queries that will provide job, student and recruiter information from the database.Environment: Standard Web Browser

See Query Database Information Use Case

Form: Search Recruiter InformationUsers: Administrator, GuestTask: Allows the user (Administrator or Guest) to view specific recruiter information using a search engine. The search engine can be used to find specific data for recruiters, companies and students in the database.Environment: Standard Web Browser

See View Recruiter Information Use Case

Form: Update and Input Data Users: AdministratorTask: Allows the Administrator account to add and update Recruiter, Company, and Student Records on the database using the Records tab.Environment: Standard Web Browser

See Update Data and Insert Data Use Cases

Test Plan

Form Test Plans

Form: HomeOutput (+/x): Comments:

Input User Name: +Input Password: +Link Register: +Link Forgot Password: +Checkbox Remember Me:

+

Button Log In: +Navigation Home Icon: +Navigation Queries Icon:

+

Navigation Search Icon: +Navigation Records Icon:

+

Image LSU Recruiter Tool Banner:

+

Image BEC Rotunda: +Additional Comments:

Tester Signature: Katherine BarriosTesting Date: 4/30/2013

Form: RegisterOutput (+/x): Comments:

Input User Name: +Input Password: +Input Password(again): +Input Email: +Input Security Question:

+

Input Security Answer: +Button Create User: +Navigation Home Icon: +Navigation Queries Icon:

+


+


+

Additional Comments:


Form: Password RecoveryOutput (+/x): Comments:

Input User Name: +Text Forgot Password: +Text Enter User Name: +Button Submit: +Navigation Home Icon: +Navigation Queries Icon:

+


+


+



Form: QueriesOutput (+/x): Comments:

Button Recruiter Contact Info:

+

Button Internship Positions:

+

Button Full Time Positions:

+

Button Part Time Positions:

+

Button Current Events: +Button Positions in LA: +Button Students with FT Positions:

+

Button Students with Internships:

+

Navigation Home Icon: +Navigation Queries Icon:

+


+


+



Form: SearchOutput (+/x): Comments:

Text Search Records Title:

+

Drop Down Search By: +Button Go: +Navigation Home Icon: +Navigation Queries Icon:

+


+


+



Form: Search By CompanyOutput (+/x): Comments:

Drop Down Search By: +Input Search By Text: +Button Search: +Navigation Home Icon: +Navigation Queries Icon:

+


+


+



Form: Search By EventOutput (+/x): Comments:


+


+


+



Form: Search By PositionOutput (+/x): Comments:


+


+


+



Form: Search By RecruiterOutput (+/x): Comments:


+


+


+



Form: Search By StudentOutput (+/x): Comments:


+


+


+



Form: RecordsOutput (+/x): Comments:

Button Add New Recruiter:

+

Button Add New Company:

+

Button Add New Job: +Navigation Home Icon: +Navigation Queries Icon:

+


+


+



Form: Add RecruiterOutput (+/x): Comments:

Details View Edit Button:

+

Details View New Button:

+

Details View Paging: +Button Add New Company:

+


+


+


+



Form: Add CompanyOutput (+/x): Comments:


+


+

Details View Paging: +Button Add New Recruiter:

+


+


+


+



Form: Add Job PostingOutput (+/x): Comments:


+


+

Details View Paging: +Button Add New Company:

+


+


+


+



Test Scenario Plans

Scenario: How to Login (Returning User, Register, Forgot Password):Action: Login Returning User Value(s)

EnteredOutput (+/x)

Comments

1. Select Home from Navigation Bar

-

2. Input User Name Katherine, 123, Joe, +-$*

+

3. Input Password October22!, 123,

+

4. Select to remember email or not

- +

5. Execute Log In Button - +Action: Register Value(s)

EnteredOutput (+/x)

Comments

1. Select Home from Navigation Bar

- +

2. Select Register - +3. Input User Name Kbarri8, hi$joe,

1234+

4. Input Password October22!, 1234, mike

+

5. Input Password(again) October22!, 1234, mike

+

6. Input Email [email protected], mikelsu.edu, mikelsuedu

+

7. Input Security Question Color?, Middle Name?,

+

8. Input Security Answer Red, Aimee, 1123

+

9. Execute Create User - +Action: Forgot Password Value(s)

EnteredOutput (+/x)

Comments

1. Select Home from Navigation Bar:

- +

2. Select Forgot Password: - +3. Input User Name: Kbarri8, joe,

1234+

4. Execute Password Search October22!, 123, $$$

+

mailto:[email protected]



Scenario: How to Query/Filter RecordsAction: Query Database Value(s)

EnteredOutput (+/x)

Comments

1. Select Query from Navigation Bar

- +

2. Execute Query Displayed - +Additional Comments:


Scenario: How to Search for RecordAction: Query Database Value(s)

EnteredOutput (+/x)

Comments

1. Select Search from Navigation Bar

- +

2. Select a Database table from Dropdown List

Recruiter +

3. Select Go Button - +3. Select Field to “Search By” from Drop Down List:

ID +

4. Input Filter Text: 123, K, %#@ +5. Execute Search: - +Additional Comments:


Scenario: How to Add Recruiter RecordAction: Add Record Value(s)

EnteredOutput (+/x) Comments

1. Select Records from Navigation Bar

- +

2. Select Add New Recruiter - +

3. Select New - +4. Input First Name Mike +5. Input Last Name Tiger +6. Input Title Manager +7. Input Email [email protected] +8. Input Work Phone 9857788472 +9. Input Cell Phone 9857788471 +10. Input Fax 9857788477 +11. Input Notes He is a nice guy

with 2 dogs.+

12. Input Company ID 3 +a. Search ID from

Lookup Table- +

b. If ID does not exist, select Add New Company

- +

13. Select Insert - +Additional Comments:


Migration Plan

Migration PlanPreparing the Business Preparing the Technology Preparing the People

Conversion Strategy Conversion Style: Direct

Conversion Conversion Location:

Simultaneous Conversion.

Conversion Module: Whole-System Conversion

Business Contingency Plan

Hardware

Software

Convert data from previous excel document to Access database.

Administer training to users

User account setups

Conversion Style Conversion Location Conversion ModulesCharacteristic Direct Simultaneous Whole-System

Risk High High HighCost Low High MediumTime Short Short Short

Training Plan

As far as training goes for our system, we have decided to train the existing staff on new business processes through one-on-one training. Our system comes with a user manual that includes the ins and outs of using this web-based recruiter tracking solution. Besides having the user manual at the employees’ disposal, we will also do an initial walkthrough of the program with the main user, Mrs. Carolyn Borne. At this time we will show her how to login, navigate from page to page, add/remove/edit information, and simply view all of the data of the system.

The training will also include an overview of all of the new features of the system compared to the original excel spreadsheet used to house recruiter information. Our main goal of the training is not to go through every single detail of how to use the system, but rather how to complete the everyday business processes that it will be used for. This being said, after the user is familiar with the systems environment, we will go over how the user wants to use the system and what makes this system more efficient than what was previously used. After the user is able to complete day-to-day tasks through the new system we will answer any questions as well as leave contact information to assist further for a period of 3 months post implementation.

User Documentation

On-Line Help

LSU ISDS Recruiting Services plans on providing end-users with an on-line user manual. The on-line user manual will display FAQ and show the end-users step-by-step instructions such as how to register a new user, Query/Filter Records, Search for a Record, Add/Edit a Record, how to retrieve a forgotten password, etc.

Sitemap

LSURecruiterTool.net

Home

Login Register Forgot Password

Query Search

Company Table

Event Table

Position Table

Recruiter Table

Student Table

Records

Recruiter Company Postion

Requirements Analysis

Functional Requirements Input for Administrators

System must allow administrator to login using the admin login function using a unique username and password.System must allow administrator to view all active recruiters.System must allow administrator to view recruiters with/within selected parameters. System must allow administrator to find contacts for a selected company. System must allow administrator to update/add recruiter information.

Input for GuestsSystem must allow guest(s) to login using the guest login function using a unique username and password.System must allow guest(s) to query data by selection. System must allow guest(s) to view saved information.

Nonfunctional Requirements

OperationalThe system will allow a user to browse saved information by querying the data.The system will store all information in a Access database.The system must have 24/7 internet connection.

PerformanceThe system must connect and maintain connection to a Access database.The system will update database information in real time.

SecurityThe system must be password protectedThe system must require a username and password for all users. The system must allow only administrator to make updates, changes and add new

recruiters to the system.

Use Case Diagram

Use Case Narratives

Use Case Name: Access the System ID: UC-1 Priority: HighPrimary Actor: AdministratorOther Participating Actors: Guest(s)Other Interested Stakeholders: The LSU Department of Information Systems Decision Sciences.Description: The user (Administrator or Guest) logs into the system using the log in form on application startup. A ‘Sponsor’ account is an account with permission to edit the data in the database, while a ‘Guest’ account can only view the data in the database as read-only.Preconditions:1. The user has started the application.2. The log-in form is displayed on the application.

Trigger: The event is initiated when the user attempts to log into the system.User Action:

1. User enters account information in the required log-in field.

2. User enters account password in the password protected field.

3. User clicks the Login button.

System Response:

4. The system responds by checking the accuracy of the user’s login information.

5. If accurate, the user will be logged into the system and the application’s main form will be displayed.

Post conditions:1. The user is logged into the system as either a Sponsor or Guest account.2. Application’s main form is displayed.

Alternative Flows: 4a. If user login information is incorrect, the system will display an error message.Conclusion: The event is completed when the user successfully logs into the system.

Use Case Name: Query Database Information ID: UC-2 Priority: MediumPrimary Actor: AdministratorOther Participating Actors: Guest(s)Other Interested Stakeholders: The LSU Department of Information Systems Decision Sciences.Description: The user (Administrator or Guest) will select from a list of premade queries that will provide job, student and recruiter information from the database.Preconditions:

1. The user is logged into the system and the main application form is displayed.Trigger: The event is initiated when the user requests to view information from the system.User Action:

1. The user clicks the ‘Queries’ tab on the main application form.

2. The user selects the filters in which they want to view the data.

3. The user sends the filtered data to be queried by the system.

System Response:

4. The system responds by running the filter query and gathering the requested information from the database.

5. The system will display the queried information on the Queries tab for the user to view.

Post conditions:1. The requested premade query information is now displayed for the user on the

Queries tab.Alternative Flows: NoneConclusion: The event is concluded when the system successfully displays the requested data to the user.

Use Case Name: View Recruiter Information ID: UC-3 Priority: HighPrimary Actor: AdministratorOther Participating Actors: Guest(s)Other Interested Stakeholders: The LSU Department of Information Systems Decision Sciences.Description: The user (Administrator or Guest) will be able to view specific recruiter information using a search engine. The search engine can be used to find specific data for recruiters, companies and students in the database.Preconditions:

1. The user is logged into the system and the main application form is displayed.Trigger: The event is initiated when the user requests to search for information stored within the system.User Action:

1. The user clicks the ‘Search’ tab on the main application form.

2. The user enters search information in the corresponding search fields.

3. The user clicks the Search Records button.

5. The user selects a displayed record.

System Response:

4. The system searches relevant records and responds by extracting and displaying the related records.

6. The system displays the information page relative to the user’s record selection. A ‘Sponsor’ account will have the option of editing the information displayed at this time.

Post conditions:1. The requested recruiting record is displayed on the form for the user to view.

Alternative Flows: 4a. If the system finds no related records then an error message will be displayed stating that no records were found.

Use Case Name: Input Data ID: UC-4 Priority: HighPrimary Actor: AdministratorOther Interested Stakeholders: The LSU Department of Information Systems Decision Sciences.Description: An Administrator account will be able to add new records to the database using the ‘Add New’ section on the Records tab.Preconditions:

1. The user is logged into the system and the main application form is displayed.Trigger: The event is initiated when the Administrator selects to input data into the system.User Action:

1. The user clicks the ‘Records’ tab on the main application form.

2. The user clicks the ‘Add New’ button on the Records tab.

3. The user enters record information in the corresponding record fields.

4. The user clicks the ‘Add Record’ button.

System Response:

5. The system responds by checking duplicate primary key occurrences.

6. If no duplicates occur, the system adds the new record to the database.

Post conditions:1. A new record is added to the database.2. The user is returned to the ‘Records’ tab.

Alternative Flows:5a. If adding the record would result in duplicating a primary key or another field that does not allow duplicates, then an error message stating that duplicates cannot occur will be displayed and the user will be returned to the ‘Add New’ page.5b. If the user does not enter data in a required field, the system will flag an error to the user, prompting the user to insert data into the required field.Conclusion: The event is concluded when the Administrator successfully inputs data into the system.

Use Case Name: Input Data ID: UC-4 Priority: HighPrimary Actor: AdministratorOther Interested Stakeholders: The LSU Department of Information Systems Decision Sciences.Description: An Administrator account will be able to add new records to the database using the ‘Add New’ section on the Records tab.Preconditions:

1. The user is logged into the system and the main application form is displayed.Trigger: The event is initiated when the Administrator selects to input data into the system.User Action:

1. The user clicks the ‘Records’ tab on the main application form.

2. The user clicks the ‘Add New’ button on the Records tab.

3. The user enters record information in the corresponding record fields.

4. The user clicks the ‘Add Record’ button.

System Response:

5. The system responds by checking duplicate primary key occurrences.

6. If no duplicates occur, the system adds the new record to the database.

Post conditions:3. A new record is added to the database.4. The user is returned to the ‘Records’ tab.

Alternative Flows:5a. If adding the record would result in duplicating a primary key or another field that does not allow duplicates, then an error message stating that duplicates cannot occur will be displayed and the user will be returned to the ‘Add New’ page.5b. If the user does not enter data in a required field, the system will flag an error to the user, prompting the user to insert data into the required field.Conclusion: The event is concluded when the Administrator successfully inputs data into the system.

Data Flow Diagrams

Context Level

Level-0

Level-

Entity Relationship Diagram

Project Assessment

Project Team Review

Throughout the duration of the project, the team divided project tasks and deliverables amongst all members of the team. Each member was expected to complete his or her tasks by a specified date and time. This tactic was successful but changes could have been made to enhance the process of completing the project. Team members could have been more considerate about the division of the tasks and who was assigned to complete certain tasks. Project tasks were completed in divided sections, preventing other members from knowing what, how, or why certain tasks were completed the way they were; this also made it difficult for another member to expand on that task when he/she did not know what the previous member had done to complete the task. To correct this mistake, better communication and project planning should be constructed. Members should try and work together at the same time to deliver the project outcomes so everyone remain in the know.

A difficult aspect of this project was lab time. The BEC provides only one lab in which students can meet and work on projects. It was difficult to meet the demands of all members schedule as well as keeping up with the labs schedule and hours. I would recommend that the BEC hire a lab worker that will stay and open the lab to allow for a more flexible lab schedule.

As a group, the team worked very well together. Every member dedicated a great deal of time to the project and sacrificed personal time on weeknights and the weekend to meet and work on the project together. Each member assumed responsibility and worked diligently to complete tasks on time and meeting the projects high standard. The team helped each other when problems or questions were raised and worked together to research and find the answers needed. Each member’s dedication made for a positive experience in completing this project.

System Review

The new system presents many benefits. Some that were discussed before the project had begun as well as others that we now know of after completing the final product. The new system has taken an excel document and various email addresses stored in email contacts and stored it all in one central location. This is probably the greatest benefit of the new system; having a single place to retrieve information. Having multiple emails and phone numbers for contacts will not be an issue with the new system since all information is housed in the same place. There is also a login portion of the system that does not allow the user to access any information until they are either logged in or, for new users, have registered. This will assure that confidential information is kept safe.

Besides the security and ease of access, the new system has improved the way in which the user is able to view the data. Information can now be searched for through the search tool in the new system as well as the prewritten queries. All data is viewed in real time and updates can be made with ease. A few benefits that we have added are the inclusion of more company any recruiter data as well as the great looking interface that has been designed. Overall there is much benefit to this system and will serve our customers for years to come.

Timecards

Alexson AndrusDate: 2/7/2013 – 3/11/13

Activity Description Date Time SpentGroup Meeting 4/12/2013 2 hoursGroup Meeting 4/16/2013 1.5 hour

Group Meeting – Coding/Design of Search Page, Login, Home Page 4/19/2013 6 hoursGroup Meeting – Coding/Design of Search Page, Login, Home

Page3/22/2013 3 hours

Group Meeting – Coding/Design of Search Page, Login, Home Page

3/24/2013 3 hours


3/29/2013 3 hours


3/30/2013 4 hours

Total Time Spent for the time period 22.5 hours

I verify by my signature that the above information is honest and valid:

Signature: Alexson AndrusDate: 3/11/13

Katherine BarriosDate: 2/7/2013 – 3/11/13


Group Meeting – Coding/Design Query Page 4/19/2013 2 hoursGroup Meeting – Coding/Design Query Page 3/22/2013 3 hours

Group Meeting – User Documentation (Created On-line Help Program)

3/24/2013 3 hours

Group Meeting – User Documentation, Test Plans 3/29/2013 8 hoursGroup Meeting – Documentation 3/30/2013 1 hours

Total Time Spent for the time period 20.5 hours


Signature: Katherine BarriosDate: 3/11/2013

Phillip NelsonDate: 2/7/2013 – 3/11/13


Group Meeting – Access Data Entry 4/19/2013 2 hoursGroup Meeting 3/22/2013 3 hours

Group Meeting – Training Plan Documentation 3/24/2013 3 hoursGroup Meeting – User Documentation (On-line Help Program) 3/29/2013 5 hours

Group Meeting – Project Assessment 3/30/2013 3 hoursTotal Time Spent for the time period 19.5 hours


Signature: Phillip NelsonDate: 3/11/2013

Alexandra TolbertDate: 2/7/2013 – 3/11/13


Group Meeting – Coding/Design of Records Page 4/19/2013 2 hoursGroup Meeting – Coding/Design of Records Page 3/22/2013 3 hoursGroup Meeting – Coding/Design of Records Page 3/24/2013 3 hours

Group Meeting – Migration Plans Documentation, Coding/Design of Records Page

3/29/2013 5 hours

Group Meeting 3/30/2013 3 hoursTotal Time Spent for the time period 19.5 hours


Signature: Alexandra TolbertDate: 3/11/2013

ISDS Recruiting Services · Web viewISDS Recruiting Services Project Plan and Analysis Alexson...

Documents

Transcript of ISDS Recruiting Services · Web viewISDS Recruiting Services Project Plan and Analysis Alexson...