Difference between revisions of "E-ticketing"
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
(→Conditional Rules Model) |
(→Customer View) |
||
Line 45: | Line 45: | ||
− | == Customer | + | == Customer Interface == |
− | + | * Suggest to follow Airasia.com way. | |
+ | * 1st the customer go to the site | ||
+ | * 2nd they choose their route, date and time | ||
+ | * The system will then check for availability of date and seat and return the value to user with price | ||
+ | * Optional : The customer can choose their sitting on the bus | ||
+ | * Then the customer login to the system and will do the transaction using Credit Card | ||
+ | * The e-Ticket will be emailed to the user for reference and bring it during travelling | ||
== Implementation == | == Implementation == |
Revision as of 23:57, 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.
Business Model
e-Ticketing System Flow
Customer Interface
- Suggest to follow Airasia.com way.
- 1st the customer go to the site
- 2nd they choose their route, date and time
- The system will then check for availability of date and seat and return the value to user with price
- Optional : The customer can choose their sitting on the bus
- Then the customer login to the system and will do the transaction using Credit Card
- The e-Ticket will be emailed to the user for reference and bring it during travelling