fgfgfg fdgdgs

1. MOBILE BASED JOB
PORTAL SYSTEM

2. CHAPTERS
INTRODUTION
This chapter is all about the baasic
conepts of the project like
background ,scope ,objective
methedology etc.....
01 Description of the
existing system
This chapter is all about the current Job
syatem and its difficulties and obstaceels
that this system is aiming to solve
02
System Analysis.
this chapter is about major discroiption of
the system such as
usecases,sequence ,activity ,state
diagrams userinterfface prototype
03 System Design
This chapter is design of the system
archetcure
Database
mapping of softwere and hardwere
diagrams like
componet and diployment
04

4. 1. Introduction
2. Background of the project
3. Stetmet of the problem
4. Objective
5. Scope and limitaions
6. Methodology
7. beneficery of the project
8. Task Breakdown
9. Feasibility

5. Introduction
Introduction!
• Job search systems are a crutial components of the employment and recruitment
process in the current world
• In our country, the vacancy announcement is there doing its work almost manually,
especially by newspapers called ADDIS ZEMEN GAZETA and others.
• It takes many resources, including time, money spent on transportation, service
effectiveness, and knowledge of the available job openings
• Due to the process's extensiveness and complexity, which necessitates a lot of labor,
resources, and money, it is vulnerable to corruption and destruction. Because it is
too monotonous, constrained, difficult to access, and laborious, it does not provide
employees with satisfaction
• Now a days there are a few national and international systems like ethio jobs
,LinkedIn which has the capacity to replace this traditonal system and we are
motivated to play a role by following those systems

6. Introduction
Background of
Project!
02
• An online job portal system is a website or an application that
connects job seekers with employers and allows them to search
and apply for jobs online.
• The concept of an online job portal can be traced back to the early
days of the internet,
• In the early 2000s, the first dedicated online job portals were
created, such as Monster.com and CareerBuilder.com
• It was somewhat functional
• An online job portal system project typically involves creating a
mobile application that includes the following features:
Database of job listings
Search and filter system for job listings
A system to create profiles and upload resumes
A system for employers to create accounts,
Post job listings, and search for candidates
Managing applications and resumes
Security features to protect personal information

7. Introduction
Stetmet of the Problem!
03
Our system provide:
• Confidentiality
• Efficency of time
• Easily accessible
• Easy to search
• Faster
• Reduces cost
• The statment of the problem is the lack of the obove key
advantages on the current traditonal system

8. Introduction
Objective of Project! 04
General Objective
• To create a cross platform that connects job
seekers with potential employers. • To design a system to solve existing problems
• Identify functional and non-functional requirements
• Automated communication features that notify both
parties
• develop a user-friendly interface
• Implement the proposed system.
• Testing the proposed system.
Specific objective
The specific objectives of this project are :to

9. Introduction
Scope of the Project&
Limitations! 05
Scope:
• Cross-platform : works on Android, iPhone/iOS and Windows Phone
• Adaptability: Works on different types of devices with different screen sizes
• Smart User Interface: its very easy and enjoyable for anyone
• Real-time Updates: gives timely notifications different activities
• Secure Login System: has secure login/verification systems
• Location: Only in Ethiopia
Limtation:
• Cannot give online examinations and interviews.

10. Introduction
Methodology (Approaches)
06
SDLC Model: We used Agile model approach
Requirement gathering methods
• Interview
• Direct observation
Analysis and design Methodology
we used the object-oriented software engineering (OOSE) approach,
Unified Modeling Language (UML)
Implementation Methodology
• Flutter:
• VS code
• Wps
• firebase DB

11. Introduction
Task Breakdown
07
I. Requirement Gathering
II. Analysis
III. Design
IV. Coding
V. Testing
VI. Implementation

12. Introduction
Feasibility study
07
I. Technical feasibility:The technical needs of the system,equipment and software are mature enough
to be easily applied to solve the problem that we identified in the existing system
II. Economic feasibility :is the cost of the system too high than the cost it saves
III. Operational feasibility
easly oprabel for every one
IV.Project Schedule / Timeline
Tangible benefits
• Reduction of paper and pen.
• Reduce the work load
• Manual Labor can be reduced
Intangible benefits:
• Increases speed
• Give better and effective service
• Increase security
• Easy to use
• Time-saving
• Convenience
• Easy to search and filter
• Easy to manage
• Effective recommendation system
• Secure payment service

14. 2.1. Introduction of
Existing System
Discripton of existing system
07
• Introduction of Existing System
Traditonal
Recent
• Major functions/activities in the existing system.
Creating the post
Printing it manually in paper
Posting it on different material in places where people gather most
Accepting applicants and storing their document manually in paper
• Players in the existing system
Employer
Job seeker

