isds 4125- flash driverslaurenlseportfolio.weebly.com/uploads/1/5/2/0/152046… · web viewputting...

ISDS 4125- Flash Drivers

Project for Job Matching System

Spring 2014March 5, 2014

Team 3- The Flash Drivers

Amen AhmedBrittny Bell

Lauren LaaksoMatt Lowery


Table of Contents

Page …………………………………………………… Executive Summary

Page ……………………………………………………. System Request

Page …………………………………………………. Work Plan

Page …………………………………………………. Feasibility Analysis

Page ………………………………………………….. Requirements Definition

Page ………………………………………………….. Use Cases

Page …………………………………………………... Process Model

Page …………………………………………………… Data Model

Page …………………………………………………… Appendices

1


Executive SummaryInternship coordinator and ISDS Professor, Carolyn Borne of Louisiana State University is responsible for keeping ISDS students and recent alumni informed about open IT positions. When Borne receives information on these positions, she emails all ISDS students about the opportunity. If a student would like to be added to the email list, they will not be able to see past job postings.

Putting together these emails and adding students are tedious tasks for Borne and raise challenges for the student who will not be able to access previous emails, or who may have to sift through their inbox to find a desired posting.

Team Flash Drivers has come up with an idea for a website that will allow students and recent alumni the opportunity to view open positions in one central location. This website will allow the student to filter by company preference, skills, job preference, and job location. The student will also be able to select if they would like to receive emails regarding job postings.

2


Initial System Requirements

System Request – Job Matching System

Project Sponsor: Carolyn Borne, Internship Coordinator

Business Need: This project has been initiated to improve the job placement process for students looking for internships and full-time positions.

Business Requirements: Using the Web a student would be able to enter his skills and job preferences. The ISDS office would enter the job requirements from recruiting employers. Students would be given suggested matches.

Students will use this information to determine which jobs to apply for. Students could comment on employers and job experiences. Students could record where they are employed.

Business Value:

Students will be more aware of opportunities. ISDS department will have a record of the types of jobs and employers employing the

students. Employers will be able to be more specific when reaching out to students for jobs. Along with the push of information through emails, students will be able to view this

information at any time.

Special Issues or Constraints:

This is viewed as a specific need of the ISDS students and is to be used along with Careers2Geaux.

This project must be completed in the time constraints of the spring semester.

3


Project Work Plan

4


Feasibility AnalysisJob Matching System Project Executive Summary

Technical Feasibility

Economic Feasibility

Organizational Feasibility

Additional Comments:

5


Current System

Currently, the ISDS students at Louisiana State University receive information about open positions in the IT field via emails sent out by ISDS Professor and Internship Coordinator, Carolyn Borne. Professor Borne receives this information from potential employers whether it be through email, phone conversations, or AITP meetings. She then types this information and emails all ISDS students. If a particular student is not on the email list, that student may ask Professor Borne to be added. However, this student will not be able to see past emails, and Professor Borne has to manually add this student to the list. Professor Borne has asked Team Flash Drivers to create a system that will allow workers in the ISDS office to enter the information she receives regarding these open positions into the system. This will allow students who have asked to be added to the list access to all job postings.

6


Project RequirementsThe system (OR WEBSITE???) will store company preference, skills, job preference, job location, email preference, and email addresses of students and recent alumni of LSU.

LSU students and recent alumni will launch the application and see checkboxes (OR DROPDOWNS….HOW ARE WE SETTING THIS SYSTEM UP??) allowing them to filter by company preference, skills, job preference, or job location. Multiple selections can be make for each preference. Depending on which preferences are selected, job openings matching the user’s desired criteria will be shown below. When the user clicks a job opening, they will be taken to another page that will display additional information on the job (WILL THEY BE REROUTED TO A DIFFERENT PAGE? WILL THE INFO BE SHOWN BELOW? WILL IT JUST BE A LINK TO THE POSITION ON THE COMPANY’S WEBSITE?)

The user may select the Opt in for Emails button (HOW ARE WE SETTING UP THE EMAIL? WILL IT BE A BUTTON?) which will take them to another page allowing them to check off preferences to received emails daily, weekly, or monthly based on what they filtered on the home page.

The system will track the following tables:NEED TO FILL IN TABLE INFO

7


Staffing Plan

Role Description Assigned To

Project Manager

Infrastructure Analyst

System Analyst

Programmer

Reporting Structure:

Special Incentives:

8


Job Matching System- System Proposal

1. Table of Contents

2. Executive Summary

3. System Request

4. Work Plan

5. Feasibility Analysis

6. Requirements Definition

7. Use Cases

8. Process Model

9. Data Model

Appendices

9


Requirements Definition

Functional Requirements

Functional Requirements Description ExamplesProcess-Oriented

Information-Oriented

Nonfunctional Requirements

Nonfunctional Requirements Description Examples

Operational

Performance

Security

Cultural and Political

10


Functional Requirements

1. Filtering by Company Preference 1.1 The user will launch the website **(Not sure if this is a website)**

1.2 The system will have a preference section that will allow users to select the companies they are interested in **(Will this be check boxes where the user can select multiple or just one??)**1.2 The user will click the Go button and job openings pertaining to the selected company will be filtered below **(Again need to know if we are doing search for multiple companies or just one at a time. Also, are we going to have a go button after the user selects their preference or will it automatically filter once they check off what they want)**

