Interface subsystem for e- job portal

The interface subsystem is primarily responsible for interaction with other

subsystems. End
users and other systems use it to interact with the system. It consists of the following
classes:
 Job management subsystem Interface – this interface enables users to
interact with the Job Management subsystem
 User management subsystem Interface – this interface enables users to
interact
with the User management subsystem.
 Notification subsystem Interface – this interface enables users to
interact with the
Notification subsystem.
 Payment subsystem interface -  this interface enables users to interact
with the
payment subsystem.

The Job management subsystem

This subsystem is in charge of managing, performing operations done on a Job. It
consists of the following components:
 Job Posting: is in charge of managing, performing operations done on
the job posting process and making it available for Job-seeking
freelancers on the platform. It also provides operations on modification
of the posted job. 
 Job apply: is in charge of overseeing, performing operations done on
the job applying process. This gives operations for Job-seekers on the
platform to propose for favored work.
 Job progress tracking: It is responsible for managing job progress from
the deal made to the completion of a job. 

User management subsystem

User management subsystem deals with managing users i.e. creating, reading,
updating, and deleting users. All subsystems depend on this subsystem as it contains
the authentication component in it. Job Management subsystem gets its job from the
job management subsystem but it needs for which user. So every subsystem depends
on this subsystem.

Data storage subsystem

All the persistent data is stored in the data storage subsystem. It contains the database
for the jobs and for the users. Therefore the user management subsystem and job
management subsystem do CRUD operations from the data storage subsystem.

Payment subsystem

The payment subsystem connects to payment service providers by using service

providers API.

Payment Management: It is responsible for making payment, canceling payment,

editing payment details and checking whether a payment is accepted by the receiver
or not.

Notification subsystem

This subsystem is in charge of informing the appropriate user when a specific action
is performed.

 Notification Management:It's  responsible for presenting various types of

notifications dependent on the user's actions.

Component Diagram 
A component diagram breaks down the actual system under development into various
high levels of functionality. Each component is responsible for one clear aim within
the entire system and only interacts with other essential elements on a need-to-know
basis.