UC AWOB CM 08 SPEC Manage Working Group Projects

MPDL,GAVO

=R0.8=

Background
For background information for WG projects, consortium projects see Background

Actors

 * 1) Working Group (WG) Lead
 * 2) WG Manager
 * 3) WG Project Manager

Preconditions

 * 1) The system status of WG is open.
 * 2) The system status of consortium is open.

Steps

 * 1) Actor selects a working group of which actor is member of
 * 2) From page showing WG project list actor chooses an option to add a working group project (or create project).
 * 3) Actor is sent to standard "create project page".
 * 4) UC_AWOB_PM_01SPEC_Create_Project

Post conditions
For valid request:
 * 1) The system creates a project(similar to Create project use case).
 * 2) It appears on working group project list immediatelty.
 * 3) Default WG project status = ‘proposed’
 * 4) For setting WG project status see CM_08_4_Change_WG_Project_Status
 * 5) It appears on the project list in the actor’s personal workspace.
 * 6) It appears on what's new of the affected WG with category like ‘WG projects’.
 * 7) It is notified
 * 8) Whom:the WG manager of the affected WG only if he/she didn’t create the project
 * By
 * 1) Email: sender = the user who creates the project
 * 2) AWOB notification
 * 3) Depending on actor’s choice  the system  brings up
 * 4) ‘overview’ of new project if actor chose to go to ‘overview’ of the new project, or
 * 5) WG project list if actor chose to WG project list.

Actors
Any consortium members can view any WG project list.
 * 1) Consortium Lead
 * 2) Consortium Manager
 * 3) Consortium Project Manager
 * 4) Consortium Member

Steps

 * 1) Actors browse WG project list.
 * 2) For those projects which are not announced to consortium, yet, there shouldn't be any value on their consortium project status column.
 * 3) See the sketch of the GUI listed on Release 0.8 scope page.

Post conditions

 * 1) For some WG projects and WG members an option to announce to consortium is available
 * 2) See CM_08_5_Announce_Project_To_Consortium_From_WG

CM_08_3_Edit_Project_Metadata_in_WG
Until R0.7 both project/consortium lead and manager were able to edit project/consortium/WG metadata. However, the use case is changed so that only Project lead can change project metadata and the way to keep log of its metadata changes.

Actors

 * 1) Project Lead

Preconditions

 * 1) The selected project’s AWOB system status is ‘open’.
 * 2) The selected WG’s AWOB system status is ‘open’.
 * 3) The selected consortium’s AWOB system status is ‘open’.

Steps

 * 1) Actor can change the following metadata:
 * 2) Title
 * 3) Goal
 * 4) Status
 * 5) Submit.

Post conditions
The system does the followings:
 * 1) Save the change.
 * 2) Log the change in what’s new of the selected project. (in a category like project info)
 * 3) Synchronize WG project list according to the change.
 * 4) if the project is already listed in consortium projects
 * 5) Synchronize Consortium project list according to the change.

CM_08_4_Change_WG_Project_Status
‘WG Project Status’
 * 1) Enumeration(wording)
 * 2) Pending(default): actor awaits working group's acceptance
 * 3) Accepted
 * 4) Rejected
 * 5) Withdrawn

Actors
In the WG where a selected project is defined
 * 1) WG lead 
 * 2) WG manager
 * 3) Project Lead who has at least WG project manager privilege.
 * 4) The additional condition to a project lead is to provide preventive measures from users abusing the system. Eg., if a project lead sets WG project status of his/her project ‘accepted’ or  announce it to consortium without WG manager’s consent, a WG lead or manager can demote him/her to WG member so that in the future he/she cannot create a project in the WG.

Preconditions

 * 1) The selected project’s AWOB system status is ‘open’.
 * 2) The selected WG’s AWOB system status is ‘open’.
 * 3) The selected consortium’s AWOB system status is ‘open’.

