Reference no: EM131315448
Case Description and Content Requirements for the Final Project
Case Description - Online Recruiting System (ORS)
AppBeyondBorders (ABB) Inc. is a non-profit organization that is committed to well beings of people in the developing countries by offering free mobile applications for safety protection (e.g., RapeHotLine, SafeNeighbourhood), healthy lifestyles (e.g., YogaCoach, FoodNutrition), and Education (e.g., WorldHistory). In order to continuously develop innovative and fun apps for people in the developing countries, ABB needs to hire talented people who are knowledgeable of not only software development, but also local culture and language.
Currently, to hire a system analysis/developer, ABB Inc. would post a job ad on its Web site (and/or other job sites if necessary). Interested applicants who view the ad on the Web site could send their resume to ABB either by phone or email. Once the HR department receives the resume, it will circulate it to a recruitment team including CIO, and people from the HR and the Software Development (SD) department for review.
Both the HR and the SD will select interview candidates and conduct interviews. Once interviews are completed, the CIO will be debriefed of the results, and then CIO will make a decision based on the recommendations from the HR and SD department.
The current hiring practice is slow and ineffective. The most time consuming task is resume evaluation. Each member of the recruitment team needs to review submitted resumes (either in PDF or MS Word format), and enters the rating in an Excel file. Then one Excel file is generated to include all the ratings of one candidate by the recruitment team. The tool doesn't make it easy to search candidates that meet certain criteria (e.g., experience, language). In addition, it takes time for the team to select sites to post the ad. With the increasing number of applicants, ABB is feeling the pressure to process applications in a timely fashion. As a result, ABB is contemplating an online recruiting system (ORS) to speed up the hiring process. The following summarizes the key functional requirements of the system:
Account Management Module
This module allows each applicant to create/modify his or her profile (e.g., name, contact information, LinkedIn link). ABB staff use this module to create their account that would allow them to access the ORS.
Job Posting Module
ABB recruitment staff uses the module to create/modify a job ad (e.g., job ad number, job description, skills required, nature of the job [full time, part time]), and select the job site(s) where the job ad is to be posted.
The staff could review previous ads, and select the content that could be used for a new job ad.
Application Module
Using this module, applicants are able to upload his or her application materials in various formats (e.g., MS Word, PDF, voice, video). In submitting an application, an applicant needs to specify the job ad number. An applicant is given flexibility to modify uploaded materials before submission, but once an application is submitted, no changes to the application are allowed.
Application Evaluation Module
This module allows ABB recruitment staff to record their ratings and associate the ratings with specific content in an application. For example, the staff could indicate a particular experience as 5, which could stand for "Most Relevant." Once the recruitment team completes its review of a candidate, the module generates a summary report (which could present the information in specified formats [e.g., chart, text]) containing ratings for all criteria from all team members.
The ABB staff could use the module to define/modify a rating scale (a scale from 1 to 5) for a particular evaluation criterion (e.g., experience, language). A set of rating scales could be developed and linked to a job ad. The defined rating scales could be reused for other job ads.
Using the module, the staff could also search applicants based on search criteria (e.g., education, gender, location, rating, language).
Project Content Requirements
Your individual project is developed based on the case description above. All the diagrams should be created using a diagramming tool (e.g., MS Visio) and copied and pasted to a MS Word document, which should be submitted to D2L.
Required Content
Domain Class diagram
Draw a domain class diagram for the system
Use case diagram
Based on the above project case description, develop a use case diagram containing all major use cases of the system. Select one key use case from the Account Management module, one from the Job Posting module, one from the Application Module, one and one from the Application Evaluation modules and use these four use cases for the rest of diagrams and descriptions
Use case description
Write a fully detailed use case description for each use case in the use case diagram. Develop one activity diagram for each use case description
System sequence diagram
Develop a system sequence diagram based on each fully detailed use case description
Design class diagram
Develop a first-cut design class diagram for the system
Detailed system sequence diagram
Develop a first-cut sequence diagram for each use case
Communication diagram
Based on the first-cut sequence diagram, develop a communication diagram for each use case
Format Requirements for the Final Project
- Font: Times New Roman, size 12
- Need to have a Table of Content listing the content of the project
- Need to use Microsoft Visio for all diagrams. Copy and paste Visio diagrams to MS Word
- The following outline is required.
o Title Page
o Table of Contents
o Assumptions (Optional)
o Domain Class diagram
o Use case diagram
o Use case descriptions
o Activity diagrams (each diagram is named by the name of use case description)
o System sequence diagrams (each diagram is named by the name of use case description)
o Design class diagram
o Detailed system sequence diagram (each diagram is named by the name of use case description)
o Communication diagram (each diagram is named by the name of use case description)