How mario-659/funeralmanagementsystem works
This is a Rails web application for managing funeral-planning records, funeral services and their orders, user accounts, and mourning cards. The principal workflow is a browser request routed to a controller, which creates, retrieves, or updates domain records; mourning-card requests can also generate a PDF. Controllers and model paths are supported by the tree and sampled code. Some controller-to-model links and persistence behavior are inferred from Rails conventions; unsampled details are not expanded.
Main entry points: routes.rb Routes · schema.rb Application database · mourning_cards_controller.rb Card controller · user.rb User record
Components 18
Web entry
- Routes
config/routes.rb - Home controller
app/controllers/home_controller.rb
Funeral planning
- Deceased controller
app/controllers/deceaseds_controller.rb - Funeral controller
app/controllers/funerals_controller.rb - Services controller
app/controllers/funeral_services_controller.rb - Orders controller
app/controllers/funeral_service_orders_controller.rb - Deceased record
app/models/deceased.rb - Funeral record
app/models/funeral.rb - Funeral service
app/models/funeral_service.rb - Service order
app/models/funeral_service_order.rb
Memorial cards
- Card controller
app/controllers/mourning_cards_controller.rb - Mourning card
app/models/mourning_card.rb - Card PDF
app/pdf/mourning_card_pdf.rb
Accounts and data
- User controller
app/controllers/users_controller.rb - Registration controller
app/controllers/users/registrations_controller.rb - User record
app/models/user.rb - Application database
db/schema.rb
Other components
- User
Connections 23
- User → Routes: sends request
- Routes → Home controller: dispatches
- Routes → Deceased controller: dispatches
- Routes → Funeral controller: dispatches
- Routes → Services controller: dispatches
- Routes → Orders controller: dispatches
- Routes → Card controller: dispatches
- Routes → User controller: dispatches
- Routes → Registration controller: dispatches
- Deceased controller → Deceased record: reads/writes
- Funeral controller → Funeral record: reads/writes
- Services controller → Funeral service: reads/writes
- Orders controller → Service order: reads/writes
- Card controller → Mourning card: reads/writes
- Card controller → Card PDF: renders
- User controller → User record: reads/writes
- Registration controller → User record: creates account
- Deceased record → Application database: persists
- Funeral record → Application database: persists
- Funeral service → Application database: persists
- Service order → Application database: persists
- Mourning card → Application database: persists
- User record → Application database: persists