The document details a project by team Delta focused on developing an employee management system called WePeople HR, aimed at alleviating the stress of traditional management practices. The proposed system features cloud hosting for accessibility, user-friendly design, and includes essential functionalities like employee and manager profiles, timesheet processing, and performance tracking. Key requirements address both functional aspects such as user profiles and non-functional aspects like performance and security to ensure a smooth operational experience.

1. Employee Management Systems
(EMS) Project
Group No: 03 - Team Delta
Contributions of Different Members:
Tahmina Ahmed - 19101479 : Introduction, Requirement Analysis, and Use-Case Diagram
Nur Fathiha Tahiat Seeum - 19101460 : Activity Diagram, and Sequence Diagram
Mir Nafis Sharear Shopnil - 17101423 : State Machine Diagram, Data Flow Diagram

2. Story Behind:
In the office, the office manager has to spend much time even after the regular office hours,
either at home or office for preparation of daily/weekly reports and other necessary records.
When the time of generating the Annual report comes, The pressure feels extreme. Thus,
the Employees amg manager loose their family time, peace and their life becomes stressful.
We all grew up seeing our parents busy. Therefore, With the motivation of Automating the
daily stressful works, We propose WePeople HR.
There are countless jobs in the current world. It is very tiresome for a manager to track it’s
employees via paper. We have tried to come up with an easy to use software to track
employees manually and provide them feedback for improvement.

3. Analysis of Current System:
The current system is not suitable for small to medium businesses
because they are very complex and have slow response time.
Analysis of Proposed System:
Our system is fast because it is hosted in cloud and it is user friendly and
easier to use

4. Planning
Managers can get an easier
time to track and provide
feedback so that they can
use their extra time.
Analysis
The system will be hosted
in the cloud so that
everyone can use it via the
internet. There is an offline
version that will function in
case of emergency.
Design
The system will feature a
dashboard connected with
several other pages such as
timesheet, review log,
progress log etc.

5. Requirement
Analysis
1. Functional Requirements
● Employee Profile
● Manager Profile
● Timesheets
2. Non- Functional Requirements
● Optional
● Performance
● Security

6. 1. Functional Requirements
1.1 Employee Profile
● Contains biographical, employment and
position data.
● Create a user profile
● Contains the badges employee work on
● Contains employee salary history.
● Employee can edit his profile.

7. 1. Functional Requirements
1.2 Manager Profile
● Edit privileges on Employee’s data.
● Create employee’s profile
● Track Employee’s progress
● Review employee’s progress
● Post announcements.

8. 1. Functional Requirements
1.3 Timesheets
● Processes the monthly payroll
● Pulls data to generate timesheet
● Generate default time sheet
● Auto assign new timesheets
● Ability to create blank timesheet

9. 2. Non-Functional Requirements
2.1 Optional
● Manager and employee can use the system
from their designated desks.
● The Software support most versions of
windows, mac and ubuntu, IOS and Android
devices.
● UX should be designed such way that a
person with minimal computer knowledge
can use it.

10. 2.2 Performance
● System needs to have very fast response
time. Ex 2-3 seconds.
● The system needs to be easily modifiable so
that future improvement can be done easily.
● System must be update in 0.1sec
● The result of searched file must be showed
in 0.5 sec
● The software needs to be regularly
monitored to keep it well maintained.
2. Non-Functional Requirements

11. 2.3 Security
● Register employee’s profile and provide
email and password for login
● Proper accountability which include not
allowing a employee to see other
employee’s account employee data should
only be visible to Manager
● Employees able to change their own
account’s password
● Data security should be managed if the
whole system comes down.
2. Non-Functional Requirements

12. Use- Case Diagram

13. Activity
Diagram

14. Activity
Diagram
(Contd.)

15. Sequence
Diagram

16. Sequence
Diagram (Contd.)

17. State Machine
Diagram

18. Data Flow Diagram

19. Conclusion
In conclusion we have can say:
● Our system will be user friendly.
● Our system will be well structured.
● Our system will save time.

20. Proposed deliverables
Deliverable 1
● Lorem ipsum dolor sit amet
● Sed do eiusmod tempor incididunt ut labore
Deliverable 2
● Lorem ipsum dolor sit amet
● Sed do eiusmod tempor incididunt ut labore
Deliverable 3
● Lorem ipsum dolor sit amet
● Sed do eiusmod tempor incididunt ut labore
Deliverable 4
● Lorem ipsum dolor sit amet
● Sed do eiusmod tempor incididunt ut labore