Steps

 * 1) Actor changes ‘WG project status’ of a project from the WG project list.

Post conditions

 * 1) The system saves the change.
 * 2) The change shows up in what’s new of the WG where the project belongs to. (in a category like WG projects)
 * 3) Synchronize WG project list according to the change.
 * 4) If the status is ‘completed/cancelled’
 * 5) Is the project still editable? Yes. The awob system status of the project doesn’t change.
 * 6) Notify the change to
 * 7) Whom:whichever of the following roles changes the status, the other who didn’t change it gets notified.
 * 8) WG manager of the affected WG
 * 9) Project  lead:The rest of the project members will be most likely informed by the project lead in detail. Therefore, notify only the project lead
 * 10) By
 * 11)  AWOB message
 * 12)  email: sender=the user who changes the status
 * 13) Those who are the WG manager as well as the project lead of a project should receive only once(one email and one awob message)

CM_08_5_Announce_Project_To_Consortium
Use case for announcing a project approved in a WG to consortium-wide.

Actors

 * 1) WG lead
 * 2) WG manager
 * 3) Project Lead who has at least WG project manager privilege.

Preconditions

 * 1) The consortium’s AWOB system status is open.
 * 2) The WG project status of the project = ‘accepted’.

Steps

 * 1) From working group project list actor chooses an option to announce a selected project to consortium project list.
 * 2) Optionally, the actor sets the value of consortium project status of the affected project from consortium project list.
 * 3) By default consortium project status = ‘pending’

Post conditions

 * 1) The project shows up on ‘Consortium project list’.
 * 2) The change shows up in what’s new of the affected consortium. (in a category like consortium projects
 * 3) Notify the change to
 * 4) Whom:  whichever of the following roles announces the project, the others get notified.
 * 5) 	Consortium lead
 * 6) 	WG manager of the affected WG
 * 7) 	Project lead
 * 8) 	By
 * 9) 	 AWOB notification
 * 10) 	 Email: sender = the user who announces the project
 * 11) 	Those who have multiple roles should receive only once(one email and one awob message)

CM_08_6_Change_Consortium_Project_Status_of_WG_Created_Project
This use case is for changing consortium project status of a project created in WG-level. The use case for changing this status of a project created in consortium-level is in CM_03_4_Change_Consortium_Project_Status.

Actors

 * 1) Consortium Lead
 * 2) WG lead of the WG to which the project belongs AND either
 * 3) Consortium Manager OR
 * 4) Consortium Project Manager
 * 5) WG manager to which the project belongs AND either
 * 6) Consortium Manager OR
 * 7) Consortium Project Manager
 * 8) Project Lead  of the project AND either
 * 9) Consortium Manager OR
 * 10) Consortium Project Manager

Preconditions

 * 1) The consortium’s AWOB system status is open.
 * 2) The selected project is already announced in consortium project list.
 * 3) This is not the same as the project is created in a consortium level.
 * 4) The selected project’s AWOB system status is ‘open’.

Steps

 * 1) From consortium project list actor chooses an option to change consortium project status of a selected project.
 * 2) Actor updates it.

Post conditions

 * 1) The system saves the change.
 * 2) Synchronize the consortium project list accordingly.
 * 3) Synchronize the affected WG project list according to the change if a WG project list displays it in the interface.
 * 4) The change shows up in what’s new of the affected consortium. (in a category like consortium projects)
 * 5) Notify the change
 * 6) Whom:  whichever of the following roles announces the project, the others get notified.
 * 7) 	Consortium lead
 * 8) 	WG manager of the affected WG
 * 9) 	Project lead
 * 10) 	By
 * 11) 	 AWOB notification
 * 12) 	 Email
 * 13) 	Those who have multiple roles should receive only once(one email and one awob message)

CM_08_7_Change_Project_Overview
This use case is the same as changing ‘overview’ a stand-alone project which is already implemented.

Actors

 * 1) Project Lead
 * 2) Project manager