| <html> |
| <!-- |
| Copyright (c) 2004, 2007 Boeing. |
| All rights reserved. This program and the accompanying materials |
| are made available under the terms of the Eclipse Public License v1.0 |
| which accompanies this distribution, and is available at |
| http://www.eclipse.org/legal/epl-v10.html |
| Contributors: |
| Boeing - initial API and implementation |
| --> |
| <head> |
| <title>Configure Team Definition</title> |
| <LINK rel="stylesheet" type="text/css" href="../../osee.help/html/style.css"> |
| </head> |
| |
| <body> |
| <h1>Configure Team Definition</h1> |
| <h2>Purpose</h2> |
| The Team Definition artifact specifies leads and members that are assigned to work on related Actionable Items. |
| <h2>How to do it</h2> |
| <ul> |
| <li>Team Definitions should match company organizational structure.</li> |
| <li>Attributes</li> |
| <ul> |
| <li>Name:[uniquely recognizable team name]</li> |
| <li>ats.Full Name:[optional full name]</li> |
| <li>ats.Description:[desc]</li> |
| <li>ats.Active:[yes]</li> |
| <li>ats.Team Uses Version:[yes if want to use release/build planning]</li> |
| </ul> |
| <li>Relations</li> |
| <ul> |
| <li>DefaultHeirarchy: Relate to parent team or top level "Teams"</li> |
| <li>TeamDefinitionToVersion: Relate to current and future VersionArtifacts</li> |
| <li>TeamLead: Relate to one or more team leads. These individuals will have priviledged edit and perform the Endorse state by default.</li> |
| <li>TeamMember: Relate to one or more team members. These individuals will have ability to priviledged edit Workflows created by themselves against the team they belong to.</li> |
| <li>Work Item.Child: Relate to a single "Work Flow Definition" artifact that defines the workflow |
| that will be used for this team.</li> |
| </ul> |
| </ul> |
| </body> |
| </html> |
| |