Filtering by Skills 2.1 The user will launch the website.

2.2 The system will have a preference section that will allow users to select the skills they possess.2.3 The user will click the Go button and job openings pertaining to the user’s selected skills will be shown below.

Filtering by Job Preference 3.1 The user will launch the website.

3.2 The system will have a preference section that will allow users to select their job preferences.3.3 The user will click the Go button and job openings pertaining to the user’s selected job preferences will be shown below.

Filtering by Job Location 4.1 The user will launch the website.

4.2 The system will have a preferences section that will allow users to select their job location preferences.

4.3 The user will click the go button and job openings pertaining to the user’s selected job location will be shown below.

Email Preferences5.1 The user will launch the website.5.2 The user will check off Company Preference, Skills, Job Preference, and Desired Job Location5.3 The user can click Opt in for Emails5.4 This will bring the user to another page that will allow them to check off for daily, weekly, or monthly emails based on their preferences.

11


Nonfunctional Requirements

1. 1.1

1.21.2

2. 2.1 2.23. 3.1

12


Use CaseUse Case Name: ID: Priority:

Actor:

Description:

Trigger:Type:

Preconditions:

Normal Course: Information for Steps:

Alternative Courses:

Postconditions:

Exceptions:

Summary Inputs Source Outputs Destination

13


Use Case Diagram

14


Data Flow Diagrams

15


Entity Relationship Diagram

16


Part 3: Design Phase

17


Alternative Matrix

Evaluation CriteriaRelative

Importance (Weight)

Alternative 1:

Score (1-

5)

Weighted Score

Alternative 2:

Score (1-

5)

Weighted Score

Alternative 3:

Score (1-

5)

Weighted Score

Tech Issues:

Criterion 1

Criterion 2

Criterion 3

Economic Issues:

Criterion 4

Criterion 5

Organizational Issues

Criterion 6

Criterion 7

Criterion 8

TOTAL

18


Architecture Report

Requirements Server-Based

Client-Based

Thin Client-Server

Thick Client-Server

Operational Requirements

System Integration Requirements

Portability Requirements

Maintainability Requirements

Performance Requirements

Speed Requirements

Capacity Requirements

Availability/Reliability Requirements

Security Requirements

High System Requirements

Access Control Requirements

Encryption/Authentication Requirements

Virus Control Requirements

Cultural/Political Requirements

Multilingual Requirements

Customization Requirements

Making Unstated Norms Explicit

Legal Requirements

19


Hardware and Software Specifications

Standard Client Standard Web Server

Standard Application

Server

Standard Database

ServerOperating

System

Special Software

Hardware

Network

Factors in Hardware and Software Selection

1. Functions and Features2. Performance3. Legacy Databases and Systems4. Hardware and OS Strategy5. Cost of Ownership6. Political Preferences7. Vendor Performance

20


Interface Design

21


Physical Process Model

22


Program Design

23


Database and File Specifications

Data Type Use Suggested Format

24


Physical Data Model

25


Part Four: Implementation Phase

26


Completed Programs

27


Test Plan

Test Stage Web Interface System Management System Interfaces

28


Program ID: Version Number:

Tester: Date Designed: Date Conducted:

Results: Passed Open Items:

Test ID: Requirement Addressed:

Objective:

Test Cases

Interface ID Data Field Value Entered

1.

2.

3.

4.

5.

6.

Script

Expected results/notes

Actual results/notes

29


30


Documentation

Help Topics

Tasks Commands Terms

Help Topic Navigation Controls

31


Migration Plan

Preparing the Business Preparing the Technology Preparing the People

Select a Conversion Strategy

Prepare a business contingency plan

32


Change Management Plan

Conversion Style Conversion Location Conversion Modules

Characteristic

Direct Conversio

n

Parallel Conversio

n

Pilot Conversio

n

Phased Conversio

n

Simultaneous Conversion

Whole-System

Conversion

Modular Conversio

n

Risk

Cost

Time

The Costs and Benefits of Change

As-Is System Transition To-Be System

Restraining Factors Enabling Factors Restraining Factors Enabling Factors

Major Factors in Successful Change

Factor Examples Effects Actions to Take

Benefits of to-be system

Certainty of benefits

Costs of transition

Certainty of costs

33


Actors in the Change Management Process

Sponsor Change Management Potential Adopters

34


Training Plan

One-on-One Training Classroom Training Computer-Based Training

Cost to Develop

Cost to Deliver

Impact

Reach

35


Support Plan

36


Problem Report

Time and date of the report Name, e-mail address, and number of the support person taking the report Name, e-mail address, and number of the person who reported the problem Software and/or hardware causing the problem Location of the problem Description of the problem Action taken Disposition (problem fixed or forwarded to system maintenance)

37


Project Assessment

38


Change Request

39

Project Manager

1. Potential Change

6. Changed 3.

Priority

2. Change request with feasibility, costs, and benefits

Change Committee

Software or Network Changes

Changes to Other Systems

Users

Problem Reports

4. Change Request

Programmer

5. Design Analys

t

isds 4125- flash driverslaurenlseportfolio.weebly.com/uploads/1/5/2/0/152046… · web viewputting...

Documents