Online Job Enrollment for Graduating Students

ONLINE JOB ENROLMENT FOR GRADUATING STUDENTS
Submitted by
ABIYU ALEMAYEHU_____________________ 23/5/2021
Student Signature Date
ANTENEH TASSEW_____________________ 23/5/2021
BARSENET ASFAW_____________________ 23/5/2021
EMAN SULEYMAN_____________________ 23/5/2021
NAHOM DARGIE_____________________ 23/5/2021
YEABSIRA LISANEWORK________________ 23/5/2021
Approved by
1. Endale Aragu _______________________ 23/5/2021
Advisor Signature Date
Page | i
Acknowledgment
We have taken efforts in this project. However, it would not have been possible without the kind
support and help of many individuals and organizations.
We would like to extend our sincere appreciation to all of them. We are highly indebted to
Adama Science and Technology University for the opportunity it provided for us to work on this
project and explore further knowledge.
We would like to express our deepest gratitude towards our advisor Mr. Endale Aragu for his
guidance and constant supervision as well as his kind co-operation and encouragement, which
helped us in completion of this project, which is a Software Requirement Specification (SRS)
document. Our thanks and an appreciation go to all of those who have willingly supported and
helped us out with their abilities.
Page | ii
Acronym
OJESS ………………………………………Online Job Enrollment Service
ERCS ………………………………………...Ethiopian Revenue Customer’s Service
DB …………………………………………...Data Base
HTML ………………………………………. Hyper Text Markup Language
GB ……………………………………………Giga Byte
RAM …………………………………………. Random Access Memory
SQL…………………………………………...Structural Query Language
PHP……………………………………………Hypertext Processor
UML…………………………………………...Unified Modeling Language
Page | iii
Abstract
Job Employment is a relationship between two parties, usually based on contract where work is
paid for, where one party, which may be a corporation, for profit, not-for-profit organization, co-
operative or other entity is the employer and the other is the employee.[1] Employees work in
return for payment, which may be in the form of an hourly wage, by piecework or an annual
salary, depending on the type of work an employee does or which sector they are working in.
Employees in some fields or sectors may receive gratuities, bonus payment or stock options. In
some types of employment, employees may receive benefits in addition to payment. Benefits can
include health insurance, housing, disability insurance or use of a gym. Employment is typically
governed by employment laws, organization or legal contracts.
Page | iv
Table of Contents
CHAPTER ONE 1.1 Introduction........................................................................................................... 1
1.2 Background of the organization ....................................................................................................... 1
1.2.1 Mission of the organization ........................................................................................................ 1
1.2.2 Vision of the organization .......................................................................................................... 1
1.3 Background of the project ................................................................................................................ 1
1.4 Task and Schedule ............................................................................................................................. 2
1.5. Statement of the problem................................................................................................................. 2
1.6 Purpose of the project ....................................................................................................................... 2
1.7 Team Composition ............................................................................................................................ 3
1.8 Objective of the project ..................................................................................................................... 3
1.8.1 General objective ........................................................................................................................ 3
1.8.2 specific objective ......................................................................................................................... 3
1.9 Feasibility study ................................................................................................................................. 4
1.9.1 Technical feasibility .................................................................................................................... 4
1.9.2 Operational feasibility ................................................................................................................ 4
1.9.3 Economical feasibility ................................................................................................................. 4
1.10 Scope and limitation ........................................................................................................................ 4
1.10.1 Scope of the study ..................................................................................................................... 4
1.10.2 Limitation of the project ........................................................................................................ 4
1.12. Beneficiaries of the project ............................................................................................................ 5
1.13 Methodology .................................................................................................................................... 5
1.14. Development tools........................................................................................................................... 6
1.15 Test plan ........................................................................................................................................... 7
1.15.1 Unit Testing ............................................................................................................................... 7
1.15.2. Integration testing.................................................................................................................... 8
1.15.3. System testing ........................................................................................................................... 8
1.15.4. Acceptance Testing .................................................................................................................. 8
1.16 Project execution phase................................................................................................................... 8
1.17 Required Resource with Cost ....................................................................................................... 10
CHAPTER TWO ...................................................................................................................................... 11
2. Description of Existing System ......................................................................................................... 11
2.1. Major function of existing system ................................................................................................. 11
2.2. Users of current system .................................................................................................................. 11
Page | v
2.3 Draw back of current system. ........................................................................................................ 12

