(SPEC) Add new mode "Revibe"

Registered by Johannes Wettinger on 2009-11-04

In the next release of RevAger a new mode will be added. The internal name of this mode is "Revibe". This mode is based on the already existing scribe mode and provides the possibility to do a kind of "desk test" of a given product. So the user can just review a product without organizing a review first.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Medium
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Approved
Series goal:
Accepted for 1.2
Implementation:
Implemented
Milestone target:
None
Started by
Johannes Wettinger on 2009-12-05
Completed by
Johannes Wettinger on 2009-12-05

Related branches

Sprints

Whiteboard

1. REQUIREMENT & SPECIFICATION

RevAger will include a mode for the immediate recording and checking of a software-product. For this feature, functions of the already existing modes 'Moderator' and 'Scribe' will be used, fractional modified and combined in the new mode 'Instant review' (temporary name):

* Planing of review-meetings
* Assigning roles to the attendees (scribe, author, reviewer, customer)
* Managing aspects/catalogs and assigning them to the reviewers
* Recording of findings
* Managing meetings and meeting protocols
* Defining meeting duration by setting begin and end time
* Exporting findings as CSV
* Exporting findings as PDF

----

2. USE CASES

2.1. CREATE NEW REVIEW IN INSTANT REVIEW MODE

* [ACTORS] Reviewer
* [PRECONDITION] The application is running, no review is opened and the assistant dialog is shown.
* [USUAL PROCEDURE] The actor selects the radiobutton 'New review' and confirms his decision by klicking on the 'Confirm'-button.
* [POSTCONDITION] A new review is created, the mainframe and the AttendeeDialog is visible.
* [ALTERNATIVE PROCEDURES] none

2.2. OPEN EXISTING REVIEW IN INSTANT REVIEW MODE

* [ACTORS] Reviewer
* [PRECONDITION] The application is running, no review is opened and the assistant dialog is shown.
* [USUAL PROCEDURE] The actor selects the radiobutton 'Open review' and selects the review file by entering a path, selecting a review file out of a directory or selecting one review out of the list of the latest reviews. To continue and load the review he has to klick on the 'Confirm'-button.
* [POSTCONDITION] A existing review is loaded and the mainframe is visible.
* [ALTERNATIVE PROCEDURES] none

2.3. MANAGE CATALOGS IN INSTANT REVIEW MODE

* [ACTORS] Reviewer
* [PRECONDITION] The application is running, no review is opened and the assistant dialog is shown.
* [USUAL PROCEDURE] The actor selects the radiobutton 'Manage aspects' and confirms his decision by klicking on the 'Confirm'-button.
* [POSTCONDITION] The aspects-manager is shown.
* [ALTERNATIVE PROCEDURES] none

We have deliberately omitted the specification of the remaining use-cases, because they were already specified in the previous software-progress.

----

3. DESIGN & TECHNICAL SOLUTION

Basis of the new mode will be the already existing scribe-mode. To realize the requirement above it will be modified like follows:

* Enabeling the textfields concerning to the product and review informations
* Adaptation of the toolbar by adding the 'New review' and 'Manage aspects'-buttons
* A new EditProtocol-button will open the protocol window of the currently selected meeting or protocol in the future
* Adding meetings will only be possible if all previous meetings have got a protocol.
* Managing present attendees will only be possible in the protocol window or via the aspects manager

Internally there will be a properties-file which defines the authorization of the new mode. This file will be used internally again.

The 'Instant Review'-mode will be available via the assistant dialog.

----

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.

5.1. TEST PROTOCOL 2009-11-30

[USE CASE 2.1] Ok, usual procedure; no errors
[USE CASE 2.2] Ok, usual procedure; no errors
[USE CASE 2.3] Ok, usual procedure; no errors

5.1. TEST PROTOCOL 2009-12-12

[USE CASE 2.1] Ok, usual procedure; no errors
[USE CASE 2.2] Ok, usual procedure; no errors
[USE CASE 2.3] Ok, usual procedure; no errors

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.