0% found this document useful (0 votes)
12 views

Case Study - PRT System v1

Uploaded by

kuma1412002
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
12 views

Case Study - PRT System v1

Uploaded by

kuma1412002
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

PRT SYSTEM

v1.0 2024-11-20

Project Resource Timesheet (PRT) System


Integrated System for Project PO Management, Resource Management, and Timesheet
Management
Document Name: PRT System Specification
Sensitivity: Internal

Table of Contents
Version History .............................................................................................................................................. 2
Instructions ................................................................................................................................................... 3
1. Abstract ................................................................................................................................................. 4
2. User Story:............................................................................................................................................. 5
2.1. Features to Develop ...................................................................................................................... 5
2.1.1. Dashboard View .................................................................................................................... 5
2.1.2. Project Management Module ............................................................................................... 5
2.1.3. Resource Cost Configuration Page ........................................................................................ 5
2.1.4. Resource/Employee Details Configuration Page ................................................................... 5
2.1.5. Resource Allocation and Utilization ...................................................................................... 5
2.1.6. Timesheet Integration: .......................................................................................................... 5
2.1.7. Alerts and Notifications......................................................................................................... 6
2.1.8. Reports and Insights .............................................................................................................. 6
3. Wireframe Specification ........................................................................................................................ 6
3.1. Dashboard View ............................................................................................................................ 6
3.2. Project Management Module ....................................................................................................... 7
3.3. Resource Cost Configuration Page ................................................................................................ 7
3.4. Resource/Employee Details Configuration Page ........................................................................... 8
3.5. Resource Allocation and Utilization .............................................................................................. 8
3.6. Timesheet Integration ................................................................................................................... 8
3.7. Wireframe Delivery ....................................................................................................................... 9
4. General Architecture ........................................................................................................................... 10
4.1. Dashboard View .......................................................................................................................... 10
4.2. Project Management Module ..................................................................................................... 11
4.3. Resource Cost Configuration ....................................................................................................... 12
4.4. Resource/Employee Details Configuration ................................................................................. 13
4.5. Resource Allocation and Utilization ............................................................................................ 14
4.6. Timesheet Integration ................................................................................................................. 15
5. Delivery ............................................................................................................................................... 16
6. Remarks............................................................................................................................................... 16

P a g e 1 | 16
Document Name: PRT System Specification
Sensitivity: Internal

Version History

Ver.No Change Description Date Author


1.0 Initial Version 20-Nov-2024 Saravanan Viswanathan

P a g e 2 | 16
Document Name: PRT System Specification
Sensitivity: Internal

Instructions

1. You have to complete the case study satisfying the acceptance criteria & present it by the
mentioned duration. No additional time will be given at any circumstances.
2. You may refer the online materials for the development and help required to successfully
complete the case study.
3. You should complete this case study with your own effort only; You may consult with
other team members for any doubts.
4. You should be regular to office & strictly follow the office business hours.
5. You should proactively provide status update to your manager on daily basis.
6. You should review the work periodically with your reporting manager prior submitting
the final work.
7. You should adhere to the goals set while working on the case study. Evaluation of the case
study will be based on the day to day progress (it wont be based on just final result)
8. You have to maintain professional communication at work while working with other team
members.
9. In the event of unsatisfactory performance, your internship shall be terminated, and this
will be reflected as a remark on your internship certificate.
10. Email is the primary communication medium at work. Ensure to maintain all the
communications over email.
11. You must bring your own laptop with all the necessary software’s installed for this
assignment.
12. Shall use your personal email ids for communication.

P a g e 3 | 16
Document Name: PRT System Specification
Sensitivity: Internal

1. Abstract

This design specification outlines the development of an integrated system that seamlessly connects
Project Purchase Order (PO) Management, Resource Management, and Timesheet Management into a
unified platform. The primary objective is to enhance operational efficiency, reduce redundancies, and
improve data accuracy by streamlining the interaction between these core project management functions.

The system will facilitate end-to-end visibility of project financials and resources, enabling organizations
to manage purchase orders, track resource allocation, and monitor timesheet submissions in a cohesive
manner. Key features include PO tracking, dynamic resource scheduling aligned with project milestones,
and real-time timesheet integration for accurate billing and cost analysis.

