Use Cases:

• A registered applicant will be able log in by entering their credentials at the login page.

• A successfully logged in applicant will also be able to apply for a position by submitting information about their previous experience, competency, and availability.

• Recruiter will be able to view and evaluate the submitted applications, and finally decide which candidate is the most compatible for the relevant field.

The use case diagram below will help to visualize the use cases.

Use Case diagram:

Actors: Applicant and Recruiter

Purpose: A use case diagram for a company that is recruiting qualified candidates.

Use Case: Registration

1. Applicant enters name, email, date of birth, and password on the registration page.
2. The server checks if the inputs are valid.
3. A) if the inputs are valid, they will be stored in the database. And applicant is successfully registered. B) Otherwise, the applicants will be notified error has occurred.

Use Case: Login

1. Applicant enters username and password.
2. A) If the given login info has a match in the database, applicant is successfully logged in. B) If not, login error will be displayed.

Web Application

This is a simplified design of what our web application is going to look like. At the center, we have the homepage. From the homepage we can access all those different pages. For instance, if registration attempt was successful applicant will be redirected to the homepage, otherwise applicant will need to retry to create an account.