RTC 3.x State model or Workflow model

Hi,

the easiest way to browse is creating a test project on a test server using the template you are interested in.

Use the administrative tools in the Eclipse Client or the Web UI to browse the workflows.

Verified is used in some workflows as a state after implemented. So a quality engineer could verify that something got implemented.

"Triaged" is typically used after something was put into the backlog as a state that it has been looked at but is waiting for being planned.

Ralph

Hello all,

Looking around RTC 3.x. Can someone point me to where in the documentation I can find out the EXACT workflow of the states in Team Concert for SCRUM, OpenUp and FormalPM? I need to know ASAP to show our quality team, but when looking at the process templates, there is no clear order of states and transitions. (this state is first, then this action goes to this, etc...)

thanks....

EDIT: Can someone explain Verified? Where does this play a role? The same for Triage?

What I am looking for is something like our current workflow:
New->Assigned->TurnedIn->Inspected->Evaluated->Closed.

It is confusing to look at the workflow (state machine matrix) and follow the progression. I ended up modeling it in visio for the simple team process, the scrum workflows might be different, I havn't modeled them yet.

Here's what I came up with:
action-->State--action-->State

initialize-->New--start working-->In Progress--resolve-->Resolved--triage-->Triaged--verify-->Verified--close-->Closed

That being the default path (or close to it, not accounting for alternate flows). There are additional/alternate actions to bypass some states and to loop back from others, in addition to having a reopen path (state & action).

Verified--reopen-->Reopened--start working-->In Progress


It would be nice to have a workflow modeler that allows for drag and drop workflow definition and visualiztion, quite surprising that this is not a feature in RTC or CQ for that matter.....

Thanks Chris for feeling my pain. :-)

You should create a WI for your modeling suggestion, maybe they can do something with RSA...

Anyway, I was in the middle of doing this the "easy" way as rschoon suggested:
-Find a server
-Install and configure software
-create projects for interested process
-model your own outcome of each state model workflow

but I thought it would have been modeled or documented somewhere by now. :-(

Anyway, thanks for the help...

SFII

It is confusing to look at the workflow (state machine matrix) and follow the progression. I ended up modeling it in visio for the simple team process, the scrum workflows might be different, I havn't modeled them yet.

Here's what I came up with:
action-->State--action-->State

initialize-->New--start working-->In Progress--resolve-->Resolved--triage-->Triaged--verify-->Verified--close-->Closed

That being the default path (or close to it, not accounting for alternate flows). There are additional/alternate actions to bypass some states and to loop back from others, in addition to having a reopen path (state & action).

Verified--reopen-->Reopened--start working-->In Progress


It would be nice to have a workflow modeler that allows for drag and drop workflow definition and visualiztion, quite surprising that this is not a feature in RTC or CQ for that matter.....

:D

Hi,

I am with you about visualizing the workflows. Would be great to have something. I know that people had created extensions to modeling and other tools to visualize, model and even update the workflows in several tools in the past. Maybe someone starts a community effort.

Otherwise, I am not aware of a documentation for the processes except whatever has been attached to the template itself. That does not necessarily mean, there is none.....

Setting up a test server on your local machine, provided it has a reasonable amount of memory is not that complicated. So I thought that would be a reasonable way to peek into the process configurations. Maybe I am wrong, because I have done that so often.

Feel free to create enhancement requests for Team Concert.

Thanks,

Ralph

Thanks Chris for feeling my pain. :-)

You should create a WI for your modeling suggestion, maybe they can do something with RSA...

Anyway, I was in the middle of doing this the "easy" way as rschoon suggested:
-Find a server
-Install and configure software
-create projects for interested process
-model your own outcome of each state model workflow

but I thought it would have been modeled or documented somewhere by now. :-(

Anyway, thanks for the help...

SFII

It is confusing to look at the workflow (state machine matrix) and follow the progression. I ended up modeling it in visio for the simple team process, the scrum workflows might be different, I havn't modeled them yet.

Here's what I came up with:
action-->State--action-->State

initialize-->New--start working-->In Progress--resolve-->Resolved--triage-->Triaged--verify-->Verified--close-->Closed

That being the default path (or close to it, not accounting for alternate flows). There are additional/alternate actions to bypass some states and to loop back from others, in addition to having a reopen path (state & action).

Verified--reopen-->Reopened--start working-->In Progress


It would be nice to have a workflow modeler that allows for drag and drop workflow definition and visualiztion, quite surprising that this is not a feature in RTC or CQ for that matter.....

:D

Ralph,

Yes, the lack of the workflow modeler goes way back to the legacy tools. If I recall there was a tech rep who developed a Rose modeler extension for CQ, but that was more targeted at getting a better understanding of the schema and user DB design and relationships.

Definitely an interesting idea for a community extension for the Jazz products though, and in the interim logging an RFE for sure.

I believe for the short term the struggle is not having the WI workflows documented for the out-of-the-box process templates. It is a bit time consuming to have to model it just to be able to communicate it to stakeholders (understandable time sink in a custom workflow).

Thanks for weighing in.

-chris

http://blog.stastnarodina.com/honza-en/category/rational-team-concert/
helps a little.
also add your support to
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=100895

On 15/01/2011 1:38 AM, chrismorgan03 wrote:

Ralph,

Yes, the lack of the workflow modeler goes way back to the legacy
tools. If I recall there was a tech rep who developed a Rose modeler
extension for CQ, but that was more targeted at getting a better
understanding of the schema and user DB design and relationships.

Definitely an interesting idea for a community extension for the Jazz
products though, and in the interim logging an RFE for sure.

I believe for the short term the struggle is not having the WI
workflows documented for the out-of-the-box process templates. It is
a bit time consuming to have to model it just to be able to
communicate it to stakeholders (understandable time sink in a custom
workflow).

Thanks for weighing in.

-chris

http://blog.stastnarodina.com/honza-en/category/rational-team-concert/
helps a little.
also add your support to
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=100895

Thanks! Also, I am the last comment on the WI asking for it to be brought out of Backlog...

SFII

Check out the Jazz Links section of my blog for things like this (https://dtoczala.wordpress.com/jazz-links/). You should go and follow the link for the workflow visualizer. It will do what you are asking.

 There is a Process Analyzer for Rational Team Concert which gives you the ability to generate workflow diagrams that novice users can understand.  In addition to the visualized workflows, additional information on each state, action and attribute is available in the licensed version.