2.4 Business rule .................................................................................................................................... 12
CHAPTER THREE .................................................................................................................................. 13
3. 1 Overview ......................................................................................................................................... 13
3.2 Functional requirement .................................................................................................................. 13
3.3 Non-functional requirement ........................................................................................................... 13
3.4. System model .................................................................................................................................. 14
3.4.1 Scenario ..................................................................................................................................... 14
3.4.2. Use case model.......................................................................................................................... 19
3.5. Object model ................................................................................................................................... 24
3.5.1 Data Dictionary ......................................................................................................................... 24
3.5.2 Class diagram ............................................................................................................................ 25
3.6 Dynamic Model ................................................................................................................................ 27
3.6.1 Sequence diagram ..................................................................................................................... 27
3.6.2. Activity diagram ...................................................................................................................... 36
3.6.3 State chart diagram .................................................................................................................. 43
Chapter 4 ................................................................................................................................................... 46
4. System design ........................................................................................................................................ 46
4.1. Overview of system design ............................................................................................................. 46
4.1.1. Purpose of the system design .................................................................................................. 46
4.1.2 Design goal................................................................................................................................. 46
4.2 Proposed system architecture......................................................................................................... 47
4.2.1 System process .......................................................................................................................... 49
4.2.2 Subsystem Decomposition ........................................................................................................ 51
4.2.3. Hardware/ software mapping ................................................................................................. 52
4.2.4. Persistent data management ................................................................................................... 53
4.2.6. Deployment diagram ............................................................................................................... 58
4.2.7 Database design......................................................................................................................... 58
4.2.8. Access control ........................................................................................................................... 59
4.2.9 User interface design ................................................................................................................ 60
Reference ................................................................................................................................................... 61
Page | vi
LIST OF FIGURE
Figure 1 use case diagram ............................................................................................................... 21
Figure 2 class diagram .................................................................................................................... 26
Figure 3 sequence diagram for student insert personal project ....................................................... 27
Figure 4 sequence diagram for company view message ................................................................... 28
Figure 5 sequence diagram for lecture insert course project ........................................................... 29
Figure 6 sequence diagram for company send message ................................................................... 30
Figure 7 sequence diagram for student change account .................................................................. 31
Figure 8 sequence diagram for club inset project ............................................................................ 32
Figure 9 sequence diagram for Student make preference ............................................................... 34
Figure 10 sequence diagram for club registration ........................................................................... 35
Figure 11 Activity diagram for Login ............................................................................................. 36
Figure 12 Activity diagram for Insert course project ...................................................................... 37
Figure 13 Activity diagram for Edit Account .................................................................................. 38
Figure 14 Activity diagram for View message ................................................................................. 39
Figure 15 Activity diagram for Company sort ................................................................................ 40
Figure 16 Activity diagram for Send message ................................................................................. 41
Figure 17 Activity diagram for project registration ........................................................................ 42
Figure 18 State chart diagram for login .......................................................................................... 43
Figure 19 State chart diagram for insert personal profile ............................................................... 44
Figure 20 State chart diagram for update contact information ....................................................... 44
Figure 21 State chart diagram for Reply message ........................................................................... 45
Figure 22 system architecture ......................................................................................................... 48
Figure 23 System activity diagram .................................................................................................. 49
Figure 24 overall ASTU online job enrollment ................................................................................ 49
Figure 25 System Process ................................................................................................................ 50
Figure 26 Subsystem decomposition ............................................................................................... 51
Figure 27 hardware software mapping ........................................................................................... 52
Figure 28 class to relational database mapping ............................................................................... 53
Figure 29 student mapping ............................................................................................................. 53
Figure 30 Club mapping ................................................................................................................. 54
Figure 31 project mapping .............................................................................................................. 54
Figure 32 company mapping........................................................................................................... 55
Figure 33 teachers mapping ............................................................................................................ 55
Figure 34 eligibility mapping .......................................................................................................... 56
Figure 35 Activity mapping ............................................................................................................ 56
Figure 36 component diagram ........................................................................................................ 57
Figure 37 deployment diagram ....................................................................................................... 58
Figure 38 database design ............................................................................................................... 58
Figure 39 User interface.................................................................................................................. 60
Page | vii
Table of list
Table 1 Task and schedule ........................................................................................................... 2
Table 2Team composition ............................................................................................................ 3
Table 3 front end implementation software tool ........................................................................ 6
Table 4 backend implementation software tools ........................................................................ 6
Table 5 other software tools ......................................................................................................... 6
Table 6 project execution phase................................................................................................... 9
Table 7 required resource and cost ........................................................................................... 10
Table 8 use case diagram description for login ........................................................................ 21
Table 9 use case diagram description for manage Account .................................................... 23
Table 10 use case diagram description for send message ........................................................ 22
Table 11 use case diagram description for change account type ............................................ 22
Table 12 use case diagram description for filling form ........................................................... 23
Table 13 use case diagram description for preference ............................................................ 23
Table 14 data dictionary ............................................................................................................. 25
Table 15 subsystem description ................................................................................................. 51
Table 16 access control ............................................................................................................... 59
Page | viii
CHAPTER ONE 1.1 Introduction

Our project works on employment service for a graduated student. the project works for
graduated student who has registered grade evaluation on system .Project works mainly for
students who has qualified projects or ideas or knowhow for that specific field .it reduce the
employment service based on GPA, relatives, ethnics, sex, and so on. This project is selected
because of very less employment service for our country, and hard to find job opportunities
without differentiate or discriminations. Our system uses Astu’s e-student as our database where
as our system contains department, CGPA, skill, certificates, team participations. Any company
who has a vacancy can get qualified student based on its own restriction. in the older system the
companies would not get the effective employee for that job because of this companies could not
grow efficiently, so this software will allow the companies to choose the right employee.
1.2 Background of the organization
As we all know, Ethiopia is one of the populous countries in Africa. Unemployment rates in
Ethiopia are highest for the age group 20-24 years old (25% in 2018) and highest for urban
young women (31% in 2018).
The labour market in Ethiopia is experiencing a strong demographic pressure as every year there
are more than 2 million youth entering the labour force. On the other hand, Companies in
Ethiopia face difficulties in finding employees with the right skill and experience. Therefore, not
only new jobs must be created but also a better match between education and job market.
1.2.1 Mission of the organization
Ensuring the highest satisfaction by being the bridge that connects graduating students to the
company they dream to work for. Also, based on the requirements the company sets, the system
provides qualified students for the job.
1.2.2 Vision of the organization
To become the most chosen way of job enrolment techniques and to reduce or eradicate the
number of unemployment in Ethiopia.
1.3 Background of the project
Even though there is already a similar software as our student profiling system: like ethio jobs,
which posts available jobs alongside the country on their site our software is a bit similar to
theirs. now a days the knowledge of computer is spreading so, It is important that the
introductory documentation and style of implementation should not make profiling seem like
“hard work”, and it is important that the value of profiling should quickly become self-evident to
those who are involved in it. This will depend on
(a) being able to demonstrate that profiling has been well researched and tested and
b) being able to accommodate the needs of both staff and students in the profiling procedure. The
keys to success in implementing and embedding the procedure will be its ease of use and its
visible effectiveness.
Page | 1
1.4 Task and Schedule

9 months is the period we ought to finish our project and provide a functional system.
Months
Jan 1 Mar 3 May 20 Jul 2 Aug 16
Phases
- - - - -
Mar 1 April 18 Jul 1 Aug 15 Sep 21
Requirement
gathering and
Analysis
Design
Implementation
Testing
Maintainance
T ABLE 1 T ASK AND SCHEDULE
1.5. Statement of the problem
The current job hunt is manually done due to this there are some problems raised due to the
manual job hunt like: -
• System is dependent on CGPA.
• Filtering is difficult.
• It takes more effort and physical space to keep track of paper documents, to find
information and to keep details secure.
• Lack of security and Transparency
• Duplication of data entry
• Time consuming and costly
• Inconsistency in data entry, room for errors, mistaken information
1.6 Purpose of the project

The main purpose of this project is work with prospective students and others involved in the
college selection process and collaborate with many colleagues to facilitate aspects of the
recruitment and enrolment process by include outreach activities to target companies and
individual prospective engagement. Ensuring the enrolment of new students and accountable for
his/her performance and achievement of enrolment goals including strong detail orientation with
good personal planning based on CGPA. Develop strategies to increase enrolment and special
projects and other duties as assigned.
Page | 2
1.7 Team Composition