By consolidating these processes, the system will provide decision-makers with actionable insights through
dashboards and reports, reduce manual intervention, and ensure compliance with organizational policies.
The specification details the functional requirements and integration points necessary to achieve a
scalable and user-friendly solution.

This initiative is aimed at organizations seeking to improve collaboration, optimize resource utilization, and
deliver projects efficiently while maintaining cost control and transparency.

P a g e 4 | 16
Document Name: PRT System Specification
Sensitivity: Internal

2. User Story:
As a Project Manager, I want to track resource utilization through timesheets against the project budget,
ensuring that resource costs are calculated accurately based on their designation. Additionally, I want to
have a separate page to configure the daily cost of resources by designation so that financial tracking
remains precise and adaptable.

2.1. Features to Develop


2.1.1. Dashboard View
a) Provide an overview of total project budget, PO value, utilized amount, and remaining
balance.

b) Separate views for Project-specific and PO-specific tracking.

c) Track resource utilization per project, PO, and designation.

2.1.2. Project Management Module


a) Manage project details and budgets.

b) Associate multiple POs with a project.

c) Show total budget utilization vs. remaining funds.

2.1.3. Resource Cost Configuration Page


a) A dedicated page to define and manage resource costs based on their designation:

b) Fields: Designation Name, Daily Cost.

c) Ability to add/edit/delete designations and costs.

d) Audit log to track historical changes for transparency.

2.1.4. Resource/Employee Details Configuration Page


a) Input fields for Resource Name, Employee ID, Designation, and Contact Details.

b) Display of all configured resources with inline edit/delete options.

2.1.5. Resource Allocation and Utilization


a) Assign resources to a project and map their costs against the corresponding PO.

b) Track utilization of hours and costs at both Project and PO levels.

2.1.6. Timesheet Integration:


a) Allow entry of hours worked per resource per day.

b) Automatically calculate the cost of work done based on resource designation.

c) Allow resource manager to approve the timesheet during month end billing.

P a g e 5 | 16
Document Name: PRT System Specification
Sensitivity: Internal

d) Allow resource manager to freeze/unfreeze the timesheet.

2.1.7. Alerts and Notifications


o Notify when resource costs exceed 80% PO limits or project budgets.

2.1.8. Reports and Insights


o Generate detailed reports for resource utilization by Project and PO.

o Provide consolidated and individual breakdowns.

o Export data to Excel or PDF.

3. Wireframe Specification
3.1. Dashboard View
Overview:

• Purpose: Provide an at-a-glance summary of project and PO-related budgets and utilization.

• Components:

1. Header Section:

▪ App name/logo.

▪ Navigation menu with tabs for "Dashboard," "Projects," "Resources,"


"Timesheets," and "Reports."

2. Summary Cards:

▪ Total Project Budget.

▪ Total PO Value.

▪ Utilized Amount.

▪ Remaining Balance.

▪ Each card displays numeric values and visual indicators (e.g., progress bars).

3. Detailed Tracking:

▪ Tabs for Project-specific and PO-specific tracking.

▪ Project View:

▪ List of projects with columns for Name, Budget, Utilized Amount,


Remaining Balance.

▪ PO View:

▪ List of POs associated with each project.

P a g e 6 | 16
Document Name: PRT System Specification
Sensitivity: Internal

▪ Columns for PO Name, Value, Utilized Amount, Remaining Balance.

4. Resource Utilization Table:

▪ Columns: Resource Name, Designation, Associated Project/PO, Total Hours,


Utilized Cost.

3.2. Project Management Module


Overview:

• Purpose: Manage projects, associate POs, and track budget usage.

• Components:

1. Project List:

▪ Table view of all projects with columns: Project Name, Total Budget, POs
Associated, Utilized Amount, Remaining Balance.

▪ Inline actions for Edit/View/Delete.

2. Project Details Page:

▪ Fields for Project Name, Description, Total Budget.

▪ Section to associate multiple POs.

▪ Budget Utilization Chart (bar or pie chart).

3. PO Association:

▪ Add/Edit/Delete POs for each project.

▪ Columns: PO Number, Value, Utilized, Remaining.

3.3. Resource Cost Configuration Page


Overview:

• Purpose: Define and manage resource costs based on designations.

• Components:

1. Designation Cost Table:

▪ Columns: Designation Name, Daily Cost, Actions (Edit/Delete).

