Airlines (component)
From UG
Prerequisites, Classified As, Parent Mantis
- Prerequisites: none
Business Needs and Requirements
We need a place in the system where we manage Airlines. This is to be used on CT record, reports, pdfs, etc.
Required functionality: list, add, edit, delete, archive.
Section last updated by/on: --Alex 18:50, 23 January 2010 (UTC)
Technical Notes from Systems Architect
This is a typical Admin component. Please apply standard patterns.
Section last updated by/on: --Alex 18:47, 23 January 2010 (UTC)
Technical Specification (TS) Summary
TS: Objects and Fields
Airline
Name
- type/format: alphanumeric; max=30 chars
2 Letter Code
- type/format: Datatypes#alpha; max=30 chars; all caps
3 Letter Numeric Code
- type/format: Datatypes#positive integer; max=3 digits
TS: User Interface
Consists of the following components - see below.
List All Airlines Panel
It has the following components:
- Columns: one per each field for object #Airline
- Sort: every column, alphabetical
- Paging: none
- Default sorting order: TBD
Edit Airlines Window
Component type: Window#Edit
See list of widgets below:
Name
| Attribute: | Value: |
| default: | pull from selected object |
| type/format: | see #Airline object |
| required?: | Y |
| validation type: | stop on max / zk standard / on submit // TBD |
Airline 2 Letter Code:
| Attribute: | Value: |
| default: | pull from selected object |
| type/format: | see #Airline object |
| required?: | Y |
| validation type: | stop on max / zk standard / on submit // TBD |
Airline 3 Letter Numeric Code:
| Attribute: | Value: |
| default: | pull from selected object |
| type/format: | see #Airline object |
| required?: | Y |
| validation type: | stop on max / zk standard / on submit // TBD |
Add Airlines Window
This is the same component as #Add Airlines Panel but with all values defaulted to blank.
Warning and Error Windows
See Use Cases.
TS: Functionality
See below a list of Use Cases (UC) and Test Cases (TC).
UC: Find Airline
- scroll up / down
- click several times on table headers to sort up and down; scroll
UC: Edit Airline. All fields are entered in a valid format
- Select airline from the list
- Click on *Add* button
- #Add Airlines Window appears
- Edit all fields
- click on "OK" or "Cancel"
- system silently closes the window; user can see that fields on #Add Airlines Window are updated
UC: Edit Airline. Some fields are entered in invalid format
UC: Edit Airline. Some required fields are blank
Use Case: Archive and Unarchive
- Apply standard archive functionality: Archive (Feature) .
- List ALL archived on #List All
Special Cases and Misc
None.
Quality Assurance
See list of Use Cases and Test Cases below.
- see #Use Case: Find Airline
- see #Use Case: Edit Airline
- see #Use Case: Add Airline
- see #Use Case: Delete Airline
- see #Use Case: Archive Airline
- see #Use Case: UnArchive Airline
Look And Feel
This section is to be written / defined by Graphic Designer and UI Designer.
Figures
Figure 1: List Airlines
Figure 2: Edit Airline
Questions and RFC
Known Non Critical Bugs
Links to Archived / Old specs
History
This doc has been created
--Alex 18:51, 23 January 2010 (UTC)<date/signat>
Re-design (Tweak) (Spec Update): ..... <summary> .....
<wiki date/signature>
- mantis: <link>
- Biz Req updated? N/Y
- Tech Spec updated? N/Y
DB
- see Tbl Airline
Code
http://mantis.jaguarfreight.com/svn/repo2/cybertrax/trunk/java/CyberTrax/proto2.0.1f/admin/carriers/