Title Online Job Enrollment for Graduating Students
Name Email Roll
Anteneh Tassew Antenehtassew2005@yahoo.com Analysis, Design,
Implementation
Team Abiyu Alemayehu AbiyuAlemayeu2006@yahoo.com Design, Testing,
composition Implementation
Barsenet Asfaw barasfaw20@yahoo.com Gather information,
Implementation, Design
Eman Suleyman Emansuleyman2008@yahoo.com Design, Testing,
Requirement gathering
Yeabsera yabilisanu@gmail.com Analysis, implementation,

Lisanework Testing
Nahom Dargie Nahomdargie2010@yahoo.com Coordinator, Analysis,
Design
Advisor Ins: Endale Aragu
T ABLE 2TEAM COMPOSITION
1.8 Objective of the project

1.8.1 General objective
The general objective of this project is to develop system which gives an opportunity of a job for
graduated skillful student and qualified student for exam based on company’s eligibility.
1.8.2 specific objective
In order to achieve the main objective, we have developed the following specific objective
1.studying about problem of the existing system of employment service
2.Gathering required information for prosed system or manual employment service
3.Analyzing the gathered information
4.considering applicability the system for fulfillment of customers wants
5.designing the proposed system.
6.implementation the system.
7.testing the system.
Page | 3
1.9 Feasibility study

Is an analysis that takes all the project relevant factors into account- including economical,
technical and operational. So as to complete the project successfully or to make sure the project
is worth making.
1.9.1 Technical feasibility
People working on the project are expected to make it technically feasible. While doing this
project the team has studied the required methodologies and tools, so this makes it technically
feasible. The team can convert the ideas into working systems. The team also evaluated
hardware, software, and other technical requirement of the proposed system. In general, using all
these techniques, the team ensures to perform the work up to the desire of the organization.
1.9.2 Operational feasibility
The proposed system solves the problems of unemployment well and it also has an incredibly
good impact on users (both students and companies). We studied carefully about how the
existing system works and we upgraded the system with this new project since it is web-based
and compatible in any web browser. To sum it up, these factors tell us that the project is
operationally feasible.
1.9.3 Economical feasibility
This step shows the cost-effectiveness of this project.
• Financial benefits – the system our team develop reduce cost.
• Business process profits.
1.10 Scope and limitation

1.10.1 Scope of the study
The scope of the current software, “Online Job Enrollment System” includes register students,
notifying graduated students when there is available job, allows companies to filter students by
grades, place of residence, by gender and the system includes all student club participation and it
allows the teachers to add course projects. This allows the companies to search for whomever
they want, because it shows every information about all the students available in the database.
1.10.2 Limitation of the project

The limitations and pitfalls of such systems are their online presence. High security is needed to
protect especially not to mention the other contact details of students. Personal information
protection is a serious responsibility and heavily punishable by the law.
1.11. Significance of the project
• It allows companies to get an employee easily.
• It decreases a lot of paperwork.
• It consumes the time require to get a job.
• Graduated students do not need to apply for a job.
Page | 4
1.12. Beneficiaries of the project

This system benefits graduated students and companies that want to higher an employee.
1.13 Methodology
Data collection methodology
We have used the following data collection method.
a. Interview: We have made an interview with head of Adama science and Technology
University to get an overview of enroll graduating student the system.
b. Observation: The online systems are not secured and there is a lack of online systems that
enroll graduating students.
c. Document analysis: We have analyzed document of enrolment of graduating student per year
that shows the overview of the existing system.
System analysis and system design methodology
In this project the team will use PHP over other language to develop our system.
PHP built support for working hand in hand with MYSQL; this does not mean we cannot use
PHP with other database management systems.
We use PHP as cross plat form which means we can deploy our application on a few different
operating system such as windows, Linux, Mac OS etc.
Deployment/ implementation methodology
Implementation is coding of all functions specified by requirements and specification analysis.
we will use server-side scripting language; to install it on the client computer requesting for the
resources from the server, do not have PHP installed; only a web browser would be enough.
System development methodology
Since the system requirement is clearly defined and fixed, we will use V shape model for the
system development specially referred up on reliable system. I.e., Describing form project and
requirement planning till coding and testing the product with phase of development.
Here we mentioned reason why we are chosen V shape model.
• Simple and easy to use.
• Testing activities like planning, test designing (verification and validation) happens well
before coding. This saves a lot of time. Hence the higher chance of success over the
waterfall model.
• Proactive defect tracking – that is defects are found at early stage.
• Avoids the downward flow of the defects.
• Works well for small projects where requirements are easily understood.
Page | 5
1.14. Development tools

While developing the project starts from each phase of documentation to the end, we will use
the following tools.
Hardware:
• Computers
• Flash
• Mobile Phone
Software tools
Tools Abbreviation Use
Hypertext markup language Html4/html5 For configuration
Cascading style sheet Css/css3 For layout design content
decoration in user interface
design and to give the style of
the interface
Java Script/Jquery Js For validating client-side

monitoring language
TABLE 3 FRONT END IMPLEMENTATION SOFTWARE TOOL
Tools Abbreviation and version Used for

Hypertext preprocessor Php5.6 Backend implementation of
the project
MySQL server MySQL 5.6 For database
Wamp,xamp server To run the project
T ABLE 4 BACKEND IMPLEMENTATION SOFTWARE TOOLS
Others
Tools Use
Enterprise Architects Designing the project
MS Word Documentation
Google Docs For project tracking
Telegram For Group meetings
Notepad++ Used for editing the source code
Lucid chart For Drawing Diagrams
SQL server For creating the database
Browser To open system
TABLE 5 OTHER SOFTWARE TOOLS
Page | 6
1.15 Test plan

