Online Job Portal

| ONLINE JOB PORTAL Project Duration: Two Months | | | | team membersShivanjali garg kejung kimsing arushi meenaclass teachermrs. uma sharmab. sC (hons) computer science (4th semester)| | ARSD CollegeUniversity of Delhi2012-2013 Academic Year| | 1. Introduction 2. 1 Purpose 2. 2 Scope 2. 3 Functional Requirements 2. 4 Definitions, Acronyms and Abbreviations 2. 5 Objective 2. 6 References 2. 7 Technologies to be used 2. 8 Overview 2. Overall Description 3. 9 Product Functions 3. 10 User Characteristics 3. 1 Constraints 3. 12 Process Model 3. 13 Architectural Design 3. 14. 1 Data Flow Diagram (DFD) 3. 14. 2 Data Dictionary 3. 14. 3 Entity-Relationship Diagram (ERD) 3. 14. 4 Sequence Diagram 3. 14 Use case Model Survey 3. 15 Timeline Chart(Gantt Chart) 3. Estimation 4. 16 Problem Based Estimation (Function Point Metrics) 4. Risk Table and RMMM plan 5. Structure design Methodology 6. Testing Software Requirements Specification 1. 0 Introduction â€Å"Online Job portal† is a web-ba sed application, which helps end user to finding a job with searching criteria like preferred location, job type, work profile and packages.One can post his/her details on this portal with all relative information. There are many respective facilities given to end user. This application provides logins to the end user and Employer type. End user can Create, edit and delete information by using his/her user ID and password. Whereas Employer can search the profiles. Application takes care of all the security issues so that only the authorize logins and even only the computers can access the relevant information. There are three primary users in this application: 1. Job Seekers 2. Employer and 3. AdministratorThe system administrator will have the ability to clean, clear and maintain the database and the whole system management issue. I. Administrator 1. Verify users account given them right to access the right 2. Block a user 3. Create categories on job 4. Create subcategories on the type of job II. Employers 1. Create vacancies for job seekers 2. Search candidates based on their profiles 3. Can schedule an interview with technical professionals 4. Can select interviewers 5. Can send email to selected candidates III. Jobseekers 1. Create an account with a complete profile 2. Search for jobs with different categories 3.Edit/update the profile 4. Apply online for jobs 1. 1 Purpose Computerized Online Job Search System is developed to facilitate the General Administrative system to manage the various information of the Job Seeker and Job Provider and the processes involved in a Placement company. So that, the organization can access accurate information quickly and easily as and when required, thereby improving its operational efficiency and effectiveness. In today’s competitive environment, where everybody is on the top, the Information plays very crucial roles. As far as information is accessed and processed, it can give good result.Today internet is a fas t way of transferring Data and Information over wide area, hence we have used internet as a way for exchanging information. Computerized Systems helps to fulfill these goals. Computerization of the official works will help in doing lot of manual work quickly. It will help in easy storage and access of all information, in short period of time. This way convenience will prevail both for the Job Seeker and the Job Provider. The development of this new website contains the following activities, which try to automate the entire process keeping in the view of database integration approach. This Site Can provide the recruitment information sending option for the Job providers * This website can provide the mail alert and mobile alert facility for the jobseekers * Administrator can control both job provider’s and as well as jobseeker’s Information 1. 2 Scope The scope of the Online Job Portal includes the following key points: 1. It should contain all the information about Com panies and Vacancies which is in this site. 2. It should contain all the information of Job seeker such as * Personal Details * Professional Details * Educational Detail etc. 3.It should process and evaluate job registered by companies. 4. It should contain information related to Job expiry and registration. 5. It should have administrator for scheduling administrative work of site. 1. 3 Functional Requirements †¢ The System should enable Project Managers to submit their job requirements to the HR for posting. †¢ System should incorporate an approval cycle where the HR validates the submitted job posting before posting to the portal †¢ On Approval, the job posting is assigned to an Internal Sourcing Team, who will receive a notification of the new job posting. System should enable Internal Sourcing Team to recommend applicants for associated jobs to the Project Manager †¢ System should enable employees to view and apply different jobs, allow discussions about job s etc. †¢ System should enable Project Managers to View their Job Postings, Applicant details and their profiles for a particular Job Posting, Recommended Applicant details and their profiles for a particular Job Posting Comments or Activities on different postings etc.. †¢ On successful selection, system should enable project Managers to close the job posting and the status of the job should reflect as â€Å"Hired† across the shared communities, dis-allowing employees to further apply for the job. 1. 4 Definitions, Acronyms, and Abbreviations: * HTML (Hyper Text Markup Language): It is used to create static web pages. * JSP (Java Server Pages): It is used to create dynamic web content. * J2EE (Java 2 Enterprise Edition): It is a programming platform, belonging to the Java platform, which is used for developing and running distributed java applications.WASCE (Web Sphere Application Server Community Edition): It is an application server that runs and supports the J2E E and the web service applications. * WSAD (Web Sphere Studio Application Developer): It is a designer toolkit which is designed to develop more complex projects by providing a complete dynamic web service. * DB2 (IBM Database 2): It is a database management system that provides a flexible and efficient database platform to raise a strong â€Å"on demand† business applications. * HTTP (Hyper Text Transfer Protocol): It is a transaction oriented client/ server protocol between a web browser and a web server. . 5 Objective: This project is aimed at developing a web site for Online Job Portal. It is of great importance to the unemployed people. This site allocates the right job information for suitable persons. All the jobseekers as well as job providers’ information are stored in the database. 1. 6 References * BOOKS * R. S. Pressman, Software Engineering: A Practitioner’s Approach * P. Jalote, An Integrated Approach to Software Engineering 1. 7 Technologies to be used * J2EE: (Servlet, JSP, JAXP, Java Beans) Application architecture. * JAVA: Application architecture. WASCE: (Web Sphere Application Server Community Edition) Web Server * DB2: IBM Database. * Ajax: Asynchronous Java Script and XML. * XML: Extension Markup Language. * Web 2. 0: RSS Feed 2. 0. * Localization: 3 Languages – Hindi, Kannada, and English 1. 8 Overview The SRS will include two sections, namely: * Overall Description: This section will describe major components of the system, interconnections, and external interfaces. * Specific Requirements: This section will describe the functions of actors, their roles in the system and the constraints faced by the system. 2. 0 Overall descriptionThe Online Job Portal System is a package to be used by agencies to improve the efficiency of business. The Online Job Portal System to be developed benefits greatly the members. The system provides jobs catalogue and information to members and helps them decide on the jobs to apply . The Admin can keep the jobs catalogue updated all the time so that the members (Job seekers and the agencies) get the updated information all the time. The main users are users: Admin, Members who are the Job seekers and the agencies. 2. 1 Product Function I. Job Employer Job Employer section, which is further sub-divided into – Call for an interview date ? Call for an interview time Call for an asking Job Seeker want to go for an interview? Call for an asking Job Seeker about feedback of interview facing? Check the status true if selecting in the job. II. Job Administrator Job Administration section, which is further sub-divided into four subsections: Check the status true if call back from the company. Also check the status false if Job Seeker is rejected. Viewing members. Emailing Register New Administrator Add Country Add State Add City Edit/Delete Recruiter Edit/Delete Job Seeker View Reports III. Employee Section * Registration Resume upload in the speci fied format * Upload Video/ Audio Resumes – giving an extra edge to the deserving candidates * References/Video References * Option of Video Interviews * Advance search by keywords, location, job title, skill, industry, company, profile * Interest list for Jobs and the option of posting resumes to the entire list in one go * Option of tracking pervious applications * Directory Services like – â€Å"Best places to work† * Creative Resume writing service (paid service). * Option of having Personal Web Page (Profile Builder) – The professional details could be filled through simple designed form.Upload images, scanned salary slips, academic records, experience certificate, passport copy etc. , with a link and it could be accessed online from anywhere with feature of differential access. * Option of taking Industry endorsed tests for better employability and put them on the personal web page along with the resume * Confidentiality feature to define privacy le vel e. g. block current employer from accessing profile. * Access to Customer care * Spell Check facility for the resume * Interview Scheduler – an alert through the email or mobile phone. 2. 2 User CharacteristicsThe user should be familiar with the internet. The user should have knowledge of the area for which he has to file the complaint. 2. 3 Constraints: * GUI is only in English. * Login and password is used for identification of user and there is no facility for guest. * This system is working for multiple servers. * There is no maintainability of back up so availability will get affected * Limited to HTTP/HTTPS. 2. 4 Process Model SPIRAL MODEL SPIRAL MODEL was defined by Barry Boehm in his 1988 article, â€Å"A spiral Model of Software Development and Enhancement. This model was not the first model o discuss iterative development, but it was the first model to explain why the iteration models. As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project. It is an evolutionary software process model that couples the iterative nature of prototyping with the controlled and systematic aspects of the waterfall method. Fig 1. 0 Spiral Model Reasons for using this model in our project: Estimates (i. e. budget, schedule etc. ) become more realistic as work progresses, because important issues discovered earlier. * It is more able to cope with the changes that are software development generally entails. * Software engineers can get their hands in and start working on the core of a project earlier. * It’s a realistic approach to the development of large scale system and software. Architectural Design 12 Data Flow Diagram Level-0 Level – 1 2. 13 Data Dictionary Job Provider Reg-info = User name + Passwords + Em ail ID + Mobile No Login = User name + Passwords Submit = Job id + Job infoView and Post = Job vacancies + update jobs Job seeker Reg-info = User name + Passwords + Email ID + Mobile No Login info = User name + Passwords Receive = notification Update info = Upload resume Apply for a job = Job id + apply for job Receive = interview call letter Admin Login = User name + Passwords Check report = Complain id 2. 11 ER Diagram C-name URL Address Contacts Home Type of Sector Contact Us Sign Up 1 M Visit Job portal Company Login 1 1 1 Visit D -Resume Post M N M N Qualification M Search Job seeker Job Location Name Category Contact Address Criteria Exp DOB Position Job id Salary 2. 5. Sequence Diagram 2. 5 Use case Model Survey Approve the vacancy Administrator Login Put the vacancy on website Download the CV Send the reply to jobseeker Search for job Register Apply the job Upload resume Employer Check their qualification Job seeker 1. ADMINISTRATOR: * Name of use case:- ADMINSTRATOR * Descr iptions:-To manage the user accounts and maintain the database and user accounts. * Pre-conditions:- administrator user name and password. * Normal flow of events:- ?new login, password, details of the user location id, roles, permissions a granted. ?save details. ?manage the permissions of other users. Alternative flow of events:-if login is wrong then message appears. * Post conditions:-Management of user accounts and permissions. 2. REGISTRATION * Name of usecase:-CREATE the account * Descriptions:-the user can create a new account in the site. * Pre-conditions:- ?not a member of the site. ?invalid username and password. * Normal flow of events:- ?enter the details and submit. ?login the site. ?logout the site. * Alternative flow of events:- ?invalid username. ?invalid password. * Post conditions:- User can use the valuable resources in the site and view the various Job Opportunities. 3.JOB SEEKER * Name of usecase:-Job Seeker * Descriptions:-Job seeker can register & login to th e website and can upload his resume and can search for a desired job followed by applying for it * Pre-conditions:- ?Must have prepared his resume. ?Must have all the required job details. ?Must be eligible to apply for a job ?Must have registered for a job ?Must have prepared his resume * Normal flow of events:- ?enter the details and submit. ?login the site. ?upload a resume ?search for a job ?apply for a job ?check his application status ?can access to customer care * Alternative flow of events:- invalid username. ?invalid password. ?not eligible for the job ?not job is available for which the seeker is eligible ?no vacancies in any company ?have already applied for all the vacancies * Post conditions:- user can wait for the companies to give him a call for the interviews and can regularly check his mails for the alerts(if any)send by he administrator 4. JOB PROVIDER * Name of use case:-Job Provider * Descriptions:-Job Provider can register & login to the website and can add the vacancies update and delete them. * Pre-conditions:- ?Must have some vacancies for chances of vacancies in the future ?Must be eligible to register his company registration ?Must have registered to the site * Normal flow of events:- ?enter the details and submit. ?login the site. ?add the vacancies ?update the vacancies ?delete the vacancies ?check who all have register their vacancy and can contact to them personally * Alternative flow of events:- ?invalid username. ?invalid password. ?not eligible for registering ?no vacancies in the company ?no user registered for the vacancy * Post conditions:- Provider can take the note of the seekers who he wants to call for an interview and can contact with them through mails or calls. . 17 Timeline Chart(Gantt Chart) Work Tasks| 1st Week| 2nd Week| 3rd Week| 4th Week| 5th Week| 1. Communication Meet with team in-charge Identify needs and project constraints Establish product statement Milestone: Product statement defined2. Planning Technical task Risk analysis Source requirement Design and product analysis Project time schedule Milestone: Completion of planning3. Modeling Deciding model Analysis used model Milestone: Model selected4. Construction Code generation Testing Milestone: Completed construction5.Deployment Review the project Delivered to the customer Feedback based on evaluation Milestone: Project completed| | | | | | | | | | | | | | | | | | | | | | | | | | 3. 2 Computing Function Points Information Domain Value| Count| | Weighting FactorsSimple Average Complex| | | External Inputs| 8| x| 3| 4| 6| =| 24| External outputs| 5| x| 4| 5| 7| =| 20| External Inquiries| 3| x| 3| 4| 6| =| 09| Internal Logical Files| 6| x| 7| 10| 15| =| 42| External Interface Files| 0| x| 5| 7| 10| =| 0| Count Total| 95| To compute function points (FP), the following relationship is used: FP = count total x [0. 5 + 0. 01 x ? (Fi)] = 95x{0. 65+0. 01Ãâ€"46} = 105. 45 Where count total is the sume of all FP entries obtained from the Fi ( i = 1 to 14) are value adjustment factors (VAF) based on responses to the following. 1. Data communication 2. Distributed processing 3. Performance objectives 4. Operation configuration load 5. Transaction rate 6. On-line data entry 7. End user efficiency 8. On-line update 9. Complex processing logic 10. Re-usability 11. Installation ease 12. Operational ease 13. Multiple sites 14. Desier to facilitate change 4. 2. 2 Empirical model based estimation (COCOMO II model) No. f screens in the project: 14 No. of reports: 5 No. of 3GL components: 1 Developer’s experience/capability: Very Low % reuse: 70 Taking the values from the given tables: Thus Object Points= [14X1 + 5X2 ] =24 NOP= (object points) X [(100-%reuse)/100] =24 X 0. 30=7. 2 PROD=4 Thus Estimated effort=NOP/PROD=7. 2/4=1. 8 person-months RISK MANAGEMENT Risks| Category| Probability| Impact| Size estimate may be significantly low| PS| 60%| 2| Large number of users than planned| PS| 30%| 3| Less use than planned| PS| 70% | 2| End users resist system| BU| 40%| 3| Delivery deadline will be tightened| BU| 50%| 2|Customer will change requirements| PS| 80%| 2| Lack of training on tools | DE| 80%| 3| Staff inexperienced| ST| 60%| 2| Poor standard of work| ST| 40%| 1| Poor feedback| BU| 30%| 2| Incomplete requirements| PS| 30%| 2| Risk | Consequence | Action | Size estimate may be significantly low. | Inefficient resource allocation for the software resulting in delivery delays. | Close look at requirement collection process. | Less reuse than planned. | Development time will increase. | Develop efficient SRS. | Customer will change requirements. | Might lead to start of development from scratch. Choose an efficient model that can cope with sudden changes in requirements. | Staff Inexperienced. | Might lead to development of incomplete software. Completed project may receive poor reviews. | Choose the project team efficiently with proper mix of experiences | Poor standard of work. | Will result in a poor q uality project. Some elements may need to be redone. Completed project may receive poor reviews. | Carry out a thorough procurement process looking at issues of experience and quality as well as cost. Include appropriate contingency. | Delivery Deadline may be tightened. Delay in deployment. | Deadline should be carefully calculated keeping all areas in mind. | Poor public response to the software. | Wastage of development efforts with financial losses. | Conduct a survey to get information about market trends. | Requirements are incomplete. | Incomplete software. May get rejected by the customer. | Requirements should be carefully understood and documented. | Lack of training on tools. | Inefficient software product with chances of defects. | Developers should be well trained and comfortable with the development tools. | | | | End users resist system. Redevelopment of the product from scratch. | End users terms and conditions should be mentioned in the SRS. | Larger number of users than planned. | Database will need to be expanded. | Database should be big enough to cope with the worst case situations. | | | | 5. Design 7. 1 Structured Design Methodology Get username & password notifications apply confirmation validate joblist userid resume name&pwd System Database Main Print confirmation Login Apply Notifications Check passwords Check username Get passwords Get username validation login input Send resume Select company pply select view notifications Print Validate Username & password 6. Testing (White Box) 8. 1 Pseudo code 1. If(name==s. name && pwd==s. pwd) 2. then display notifications 3. else re-enter name and password 4. print â€Å"enter valid job category† 5. read j_c 6. if(j_c==s. jc[]) 7. then display job list 8. else print † no such category† 9. display â€Å"select valid job_id† 10. i=1,n=5; 11. do while(i