Airlines (component)

From UG

Revision as of 19:26, 23 January 2010 by Alex (Talk | contribs)
Jump to: navigation, search


Contents

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

Airline 2 Letter Code

  • type/format: alphanumeric; max=30 chars; all caps

Airline 3 Letter Numeric Code

  • type/format: positive integer; max=3 digits


TS: User Interface

Consists of the following components - see below.


List All Airlines Panel

See #Figure 1: List Airlines

It has the following components:

  • Columns: one per each field for object #Airline
  • Sort: every column, alphabetical
  • Paging: none
  • Default sorting order: TBD

Add Airlines Window

Component type: Window#Edit

See #Figure 2: Edit Airlines

See list of widgets below:


Edit Airlines Window

This is the same component as #Add Airlines Panel but with values pre-filled from selected Airline.

Warning and Error Windows

See Use Cases.


TS: Functionality

See below a list of Use Cases (UC) and Test Cases (TC).

UC: Find Airline

  1. scroll up / down
  2. click several times on table headers to sort up and down; scroll

UC: Edit Airline. All fields are entered in a valid format

  1. Select airline from the list
  2. Click on *Add* button
  3. #Add Airlines Window appears
  4. Edit all fields
  5. click on "OK" or "Cancel"
  6. 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

Special Cases and Misc

None.

Quality Assurance

See list of Use Cases and Test Cases below.

Look And Feel

This section is to be written / defined by Graphic Designer and UI Designer.


Figures

Figure 1: List Airlines

File:Airlines.JPG

Figure 2: Edit Airline

File:Airlines Edit.JPG

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

Code

http://mantis.jaguarfreight.com/svn/repo2/cybertrax/trunk/java/CyberTrax/proto2.0.1f/admin/carriers/

Personal tools