Widget Copy Yes / No (feature)

From UG

Revision as of 20:41, 19 January 2010 (edit) Alex (Talk | contribs) (→Classified As and Parent Mantis) ← Older edit		Revision as of 13:46, 28 January 2010 (edit) (undo) Alex (Talk | contribs) (→Comments from Systems Analyst) Newer edit →
Line 26:		Line 26:
	* Master ocean profile		* Master ocean profile
-	=== Comments from Systems Analyst ===	+	=== Comments from Systems Architect ===
-	Not all details are captured in above requirements. For example, should system clear Terminal fields after user selects from Y to N? Same question for change of state from N to Y, etc.	+	# This feature is already implemented for CT ocean
		+	# Now we need to describe existing behaviour
		+	# Describe in details. For example - what happens with state of every field on change from Y to N? From N to Y?
		+	# Above description could be done in style similar as in [[Delivery Comment]]
		+	--[[User:Alex|Alex]] 13:46, 28 January 2010 (UTC)
	== Technical Specification ==		== Technical Specification ==

---

Revision as of 13:46, 28 January 2010

Contents 1 Classified As and Parent Mantis 2 Business Needs 3 Business Requirements 3.1 Comments from Systems Architect 4 Technical Specification 4.1 Summary 4.2 User Interface and Functionality 4.3 Entities and Attributes 4.4 Special Cases and Misc 4.5 Look And Feel 4.6 Figures 4.6.1 Figure 1: UI 5 Questions and RFC 6 Known Non Critical Bugs 7 Links to Archived / Old specs 8 History 8.1 This doc has been created 8.2 Spec Update: : (Terminal Yes / No (feature)) Implement this feature for Master Terminals (Origin and Dest) 9 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)

Technical Specification

Summary

User Interface and Functionality

Entities and Attributes

Special Cases and Misc

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