Job Booth Using Android
The objective of Job Booth is to develop a system using which job applicants and recruiters can communicate with each other. Job Booth is an android application where job seeker can register themselves and search jobs which are suitable for them. Companies are also get register themselves and appoint the employees according to their requirements. The main aim of developing this Job Booth android application is to provide job opportunities to the job seekers, to meet manpower requirements of Industries and Projects in corporate sectors and To provide live vacancies on the android application. The main objective is to provide a app-based interface for the corporate sector Employers to choose from amongst the registered candidate database.
Characteristics of existing system
Company will find the Employee with skills required in a convenient way. User will be able to search jobs offers from various company .As it is accessible 24 hours anywhere and every time.
DISADVANTAGES:
· Wastage of time.
· Don’t get the current information.
· Wastage of money in travelling.
· Doesn’t get proper information.
Overview of proposed system with advantages
With the help of our online system, people who want to develop their I.T. projects can easily get it done at the lowest cost by the best experts and experienced people and who are really interested in it. Freelancers interested in the specific project can apply bid on it and work by sitting at their place only.
Advantages:
· User will be able to search jobs offers from various company.
· Reach a bigger audience easily.
· Cost effective
· Accessible 24 hours anywhere and everywhere.8
Scope
a) User side:
In-scope:
· Client can view post according to category.
· Client can view trending information.
· Client can select company as per their requirements.
· Client can give feedback
Out-scope:
· Client cannot modify the database
· Client cannot manage resume
· Client cannot submit wrong information
· Client cannot change the functionality of site
b) Admin:
In-scope:
· Admin can view all registrations and logins and feedbacks of users.
· Admin can manage category
· Admin can approve posts of clients
· User data and company data is differentiate by admin
Out-scope:
· Admin cannot apply post.
· Admin cannot select any candidate.
· Admin cannot reply to forums.
· Admin cannot give any feedback
c) Company:
In-scope:
· Company can view information related user.
· Company can select candidate
· Company can prepare result
· Company can give feedback
Out-scope:
· Company cannot modify the database
· Company cannot change data or information of user
· Company cannot make fake result
· Company cannot manage results
Process Model
Software Development Life Cycle:
Software Development Life Cycle, SDLC for short, is a well-defined, structured sequence of stages in software engineering to develop the intended software product.
SDLC Activities:
SDLC provides a series of steps to be followed to design and develop a software product efficiently. SDLC framework includes the following steps:
1.Communication:
This is the first step where the user initiates the request for a desired software product. He contacts the service provider and tries to negotiate the terms. He submits his request to the service providing organization in writing.
2. Requirement Gathering:
This step onwards, the software development team works to carry on the project. The team holds discussions with various stakeholders from problem domain and tries to bring out as much information as possible on their requirements. The requirements are contemplated and segregated into user requirements, system requirements and functional requirements. The requirements are collected using a number of practices as given -
· Studying the existing or obsolete system and software
· Conducting interviews of users and developers
· Referring to the database or
· Collecting answers from the questionnaries.
3. Feasibility Study:
A feasibility study is undertaken to determine the possibility or probability of either improving the existing system or developing a completely new system.
A feasibility study is defined as an evaluation or analysis of the potential impact of a proposed project. Feasibility study is conducted once the problem is clearly understood. Feasibility study is a high level capsule version of the entire system analysis and design process. The objective is to determine quickly at a minimum expense how to solve a problem. The purpose of feasibility is not to solve the problem but to determine if the problem is worth solving. Feasibility and risk analysis are related in many ways. If project risk is huge, the feasibility of producing quality software is reduced. During product engineering, however, we concentrate our attention on following primary areas of interest.
4. System Analysis:
At this step the developers decide a roadmap of their plan and try to bring up the best software model suitable for the project. System analysis includes understanding of software product limitations, learning system related problems or changes to be done in existing systems beforehand, identifying and addressing the impact of project on organization and personnel etc. The project team analyzes the scope of the project and plans the schedule and resources accordingly.
5. Software Design:
Next step is to bring down whole knowledge of requirements and analysis on the desk and design the software product. The inputs from users and information gathered in requirement gathering phase are the inputs of this step. The output of this step comes in the form of two designs: logical design and physical design. Engineers produce meta-data and data dictionaries, logical diagrams, data-flow diagrams and in some cases pseudo codes.
6. Coding:
This step is also known as programming phase. The implementation of software design starts in terms of writing program code in the suitable programming language and developing error- free executable programs efficiently.
7. Testing:
An estimate says that 50% of whole software development process should be tested. Errors may ruin the software from critical level to its own removal. Software testing is done while coding by the developers and thorough testing is conducted by testing experts at various levels of code such as module testing, program testing, product testing, in-house testing and testing the product at user’s end. Early discovery of errors and their remedy is the key to reliable software.
8. Implementation:
This means installing the software on user machines. At times, software needs post- installation configurations at user end. Software is tested for portability and adaptability and integration related issues are solved during implementation.
9. Integration:
Software may need to be integrated with the libraries, databases and other program. This stage of SDLC is involved in the integration of software with outer world entities.
10. Operation and Maintenance:
This phase confirms the software operation in terms of more efficiency and less errors. If required, the users are trained on, or aided with the documentation on how to operate the software and how to keep the software operational. The software is maintained timely by updating the code according to the changes taking place in user end environment or technology. This phase may face challenges from hidden bugs and real-world unidentified problems.
11. Disposition:
As time elapses, the software may decline on the performance front. It may go completely obsolete or may need intense upgradation. Hence a pressing need to eliminate a major portion of the system arises. This phase includes archieving data and requires software components, closing down the system, planning disposition activity and terminating system at appropriate end-of-system time.
User characteristics
a) Admin:
· Admin will login to the site using his username and password
· Admin will view all registrations and logins of all clients and developers
· Admin can manage all categories and subcategories and can even add or modify a category
· Admin will approve all posts of clients before displaying them in the site
· Admin will manage all results of all the posts
· Admin will view all the feedbacks and complaints and reply if he feels
b) User:
· Client will register using his personal information like name, email, DOB, mobile no, gender etc.
· Client will login using his username and password
· Client will choose a particular category as per their requirements.
· Client will view all post
· Client can give reviews of any company
· Client can give any feedbacks, comments or complaints to the site
c) Company:
· Company will register using details like his name, email-id, portfolio, experience, expertise, his charge etc.
· Company will login using his username and password
· Company will choose a particular category and submit all posts related to it
· Company can view result of any post submitted
· Company can view all reviews about him given by his previous
· clients
· Company can give any feedbacks, comments or complaints to the site
Functional Requirements
a) Login
b) Sign up
c) View category by user
d) Sub category
e) Resume
f) Forum
g) Company send selection letter
h) Selection letter through e-mail
i) Feedback
j) Logout
Non-Functional Requirements
a) Reliability
b) Availability
c) Security
d) Maintainability
e) Usability
f) Scalability
g) Cost Effective
Use-case Diagrams
a) Admin:-
b) User:
c) Company:
Output:
Online jobs can be valuable tools for connecting real people with real jobs, in real time especially for college graduates who are more likely to search for jobs on the internet.
GitHub link: https://github.com/dhruvi410/Job_Booth
I hop you enjoyed reading of my blog!! Thank you for reading my blog.