Testing is the prosses of executing the program with intention of finding errors. A test plan is a
document that outlines what, when, how, who, and more of the project. This detailed document
specifies the project background information, resources, schedule & timeline, entry and exit
criteria, tests to be performed, and the resources required for completing that project.
1.15.1 Unit Testing
How Developers Test Their Own Code? write Unit tests to improve code quality by verifying
every unit of the code used to implement functional requirements “Unit Testing is the method of
verifying the smallest piece of testable code against its purpose.” If the purpose or requirement
failed, then the unit test has failed. In Unit testing, developers use manual or automated tests to
ensure that each unit in the software meets the customer’s requirement.
Techniques Within Unit Testing
1) White box testing:
In white box testing, the tester knows the internal structure of the software including the code
and can test it against the design and the requirements. Hence white box testing is also known
as transparent testing. We use this technique for the following reason.
• It is easy to find out which type of input data can help in testing the application
effectively.
• To optimize the code
• It helps in removing the extra lines of the code which can bring hidden defects.
• Early detection of errors during software development
2) black box testing
Page | 7
In black box testing, the tester does not know the internal structures either the code of the
software. In this technique we will taste to see if the function of the system is fully operational or
error free. That is testing the interface of the system rather than logical structure of the system.
we used this testing for the following reason:
• more effective on larger unit of code
• tester needs no knowledge of implementation, including specific programing language.
• tester and programmer are independent each other.
• test is done from the user’s point of view.
1.15.2. Integration testing

In these strategies the group member will focuses on testing the design and construction of the
software architecture. To do the two techniques of integration testing will considered.
• Top –Down integration testing
This will perform starting from the top module up to the last or bottom module individually (tests
were run as each individual module is integrated).
• Bottom-up integration
We will begin with the lowest –level modules which are combined to cluster or build that
perform a specific software sub-function (top-level).
• Big-Bang Integration Testing
It is the simplest integration testing approach, where all the modules are combining.
1.15.3. System testing
After all of the above testing is checked then we will test our system by other peoples and we
will conduct some comments how they get our system.
1.15.4. Acceptance Testing
This testing is done by the customer to ensure that the delivered product meets the requirements
and works as the customer expected. It includes: -
Alpha- Conducted by users to ensure they accept the system.
Beta- Users use real data, not test data.
1.16 Project execution phase
It involves carrying out the details of our project charter in order to deliver our service to our
clients.
Page | 8
Roll no Phase Required Required Function

time tools
1 Data collection and March 13 Pen Collecting and
gathering - Paper gathering
March 15 Computer information about
Mobile how the existing
phone system works and
Cable how we could
Flash improve it to satisfy
Microsoft the users
word
2 Requirement elicitation and March 16 Pen Identify the
analysis - Paper requirements and
March 19 Computer research and
Mobile discover the
phone requirements of a
Flash system from users
Microsoft (elicitation).
word Analyse, validate
PHP and understand the
requirement
(analysis).
3 Design March 20 SQL server This stage requires

- Pen transforming the
March 24 Paper above requirements
Computer into an
Mobile implementation
phone form
Flash
4 CRUD (create, read update March 25 Editors Used to create,

,delete) - Microsoft read, update and
Operation March 26 word delete records from
Servers a database.
5 Coding and implementation March 27 SQL server This is the phase
- Flash where we code with
March 29 Php the programing
Html language
xaamp
6 Testing March 30 Computers Look for errors if

Browsers there is any
T ABLE 6 PROJECT EXECUTION PHASE
Page | 9
1.17 Required Resource with Cost

Material name No. Material Price Total
Paper Half packet 1 100
Pen 5 10 60
Laptop 3
Flash& GB 2
Print
Binding
Coffee and tea
Total cost of 160
material
T ABLE 7 REQUIRED RESOURCE AND COST
Page | 10
CHAPTER TWO
2. Description of Existing System
The old system requires a face-to-face meeting between the companies and the graduated
students, this system is not efficient because the company could not get the perfect employee
rather the company will choose the better among the students who applied for a job. In order to
get a job. A student must apply to work for that company, which makes it so boring because a
student has to read every employee finder boards.
2.1. Major function of existing system
The major function of the existing system of project management comprises the following:
• Monitor enrolment.
• Monitor personal info.
• Provide the required job.
• Control job enrolment process.
• Reduce the time and cost.
• Ensuring a data security.
2.2. Users of current system

The number of people involved in a hiring team is unique to each organization. However, most
hiring teams include the following role:
Recruiter: recruiters oversee the end-to-end process of talent acquisition for a company. Some of
a recruiter’s key responsibilities within the hiring team include:
• Meeting with the hiring manager
• Attracting and sourcing (recruitment marketing) desirable applicants; prescreening
candidates, and presenting qualified applicants to the hiring manager.
• Serving as the main point of contact for all parties throughout the hiring process
• Conducting reference checks, background checks and the job offer management process
• Ensuring an exceptional candidate experience
• Facilitating employee on boarding to ensure the new hire is prepared to begin the new
position on day one.
Interviewers: The size and roles within an interview team vary based on the size of an
organization, the level of the position being filled, and other factors. The interview team can
include the hiring manager, relevant supervisors and managers, key internal customers or
stakeholders, and important potential colleagues.
Recruiting coordinators perform a vital support role to recruiters throughout the hiring process.
Recruiting coordinators help with various tasks including posting positions to job boards,
scheduling interviews, assisting with coordinating candidate travel (if needed), creating offer
letters and running background checks.
Applicant: Given the number of people included in the hiring team, you’ll likely interact with
several members of the team individually, and also interface with the entire team.
Page | 11
2.3 Draw back of current system.

The employment service for graduated student is very less because of
• The system to link those companies have vacancy for employment service and qualified
person for that job since the system is manual and not handled by the government.
• The loyalty of the previous system questionable, there is discrimination based on ethics,
Gender, relatives, speeches and they have an abuse.
• There is wastage of time for gating preferable person for that specific work. Because of
this the productivity of job, profit of companies will reduce. And have a shortage of
gating information on employment service for students.
2.4 Business rule

It describes the operations, definitions and constraints that apply to an organization.
• User must be authenticated to access the developed system
• User who is not registered is not allowed to perform any activity regarding this system.
• Requirements of the company must be set before any graduating student apply for a job.
• Student is the only user who is allowed to manage his/her account.
Page | 12
CHAPTER THREE
3. 1 Overview
This new system will replace the existing (the old) system by making all features computerized
and effective because the system will notify you when you are chosen for a particular job, this
makes the job finding and employee finding process easier for both graduating students and for
the companies. The system uses all university’s student’s databases to create an effective and very
applicable. Software, which reduces a lot of cost, time and paperwork. Once a company decides
to higher an employee the owner or the company’s manager can go to the software and search for
what the company wants. The software will post students sequentially by the sorting option (by
grade, by place of residence, by club participation) that the company wants. This is a better
software when we compare to the old system because since the owner of this software would be
MINISTRY OF EDUCATION it will decrease nepotism and unemployment rate and it make it
easier for doing a research on unemployment.
3.2 Functional requirement
1. Manage account.
2. Register personal profile
3. Upload project on the system
4. Register status (add, delete, update)
5. View notification.
6. Register employment (active, deactivate)
7. Qualification of project
8. Record Employment rate.
3.3 Non-functional requirement
It is a requirement that is not necessarily essential for the system but it gives more quality and
additional attributes to the system.
• Usability
• Recoverability
• Serviceability
• Manageability
• Security
• Capacity
Page | 13
• Availability
• Data integrity
• User interface requirement
• Should be attractive and user friendly.
• Authentication requirement
• Username and password should be authentic.
• Reliability
• Software and hardware consideration
3.4. System model

