Airlines (component)

From UG

Revision as of 18:45, 23 January 2010 (edit) Alex (Talk | contribs) (→Test Cases and QA) ← Older edit		Revision as of 18:46, 23 January 2010 (edit) (undo) Alex (Talk | contribs) (→Business Needs and Business Requirements) Newer edit →
Line 12:		Line 12:
	== Business Needs and Business Requirements ==		== Business Needs and Business Requirements ==
-	We need a place in the system where we manage Airlines. This is to be used on CT record, etc.	+	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.		Required functionality: list, add, edit, delete, archive.

---

Revision as of 18:46, 23 January 2010

Contents 1 Prerequisites, Classified As, Parent Mantis 2 Business Needs and Business Requirements 3 Technical Notes from Systems Architect 4 Technical Specification 4.1 Summary 4.2 Objects and Fields 4.2.1 Airline 4.3 User Interface and Functionality 4.3.1 List All 4.3.2 Add 4.3.3 Edit 4.3.4 Delete 4.3.5 Archive / Unarchive 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 8 Questions and RFC 9 Known Non Critical Bugs 10 Links to Archived / Old specs 11 History 11.1 This doc has been created 11.2 Re-design (Tweak) (Spec Update): ..... <summary> ..... 12 DB 13 Code

Prerequisites, Classified As, Parent Mantis

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

• Prerequisites:
  • none

Business Needs and Business 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.

Technical Notes from Systems Architect

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

Technical Specification

Summary

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

User Interface and Functionality

List All

See #Figure 1: List Airlines

• Columns: one per field

• Sort: every column, alphabetical

• Paging: none

Add

Edit

Delete

Archive / Unarchive

• Apply standard archive functionality: Archive (Feature) .

• List all archived on #List All

• Confirm Window

• Error Window

Special Cases and Misc

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

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