Complete Motor Freight Carrier Use Cases

[BenGardiner]

The changeset completes all the data models and endpoints that were driven by the motor freight carrier use cases. More input on refining the use cases and/or defining more use cases is most welcomed. Also input on how the API endpoints might better serve the use cases as presently defined.

This set of changes has been posted to a preview apiary project to make review of the rendering possible:

https://previewotapi.docs.apiary.io/#

The following issues are resolved by the PR

• issue #45 complete use cases
• issue #49 use return code 400 for requests with query parameters
• issue #52 hard wrap the text for easier review
• issue #54 make time search behaviour clear

[ujonson]

The use cases look good but as per group discussion we will need to add some more vehicle only type use cases for standard fleet maintenance usage scenarios.

[BenGardiner]

The use cases look good but as per group discussion we will need to add some more vehicle only type use cases for standard fleet maintenance usage scenarios. Looks good but we need to expand the use cases to include more straight vehicle/fleet maintenance usage scenarios. I am sure that we add that in the next revision.

For vehicle-only use cases, we presently have:

• Vehicle-Only Data Export
• Vehicle Location Time History Tracking
• Carrier Custom Business Intelligence
• In-Field Maintenance & Repair

I'm at a loss as to what the additional use cases would be -- although I would welcome insights from any collaborators. I opened issue #57 more vehicle-only use cases for anyone to propose ideas