Used to construct an abstraction of a system that focuses on interesting aspects and ignores
irrelevant details. Our system includes three types of system model.
Those are: -
1. Functional model (scenario, use case model)
2. Object model (class diagram)
3. Dynamic model (sequence, activity and state chart diagrams).
3.4.1 Scenario
Scenarios are real-life examples of how a system can be used. It should include: the scenario
name, the normal flow of events, what can go wrong and how this is handled, Information about
other concurrent activities, a description of the state when the scenario finishes.
1. Name of scenario: manage account
Participating actors: student
Flow event:
• student open and login to the system.

• user select manage account tab.
• The form is displayed to the student page.
• the detail displayed at this page with edit tab.
• He/she selects edit tab.
• He/she select edit profile tab.
• He/she hover over his profile and click update button .
• The system displays successful message
• He/she selects change password tab.
Page | 14
• User enter current password.

• User enter new password and click update button.
• System display successful message.
Exceptional flow: if he/she enters wrong data, the system displays a message to enter correct
data.
2. Name of scenario: Login

Participating actor: - all users
Flow event: -
• The user opens the system.

• The login form is displayed to the user.
• The user enters a valid username and password.
• The user clicks the login button.
• The user display user page.
Exceptional flow:-
a. If the user does not fill the correct username and password, the system notifies to enter
Correct username and password.
b. The system does not work when the connection is not available
3. Name of scenario: insert personal project

Participating actor: student
Flow of events:-
• user open and login to the system

• student hover over project and select submit personal project.
• Submit project form is displayed.
• Student attach their personal project to the form.
• Click attach project
Exceptional flow: - system doesn’t work if connection is not available.
4. Name of scenario: send message
Participating actor: company
Flow of events:
• User opens and login to the system
Page | 15
• User selects send message tab
• Send message tab is displayed
• User writes his/her message on the free text
• User clicks send message button.
Exceptional flow:
•
The system doesn’t work when network connection is unavailable
•
The user enters wrong information on the send message tab, he had to re
send a new one again.
5. Name of scenario: filling form
Participating actor: - company
Flow of events: -
• Company opens and login to the system

• Company selects fill form tab.
• A new form page is displayed.
• The form displayed in this page with required number of students, project title,
cgpa range, club participation and attendance result tab.
• Company attaches its requirement to the form.
• Click attach button
• Exceptional flow: -
• System don’t work if network connection is unavailable
• If user doesn’t enter the correct information, the system asks it to enter the
correct data.
6.Name of scenario: choose students

Participating actor: - company
Flow of events: -
• company selects student tab

• Student form is displayed
• Company clicks on student who fulfil the criteria of the company
• Company clicks choose student button
• System displays successful message.
• Exceptional flow: -System doesn’t work when network is unavailable
Page | 16
• If the company doesn’t enter the correct information, the system

asks him/her to enter the correct data.
7. Name of scenario: logout

Participating actor: all users
Flow of events: -
• The user opens and login into the system
• The user tap manages accounts
• The user chooses its account
• The user clicks the logout button
Exceptional flow: - the system only works when network connection is available
8.Name of scenario: preference
Participating actor: student

Flow of events:-
• Student opens and log into the system.
• Student click job offer tab.
• Job offer form is displayed.
• Student click accept if it’s the job he/she is looking for
• Student click decline if it’s not the job he /she is looking for
Exceptional flow:-
• The system don’t work if network connection is unavailable

9.Name of scenario: insert course project
Participating actors: teacher
Flow of events:
• Teacher select student tab.

• Student tab is displayed.
• Teacher hover over students project and select submit course project.
• Submit project form is displayed.
Page | 17
• Teacher attaches course project to the form.

• Click attach course project.
Exceptional flow:-The system don’t work if network connection is unavailable
10.Name of scenario: change account type
Participating actor: student and company
Flow of events:
• User opens and login to the system.

• User selects manage account tab
• User selects deactivate tab/ if he/she wants to deactivate his/her account.
• User selects reactivate tab/ if he/she wants to reactivate his/her account.
Exceptional flow: -The system don’t work if network connection is unavailable.
11.Name of scenario: insert team activities.
Participating actor: clubs
Flow of events:
• User opens and login to the system.

• Club select student tab.
• Student tab is displayed.
• Club hover over student team activities and select submit team activities.
• Submit team activities form is displayed.
• Club attaches student team activities to the form.
• Club click submit team activities.
Exceptional flow:-
• System doesn’t work when network is unavailable
• If the company doesn’t enter the correct information, the system asks him/her
to enter the correct data.
12.Name of scenario: registration
Participating actors: clubs
Flow of events:
Page | 18
• User click on registration form.

• Registration form is displayed.
• the detail display with username , password, email id.
• User click on register.
• System display successful message.
Exceptional flow:-The system don’t work if network connection is unavailable.
3.4.2. Use case model.

A. actor identification
• login
• Manage account
• Insert personal project
• Receive message
• Accept preference
• Change account type
• logout
• login
• Insert course project
• logout
Page | 19
• login
• Change account type
• Fill form
• Choose student
• Send message
• logout
• register
• Login
• Insert team activities
• logout
B. Use case identification.

➢ Registration
➢ Login
➢ Insert personal project
➢ Manage account
➢ Change account type
➢ Insert course project
➢ Filling form
➢ Choose a student
➢ Insert team activities
➢ Preference
➢ Send message
➢ Logout
Page | 20
C. Use case diagram
F IGURE 1 USE CASE DIAGRAM

Use case name login
Use case id 01
Use case To authenticate user
description
Actors Students, clubs, teachers and Admin
Pre-condition Users must have username and password and internet connection is
available.
Post condition Login to the actor page/leave from page.
Main flow a. Actor open the system
b. The system display login form.
c. User fills correct username and password.
d. Click login button.
e. The system will take the user to the index page.
T ABLE 8 USE CASE DIAGRAM DESCRIPTION FOR LOGIN
Page | 21
Use case name Manage account

