forked from nus-cs2103-AY2425S1/tp
-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #24 from dominic2412/update-readme
The README looks good
- Loading branch information
Showing
1 changed file
with
207 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,16 +1,211 @@ | ||
[![CI Status](https://github.com/se-edu/addressbook-level3/workflows/Java%20CI/badge.svg)](https://github.com/se-edu/addressbook-level3/actions) | ||
![Build Status](https://img.shields.io/github/workflow/status/AY2425S1-CS2103T-T09-2/CI?style=flat-square) | ||
|
||
|
||
![Ui](docs/images/Ui.png) | ||
|
||
* This is **a sample project for Software Engineering (SE) students**.<br> | ||
Example usages: | ||
* as a starting point of a course project (as opposed to writing everything from scratch) | ||
* as a case study | ||
* The project simulates an ongoing software project for a desktop application (called _AddressBook_) used for managing contact details. | ||
* It is **written in OOP fashion**. It provides a **reasonably well-written** code base **bigger** (around 6 KLoC) than what students usually write in beginner-level SE modules, without being overwhelmingly big. | ||
* It comes with a **reasonable level of user and developer documentation**. | ||
* It is named `AddressBook Level 3` (`AB3` for short) because it was initially created as a part of a series of `AddressBook` projects (`Level 1`, `Level 2`, `Level 3` ...). | ||
* For the detailed documentation of this project, see the **[Address Book Product Website](https://se-education.org/addressbook-level3)**. | ||
* This project is a **part of the se-education.org** initiative. If you would like to contribute code to this project, see [se-education.org](https://se-education.org/#contributing-to-se-edu) for more info. | ||
|
||
[note] Change | ||
# TALENT SG | ||
|
||
### Team Project: | ||
Aditya, Darren, Dominic, Stanley & Rithani | ||
|
||
## Table of Contents: | ||
## 📑 Table of Contents: | ||
- [🎯 Target User](#target-user) | ||
- [💡 Value Proposition](#value-proposition) | ||
- [🚀 Project Direction](#project-direction) | ||
- [📝 User Stories](#user-stories) | ||
- [🔍 Use Cases](#use-cases) | ||
- [⚙️ Features](#features) | ||
- [🧠 Non-functional Requirements](#non-functional-requirements) | ||
- [📖 Glossary](#glossary) | ||
|
||
--- | ||
## Target User: | ||
|
||
Our primary target users are **Recruiters** and **HR professionals** who are responsible for managing job candidates and employee information. These users typically work in fast-paced environments where efficient management of candidate and employee data is crucial for streamlining the recruitment process and ensuring organizational growth. | ||
|
||
--- | ||
|
||
## Value Proposition: | ||
|
||
TalentSG aims to simplify and enhance the recruitment process for HR professionals and recruiters. The application will provide robust features for tracking applicants, managing interview schedules, and maintaining comprehensive records of employment details. By centralizing these tasks in one intuitive platform, TalentSG will help users reduce administrative burden, improve efficiency, and make better hiring decisions. | ||
|
||
--- | ||
|
||
## Project Direction: | ||
|
||
TalentSG will evolve from the existing AddressBook-Level3 (AB3) codebase, transforming it into a powerful contact management tool for recruitment and HR management. Key areas of development include: | ||
|
||
- **Customizable Applicant Profiles**: Recruiters can add, modify, and manage detailed profiles for job candidates. | ||
- **Interview and Task Scheduling**: Track interview schedules, follow-up tasks, and milestones. | ||
- **Employment Record Management**: Tools for managing employee information post-hiring. | ||
- **Search and Filter Enhancements**: Advanced search and filtering options to locate candidate profiles. | ||
- **Data Import/Export**: Import data from other systems and export records for reporting. | ||
- **Improved User Experience**: Tweak the UI for HR professionals, with enhanced data visualization and intuitive navigation. | ||
|
||
--- | ||
|
||
## Brainstormed User Stories for TalentSG: | ||
|
||
| ID | As a/an | I want to be able to... | So that I can... | | ||
| --- | ------------------ | -------------------------------------------------------------- | --------------------------------------------------- | | ||
| 1 | recruiter | add new candidate profiles | keep track of all candidates applying for positions | | ||
| 2 | recruiter | edit candidate profiles | update candidate information as new details arise | | ||
| 3 | HR professional | view a list of all candidates | easily access any candidate’s details on demand | | ||
| ... | ... | ... | ... | | ||
|
||
*Above is only a fraction of the ideas we have brainstormed.* | ||
|
||
--- | ||
|
||
## Selecting User Stories for the MVP: | ||
|
||
The selected user stories for the MVP(Minimium Viable Product) include: | ||
- **📝Add/Edit/Delete Candidate Profiles** | ||
- **👥 View a List of Candidates** | ||
- **🔍Search Candidates by Criteria** | ||
- **🗓️Schedule and Manage Interviews** | ||
- **🔔Set Interview Reminders** | ||
- **📊Track Candidate Status** | ||
|
||
These stories form the core of the MVP, providing basic functionality for recruiters and HR professionals. | ||
|
||
--- | ||
|
||
|
||
## Feature Specification for TalentSG: | ||
|
||
| Feature | Purpose | | ||
| -------------------------------- | ----------------------------------------------------------- | | ||
| **Add/Edit/Delete Candidate** | Allows the recruiter to manage candidate profiles | | ||
| **View Candidate List** | Displays a list of all candidates | | ||
| **Search Candidates by Criteria**| Enables recruiters to search candidates by skills or roles | | ||
| **Schedule Interviews** | Schedule and manage candidate interviews | | ||
| **Set Interview Reminders** | Set reminders for upcoming interviews | | ||
| **Track Candidate Status** | Track recruitment stages like interview, shortlisted, hired | | ||
|
||
--- | ||
|
||
## Use Cases | ||
|
||
### Use Case 1: Add a New Candidate Profile | ||
**Actor**: Recruiter | ||
|
||
**Preconditions**: The system is running, and the recruiter is logged into the application. | ||
|
||
**Main Success Scenario**: | ||
1. Recruiter selects the "Add Candidate" option. | ||
2. System prompts recruiter to input candidate details (name, phone, email, address, role). | ||
3. Recruiter enters candidate details. | ||
4. System confirms that the details are valid and adds the candidate profile. | ||
5. System displays a success message: "Candidate profile added successfully." | ||
|
||
**Extensions**: | ||
- 3a. Recruiter inputs invalid phone number or email. | ||
- System shows an error message: "Invalid phone number or email. Please enter valid information." | ||
- 4a. A duplicate candidate profile is detected. | ||
- System shows an error message: "Duplicate candidate detected. Profile not added." | ||
|
||
--- | ||
|
||
### Use Case 2: Schedule an Interview | ||
**Actor**: Recruiter | ||
|
||
**Preconditions**: Recruiter is logged in, and a candidate profile exists. | ||
|
||
**Main Success Scenario**: | ||
1. Recruiter selects the "Schedule Interview" option for a specific candidate. | ||
2. System prompts recruiter to input the date and time for the interview. | ||
3. Recruiter inputs valid date and time. | ||
4. System saves the interview schedule for the candidate. | ||
5. System displays a success message: "Interview scheduled for [Candidate Name] on [Date and Time]." | ||
|
||
**Extensions**: | ||
- a. Recruiter inputs invalid date or time. | ||
- System shows an error message: "Invalid date or time format. Please follow the format YYYY-MM-DD and HH:MM." | ||
- b. The selected time slot is already booked for another interview. | ||
- System shows an error message: "Time slot is already booked. Please select a different time." | ||
|
||
--- | ||
|
||
### Use Case 3: Search for Candidates by Criteria | ||
**Actor**: HR Professional | ||
|
||
**Preconditions**: Candidate profiles exist in the system. | ||
|
||
**Main Success Scenario**: | ||
1. HR professional selects the "Search" option. | ||
2. System prompts HR professional to input search criteria (e.g., candidate name, role, or skill). | ||
3. HR professional enters search criteria (e.g., role: Software Engineer). | ||
4. System retrieves and displays a list of candidates matching the criteria. | ||
5. HR professional selects a candidate from the list to view detailed information. | ||
|
||
**Extensions**: | ||
- 3a. No candidates match the search criteria. | ||
- System displays a message: "No candidates found for the given criteria." | ||
|
||
--- | ||
|
||
## Non-functional Requirements | ||
|
||
1. **Performance**: | ||
- The system should be able to handle up to 100 simultaneous users without a significant decrease in performance. | ||
- System response time for any operation should not exceed 1 second. | ||
|
||
2. **Scalability**: | ||
- The system should support the management of up to 10,000 candidate profiles without performance degradation. | ||
- The system should be able to integrate with external recruitment systems (e.g., LinkedIn, job portals) to import candidate data. | ||
|
||
3. **Usability**: | ||
- The system should be intuitive for users with basic computer skills. | ||
- The user interface should provide clear navigation, with minimal need for user training. | ||
|
||
4. **Reliability**: | ||
- The system should have a 99.9% uptime, ensuring availability for recruiters and HR professionals during business hours. | ||
- Data should be backed up every 24 hours to prevent data loss. | ||
|
||
5. **Security**: | ||
- The system must comply with GDPR regulations and ensure that candidate data is securely stored and handled. | ||
- All user data (including candidate information) should be encrypted both at rest and in transit. | ||
|
||
6. **Portability**: | ||
- The system should be compatible with Windows, macOS, and Linux operating systems. | ||
- The system should be able to run on machines with at least 4GB of RAM and 2GHz processors. | ||
|
||
7. **Accessibility**: | ||
- The system should comply with WCAG 2.1 standards for web accessibility, ensuring that users with disabilities can use the system effectively. | ||
|
||
|
||
|
||
⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️ | ||
## Glossary | ||
|
||
1. **Recruiter**: | ||
- A professional responsible for managing job applicants and their application process. | ||
|
||
2. **HR Professional**: | ||
- A Human Resources professional responsible for managing employee information and candidate data during the recruitment process. | ||
|
||
3. **Candidate Profile**: | ||
- A record containing all relevant details about a job applicant, including contact information, skills, experience, and interview notes. | ||
|
||
4. **MVP (Minimum Viable Product)**: | ||
- The minimum version of a product that meets the basic requirements to be usable by the target audience. | ||
|
||
5. **Interview Schedule**: | ||
- The process of setting a date and time for a job applicant to be interviewed by the recruiter or hiring manager. | ||
|
||
6. **NFR (Non-functional Requirements)**: | ||
- Requirements that specify the quality and performance characteristics of the system (e.g., performance, security, usability). | ||
|
||
7. **CRUD**: | ||
- Refers to the basic operations of Create, Read, Update, and Delete, typically applied to data management within an application. | ||
|
||
8. **GDPR (General Data Protection Regulation)**: | ||
- A European regulation on data protection and privacy for individuals within the EU, applicable to the handling of personal data. | ||
|
||
|
||
|
||
--- | ||
|