ICREATESOFTWARE

Project Day.

Problem

• Working in a management-based environment has managers managing employees, teams, and projects, and tracking how effectively they are being utilized within an organization.
• This problem was exacerbated by the COVID-19 pandemic which saw most of the workforce working from home making it difficult for managers to track how effectively their employees are being utilized.
• Utilization is a measure of how much work your employee or team has e.g a 50% utilization implies that the employee’s contractual hours are 50% being used up and that employee can still direct 50% of his hours to another job. So, the employee is not being fully utilized.
• To have a balanced utilization of employees you need to consider the following factors:
• How many projects you have.
• How many Teams are working on the project(s)
• How many employees are part of the teams working on the projects.
• Our system helps to solve that issue by considering all these factors and give the manager a single metric to see how efficiently the organization is running.

​

HOW DOES TEAM UTILIZATION MONITOR SOLVE THESE ISSUES?

Overview

Our system provides:

​

• Utilization percentage metrics to give an overview of the company’s total utilization.
• Individual utilization targets that can determine if a resource (employee or team)  is under/overused or requires more training.
• Team recommendation system to propose ideal teams for projects based on individual parameters such as skills and availability.
• A visual depiction of all these elements in a clear concise manner like:
• Historic utilization of a company
• Individual utilization
• Team utilization
• Ability for admins to create teams and assign members based on preference.

​

​

Utilization System

DEMOs

Testing

• For our tests we used the following technologies:
• Jest for unit testing and integration testing.
• Cypress for end-to-end testing.
• GitHub actions to automate our tests.

​

Unit Testing – Service Layer

Unit Testing – Database Access Layer

End-to-End Testing

Front End Tests

Testing Automation – Git Actions

Non- functional Requirements Testing

• Our main functional requirements are:
• Security
• Usability
• Maintainability
• Reliability

​

Security Testing

Maintainability Testing

Reliability Testing

Usability

Security

• Bcrypt: Used to hash and salt passwords.
• We do not store passwords as plain text.
• N-tier architecture: Allows unique security measures to be implemented at multiple layers.
• Tokens: All our api calls to the backend sever are handled through unique tokens assigned to each user.
• Role Based Access Management System: We have two roles, admin and individual (employee)
• Critical information like contract hours, is only accessed by the admin and not available to the employee.

​

​

​

Architectural Design

Technologies

DEPLOYMENT MODEL

Project Management

QUESTIONS