Airlines (component)

From UG

(Difference between revisions)

Jump to: navigation, search

Revision as of 00:36, 24 January 2010

1 Classified As, Parent Mantis, Prerequisites
2 Business Needs and Requirements
3 Technical Notes from Systems Architect
4 Technical Specification (TS)
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

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

These are standard windows. See Use Cases.

TS: Functionality

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

UC1: Find Airline

scroll up / down
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

set some fields in invalid type/format
click on "OK"
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

Questions

RFC and Ideas for Future

Known Non Critical Bugs

History

Section maintained by:	In completed state?:
TBD	Yes

Links to Archived / Old specs