2. Add Designation Form:

▪ Fields: Designation Name, Daily Cost.

▪ Submit button for saving.


P a g e 7 | 16
Document Name: PRT System Specification
Sensitivity: Internal

3. Audit Log Section:

▪ Table showing historical changes with columns: Designation, Old Cost, New Cost,
Change Date, Modified By.

3.4. Resource/Employee Details Configuration Page


Overview:

• Purpose: Manage and display resource details.

• Components:

1. Resource Table:

▪ Columns: Resource Name, Employee ID, Designation, Contact Details, Actions


(Edit/Delete).

2. Add Resource Form:

▪ Fields: Name, Employee ID, Designation (dropdown), Contact Details.

▪ Submit button for saving.

3.5. Resource Allocation and Utilization


Overview:

• Purpose: Assign resources to projects and track utilization.

• Components:

1. Resource Assignment Form:

▪ Fields: Project Name, Resource Name, Associated PO, Assigned Hours.

▪ Submit button for saving.

2. Utilization Table:

▪ Columns: Project, PO, Resource Name, Designation, Total Hours, Total Cost.

3.6. Timesheet Integration


Overview:

• Purpose: Log hours, calculate costs, and enable manager approvals.

• Components:

1. Timesheet Entry Form:

P a g e 8 | 16
Document Name: PRT System Specification
Sensitivity: Internal

▪ Fields: Date, Resource Name, Project/PO, Hours Worked.

▪ Auto-calculated cost based on designation and hours.

▪ Submit button for saving.

2. Approval Section:

▪ Manager view of pending timesheets.

▪ Approve/Reject buttons.

3. Freeze/Unfreeze Control:

▪ Toggle button for freezing/unfreezing timesheet entries.

3.7. Wireframe Delivery


• Tool: Adobe XD or equivalent.

• Pages to Include:

o Dashboard.

o Project Management.

o Resource Cost Configuration.

o Resource/Employee Configuration.

o Resource Allocation and Utilization.

o Timesheet Entry/Approval.

• Interactive Features:

o Navigation between pages.

o Form validation for required fields.

o Dynamic data visualization elements.

P a g e 9 | 16
Document Name: PRT System Specification
Sensitivity: Internal

4. General Architecture
Frontend

• Framework: Angular 15+ for the UI.

• Styling: Angular Material or Bootstrap 5 for consistent UI components and responsiveness.

• State Management: Use NgRx or Angular Services for handling application state.

• Design:

o Component-based architecture: Separate components for Dashboard, Resource


Management, Timesheet, etc.

o Lazy loading modules for better performance.

o Implement routing for page navigation.

Backend

• Framework: Spring Boot 3.0+ for backend APIs.

• API Design:

o RESTful API principles.

o Versioning APIs (e.g., /api/v1/...).

• Security:

o Implement Spring Security with OAuth2/JWT for authentication and authorization.

o Role-based access control (e.g., Admin, Manager, Employee).

• Database: PostgreSQL.

o Table columns to be created with appropriate data types and meaningful names.

o Optimize queries for large datasets with indexes.

o Foreign key constraints

o Normalization of tables

o Prepare ER Relation diagram

4.1. Dashboard View


Features

• Display key metrics: Total project budget, PO value, utilized amount, remaining balance.

• Separate views for:

P a g e 10 | 16
Document Name: PRT System Specification
Sensitivity: Internal

o Project-specific tracking.

o PO-specific tracking.

• Resource utilization by:

o Project.

o Purchase Order (PO).

o Designation.

Frontend Development

• Components:

o Charts: Use Chart.js or D3.js for visualizations (e.g., pie charts for budget breakdown, bar
charts for resource utilization).

o Summary Cards: Angular Material cards to show metrics at a glance.

• Routing:

o /dashboard/projects

o /dashboard/pos

• Filters: Dropdowns or multi-selects for project and PO filtering.

Backend Development

• APIs:

o /api/dashboard/projects – Fetch budget utilization per project.

o /api/dashboard/pos – Fetch PO-specific utilization.

o /api/dashboard/utilization – Fetch utilization data by resource and designation.

Database Design

• Tables:

o projects – Holds project details.

o purchase_orders – Tracks POs and their association with projects.

o utilizations – Tracks resource utilization data.

4.2. Project Management Module


Features