Use case id 02
Use case To format his/her profile
description
Actors Students
Pre-condition User first has to login.
Post condition Edit his/her profile or leave it as it is.
Main flow a. Student first has to login.
b. they have to choose from the 2 options
➢ Edit profile
➢ Change password
Table 9 use case diagram description for manage Account
Use case name Send message

Use case id 04
Use case To make a bridge b/n the admin and students
description
Actors clubs
Pre-condition Login
Post condition Sending message
Main flow If the company wants to send a message for the students
The student will first login then they will go to the view message option
then
The txt will appear then after they write the message, they will choose
the accept or decline button, after that the answer will be automatically
Sent to the companies and they will receive a notification.
TABLE 10 USE CASE DIAGRAM DESCRIPTION FOR SEND MESSAGE
Use case name Change account type

Use case id 03
Use case To change student’s account type
description
Actors Students and companies
Pre-condition Either has to login
Post condition Updating the database or register new student
Main flow The administrator will register new graduated students
After filling all the student profile, the admin will update the database
TABLE 11 USE CASE DIAGRAM DESCRIPTION FOR CHANGE ACCOUNT TYPE
Page | 22
Use case name Filling form

Use case id 05
Use case To allow the companies to search and filter students by their preference
description
Actors Companies
Pre-condition Only interest there is No pre-condition
Post condition Choose student
Main flow The company will go to the search bar and search and filter students
based on their interest
After filtering the students, the companies will choose students
Then the admin will automatically send a message for the selected
students
TABLE 12 USE CASE DIAGRAM DESCRIPTION FOR FILLING FORM
Use case name Preference

Use case id 06
Use case To give the students an option if they don’t want the job
description
Actors Students
Pre-condition Student has to be chosen
Post condition Either decline or accept the job
Main flow If A student choose the accept option then the system will notify the
Admin then the admin will deactivate the student .
TABLE 13 USE CASE DIAGRAM DESCRIPTION FOR PREFERENCE
Page | 23
3.5. Object model

3.5.1 Data Dictionary
Class Attributes Operations Description
User userId verifyLogin() Used as the
Password parent for the
loginStatus users
Student,Club
and Teacher
Student name Login() Allow Students
status updateContactInfo() to login, update
changePassword() and upload
changeAccountStatus() materials
updateContactInfo()
insertPersonalProject()
Contact Info address getAddress() Used to identify
email and contact the
phone user
Used for login
Eligible replayMessage() Describes
Student students that
satisfy the
criteria of the
company
Personal Attendance getInfo() Describes the
Profile c.gpa students
courseProject academic
clubTeamParticipation history in the
university
Club name Login() Allows clubs to
insetClubParticipation() insert the
participation of
the student in
his academic
history
Teacher department insetCourseGrade() Used to upload
insetAttendance() the data of the
insetProjects() student
Login()
Ethiopian Email checkCompanies() Used as a
revenue and Name giveTinNumber() verification
customer password registerNewCompanie() process for the
system companies
Page | 24
Database nameofCompany checkCompanies() Used to store

tinNumberofCompany giveTinNumber() the data of the
registerNewCompanie() companies
Company Name ApproveRecruitment() Allows the
Hiring tinNumber EditRecruitment() company to
Manager InsertRequirement() login to the
rejectRecruitment() system and
sendRecommendedCandidateList() search students
sendMessage()
viewCandidate()
Criteria Qualification getListofEligebleStudent() Used as a
serviceYear insertCriteria() criteria to sort
c.gpa students based
on the desire of
the company
Application hireDate isSelectedCandidate() Used to
terminationDate determine the
status of the
student
Message jobTitle sendMessage() Used as a
jobDescription replayMessage() communication
NumberofCandidate line between
the company
and the student
TABLE 14 DATA DICTIONARY
3.5.2 Class diagram
We use class diagram to describe the structure of a system by showing the system's classes, their
attributes, operations (or methods), and the relationships among objects. For designing of Class
diagram, we have used Unified Modeling Language (UML). This diagram is the main building
block of our object-oriented modeling. The team applies it for both general conceptual modeling
of the systematic of the application, and for detailed modeling translating the models into
programming code. The classes in a class diagram represent both the main objects, interactions in
the application and the classes to be programmed. In the system, Classes are abstractions that
specify the attributes and behavior of a set of objects and Objects are entities that encapsulate state
and behavior. Each object has an identity: It can be referred individually and is distinguishable
from other objects. In mapping the diagram, we have used the following criteria: One –to- One
relationship:-here when both involved entities exchange primary keys where the new exchanged
primary keys become the new foreign keys of the tables. One –to- many relationships:-here the
primary key on the many side has been mapped to the one side. Many –to- many relationships:-
here the primary key on the many side has been mapped to the many side. The association of
classes is described with diagrams as follows
Page | 25
F IGURE 2 CLASS DIAGRAM
Page | 26
3.6 Dynamic Model

3.6.1 Sequence diagram
As the name indicates, the system used sequence diagram to show sequence of activities or how
processes operate with one another and in what order. It is a construct of a Message Sequence
Chart. It shows object interactions arranged in time sequence. It depicts the objects and classes
involved in the scenario and the sequence of messages exchanged between the objects needed to
carry out the functionality of the scenario. Sequence diagrams are typically associated with use
case realizations in the Logical View of the system under development. With this diagram we
show, as parallel vertical lines (lifelines), different processes or objects that live simultaneously,
and as horizontal arrows, the messages exchanged between them, in the order in which they
occur. This allows the specification of simple runtime scenarios in graphical manner. So, the
group member lists some sequence diagrams for the system scenario are listed below.
1. Student insert personal project.
F IGURE 3 SEQUENCE DIAGRAM FOR STUDENT INSERT PERSONAL PROJECT
Page | 27
2. Company view message.
F IGURE 4 SEQUENCE DIAGRAM FOR COMPANY VIEW MESSAGE
Page | 28
3. lecture insert course project
F IGURE 5 SEQUENCE DIAGRAM FOR LECTURE INSERT COURSE PROJECT
Page | 29
4. Company send message
F IGURE 6 SEQUENCE DIAGRAM FOR COMPANY SEND MESSAGE
Page | 30
5. Student change account
F IGURE 7 SEQUENCE DIAGRAM FOR STUDENT CHANGE ACCOUNT
Page | 31
6. Club insert project
F IGURE 8 SEQUENCE DIAGRAM FOR CLUB INSET PROJECT
Page | 32
7. Student view message
Figure 9 sequence diagram for student view message
Page | 33
8. Student make preference
F IGURE 9 SEQUENCE DIAGRAM FOR S TUDENT MAKE PREFERENCE
Page | 34
9.Club registration
F IGURE 10 SEQUENCE DIAGRAM FOR CLUB REGISTRATION
Page | 35
3.6.2. Activity diagram

