Data Flow Diagrams
A graphical tool used to describe and analyze the moment of data through a system manual
or automated including the process, stores of data, and delays in the system. Data Flow Diagrams
are the central tool and the basis from which other components are developed.
The
transformation of data from input to output, through processes, may be described logically and
independently of the physical components associated with the system. The DFD is also know as
a data flow graph or a bubble chart.
DFDs are the model of the proposed system. They clearly should show the requirements on
which the new system should be built. Later during design activity this is taken as the basis for
drawing the system’s structure charts. The Basic Notation used to create a DFD’s are as follows:
1. Dataflow: Data move in a specific direction from an origin to a destination.
2. Process: People, procedures, or devices that use or produce (Transform) Data. The physical
component is not identified.
3. Source: External sources or destination of data, which may be People, programs,
organizations or other entities.
4. Data Store: Here data are stored or referenced by a process in the System.
Context Level Data Flow Diagrams
Admin
Data Input Stage
Data Output Stage
database
Employers
categories
news
Employer
Data Output Stage
UI Screens
Data Output Stage
Reports
Data Input Stage
emails
companies
Job opens
Job seeker
Data Input Stage
Sample
resumes
faqs
Virtual Job Fair
System Process
Authentication Data Flow Diagram:
UI Interface
Username,Password
Authentication Server
Authentication Server
Authentication
UI Interface
NO
Admin Level1 Data Flow Diagram:
Register
Employer
s
ViewEmpl
oyers
Post Faqs
View
Faqs
Admin
Login
Post
Sample
Resumes
UI Content to
Operation
View
Sample
Resumes
General
Informatio
n
View Job
seekers
Send
Emails
View
Emails
Employer Level1 Data Flow Diagram:
Register
Compani
es
View
Companie
s
Post jobs
based on
category
View
jobs
Employer
Login
View
applied
job
seekers
UI Content to
Operation
Give
status to
applied
jobs
General
Informatio
n
View
profile
Send
Emails
View
Emails
Jobseeker Level1 Data Flow Diagram:
View
Faqs
View
Companie
s
View
Sample
resumes
View
jobs
Login
Jobseeker
UI Content to
Operation
Apply for
a job
View
status of
job
General
Informatio
n
View
profile
Send
Emails
View
Emails
Level 2 Data Flow Diagram:
Admin:
Admin
Input State
Employers
Output State
Data Store
Input State
Sample
resumes
Output State
Data Store
Employer
Input State
Companie
s
Output State
Data Store
Employer
Input State
Job
openings
Output State
Data Store
Input State
Job
openings
Output State
Data Store
Input State
Post
sample
resumes
Output State
Data Store
Input State
Register
Employers
Output State
Data Store
Admin
Employer:
Jobseeker:
Jobseeker
Level 3 Data Flow Diagrams
Admin:
Admin
Employers:
Employer
Jobseeker:
Jobseeker
Input State
Apply for
Job
openings
Output State
Data Store
E-R Diagram
UML Diagrams
(Unified Modeling Language)
The Unified Modeling Language allows the software engineer to express an analysis model
using the modeling notation that is governed by a set of syntactic semantic and pragmatic rules.
A UML system is represented using five different views that describe the system from distinctly
different perspective. Each view is defined by a set of diagram, which is as follows.

User Model View:
i.
This view represents the system from the users perspective.
ii.
The analysis representation describes a usage scenario from the end-users
perspective.


Structural model view:
i.
In this model the data and functionality are arrived from inside the system.
ii.
This model view models the static structures.
Behavioral Model View:
It represents the dynamic of behavioral as parts of the system, depicting the
interactions of collection between various structural elements described in the user
model and structural model view.

Implementation Model View:
In this the structural and behavioral as parts of the system are represented as they are
to be built.

Environmental Model View:
In this the structural and behavioral aspects of the environment in which the system
is to be implemented are represented.

UML is specifically constructed through two different domains they are:
i.
UML Analysis modeling, this focuses on the user model and structural model
views of the system.
ii.
UML
design
modeling,
which
focuses
on
the
behavioral
modeling,
implementation modeling and environmental model views.

Use case Diagrams represent the functionality of the system from a user’s point of view.
Use cases are used during requirements elicitation and analysis to represent the
functionality of the system. Use cases focus on the behavior of the system from external
point of view.

