Carriers (component)

From UG

Revision as of 18:24, 21 January 2010 (edit) Alex (Talk | contribs) ← Older edit		Current revision as of 16:37, 26 September 2011 (edit) (undo) Denise (Talk | contribs) (→History)
(6 intermediate revisions not shown)
Line 2:		Line 2:
-	== Mantis ==	+	== Prerequisites, Classified As, Parent Mantis ==
-	[http://mantis.jaguarfreight.com/mantis/view.php?id=55 0000055(Admin)]	+
-	== Business Needs and Requirements BNR ==	+	* Classified As:  (large) [[component]]
		+	* Parent Mantis: [http://mantis.jaguarfreight.com/mantis/view.php?id=606 606]
-	== Technical Specification TS ==	+	=== Scope ===
-	== Dev and History ==	+	Cariers consists of 2 sub components:
		+	* [[Airlines (component)]]
		+	* [[Steamshiplines (component)]]
-	=== Ver 2.0 ===	+	Describe here only common and shared features of the above components. Example: "tabbed shell" for above and navigation above it.
-	* Replace old User Interface with a "standard CT2 UI"	+
-	* mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=1570	+	== 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 ===
		+
		+	--[[User:Alex|Alex]] 21:08, 21 January 2010 (UTC)
		+
		+
		+	=== Re-design (Tweak) (Spec Update): ..... <summary> ..... ===
		+
		+
		+	===  Replace old User Interface with a "standard CT2 UI" ===
		+
		+	--[[User:Alex|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
		+
		+	=== 0002658: (Carriers) Add archive option for duplicate carriers that are already used in the system ===
		+
		+	*Currently there are only options to Add Edit and Remove a carrier.  We need options to be able to archive a carrier that's no longer being used in transportation.
		+
		+	*WU: ?

---

Current revision as of 16:37, 26 September 2011

Contents 1 Prerequisites, Classified As, Parent Mantis 1.1 Scope 2 Business Needs and Business Requirements 2.1 Technical Requirements 3 Technical Specification 3.1 Summary 3.2 User Interface and Functionality 3.3 Entities and Attributes 3.4 Special Cases and Misc 4 Look And Feel 5 Figures 5.1 Figure 1: 6 Questions and RFC 7 Known Non Critical Bugs 8 Links to Archived / Old specs 9 History 9.1 This doc has been created 9.2 Re-design (Tweak) (Spec Update): ..... <summary> ..... 9.3 Replace old User Interface with a "standard CT2 UI" 9.4 0002658: (Carriers) Add archive option for duplicate carriers that are already used in the system

[edit] Prerequisites, Classified As, Parent Mantis

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

[edit] Scope

Cariers consists of 2 sub components:

• Airlines (component)
• Steamshiplines (component)

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"

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

[edit] 0002658: (Carriers) Add archive option for duplicate carriers that are already used in the system

• Currently there are only options to Add Edit and Remove a carrier. We need options to be able to archive a carrier that's no longer being used in transportation.

• WU: ?