Carriers (component)
From UG
(→Prerequisites, Classified As, Parent Mantis) |
(→Business Needs and Business Requirements) |
||
| Line 16: | Line 16: | ||
== Business Needs and Business Requirements == | == 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. | ||
=== Technical Requirements === | === Technical Requirements === | ||
Revision as of 16:31, 26 September 2011
Contents |
Prerequisites, Classified As, Parent Mantis
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.
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.
Technical Requirements
This section is defined by Systems Architect. It is written after #Business Requirements are defined.
Technical Specification
This section is defined by Systems Analyst. It contains detailed technical design is written after #Business Requirements and #Technical Requirements are defined.
Summary
User Interface and Functionality
Entities and Attributes
Special Cases and Misc
Look And Feel
This section is to be written / defined by Graphic Designer and UI Designer.
Figures
Figure 1:
Questions and RFC
Known Non Critical Bugs
Links to Archived / Old specs
History
This doc has been created
--Alex 21:08, 21 January 2010 (UTC)
Re-design (Tweak) (Spec Update): ..... <summary> .....
Replace old User Interface with a "standard CT2 UI"
--Alex 21:08, 21 January 2010 (UTC)
- mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=1570
- Biz Req updated? N
- Tech Spec updated? N
