Airlines (component)

From UG

Revision as of 00:22, 24 January 2010 (edit) Alex (Talk | contribs) (→Edit Airlines Window) ← Older edit		Revision as of 00:23, 24 January 2010 (edit) (undo) Alex (Talk | contribs) (→Name) Newer edit →
Line 102:		Line 102:
	| required?:    || Y		| required?:    || Y
	|-		|-
-	| validation type:  || Textbox#hit_the_wall / zk standard / on submit  // [[TBD]]	+	| validation type:  || [[Textbox#hit_the_wall]] / zk standard / on submit  // [[TBD]]
	|}		|}

---

Revision as of 00:23, 24 January 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: Objects and Fields 4.2.1 Airline 4.3 TS: User Interface 4.3.1 List All Airlines Panel 4.3.2 Edit Airlines Window 4.3.2.1 Name 4.3.2.2 Airline 2 Letter Code 4.3.2.3 Airline 3 Letter Numeric Code: 4.3.3 Add Airlines Window 4.3.4 Warning and Error Windows 4.4 TS: Functionality 4.4.1 UC: Find Airline 4.4.2 UC: Edit Airline. All fields are entered in a valid format 4.4.3 UC: Edit Airline. Some fields are entered in invalid format 4.4.4 UC: Edit Airline. Some required fields are blank 4.4.5 UC: Archive and Unarchive 4.4.6 TC: Set 2 airlines with the same code 4.5 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 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: 606

• 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: Objects and Fields

Airline

Name

• type/format: alphanumeric; min=1 char; max=30 chars

2 Letter Code

• type/format: Datatypes#alpha; exactly 2 chars; all caps

3 Letter Numeric Code

• type/format: Datatypes#positive integer; exactly 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

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:	see #Airline object
required?:	Y
validation type:	Textbox#hit_the_wall / 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:	see #Airline object
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:	see #Airline object
required?:	Y
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

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

UC: Archive and Unarchive

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

TC: Set 2 airlines with the same code

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

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

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

...