neos team mailing list archive

[Davide Casciato <casciade@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>]

Blueprint changed by Davide Casciato:

Whiteboard changed:
  UI prototypes for this blueprint:
- http://bazaar.launchpad.net/~neos/%2Bjunk/development-
+ http://bazaar.launchpad.net/~neos/%2Bjunk/revager-dev-
  files/files/head%3A/blueprints-files/spec-redesign-first-screen/
  
- //prototypes will be commited this evening because i can't check in from
- my work place.
  
  1. REQUIREMENTS & SPECIFICATION
  Topic of this blueprint is the redesign of the AssistantDialog which opens up after starting the application. This feature has been discussed in the (FR) Bug #493797. 
  
  ----
  
  
  2. USE CASES
  
  
  2.1. SCHEDULE NEW REVIEW
  
  [ACTORS]
  Moderator
  
  [PRECONDITION]
  -The application is running
  -The assistant dialog is shown
  
  [NORMAL FLOW OF EVENTS]
  (1) While the actors cursor hovers over the 'Schedule new review'-button the description text for this function is shown in the header of the assistant dialog
  (2) The actor clicks on 'Schedule new review'
  (3) A new review is created
  (4) The mainframe in the so called moderator mode is shown
  
  [POSTCONDITION]
  A new review in the moderator mode has been arranged.
  
  [ALTERNATIVE FLOWS OF EVENTS]
  none
  
  --
  
  
  2.2. SCHEDULE NEW REVIEW ON QUICKSTART
  
  [ACTORS]
  Moderator and/or scribe
  
  [PRECONDITION]
  -The application is running
  -The assistant dialog is shown
  
  [NORMAL FLOW OF EVENTS]
  (1) While the actors cursor hovers over the 'Quickstart'-button the description text for this function is shown in the header of the assistant dialog.
  (2) The actor clicks on 'Quickstart'
- (3) A new review is created
- (4) The mainframe in the so called instant review mode is shown
+ (3) The actor enters his personal information and confirms his input.
+ (4) A new review is created
+ (5) The mainframe in the so called instant review mode is shown
  
  [POSTCONDITION]
  A new review in the instant review mode has been arranged.
  
  [ALTERNATIVE FLOWS OF EVENTS]
- none
+ (3a) The actor selects himself out of the address book and confirms
  
  --
  
  
  2.3. OPEN EXISTING REVIEW
  
  [ACTORS]
  Scribe
  
  [PRECONDITION]
  -The application is running
  -The assistant dialog is shown
  
  [NORMAL FLOW OF EVENTS]
  (1) While the actors cursor hovers over the 'Open existing review'-button the description text for this function is shown in the header of the assistant dialog.
  (2) The actor clicks on 'Open existing review'
- (3) The assistant dialog will change it's contents (See:prototype6b1a)
+ (3) The assistant dialog will change it's contents (See:prototype6b1_openReview)
  (4) The actor selects one file via file chooser and confirms his selection by clicking on the 'open'-button.
  (5)The selected review opens up in the mainframe.
  
  [POSTCONDITION]
  The selected review in the moderator mainframe has been opened up.
  
  [ALTERNATIVE FLOWS OF EVENTS]
- (4.a) The actor inserts the file path manually and confirms his input by clicking on the 'open'-button.
- (4.b) The actor selects one review out of the table and confirms his selection by clicking on the 'open'-button.
+ (4.b) The actor clicks on one review of the listed review-file-links.
  
  --
  
  
  2.4. SELECT LANGUAGE
  
  [ACTORS]
  User
  
  [PRECONDITION]
  -The application is running
  -The assistant dialog is shown
  
  [NORMAL FLOW OF EVENTS]
  (1) While the actors cursor hovers over the 'Select language'-button the description text for this function is shown in the header of the assistant dialog.
  (2) The actor clicks on 'Select language'
  (3) A popup with the selectable languages opens up
  (4) The user selects one of them and confirm his selection by clicking on the 'confirm'-button.
  (5) Regarding to his choice, the application will be updated after a restart of the application.
  
  [POSTCONDITION]
  The application will start in the selected language after a restart of the program.
  
  [ALTERNATIVE FLOWS OF EVENTS]
  (4.b) The user uses the 'cancel'-button or closes the pop-up.
  
  --
  
  
  2.5. OPEN ASPECTS MANAGER
  
  [ACTORS]
  User
  
  [PRECONDITION]
  -The application is running
  -The assistant dialog is shown
  
  [NORMAL FLOW OF EVENTS]
  (1) While the actors cursor hovers over the 'Open aspects manager'-button the description text for this function is shown in the header of the assistant dialog.
  (2) The actor clicks on 'Open aspects manager'
  (3) The aspects manager opens up in a new window.
  
  [POSTCONDITION]
  The focused and maximized aspects manager is shown. The application stays in it's state. This means that the empty mainframe with the assistant dialog is allready open but not focused.
  
  [ALTERNATIVE FLOWS OF EVENTS]
  none
  
  --
  
  
  2.6. CLOSE ASSISTANT
  
  [ACTORS]
  User
  
  [PRECONDITION]
  -The application is running
  -The assistant dialog is shown
  
  [NORMAL FLOW OF EVENTS]
  (1) The actor clicks the 'finish'-button and the assistant disappears
  (2) The maximized mainframe without contents, which was in the background is now focused. Only the menu is available.
  
  [POSTCONDITION]
  The maximized mainframe without contents, which was in the background is now focused. Only the menu is available.
  
  [ALTERNATIVE FLOWS OF EVENTS]
  none
  
  ----
  
  
  3. DESIGN & TECHNICAL SOLUTION
  Only existing SWING- and revager-components will be used.
  
  ----
  
  
  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.

-- 
(SPEC) Redesign the first screen
https://blueprints.launchpad.net/revager/+spec/spec-redesign-first-screen