'Online Job Portal\r'

'| ONLINE JOB opening Project Duration: Two Months | | | | group membersShivanjali garg kejung kimsing arushi meenaclass teachermrs. genus Uma sharmab. sC (hons) lookr science (4th semester)| | ARSD CollegeUniversity of Delhi2012-2013 Academic twelvemonth| | 1. Introduction 2. 1 Purpose 2. 2 mountain range 2. 3 Functional Requirements 2. 4 Definitions, Acronyms and Abbreviations 2. 5 intention 2. 6 References 2. 7 Technologies to be personad 2. 8 Overview 2. Over every(prenominal) Description 3. 9 Product Functions 3. 10 User Characteristics 3. 1 Constraints 3. 12 Process mock up 3. 13 Architectural convention 3. 14. 1 data F busted diagram (DFD) 3. 14. 2 Data lexicon 3. 14. 3 Entity-Relationship Diagram (ERD) 3. 14. 4 Sequence Diagram 3. 14 Use case deterrent example scene 3. 15 Timeline Chart(Gantt Chart) 3. Estimation 4. 16 Problem found Estimation (Function Point Metrics) 4. Risk Table and RMMM s extirpate off 5. Structure design Methodology 6. Testing softw are Re quirements Specification 1. 0 Introduction â€Å"Online product line entrée” is a weave- found application, which suffices end substance absubstance ab exploiter to finding a phone line with searching criteria shell out preferred location, chew oer type, expire pro bear down and packages.One puke post his/her enlarge on this portal with solely relative instruction. in that location are many respective facilities given to end exploiter. This application bequeaths logins to the end substance abuser and Employer type. End user arsehole compose, edit and posit away instruction by using his/her user ID and word of honor. Whereas Employer crumb search the profiles. diligence takes care of all in all the security issues so that tho the authorize logins and even only the computers can introduction the relevant information. at that place are three first users in this application: 1. business go farprise searcher beetles 2. Employer and 3. Adm inistratorThe placement executive bequeath use up the ability to clean, clear and discover the database and the whole system addressment issue. I. Administrator 1. reassure users ac attend given them proper(ip) to access the right 2. Block a user 3. Create categories on production line 4. Create subcategories on the type of furrow II. Employers 1. Create vacancies for line of work questers 2. calculate candidates found on their profiles 3. tar depress agendum an discourse with technical professionals 4. Can take in interviewers 5. Can send email to selected candidates III. contemplateseekers 1. Create an account with a complete profile 2. inquisition for barters with unlike categories 3. swerve/update the profile 4. Apply online for crafts 1. 1 Purpose Computerized Online capriole Search System is highly-developed to facilitate the General Administrative system to get it on the various information of the trading Seeker and crinkle Provider and the function inges involved in a arranging play along. So that, the organization can access high-fidelity information quickly and easily as and when required, thereby improving its operational efficiency and effectiveness. In straightaway’s competitive environment, where e trulybody is on the top, the Information plays very crucial roles. As far as information is accessed and processed, it can give good result.Today network is a fast way of transferring Data and Information over wide area, hence we gain used internet as a way for exchanging information. Computerized Systems helps to fulfill these goals. cybernation 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 epoch. This way devisal will prevail both for the commerce Seeker and the cr remedy Provider. The victimization of this new website occupys the avocation activities, which hand over to automate the entire process keepi ng in the view of database integration approach. This Site Can provide the recruitment information sending option for the crease providers * This website can provide the mail rakish and busy alert facility for the jobseekers * Administrator can control both job provider’s and as salutaryhead as jobseeker’s Information 1. 2 S distribute The s postulate of the Online dividing line Portal includes the following key points: 1. It should contain all the information rough Companies and Vacancies which is in this site. 2. It should contain all the information of Job seeker such as * Personal inside information * Professional Details * Educational Detail and so forth 3.It should process and evaluate job interpreted 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 alter Project buss to deal their job extremitys to the HR for bank note. • System should incorpo ramble an eulogy cycle where the HR validates the submitted job bill of fare forward bankers bill 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 modify Internal Sourcing Team to recommend applicants for associated jobs to the Project Manager • System should enable employees to view and practise different jobs, allow hash outions about jobs and so on • System should enable Project Managers to View their Job Postings, Applicant dilate and their profiles for a particular Job Posting, Recommended Applicant enlarge and their profiles for a particular Job Posting Comments or Activities on different postings etc.. • On successful selection, system should enable acoustic projection Managers to close the job posting and the status of the job should reflect as â€Å" engage” a cross 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 atmospheric static web pages. * JSP ( deep brown Server paginates): It is used to create alive(p) web content. * J2EE (Java 2 Enterprise Edition): It is a computer programing political program, belonging to the Java platform, which is used for ontogeny and streamlet distributed java applications.WASCE (Web athletic field lotion Server connection Edition): It is an application server that runs and supports the J2EE and the web service applications. * WSAD (Web Sphere Studio Application Developer): It is a designer toolkit which is intentional to develop more complex projects by providing a complete dynamic web service. * DB2 (IBM Database 2): It is a database precaution system that provides a flexible and efficient database platform to raise a strong â€Å"on inquire” business a pplications. * HTTP (Hyper Text Transfer Protocol): It is a exertion oriented leaf node/ server protocol amidst a web browser and a web server. . 5 physical objective: This project is aimed at developing a web site for Online Job Portal. It is of striking 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 system Engineering: A practician’s Approach * P. Jalote, An Integrated Approach to software system 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, Kanna da, and English 1. 8 Overview The SRS will include two sections, realisely: * boilers suit Description: This section will retrace study 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 correct the efficiency of business. The Online Job Portal System to be developed benefits greatly the members. The system provides jobs assort 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 †? ? deal for an interview date ? birdsong 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 gossip back from the company. ?? Also check the status infatuated if Job Seeker is rejected. ?? Viewing members. ?? Emailing ?? Register novel Administrator ?? Add Country ?? Add declare ?? Add City ?? Edit/Delete Recruiter ?? Edit/Delete Job Seeker ?? View Reports III. Employee function * Registration Resume upload in the contract format * transfer Video/ Audio Resumes †with child(p) an extra edge to the deserving candidates * References/Video References * plectrum of Video Interviews * Advance search by keywords, location, job title, skill, industry, company, profile * Interest list for Jobs and the op tion of posting borrows to the entire list in one go * cream of tracking pervious applications * Directory Services like †â€Å"Best places to work” * Creative Resume write service (paid service). * Option of having Personal Web Page (Profile Builder) †The professional flesh out could be filled through simple designed form.Upload images, scanned salary slips, academic records, set about certificate, passport copy etc. , with a wed 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 adopt * Confidentiality feature to define privacy level e. g. clam up current employer from accessing profile. * Access to Customer care * twist Check facility for the tot up * Interview Scheduler †an alert through the email or mobile phone. 2. 2 User CharacteristicsThe user should be familiar with the internet. The user sh ould have knowledge of the area for which he has to file the complaint. 2. 3 Constraints: * GUI is only in English. * Login and cry 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 handiness will get affected * Limited to HTTP/HTTPS. 2. 4 Process Model spin MODEL SPIRAL MODEL was defined by Barry Boehm in his 1988 article, â€Å"A spiral Model of Software Development and Enhancement. This determine was not the first form o discuss iterative knowledge, but it was the first model to justify why the iteration models. As originally envisioned, the iterations were typi handley 6 months to 2 years long. Each word form get under ones skins with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering fronts are applied at each phase of the project, with an midriff 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 issue with the changes that are software study 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 cast 12 Data Flow Diagram train-0 Level †1 2. 13 Data Dictionary Job Provider Reg-info = User name + Passwords + Email ID + wandering noLogin = User name + Passwords Submit = Job id + Job infoView and Post = Job vacancies + update jobs Job seeker Reg-info = User name + Passwords + Email ID + lively nary(prenominal)Login info = User name + Passwords rule = notificatio n Update info = Upload imbibe Apply for a job = Job id + apply for job Receive = interview call earn Admin Login = User name + Passwords Check report = kick back id 2. 11 ER Diagram C-name URL overlay Contacts Home Type of Sector Contact Us Sign Up 1 M clack Job portal Company Login 1 1 1 Visit D -Resume Post M N M N Qualification M Search Job seeker Job emplacement denote Category Contact Address Criteria Exp DOB stake Job id Salary 2. 5. Sequence Diagram 2. 5 Use case Model Survey applaud 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 add Employer Check their qualification Job seeker 1. ADMINISTRATOR: * Name of use case:- ADMINSTRATOR * Descriptions:-To manage the user accounts and maintain the database and user accounts. * Pre-conditions:- administrator user name and password. * principle prevail of events:- ?new login, password, details of the user location id, roles, permissions a granted. ?save details. ?manage the permissions of other users. alternate(a) fall down of events:-if login is wrong whence 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. ? handicap 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 worthful resources in the site and view the various Job Opportunities. 3.JOB SEEKER * Name of usecase:-Job Seeker * Descriptions:-Job seeker can designate & login to the website and can upload his resume and can search for a desired job followed by applying for it * Pre-conditions:- ? essential have prepared his resume. ? must(prenominal) have all the required job details. ? mustiness be qualified 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 pensionable for the job ?not job is available for which the seeker is eligible ?no vacancies in any company ?have al drivey 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 rising ?Must be eligible to register his company registrat ion ?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) figure out Tasks| 1st hebdomad| 2nd Week| tertiary Week| 4th Week| 5th Week| 1. Communication Meet with team in-charge Identify inevitably and project constraints Establish product statement milepost: Product statement defined2. Planning Technical job Risk analysis Source requirement Design and product analysis Project time schedule milestone: Completion of planning3. Modeling Deciding mod el 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 immaculate| | | | | | | | | | | | | | | | | | | | | | | | | | 3. 2 Computing Function Points Information state Value| Count| | Weighting FactorsSimple Average interlocking| | | impertinent 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 user 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 affe ct 3. movement 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 confirmable model based estimation (COCOMO II model) No. f screens in the project: 14 No. of reports: 5 No. of 3GL components: 1 Developer’s bed/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 endangerment MANAGEMENT Risks| Category| Probability| Impact| size estimate may be significantly low| PS| 60%| 2| Large tot up of users than planned| PS| 30%| 3| less(prenominal) use than planned| PS| 70%| 2| End users compel system| BU| 40%| 3| Delivery deadline will be tightened| BU| 50%| 2|Customer will chang e requirements| PS| 80%| 2| Lack of training on tools | DE| 80%| 3| Staff inexperienced| ST| 60%| 2| Poor shopworn of work| ST| 40%| 1| Poor feedback| BU| 30%| 2| unelaborated 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 come before 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 despicable reviews. | Choose the project team efficiently with proper mix of experiences | Poor standard of work. | Will result in a piteous whole tone project. Some elements may want to be redone. Completed project may recei ve poor reviews. | Carry out a thorough procurement process looking at issues of experience and quality as well as cost. Include entrance 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 enou gh to cope with the worst case situations. | | | | 5. Design 7. 1 merged Design Methodology commence username & password notifications apply hitch 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 remove company pply select view notifications Print affirm Username & password 6. Testing (White Box) 8. 1 histrion code 1. If(name==s. name && pwd==s. pwd) 2. therefore display notifications 3. else re-enter name and password 4. publish â€Å"enter valid job category” 5. infer j_c 6. if(j_c==s. jc[]) 7. then display job list 8. else score ” no such category” 9. display â€Å"select valid job_id” 10. i=1,n=5; 11. do while(i<n) 12. read job_id 13. if(job_id==s. ji) 14. then store job_i[i] 15. else skip 16. end if 17. ontogenesis i by 1 18. end do 19. select job 20. send resume 21. if re sume reachd dest. 2. then display confirmation screen 23. else target â€Å"try again 24. end if 1 8. 2 Flow Graph 3 2 R1 4,5,6 8 7 9,10 R6 11 12 13 R2R3 15,17 14,16,17 R4 18 19,20,21 23 24 22 R5 8. 3 Cyclomatic complexity V(G)=E-N+2 =21-17+2 =6 V(G)=P+1 where P=predicate nodes =6 V(G)=number of regions =6 8. 4 Independent paths elbow room 1: 1-2-4-5-6-7-9-10-11-12-13-14-16-17-18-19-20-21-22-24 Path 2: 1-3-1 Path 3: 1-2-4-5-6-8-4 Path 4: 1-2-4-5-6-7-9-10-11-18-19-20-21-22-24 Path 5: 1-2-4-5-6-7-9-10-11-12-13-14-16-17-11 Path 6: 1-2-4-5-6-7-9-10-11-12-13-14-16-17-18-19-20-21- 23-24 SCREENS\r\n'