Carriers (component)

From UG

[edit] Prerequisites, Classified As, Parent Mantis

Classified As: (large) component
Parent Mantis: 606

[edit] Scope

Cariers consists of 2 sub components:

Describe here only common and shared features of the above components. Example: "tabbed shell" for above and navigation above it.

[edit] Business Needs and Business Requirements

Have an area in the Admin section of CyberTrax that can be used to manage the names of all carriers. A carrier is an airline &/or a steamship line.

Each carrier has a specific code that's used identify them within the transportation industry. Their names do not need to be unique, as it's possible to have 1 airline and/or steamship line with more than 1 code to identify them.

Need ability to add, edit, delete, archive & restore all carriers.

[edit] Technical Requirements

This section is defined by Systems Architect. It is written after #Business Requirements are defined.

[edit] Technical Specification

This section is defined by Systems Analyst. It contains detailed technical design is written after #Business Requirements and #Technical Requirements are defined.

[edit] Summary

[edit] User Interface and Functionality

[edit] Entities and Attributes

[edit] Special Cases and Misc

[edit] Look And Feel

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

[edit] Figures

[edit] Figure 1:

[edit] Questions and RFC

[edit] Known Non Critical Bugs

[edit] Links to Archived / Old specs

[edit] History

[edit] This doc has been created

--Alex 21:08, 21 January 2010 (UTC)

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

[edit] Replace old User Interface with a "standard CT2 UI"