Airlines (component)

From UG

Revision as of 16:22, 29 March 2010 (edit) Montira (Talk | contribs) (→Figure 2: Edit Airline Local info) ← Older edit		Revision as of 16:47, 29 March 2010 (edit) (undo) Montira (Talk | contribs) (→Figure 2: Edit Airline Local info) Newer edit →
Line 278:		Line 278:
	=== Figure 2: Edit Airline Local info  ===		=== Figure 2: Edit Airline Local info  ===
-	[[]]	+	[[File:Airline.JPG]]
	== Questions  ==		== Questions  ==

---

Revision as of 16:47, 29 March 2010

Contents 1 Classified As, Parent Mantis, Prerequisites 2 Business Needs and Requirements 3 Technical Notes from Systems Architect 4 Technical Specification (TS) 4.1 TS: Summary 4.2 TS: User Interface 4.2.1 List All Airlines Panel 4.2.2 Edit Airlines Window 4.2.2.1 Name 4.2.2.2 Airline 2 Letter Code 4.2.2.3 Airline 3 Letter Numeric Code: 4.2.2.4 Carrier's headquarter address 4.2.2.5 Agent's IATA code 4.2.2.6 Carrier's account number 4.2.3 Add Airlines Window 4.2.4 Warning and Error Windows 4.3 TS: Functionality 4.3.1 UC1: Find Airline 4.3.2 UC2: Edit Airline. All fields are entered in a valid type/format. Click on "OK" 4.3.3 UC3: Edit Airline. All fields are entered in a valid format. Click on "Cancel" 4.3.4 UC4: Edit Airline. Some fields are entered in invalid type/format 4.3.5 UC: Archive and Unarchive 4.3.6 UC: TBD 4.3.7 TC: Set 2 airlines with the same code 4.3.8 TC: TBD 4.3.9 TC: Misc 4.4 Special Cases and Misc 5 Quality Assurance 6 Look And Feel 7 Figures 7.1 Figure 1: List Airlines 7.2 Figure 2: Edit Airline 7.3 Figure 2: Edit Airline Local info 8 Questions 9 RFC and Ideas for Future 10 Known Non Critical Bugs 11 History 11.1 Links to Archived / Old specs 11.2 Re-design (Tweak) (Spec Update): ..... <summary> ..... 12 Implementation 12.1 DB 12.2 Front End Code 12.3 Back End Code

Classified As, Parent Mantis, Prerequisites

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

• Prerequisites: none

Business Needs and Requirements

Section maintained by:	In completed state?:
Alex	Yes

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.

Technical Notes from Systems Architect

Section maintained by:	In completed state?:
Alex	Yes

This is a typical Admin component. Please apply standard patterns.

Technical Specification (TS)

Section maintained by:	In completed state?:
TBD	Yes

TS: Summary

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

Attribute:	Value:
widget type:	Window#Edit
caption:	Edit Airline
see Figure:	#Figure 2: Edit Airline

This window hosts the widgets below:

Name

Attribute:	Value:
widget type:	Textbox
adjusent label:	Name:
default:	pull from selected object
type/format/DB:	see Tbl Airline#Name
required?:	Y
validation type:	zk standard / on submit // TBD

Airline 2 Letter Code

Attribute:	Value:
widget type:	Textbox
adjusent label:	2 Letter Code:
default:	pull from selected object
type/format/DB:	see Tbl Airline#TwoLetterCode
required?:	Y
validation type:	stop on max / zk standard / on submit // TBD

Airline 3 Letter Numeric Code:

Attribute:	Value:
widget type:	Textbox
adjusent label:	Numeric Code:
default:	pull from selected object
type/format/DB:	see Tbl Airline#NumericCode
required?:	Y
validation type:	stop on max / zk standard / on submit // TBD

Carrier's headquarter address

Attribute:	Value:
widget type:	Textbox
adjusent label:	Carrier's headquarter address:
default:	pull from selected object
type/format/DB:	see Airline_bo#Carrier.27s_headquarter_address
required?:	N
validation type:	stop on max / zk standard / on submit // TBD

Agent's IATA code

Attribute:	Value:
widget type:	Textbox
adjusent label:	Agent's IATA code:
default:	pull from selected object
type/format/DB:	see Airline_bo#Agent.27s_IATA_code
required?:	N
validation type:	stop on max / zk standard / on submit // TBD

Carrier's account number

Attribute:	Value:
widget type:	Textbox
adjusent label:	Agent's IATA code:
default:	pull from selected object
type/format/DB:	see Airline_bo#Carrier.27s_account_number
required?:	N
validation type:	stop on max / zk standard / on submit // TBD

Add Airlines Window

This is the same component as #Edit Airlines Window but with all values defaulted to blank.

Warning and Error Windows

These are standard windows. See Use Cases.

TS: Functionality

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

UC1: Find Airline

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

UC2: Edit Airline. All fields are entered in a valid type/format. Click on "OK"

1/ Select airline from the list 2/ Click on *Add* button 3/ #Add Airlines Window appears 4/ set all fields in a valid type/format 5/ click on "OK" 6/ system silently closes the window; user can see that fields on #Add Airlines Window ARE updated

UC3: Edit Airline. All fields are entered in a valid format. Click on "Cancel"

1-4/ as in above UC 5/ click on "Cancel" 6/ system silently closes the window; user can see that fields on #Add Airlines Window ARE NOT updated

UC4: Edit Airline. Some fields are entered in invalid type/format

1-3/ as in UC2

1. set some fields in invalid type/format
2. click on "OK"
3. system gives Window#Error. Message specify WHAT filed and WHAT is the problem.

UC: Archive and Unarchive

• Apply standard archive functionality: Archive (Feature) .
• List ALL archived on #List All

UC: TBD

TBD

TC: Set 2 airlines with the same code

System must give Window#error saying: "Airline with this code already exists."

TC: TBD

TBD

TC: Misc

Here is the list of Standard TCs that can be applied for this component:

TBD

Special Cases and Misc

None.

Quality Assurance

Section maintained by:	In completed state?:	Last updated by/on:
TBD	Yes	--Alex 20:29, 23 January 2010 (UTC)

See list of major Use Cases and Test Cases defined in section #TS: Functionality .

Additional cases defined below:

TBD

Look And Feel

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

Section maintained by:	In completed state?:	Last updated by/on:
TBD	Yes	--Alex 20:29, 23 January 2010 (UTC)

Figures

Figure 1: List Airlines

Figure 2: Edit Airline

Figure 2: Edit Airline Local info

Questions

RFC and Ideas for Future

Known Non Critical Bugs

History

Section maintained by:	In completed state?:
TBD	Yes

Links to Archived / Old specs

None.

Re-design (Tweak) (Spec Update): ..... <summary> .....

<wiki date/signature>

• mantis: <link>
• Biz Req updated? N/Y
• Tech Spec updated? N/Y

Implementation

Section maintained by:	In completed state?:
TBD	Yes

DB

• see Tbl Airline

Front End Code

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

Back End Code

...