neos team mailing list archive

[Johannes Wettinger <revager@xxxxxxxxxxxxxx>]

Blueprint changed by Johannes Wettinger:

Whiteboard changed:
  1. REQUIREMENT & SPECIFICATION
  
  Inside the 'findings' tab of the protocol window the last findings
  should be visible with their most important details (finding's number,
  severity and the beginning of the description). This is the findings'
  compact view. Only one finding should be displayed in edit view at the
  same time. It's also possible to display all findings in compact view by
  collapsing the finding which is currently displayed in edit view. When a
  new protocol is created, the first finding is created automatically and
  displayed in edit view.
  
  Please find attached to this blueprint a prototype for the user
  interface.
  
  ----
  
  2. USE CASES
  
  2.1. ADD FINDINGS
  
  [ACTORS]
  Scribe
  
  [PRECONDITION]
  The application is running and shows the findings tab inside the protocol window for a particular review meeting. The first finding is created automatically and displayed in edit view.
  
  [NORMAL FLOW OF EVENTS]
  (1) The actor adds some details like its description and a reference to the first finding.
  (2) The actor clicks on "Add new finding" in order to add a new finding into the protocol.
  (3) The actor collapses the second finding.
  (4) The actor clicks on the compact view of the first finding.
  
  [POSTCONDITION]
  There are two findings displayed, the first in edit view, the second in compact view.
  
  [ALTERNATIVE FLOWS OF EVENTS]
  None.
  
  --
  
  2.2. DELETE FINDING IF THERE IS ONE INSIDE THE PROTOCOL ONLY
  
  [ACTORS]
  Scribe
  
  [PRECONDITION]
  The application is running and shows the findings tab inside the protocol window for a particular review meeting. There is one finding inside the protocol displayed in compact view.
  
  [NORMAL FLOW OF EVENTS]
  (1) The actor clicks on the compact view of the existing finding.
  (2) The actor clicks on "Remove this finding".
  (3) A dialog box is shown in order to confirm the removal of the finding.
  (4) The actor confirms the removal.
  
  [POSTCONDITION]
  The finding is not part of the protocol anymore. A new finding is created automatically and displayed in edit view.
  
  [ALTERNATIVE FLOWS OF EVENTS]
  (4b) The actor cancels the removal; in this case nothing changes inside the protocol.
  
  --
  
  2.3. DELETE FINDING IF THERE ARE MORE THAN ONE INSIDE THE PROTOCOL
  
  [ACTORS]
  Scribe
  
  [PRECONDITION]
  The application is running and shows the findings tab inside the protocol window for a particular review meeting. There are at least two findings inside the protocol displayed in compact view.
  
  [NORMAL FLOW OF EVENTS]
  (1) The actor clicks on the compact view of one existing finding.
  (2) The actor clicks on "Remove this finding".
  (3) A dialog box is shown in order to confirm the removal of the finding.
  (4) The actor confirms the removal.
  
  [POSTCONDITION]
  The selected finding is not part of the protocol anymore. All the other findings are shown in compact view.
  
  [ALTERNATIVE FLOWS OF EVENTS]
  (4b) The actor cancels the removal; in this case nothing changes inside the protocol.
  
  --
  
  2.4. CHANGE ORDER OF EXISTING FINDINGS
  
  [ACTORS]
  Scribe
  
  [PRECONDITION]
  The application is running and shows the findings tab inside the protocol window for a particular review meeting. There are exactly three findings (no. 1, no. 2 and no. 3) inside the protocol displayed in compact view.
  
  [NORMAL FLOW OF EVENTS]
  (1) The actor clicks on the compact view of finding no. 3.
  (2) The actor clicks on "Move top".
  (3) The actor clicks on "Move down".
  (4) The actor clicks on the compact view of finding no. 1.
  (5) The actor clicks on "Move bottom".
  (6) The actor clicks on "Move up".
  
  [POSTCONDITION]
  The findings are displayed in the following order inside the protocol: no. 3, no. 1, no. 2. Finding no. 1 is displayed in edit view; the other findings are displayed in compact view.
  
  [ALTERNATIVE FLOWS OF EVENTS]
  None.
  
  ----
  
  3. DESIGN & TECHNICAL SOLUTION
  
- <<TODO>>
+ First of all, we are going to "extract" the whole Findings tab of the
+ 'ProtocolFrame' class into a new class called 'FindingsTab'. Besides of
+ that, two new classes will be introduced:
+ 
+ * FindingPanel (abstract) - this class acts as superclass for the follwing two classes
+ * FindingCompactPanel (extends FindingCompactPanel) - this class represents the compact view of one finding
+ * FindingEditPanel (extends FindingEditPanel) - this class represents the edit view of one finding
+ 
+ Inside the 'FindingsTab' class we are going to implement a list of
+ findings like you can see it from the attached prototype.
  
  ----
  
  4. UNIT TESTING
  
  For this feature there is no unit testing because it is part of the user
  interface only.
  
  ----
  
  5. SYSTEM TEST
  
  This feature is tested by running each of the Use Cases defined above.
  The results of the execution(s) of this test will be recorded here.

-- 
Show the last findings with all details, not just its number
https://blueprints.launchpad.net/revager/+spec/spec-findings-list