Actors are external entities that interact with the system. Examples of actors include users
like administrator, Employer, job seeker…etc., or another system like central database.
Class Collaboration Diagram
Use Case Diagrams
System Use Case Diagram:
SYSTEM
Admin
Employers
Job seekers
"Data store" used by
Employers and JOB
Seekers
Admin:
Employer:
Job Seeker:
Sequence Diagrams
Admin:
Admin
Employers
FAQs
News
Categories
1 : Register Employers()
2 : View Employers()
3 : Post FAQs()
4 : View FAQs()
5 : Post News()
6 : view News()
7 : Register Categories()
8 : view Categories()
9 : Post Sample Resumes()
10 : View Sample Resumes()
11 : View Companies()
12 : View Job Openings()
13 : View Job Seekers()
Sample Resumes
Companies
Job openings
jobseekers
Employer:
Employer
Comapnies
News
Companies
1 : Register Companies()
2 : View Companies and post opening jobs()
3 : view News()
4 : View all Companies()
5 : View Job Openings()
6 : View Job Seekers()
7 : View Job Seeker Applied jobs()
Job openings
jobseekers
job Applicants
Job Seeker:
Jobseeker
Comapnies
FAQs
News
Sample Resumes
1 : View Companies()
2 : View FAQs()
3 : view News()
4 : View Sample Resumes()
5 : View Companies by Catefgory()
6 : View Job Openings and apply for job()
7 : View Job Seekers()
Companies
Job openings
jobseekers
Collaboration Diagrams
Admin:
Categories
News
6 : view News()
8 : view Categories()
9 : Post Sample Resumes()
5 : Post News()
FAQs
Sample Resumes
7 : Register Categories()
10 : View Sample Resumes()
1 : Register Employers()
4 : View FAQs()
Employers
Admin
3 : Post FAQs()
2 : View Employers()
11 : View Companies()
13 : View Job Seekers()
12 : View Job Openings()
jobseekers
Companies
Job openings
Employer:
News
Comapnies
1 : Register Companies()
3 : view News()
4 : View all Companies()
Companies
2 : View Companies and post opening jobs()
Employer 7 : View Job Seeker Applied jobs() job Applicants
6 : View Job Seekers()
5 : View Job Openings()
Job openings
jobseekers
Job Seeker:
News
Categories
Sample Resumes
3 : view News()
FAQs
4 : View Sample Resumes()
2 : View FAQs()
Jobseeker
1 : View Companies()
5 : View Companies by Catefgory()
7 : View Job Seekers()
Companies
6 : View Job Openings and apply for job()
jobseekers
Job openings
Comapnies
Activity Diagrams
Admin Activity Diagram:
Admin
Login
Failure
Success
Employers
News
Post news
Categories
Register Categories
FAQs
Post FAQs
Sample Resumes
Job Seekers
Companies
Post sample Resumes
Register Employers
View Employers
View News
View Categories
View FAQs
View Sample Resumes
View Job seekers
View Companies
Employer Activity Diagram:
Employer
Login
Failure
Success
Employers
News
Categories
FAQs
Job Seekers
Sample Resumes
Companies
Register Companies
View FAQs
View Employers
View News
View Categories
View Job seekers
View Sample Resumes
view applied jobs
View Companies and post jobs
Job Seeker Activity Diagram:
Job Seeker
Login
Failure
Success
Employers
News
Categories
FAQs
Sample Resumes
Job Seekers
Companies
Job opens
View FAQs
View Job seekers
View Employers
View News
View Categories
View Companies
View Sample Resumes
View opening jobs and apply
Component Diagram
Deployment Diagram
Architecture Diagram
Data Dictionary
UserMaster:
Column Name
Data type
Size
Userid
Number
Username
Varchar2
20
Password
Varchar2
20
Logintype
Varchar2
15
Firstname
varchar2
20
lastname
Varchar2
20
DOR
Date
DOB
Date
photo
blob
Location
varchar2
20
city
Varchar2
20
State
Varchar2
20
country
Varchar2
20
pincode
Varchar2
10
phoneno
Varchar2
10
Email
Varchar2
50
Constratints
Primary key
Sex
Varchar2
10
status
Varchar2
10
Squestion
Varchar2
30
Sanswer
Varchar2
20
Columnname
Datatype
Size
CATEGORYID
Number
CATEGORYNAME
Varchar2
20
CATEGORYDESC
Varchar2
30
Columnname
Datatype
Size
NEWSID
Number
NEWSHEADER
VARCHAR2
NEWSPOSTEDDATE
DATE
NEWSDESC
VARCHAR2
50
Columnname
Datatype
Size
RESUMEID
Number
CategoryMaster:
Constraint
Primary key
NewsMaster:
Constraint
primary key
20
SAMPLERESUMES:
Constratint
primary key
RESUMETITLE
VARCHAR2
25
RESUMEDESC
VARCHAR2
50
RESUMEDOC
blob
EMAILMASTER:
Columnname
Datatype
Size
Constratint
EMAILID
Number
SENDERID
NUMBER
20
Foreign key
RECEIVERID
NUMBER
20
Foreign key
SENDDATE
Date
20
SUBJECT
VARCHAR2
20
MAILDESC
VARCHAR2
50
Primary key
COMPANYMASTER:
Columnname
Datatype
COMPANYID
NUMBER
COMPANYNAME
VARCHAR2
COMPANYLOCATIONMAP
BLOB
COMPANYINDUSTRY
VARCHAR2
Size
Constratint
Primary key
20
25
COMPANYTYPE
Varchar2
20
COMPANYSIZE
VARCHAR2
3
COMPANYDESC
VARCHAR2
20
COMPANYLOCATION
VARCHAR2
20
COMPANYCITY
VARCHAR2
20
COMPANYSTATE
VARCHAR2
20
COMPANYCOUNTY
VARCHAR2
20
COMPANYZIP
VARCHAR2
10
COMPANYCATEGORYID
NUMBER
Foreign key
EMPLOYERID
NUMBER
Foreign key
COMPANYJOBOPENS:
Columnname
Datatype
Size
COMPANYID
NUMBER
VACANCYJOBTYPE
VARCHAR2
25
JOBCATEGORYTYPE
VARCHAR2
20
JOBVACANCIES
NUMBER
JOBUPDATED
DATE
JOBID
NUMBER
Constratint
foreign key
Primary key
JOBSEEKERAPPLYJOBS:
Columnname
Datatype
Size
Constratint
APPLYID
Number
Primary key
JOBSEEKERID
Number
Foreign key
JOBID
Number
Foreign key
APPLYDATE
Date
FAQS:
Columnname
Datatype
Size
FAQID
Number
FAQTYPE
VARCHAR2
20
FAQQUESTION
VARCHAR2
100
FAQANSWER
VARCHAR2
150
Constratint
Primary key