Difference between revisions of "E-ticketing"
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
(→Team Members) |
(→Conditional Rules Model) |
||
| Line 29: | Line 29: | ||
-- Insurance | -- Insurance | ||
| − | == | + | == Application Model == |
| + | * It is the intention of our team to reuse and build a vertical on top of the ADempiere Model, i.e. reusing its DataModel, AD features, application platform and ERP context. | ||
| + | * Business logic will follow the field Calllout and Process module | ||
| + | * Printouts will follow the Report and PrintFormat modules | ||
| + | * Customers will follow the BPartner model | ||
| + | * Bus and seating will follow the Product and Resource models | ||
| + | ** Seating as children of a bus BOM will be a new model extension. | ||
| + | ** Bookings to follow the InfoSchedule model. | ||
| + | * Thus ensuring heavy reuse or ready components and avoidance of model disruption. | ||
| + | |||
| + | == Business Model == | ||
== e-Ticketing System Flow == | == e-Ticketing System Flow == | ||
Revision as of 23:56, 18 May 2009
Contents
Introduction
- This page is for the proposal of e-Ticketing system built-in inside ADempiere.
- Sponsored by Energetic Point Sdn Bhd
- Will be based on e-Ticketing for Express Bus service between cities
Team Members
Product Modeling
- How many bus?
-- Model it on number of bus -- What is inside to measure? the seat. -- ie; 1 bus = 20 seats = 20 ticket
- Route
-- Location bus from Point A to Point B -- ie: Kuala Lumpur to Skudai
- Trips
-- How many trips in 1 day? 1 months?
- Resource
-- Petrol -- Driver -- Maintenance -- Insurance
Application Model
- It is the intention of our team to reuse and build a vertical on top of the ADempiere Model, i.e. reusing its DataModel, AD features, application platform and ERP context.
- Business logic will follow the field Calllout and Process module
- Printouts will follow the Report and PrintFormat modules
- Customers will follow the BPartner model
- Bus and seating will follow the Product and Resource models
- Seating as children of a bus BOM will be a new model extension.
- Bookings to follow the InfoSchedule model.
- Thus ensuring heavy reuse or ready components and avoidance of model disruption.
