Widget Copy Yes / No (feature)

From UG

(Difference between revisions)
Jump to: navigation, search
(Comments from Systems Analyst)
(Comments from Systems Architect)
Line 26: Line 26:
* Master ocean profile
* Master ocean profile
-
=== Comments from Systems Architect ===
+
== Comments from Systems Architect ==
# This feature is already implemented for CT ocean
# This feature is already implemented for CT ocean
# Now we need to describe existing behaviour
# Now we need to describe existing behaviour
Line 32: Line 32:
# Above description could be done in style similar as in [[Delivery Comment]]
# Above description could be done in style similar as in [[Delivery Comment]]
--[[User:Alex|Alex]] 13:46, 28 January 2010 (UTC)
--[[User:Alex|Alex]] 13:46, 28 January 2010 (UTC)
 +
 +
== Preliminary Design / Prototype ==
 +
Not needed. --[[User:Alex|Alex]] 13:51, 28 January 2010 (UTC)
 +
 +
== Detailed Design (Technical Specification) ==
== Technical Specification ==
== Technical Specification ==

Revision as of 13:51, 28 January 2010


Contents

Classified As and Parent Mantis

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.

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)

Technical Specification

Summary

User Interface and Functionality

Entities and Attributes

Special Cases and Misc

Look And Feel

Figures

Figure 1: UI

File:Terminal Yes No (feature) UI.JPG

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)

DB

Personal tools