Are Team Areas and Components mandatory?
I continue playing around with RTC 2.0 concepts and I would appreciate
if you can confirm me these two assertions:
- You can work with a Project Area without any Team Areas. It isn't
mandatory to have a Team Area defined in a Project Area. Of course, it
is less flexible but for simple and small projects could be enough. Just
having a Project Area you can define a stream, members with different
roles, etc.... Am I right?
- It is mandatory to have at least one Component in a stream. It isn't
possible to share any code into a stream if that stream hasn't a
Component defined. So, although my development could be small and simple
(not needing a flexible structure based in different Components) I have
to define at least one Component were deliver all the code. Am I right?
I was not able to find a document or tech note with these assertions.
Thanks in advance,
Chemi.
if you can confirm me these two assertions:
- You can work with a Project Area without any Team Areas. It isn't
mandatory to have a Team Area defined in a Project Area. Of course, it
is less flexible but for simple and small projects could be enough. Just
having a Project Area you can define a stream, members with different
roles, etc.... Am I right?
- It is mandatory to have at least one Component in a stream. It isn't
possible to share any code into a stream if that stream hasn't a
Component defined. So, although my development could be small and simple
(not needing a flexible structure based in different Components) I have
to define at least one Component were deliver all the code. Am I right?
I was not able to find a document or tech note with these assertions.
Thanks in advance,
Chemi.
5 answers
jlemieux wrote:
Thanks. I am finding a problem with this option. And it is I don't see
how to move Operation Behavior from Team Configuration to Project
Configuration so Preconditions for operations such Deliver (server) can
be defined. I asked this in a different thread (Subject: -
Adding more operations to Operation Behavior table (2.0M3)).
If that is not possible, then, decide to use just a Project Area could
be very restrictive. Any idea?
Thanks again,
Chemi.
- yes, you can have a project area and all artifact types can now be
associated with a project.
Thanks. I am finding a problem with this option. And it is I don't see
how to move Operation Behavior from Team Configuration to Project
Configuration so Preconditions for operations such Deliver (server) can
be defined. I asked this in a different thread (Subject: -
Adding more operations to Operation Behavior table (2.0M3)).
If that is not possible, then, decide to use just a Project Area could
be very restrictive. Any idea?
Thanks again,
Chemi.
jlemieux wrote:
Hummm... I will try again then. I created a Project Area with Eclipse
Way Process, removed the Team Area and when I deliver something to the
Stream I am not forced to associate a WorkItem. I thought this was part
of the Eclipse Way Process by default and it was not working because I
hadn't a Team Area. I will come back with any news.
Thanks,
Chemi.
Although maybe not the best name, the "Operation Behavior"
node under Team Configuration actually applies to the project area as
well. So you won't loose function and can enable pre/post conditions
when there are no team areas.
Hummm... I will try again then. I created a Project Area with Eclipse
Way Process, removed the Team Area and when I deliver something to the
Stream I am not forced to associate a WorkItem. I thought this was part
of the Eclipse Way Process by default and it was not working because I
hadn't a Team Area. I will come back with any news.
Thanks,
Chemi.
Chemi wrote:
Forget it, you are correct. I was not asked for a description because I
was sharing the project for the first time. Now, after I modified
something, I was required to describe the change.
Thanks,
Chemi.
jlemieux wrote:
Although maybe not the best name, the "Operation Behavior"
node under Team Configuration actually applies to the project area as
well. So you won't loose function and can enable pre/post conditions
when there are no team areas.
Hummm... I will try again then. I created a Project Area with Eclipse
Way Process, removed the Team Area and when I deliver something to the
Stream I am not forced to associate a WorkItem. I thought this was part
of the Eclipse Way Process by default and it was not working because I
hadn't a Team Area. I will come back with any news.
Thanks,
Chemi.
Forget it, you are correct. I was not asked for a description because I
was sharing the project for the first time. Now, after I modified
something, I was required to describe the change.
Thanks,
Chemi.