• CRUD operations for projects and POs.

P a g e 11 | 16
Document Name: PRT System Specification
Sensitivity: Internal

• Associate multiple POs with a project.

• Show budget utilization vs. remaining funds.

Frontend Development

• Components:

o Project List with inline editing for budget adjustments.

o PO List with add/remove association to projects.

• Forms:

o Reactive Forms with validation for budget inputs.

o Dropdowns to link POs to projects.

• Routing:

o /projects

o /projects/:id/pos

• UX Enhancements:

o Snackbar notifications for save, update, and delete actions.

Backend Development

• APIs:

o /api/projects – CRUD for projects.

o /api/projects/:id/pos – Associate POs with a project.

o /api/pos – CRUD for POs.

• Business Rules:

o Ensure the total PO value doesn’t exceed the project budget.

Database Design

• Tables:

o projects (columns: id, name, budget, description, created_at).

o purchase_orders (columns: id, project_id, po_number, value, created_at).

4.3. Resource Cost Configuration


Features

• Define and manage resource costs based on designation.


P a g e 12 | 16
Document Name: PRT System Specification
Sensitivity: Internal

• Maintain an audit log for changes.

Frontend Development

• Components:

o Table with editable rows for designation and cost.

o Modal to view audit logs.

• Forms:

o Validation for unique designation names.

o Numeric input for daily costs.

Backend Development

• APIs:

o /api/designations – CRUD for designations and costs.

o /api/designations/audit – Fetch audit logs.

• Business Rules:

o Prevent deletion of designations in use.

Database Design

• Tables:

o designations (columns: id, name, daily_cost, created_at).

o designation_audit_logs (columns: id, designation_id, old_cost, new_cost, updated_by,


updated_at).

4.4. Resource/Employee Details Configuration


Features

• Input fields: Resource Name, Employee ID, Designation, and Contact Details.

• Manage resource data with inline editing and deletion.

Frontend Development

• Components:

o Searchable and sortable resource list.

o Inline edit for resource details.

• Forms:

P a g e 13 | 16
Document Name: PRT System Specification
Sensitivity: Internal

o Dropdowns for selecting designations.

Backend Development

• APIs:

o /api/resources – CRUD for resources.

• Business Rules:

o Validate unique Employee IDs.

Database Design

• Tables:

o resources (columns: id, name, employee_id, designation_id, contact_details,


created_at).

4.5. Resource Allocation and Utilization


Features

• Assign resources to projects and map their costs against POs.

• Track utilization of hours and costs.

Frontend Development

• Components:

o Resource allocation form.

o Utilization tracking table with filters for project and PO.

Backend Development

• APIs:

o /api/resource/allocation – Assign resources to projects.

o /api/resource/utilization – Fetch utilization data.

• Business Rules:

o Prevent over-allocation of resources beyond available budget.

Database Design

• Tables:

o allocations (columns: id, resource_id, project_id, po_id, allocated_hours, allocated_cost,


created_at).

P a g e 14 | 16
Document Name: PRT System Specification
Sensitivity: Internal

4.6. Timesheet Integration


Features

• Entry of hours worked per resource per day.

• Automatic cost calculation based on resource designation.

• Resource manager approval, freeze/unfreeze.

Frontend Development

• Components:

o Calendar view for timesheet entries.

o Approval dashboard for managers.

• Forms:

o Validation for date and hour entries.

Backend Development

• APIs:

o /api/timesheets – Submit and fetch timesheets.

o /api/timesheets/approve – Approve timesheets.

o /api/timesheets/freeze – Freeze/unfreeze timesheets.

• Business Rules:

o Disallow edits to frozen timesheets.

Database Design

• Tables:

o timesheets (columns: id, resource_id, project_id, date, hours_worked, cost, status,


created_at).

P a g e 15 | 16
Document Name: PRT System Specification
Sensitivity: Internal

5. Delivery

• Wireframe specifications of each screen

o Wireframe specification review and signoff

• Low Level Design documentation (LLD)

o LLD Review and signoff

• Source Code of UI, Backend & DB Objects.

o Review source code & address comments

• Integration / E2E Test log documentation.

o Review the test results

• User Manual / Operations Manual

o UAT Demo & Signoff

6. Remarks

Subsequent details shall be added as we groom this requirement.

P a g e 16 | 16

You might also like