Difference between revisions of "Idrive 2.0 Admin Center Specs"
Jump to navigation
Jump to search
| (23 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
==External Interface Requirements== | ==External Interface Requirements== | ||
==System Features== | ==System Features== | ||
| + | ===Home=== | ||
| + | =====Description and priority===== | ||
| + | |||
| + | =====Action/result===== | ||
| + | =====Functional requirements===== | ||
| + | =====External interface requirements===== | ||
| + | |||
| + | ===Support=== | ||
| + | =====Description and priority===== | ||
| + | |||
| + | =====Action/result===== | ||
| + | =====Functional requirements===== | ||
| + | =====External interface requirements===== | ||
| + | |||
| + | ===Manufacturing=== | ||
| + | =====Description and priority===== | ||
| + | |||
| + | =====Action/result===== | ||
| + | =====Functional requirements===== | ||
| + | =====External interface requirements===== | ||
| + | |||
| + | ===Sales=== | ||
| + | =====Description and priority===== | ||
| + | |||
| + | =====Action/result===== | ||
| + | =====Functional requirements===== | ||
| + | =====External interface requirements===== | ||
| + | |||
| + | ===Tickets=== | ||
| + | =====Description and priority===== | ||
| + | |||
| + | =====Action/result===== | ||
| + | =====Functional requirements===== | ||
| + | =====External interface requirements===== | ||
| + | |||
| + | ===Managed Serivece=== | ||
| + | =====Description and priority===== | ||
| + | |||
| + | ====Dashboard==== | ||
| + | =====Functional requirements===== | ||
| + | * Search customer | ||
| + | * Search Event ID | ||
| + | * Search Ticket ID | ||
| + | * Alerts panels | ||
| + | ** CC Sync Overdue | ||
| + | ** CC Transfer service not running | ||
| + | |||
| + | =====External interface requirements===== | ||
| + | Left side panel - Search panels | ||
| + | |||
| + | Content panel - Alerts displayed using portlet panels | ||
| + | |||
| + | ====Customers==== | ||
| + | =====Functional requirements===== | ||
| + | Customers List | ||
| + | =====External interface requirements===== | ||
| + | |||
| + | ====Reports==== | ||
| + | =====Functional requirements===== | ||
| + | =====External interface requirements===== | ||
| + | |||
| + | |||
| + | ====Import==== | ||
| + | =====Description and priority===== | ||
| + | Import external vehicles trip info from file | ||
| + | =====Functional requirements===== | ||
| + | Upload file to server folder; | ||
| + | * for only one file type (seams to be xls) | ||
| + | Display list of uploaded files | ||
| + | |||
| + | File format: | ||
| + | Row 1 header merged | ||
| + | Date | ||
| + | Row 2 header | ||
| + | Confirmation # | Sch. Pick-up | Est. End Time | Trip Type | Vehicle | Driver Name | Passenger name | ||
| + | number | datetime | datetime | string | string | string | string | ||
| + | |||
| + | Parse and store data to database; | ||
| + | |||
| + | Verify driver/vehicle correspondence to GC DB, if not exist show log/alert; | ||
| + | |||
| + | Update events vehicles and driver info based on scheduler; | ||
| + | |||
| + | Use relation table between events and scheduler tables - needed for reports; | ||
| + | |||
| + | Save trip info on review comments: confirmation id, trip type, passenger | ||
| + | |||
| + | =====External interface requirements===== | ||
| + | |||
| + | ===Reports=== | ||
| + | ===Settings=== | ||
| + | ===Downloads=== | ||
| + | ===Internal acWiki=== | ||
| + | ===Calendar=== | ||
| + | |||
==Other Nonfunctional Requirements== | ==Other Nonfunctional Requirements== | ||
===Performance requirements=== | ===Performance requirements=== | ||
===Safety requirements=== | ===Safety requirements=== | ||
===Security requirements=== | ===Security requirements=== | ||
Latest revision as of 12:42, 31 May 2018
Introduction
Overall Description
External Interface Requirements
System Features
Home
Description and priority
Action/result
Functional requirements
External interface requirements
Support
Description and priority
Action/result
Functional requirements
External interface requirements
Manufacturing
Description and priority
Action/result
Functional requirements
External interface requirements
Sales
Description and priority
Action/result
Functional requirements
External interface requirements
Tickets
Description and priority
Action/result
Functional requirements
External interface requirements
Managed Serivece
Description and priority
Dashboard
Functional requirements
- Search customer
- Search Event ID
- Search Ticket ID
- Alerts panels
- CC Sync Overdue
- CC Transfer service not running
External interface requirements
Left side panel - Search panels
Content panel - Alerts displayed using portlet panels
Customers
Functional requirements
Customers List
External interface requirements
Reports
Functional requirements
External interface requirements
Import
Description and priority
Import external vehicles trip info from file
Functional requirements
Upload file to server folder;
- for only one file type (seams to be xls)
Display list of uploaded files
File format:
Row 1 header merged
Date
Row 2 header
Confirmation # | Sch. Pick-up | Est. End Time | Trip Type | Vehicle | Driver Name | Passenger name
number | datetime | datetime | string | string | string | string
Parse and store data to database;
Verify driver/vehicle correspondence to GC DB, if not exist show log/alert;
Update events vehicles and driver info based on scheduler;
Use relation table between events and scheduler tables - needed for reports;
Save trip info on review comments: confirmation id, trip type, passenger