Airlines (component)

From UG

Revision as of 19:41, 23 January 2010 (edit) Alex (Talk | contribs) ← Older edit		Revision as of 19:50, 23 January 2010 (edit) (undo) Alex (Talk | contribs) (→Airline) Newer edit →
Line 30:		Line 30:
	'''Name'''		'''Name'''
-	:* ''type/format:''  alphanumeric; max=30 chars	+	:* ''type/format:''  [[alphanumeric]]; max=30 chars
	'''Airline 2 Letter Code'''		'''Airline 2 Letter Code'''
-	:* ''type/format:''  alphanumeric; max=30 chars; all caps	+	:* ''type/format:''  [[Datatypes#alpha]]; max=30 chars; all caps
	'''Airline 3 Letter Numeric Code'''		'''Airline 3 Letter Numeric Code'''
-	:* ''type/format:'' positive integer; max=3 digits	+	:* ''type/format:'' [[Datatypes#positive integer]]; max=3 digits
-		+
	== TS: User Interface ==		== TS: User Interface ==

---

Revision as of 19:50, 23 January 2010

Contents 1 Prerequisites, Classified As, Parent Mantis 2 Business Needs and Requirements 3 Technical Notes from Systems Architect 4 Technical Specification (TS) Summary 5 TS: Objects and Fields 5.1 Airline 6 TS: User Interface 6.1 List All Airlines Panel 6.2 Edit Airlines Window 6.3 Add Airlines Window 6.4 Warning and Error Windows 7 TS: Functionality 7.1 UC: Find Airline 7.2 UC: Edit Airline. All fields are entered in a valid format 7.3 UC: Edit Airline. Some fields are entered in invalid format 7.4 UC: Edit Airline. Some required fields are blank 7.4.1 Use Case: Archive and Unarchive 7.5 Special Cases and Misc 8 Quality Assurance 9 Look And Feel 10 Figures 10.1 Figure 1: List Airlines 10.2 Figure 2: Edit Airline 11 Questions and RFC 12 Known Non Critical Bugs 13 Links to Archived / Old specs 14 History 14.1 This doc has been created 14.2 Re-design (Tweak) (Spec Update): ..... <summary> ..... 15 DB 16 Code

Prerequisites, Classified As, Parent Mantis

• Classified As: (large) component
• Parent Mantis: 606

• 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: Datatypes#alpha; max=30 chars; all caps

Airline 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

See #Figure 1: List Airlines

It has the following components:

• Buttons: Add, Edit, Remove.
• Listbox with properties defined below:

• 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 #Figure 2: Edit Airlines

See list of widgets below:

Name

Attribute:	Value:
default:	pull from selected object
type/format:	alphanumeric; max = 30; min = 2
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:	alpha; all caps; max = 2; min = 2
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:	positive integer; max = 3; min = 3
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

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

• 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/