Difference between revisions of "Software Integration and Distribution: Roles"

From Gcube Wiki
Jump to: navigation, search
(Created page with 'a gCube release process includes several activities (e.g, development, build, testing, packaging, etc...) and each activity involves a number of different persons playing differe…')
 
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
a gCube release process includes several activities (e.g, development, build, testing, packaging, etc...) and each activity involves a number of different persons playing different roles. In this section we define a set of roles and their duties and responsibilities in release's activities. Where available, a binding between role and persons playing that role is provided.
+
The gCube release process includes several activities (e.g, development, build, testing, packaging, etc...) and each activity involves a number of different persons playing different roles. In this section we define a set of roles and their duties and responsibilities in release activities. When possible, name and contact of persons playing the different roles are provided.
  
 
== Release Roles in a nutshell  ==
 
== Release Roles in a nutshell  ==
  
[[Image:Release_cycle_roles.png|right]]
+
The Release Cycle procedure is overseen by [[Role Release Manager|Release Managers]] that manage the overall procedure progress and fulfill activities at project-scope. [[Role Subsystem Manager|Subsystem Managers]] play a role similar to Release Managers, but in the scope of the assigned subsystem. [[Role Developer|Developers]] implement and fix the assigned components and usually provide documentation for them (playing, in fact, also the role of [[Role Documentation Author|Documentation Author]]). Testing team is formed by [[Role Tester|Testers]] who carry out tests against software candidate to be released. Finally the [[Role Documentation Editor|Documentation Editor]] manages entire documentation process.
 
+
Picture on the right shows which roles are defined for the Release Cycle procedure. The Release Cycle procedure is overseen by [[Role Release Manager|Release Managers]] that manage the overall procedure progress and fulfill activities at project-scope. [[Role Subsystem Manager|Subsystem Managers]] play a role similar to Release Managers, but in the scope of the assigned subsystem. [[Role Developer|Developers]] implement and fix the assigned components and usually provide documentation for them (playing, in fact, also the role of [[Role Documentation Author|Documentation Author]]). Testing team is formed by [[Role Tester|Testers]] who carry out tests against software candidate to be released. Finally the [[Role Documentation Editor|Documentation Editor]] manages entire documentation process.
+
  
  

Latest revision as of 08:25, 22 December 2016

The gCube release process includes several activities (e.g, development, build, testing, packaging, etc...) and each activity involves a number of different persons playing different roles. In this section we define a set of roles and their duties and responsibilities in release activities. When possible, name and contact of persons playing the different roles are provided.

Release Roles in a nutshell

The Release Cycle procedure is overseen by Release Managers that manage the overall procedure progress and fulfill activities at project-scope. Subsystem Managers play a role similar to Release Managers, but in the scope of the assigned subsystem. Developers implement and fix the assigned components and usually provide documentation for them (playing, in fact, also the role of Documentation Author). Testing team is formed by Testers who carry out tests against software candidate to be released. Finally the Documentation Editor manages entire documentation process.


Roles Description

Responsibilities and assignments for each role are described in details in following sub-sections: