Project Structure

Audience

Developers, QA engineers, support engineers, security engineers, solution architects, and implementation partners.

Reference Content

This page records source-verified technical behavior and boundaries for the workforce-scheduling capability.

Summary

Scheduling shares one Attendance Service project. Separation is folder- and namespace-based, with project references only to shared contracts and shared kernel.

Area	Verified responsibility
Api	Direct and legacy-shaped HTTP adaptation
Application/Services	Commands, queries, effective-policy resolution
Application/TimeOffice	Request/response models and parsing/projection helpers
Application/Compatibility	Legacy behavior translation
Domain/TimeOffice	Shift, assignment, weekly-off, policy aggregates
Infrastructure	EF mappings, repositories, tenant context, audit/timeline persistence
Messaging	Transactional outbox relay shared with attendance flows

Project boundary

There is no separate scheduling project, package, or deployable. Tests were not found under a dedicated Attendance Service test project. Gateway, monolith, frontend, leave, and payroll evidence therefore lives in sibling projects and must be read as integration context, not as owned scheduling code.

Source References

• microservices/src/attendance-service/attendance-service.csproj
• microservices/src/attendance-service/Api/AttendanceShiftPolicyEndpoints.cs
• microservices/src/attendance-service/Application/Services/ShiftPolicyCommands.cs
• microservices/src/attendance-service/Domain/TimeOffice/Shift.cs
• microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs

Related Articles

• Technical overview
• Technical limitations
• Workforce Scheduling

See Also

• Technical overview
• Technical limitations
• Workforce Scheduling

Keywords

• Workforce scheduling
• Shift policy
• Attendance integration

Revision Information

• Status: Draft
• Last reviewed: 2026-07-20
• Next review: 2026-10-20