An activity diagram is used to understand the flow of work that an object or component
performs. It can also be used to visualize the interaction between different use cases. One of the
strengths of activity diagrams is the representation of concurrent activities. Some of the activity
diagrams of our system are listed below.
1.Login
F IGURE 11 ACTIVITY DIAGRAM FOR LOGIN
Page | 36
2.Insert course project.
F IGURE 12 ACTIVITY DIAGRAM FOR INSERT COURSE PROJECT
Page | 37
3. Edit Account
F IGURE 13 ACTIVITY DIAGRAM FOR EDIT ACCOUNT
Page | 38
4.view message
F IGURE 14 ACTIVITY DIAGRAM FOR V IEW MESSAGE
Page | 39
5.Company sort
F IGURE 15 ACTIVITY DIAGRAM FOR COMPANY SORT
Page | 40
6. Send message
F IGURE 16 ACTIVITY DIAGRAM FOR SEND MESSAGE
Page | 41
7.project registration
F IGURE 17 ACTIVITY DIAGRAM FOR PROJECT REGISTRATION
Page | 42
3.6.3 State chart diagram

It is used to describe the externally visible behavior of a system or of an individual object.
Some of the state chart diagrams of our system are described below.
1. Login
F IGURE 18 STATE CHART DIAGRAM FOR LOGIN
Page | 43
2.Insert personal profile
F IGURE 19 STATE CHART DIAGRAM FOR INSERT PERSONAL PROFILE

3.Update contact information
F IGURE 20 STATE CHART DIAGRAM FOR UPDATE CONTACT INFORMATION
Page | 44
4. Reply message
F IGURE 21 STATE CHART DIAGRAM FOR REPLY MESSAGE
Page | 45
Chapter 4
4. System design
4.1. Overview of system design

System design part of the system is the transformation of the analysis model into a system design
model. Up to now, we were in the problem domain. System design is the first part to get into the
solution domain in a software development. This chapter focuses on transforming the analysis
model into the design model that takes into account the non-functional requirements and
constraints described in the problem statement and requirement analysis sections discussed
earlier.
This document describes the design issues of the overall system, such as design goal, subsystem
decomposition, hardware/software mapping, and persistent data management. It provides the
complete architectural overview of the proposed system. It is intended to capture and express the
significant architectural decisions, which have been made, on the system.
4.1.1. Purpose of the system design

The purpose of designing is to help both designers and developers to create a stable visual
language and to contribute information efficiently and also to provide sufficient detailed data.
The objectives of design are to model the system with high quality. Implementing of high quality
system depend on the nature of design created by the designer.
Moreover, it helps the new team members to dive into the project as fast as possible and they
don’t have to spend much time understanding its structure.
Eventually, the purpose is to supplement the system architecture by providing information and
data useful and necessary for implementation of the system elements.
4.1.2 Design goal

The objectives of design are to model the system with high quality. The design goals are derived
from nonfunctional requirements that means non-functional requirement is the description of the
feature characteristics and attribute of the system as well as any constraints that may limit the
boundary of the proposed solution.
Design goals describe the qualities of the system that the developers should consider.
• Performance
• Dependability
• Maintenance
• End user
Performance
The system should respond fast with high throughput, i.e. it should perform the task quickly
as possible such as generating report and receiving, viewing project status and also
employee and material information etc. The system performs its task within a user acceptable
time and space. This includes the following:-
Page | 46
• Response time: - depending on the strength of available network the system should be
response in short period of time.
• Storage space: -to do work efficiently the processor to be more than 2GB RAM and HD
storage to be more than20MB
Dependability
Our system includes the following dependability criterion’s: -
• Reliability: - ASTU Online Job Enrollment system should be reliable.
• Fault Tolerance: - ASTU Online Job Enrollment should be fault tolerant to loss of
connectivity with the service.
• Security: - ASTU Online Job Enrollment should be secured, i.e., not allow other users or
unauthorized users to access data that has no the right to access it.
• Availability: - as long as there is an internet connection and no system failure the system
will be available 24 hours a day.
Maintainability
To be maintainable the system should meet the following maintenance criteria: -
• Modifiable: ASTU Online Job Enrollment system should be modifiable for further
modification and enhancement of the system.
• Portability: - the system is developed to be viewed and retrieved from any web browser
regardless of their version and platform it resides in it.
• Extensible: - if it is needed to add new functionality to the system, this must be achieved
by only making a separate page and integrate this page with the existing system.
• Readability: - the system code can be viewed by clicking on the current web page and
choose “view the source code” option.
End User Criteria
The system should have simple and understandable graphical user interface such as forms and
buttons, which have descriptive names. It should give reliable response for each user comment.
All the interfaces, forms and buttons are written or designed in a simple language or common
language so that the user can access it without any difficult.
4.2 Proposed system architecture

One of the powerful features of the layered architecture pattern is the separation of
concerns among components. Components within a specific layer deal only with logic that
pertains to that layer. In this project, the team uses a three-tier architecture, which has three
layers. These three layers are the Application or Presentation layer, the business layer and the
data access layer. Application or presentation layer is the form, which provides the user interface
to either programmer or end user. The business layer is the class, which the team uses to write
the function, which works as a mediator to transfer data from application layer or presentation
layer to data layer. This layer also has a property layer which is a class where variables are
declared corresponding to the fields of the database which can be required for the application and
make the properties so that the team can get or set the data using these properties into the
variables. The third tire is the data access layer which is also a class to get or set data to the
database queries back and forth. This layer only interacts with the database. The database queries
Page | 47
or stored procedures will be written here to access the data from the database or to perform any
operation to the database
This
INTERNET IINTERNET
CONNECTION SERVICE
PORTAL
WEB SERVER OJES
OJES DB
F IGURE 22 SYSTEM ARCHITECTURE
Page | 48
4.2.1 System process
F IGURE 23 SYSTEM ACTIVITY DIAGRAM
Over all system of the service depicted below
F IGURE 24 OVERALL ASTU ONLINE JOB ENROLLMENT
Page | 49
OJESS System process
F IGURE 25 S YSTEM PROCESS
Page | 50
4.2.2 Subsystem Decomposition
To reduce the complexity of the solution domain, we decompose a system into simpler parts,
called subsystems. The main need of this portion is to design the external part of the system. In
this project, there are seven sub system decompositions
F IGURE 26 S UBSYSTEM DECOMPOSITION

