-
Notifications
You must be signed in to change notification settings - Fork 3
Vehicle
jmrowe edited this page Jan 22, 2012
·
4 revisions
identifierFieldName = "vehicleId"
Vehicle(val vehicleId: Identifier, val vehicleName: String, val vehicleManual: Option[String] = None)
- vehicleId: Identifier - Mandatory id required for DB storage
- vehicleName: String - Mandatory short name for the vehicle
- vehicleManual: String - Optional link to a PDF manual for this vehicle
- Add vehicle
- Edit vehicle
- Find vehicle
- List all parts for a specific vehicle
- There is no scope for categorising different model variants for a vehicle. This can only be achieved by correct management of the vehicleName.
- The vehicles list will be populated by the database users as parts are ordered for vehicles and supplied to the end customer. There is no definitive vehicles list.
- The vehicle name can either be extremely specific e.g. down to the model number or quite generic. With a vehicle name containing a model number, the advantage of being very specific is that one part may only be applicable to a certain model of the vehicle, the disadvantage is that if a part is applicable to all models of this vehicle then it needs to be added to all the models of this vehicle.
- There will only be one link to a manual for each vehicle. If there is more than one manual then the link can be configured to be a directory.
- The link to the manual is only for further information to help the user. It is not used in the code.