Widget Copy Yes / No (feature)

From UG

Revision as of 13:51, 28 January 2010 (edit) Alex (Talk | contribs) (→Comments from Systems Architect) ← Older edit		Revision as of 13:56, 28 January 2010 (edit) (undo) Alex (Talk | contribs) (→Technical Specification) Newer edit →
Line 38:		Line 38:
	== Detailed Design (Technical Specification) ==		== Detailed Design (Technical Specification) ==
-	== Technical Specification ==
-	=== Summary ===
-	=== User Interface and Functionality ===
-	=== Entities and Attributes ===
-	=== Special Cases and Misc ===	+	=== User Interface ===
		+	''No need to define [[widget]]s here, it is to be defind in [[Imp Tab]] component.
		+
		+	=== Functionality / Use Cases ===
		+
	=== Look And Feel ===		=== Look And Feel ===

---

Revision as of 13:56, 28 January 2010

Contents 1 Classified As and Parent Mantis 2 Business Needs 3 Business Requirements 4 Comments from Systems Architect 5 Preliminary Design / Prototype 6 Detailed Design (Technical Specification) 6.1 User Interface 6.2 Functionality / Use Cases 6.3 Look And Feel 6.4 Figures 6.4.1 Figure 1: UI 7 Questions and RFC 8 Known Non Critical Bugs 9 Links to Archived / Old specs 10 History 10.1 This doc has been created 10.2 Spec Update: : (Terminal Yes / No (feature)) Implement this feature for Master Terminals (Origin and Dest) 11 DB

Classified As and Parent Mantis

• Classified As: common feature
• Parent Mantis: 1692

Business Needs

Terminals (Origin and Dest) are additional optional CT milestones. We need to automate updating this fields to save time.

Business Requirements

• [r0] There are 2 pairs of Port /Terminal. They should behave identically:
  • Origin Terminal / Port Of Loading
  • Port Of Discharge / Destination Terminal

• [r1] By default any edits from Port should propagate into Terminal.

• [r2] System should provide option to make Terminal fields "independent from" Port fields. This could be done by adding Yes/No radio.

• [r3] See possible UI design here: #Figure 1: UI

So far there are 2 places where these fields appear:

• ocean CT profile
• Master ocean profile

Comments from Systems Architect

1. This feature is already implemented for CT ocean
2. Now we need to describe existing behaviour
3. Describe in details. For example - what happens with state of every field on change from Y to N? From N to Y?
4. Above description could be done in style similar as in Delivery Comment

--Alex 13:46, 28 January 2010 (UTC)

Preliminary Design / Prototype

Not needed. --Alex 13:51, 28 January 2010 (UTC)

Detailed Design (Technical Specification)

User Interface

No need to define widgets here, it is to be defind in Imp Tab component.

Functionality / Use Cases

Look And Feel

Figures

Figure 1: UI

Questions and RFC

Known Non Critical Bugs

Links to Archived / Old specs

History

This doc has been created

--Alex 19:54, 19 January 2010 (UTC)

Spec Update: : (Terminal Yes / No (feature)) Implement this feature for Master Terminals (Origin and Dest)

--Alex 19:54, 19 January 2010 (UTC)

• mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=1692
• Biz Req updated? Y
• Tech Spec updated? N

DB