Subsystem decomposition description
Subsystem Purpose Class
Student Profiling To manage student profile, Contact info,Profile,E-student
contact information and register
the students to the system
Company Profiling Responsible for registering new Ethiopian revenue and customer
companies and checking the if manager,Ethiopian revenue and
the companies are register in customer system
the database
Hiring System Responsible for managing the Criteria, Generate Candidates,
hiring process, such as submit Application Status, Message
criteria, generating candidates
based on the criteria, sending
message between the company
and the Eligible Student and
register and post Application
status
TABLE 15 SUBSYSTEM DESCRIPTION
Page | 51
4.2.3. Hardware/ software mapping

When we say hardware/software mapping for the system, it describes how subsystems are
assigned to hardware and off-the-shelf components. It also lists the issues introduced by multiple
nodes and software reuse.
In this system design mainly, there are three hardware components. The client side, server side
and database side. When the team applies the system, necessary software will be loaded to each
side hardware components. Network should be installed between each side. Then each sub
system software will be assigned and configured to the mapped hardware. Then the local area
network will be connected to the internet and the system will be functional. But now it is a
design phase. The hardware software mapping of the system is described below with a simple
diagram.
client
Hiring
Student
profiling
Company
OJESS
profiling
DB
FIGURE 27 HARDWARE SOFTWARE MAPPING
Page | 52
4.2.4. Persistent data management

The purpose of this section is to show the mapping of the objects/classes of the system, identified
during the analysis stage, in to the corresponding relational database.
F IGURE 28 CLASS TO RELATIONAL DATABASE MAPPING
F IGURE 29 STUDENT MAPPING
Page | 53
F IGURE 30 CLUB MAPPING
F IGURE 31 PROJECT MAPPING
Page | 54
F IGURE 32 COMPANY MAPPING
F IGURE 33 TEACHERS MAPPING
Page | 55
F IGURE 34 ELIGIBILITY MAPPING
F IGURE 35 ACTIVITY MAPPING
Page | 56
4.2.5. Component diagram

The following component diagram represents a group of graph of components connected by
dependency relationships and dependencies are shown as dashed arrows from the client
component to the supplier component
F IGURE 36 COMPONENT DIAGRAM
Page | 57
4.2.6. Deployment diagram
F IGURE 37 DEPLOYMENT DIAGRAM
4.2.7 Database design
F IGURE 38 DATABASE DESIGN
Page | 58
4.2.8. Access control

In multi user systems, different actors have access to different functionality and data. We
modeled these distinctions by associating different use cases to different actors. This is described
by the following access matrix.
Object Account Contact Profile E-Student Ethiopian Criteria and candidates

Actor Info revenue and
customer
system
Student viewAccount() Update attachPersona viewCriteria()
updateAccount() Address() lProjects()
change Update
AccountStatus() Phone()
Update
Email()
Teacher viewAccount() insertProjects() register()

updateAccount
Club ViewAccount() insertClub

updateAccount() Participation()
Company Change submitCriteria()

Hiring Status()
Manager
Ethiopian register()
revenue changeStatus()
and
customer
system
admin
TABLE 16 ACCESS CONTROL
Page | 59
4.2.9 User interface design

Navigational paths
F IGURE 39 USER INTERFACE
Page | 60
Reference
1. http://www.sqlservermain.com/
2. Lethbridge, Timothy C.
Object_Oriented_Software_Engineering__Practical_Software_Development_using_UML_
and_J
ava hal 56
3. Navathe, Elmasri. Fundamentals of Database System 6th edition.
4. www.google.com
5. Teklebirhan Ambaye Construction Project Management System.pdf(Templete)
6. Endale Aragu. Fundamental of Software Engineering CSE 3205 ppt
Page | 61

Online Job Enrollment for Graduating Students

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Online Job Enrollment for Graduating Students

Uploaded by

Copyright:

Available Formats

ONLINE JOB ENROLMENT FOR GRADUATING STUDENTS

2.3 Draw back of current system. ........................................................................................................ 12

CHAPTER ONE 1.1 Introduction

1.4 Task and Schedule

1.6 Purpose of the project

1.7 Team Composition

Yeabsera yabilisanu@gmail.com Analysis, implementation,

1.8 Objective of the project

1.9 Feasibility study

• Business process profits.

1.10 Scope and limitation

1.10.2 Limitation of the project

1.12. Beneficiaries of the project

• Proactive defect tracking – that is defects are found at early stage.

• Avoids the downward flow of the defects.

1.14. Development tools

Java Script/Jquery Js For validating client-side

Tools Abbreviation and version Used for

1.15 Test plan

• To optimize the code

• Early detection of errors during software development

2) black box testing

• tester needs no knowledge of implementation, including specific programing language.

• tester and programmer are independent each other.

• test is done from the user’s point of view.

1.15.2. Integration testing

Roll no Phase Required Required Function

3 Design March 20 SQL server This stage requires

4 CRUD (create, read update March 25 Editors Used to create,

6 Testing March 30 Computers Look for errors if

1.17 Required Resource with Cost

• Monitor personal info.

• Provide the required job.

• Control job enrolment process.

• Reduce the time and cost.

• Ensuring a data security.

2.2. Users of current system

2.3 Draw back of current system.

2.4 Business rule

• Student is the only user who is allowed to manage his/her account.

• User interface requirement

• Should be attractive and user friendly.

• Username and password should be authentic.

• Software and hardware consideration

3.4. System model

• student open and login to the system.

• User enter current password.

2. Name of scenario: Login

• The user opens the system.

Correct username and password.

3. Name of scenario: insert personal project

• user open and login to the system

• User opens and login to the system

• User selects send message tab

• Send message tab is displayed

• User writes his/her message on the free text

• User clicks send message button.

• The system displays successful message

• Company opens and login to the system

6.Name of scenario: choose students

• company selects student tab

• If the company doesn’t enter the correct information, the system