15. 2.1. Introduction of
Existing System
Discripton of existing system
07
• Bottlenecks of the existing system
Security and control problem
Performance problem
Efficiency problem:
Information problem:
Data storage
• Proposed solution to address problems
• account is protected by password
• Speed for updating and deleting since its digtal
• Making Most out of the applicants information available
• Have better database and reduce Lack of well-organized database, accessibility, data
redundancy and inconstancy

16. 2.1. Introduction of
Existing System
Discripton of existing system
07
Functional requirement explains how the system must work,while
Nonfuncctional requiremnts explain how the system shoude prerform.
Requirements of the Proposed System

17. 2.1. Introduction of
Existing System
Discripton of existing system
2.7 Requirements of the Proposed System
07
• Functional Requirement
Enable the job seeker and employer login and logout.
Enable the job seeker, employer to view and update his/her profile.
Enable the job seeker to receive and view job notification.
Enable the job seeker to upload his/her CV.
Enable job seekers to search for a job, view job detail, apply for jobs, view jobs based on their category.
Enable the employer to post, edit and delete Job.
Enable the employer to view the selected applicant and applicant’s detail.
Enable the employer to View, download the CV.
Enable the employer to generate reports.
• Non functional Requirement
• User-friendly interface :- an easily understandable interface.
• Maintainability: If there are any additional requirements the system is flexible to change.
• Ease of accessibility:- wherever they are with consistent network connection and network-accessible device.
• Performance: - use efficient way for each task
• Availability:- The system is available 24 hours Authorization and
• Authentication:- facilities by asking username and password
Requirements of the Proposed System

19. 2.1. Introduction of
Existing System
System analysis
2.7 Requirements of the Proposed System
07
• Actors: external entities that interact with the system. job seekers, employers, unregistered
and administrators.
Actors and use case Identification
specific functions or
processes that the
system performs to
meet the needs of
the actors.
Usecase

20. 2.1. Introduction of
Existing System
System analysis
2.7 Requirements of the Proposed System
07
• .
use case descripon
specific functions or
processes that the
system performs to
meet the needs of
the actors.
Use case id: Uc14
Use case
name:
Edit vacancy
Actors: Employer
Description: Edit the vacancy that is posted on the system
Pre condition: The user must login to the system, and there must be a job that is posted by the actor
Normal flow: Action System response
login to the system3.The user click on my posts 5.Click on the
job 7.Click on edit job button9.Edit the post and click save
2.the system displays the home page4.Displays the
jobs posted by the user6.Displays the details of the job
8.The system allows the user to edit the post10.Save
changes and exit the page11.End use case
Post
conditions:
Edit the job that was previously posted
Alternative
flows:
If the user does no changes on the post, the system simply remains as it was.

21. 2.1. Introduction of
Existing System
System analysis
07
specific functions or
processes that the
system performs to
meet the needs of
the actors.
Object model

22. System analysis
07
Sequence Diagram
Usecase

23. System analysis
07
Sequence Diagram
Usecase

24. System analysis
07
Actvity Diagram
Usecase

25. System analysis
07
State Diagram
Usecase

26. System analysis
07
State Diagram
Usecase

28. System Design
07
software Architecture
Usecase
Architecture Overview: This system will be built using the Flutter
framework and Firebase as its primary storage layer. The architecture
divided into two main components,
Mobile application :
using Flutter as the UI/UX layer, offering cross-platform capabilities on
iOS and Android devices. It will include necessary services
Firebase infrastructure:
provides a range of cloud services that help speed up development of
mobile applications by providing real-time database, cloud functions
and analytics support that can simplify many important tasks of the job

29. System Design
07
software Architecture
Usecase

30. System Design
07
subsystem Decomposition
Usecase
Subsystem decomposition
is a process of breaking
down a complex system
into manageable parts that
are easier to maintain and
update.

31. System Design
07
Database Design
Usecase
Database design is the
process of designing a
database system by
conceptualizing it as a
schematic that defines the
structure, organization and
content of data within a
database.

32. System Design
07
Component diagrams
Usecase
Component diagrams are
used to model the
software components of a
system, their interactions,
and the relationships
between them.

33. System Design
07
Deployment Diagram
Usecase
Deployment diagrams are
used to visualize the
physical components of a
distributed system and
how they're connected.

34. Prepared by
Hailemeskel yilma
ID 1766
01 Gizework marye
0256
02
Mulat asmare
130/11
03

35. Thank you for your attention