Sure thing. One thing about the scenarios would be that although we have
described the scenarios we have, they are detailed. Also they express all
the scenarios which each domain has.
However in V1 we discussed and decided to keep some for v2 (eg. the
Chaining scenario, agent scenario). Having a space explaining the contents
of the v1 specs helps. Spec backlog may point the remaining scenarios and
there maybe prioritize whats high for v2. Saw the same in other specs as
well like CM, QM...

Thanks
Vaibhav



From:   Michael F Fiedler <[email protected]>
To:     Vaibhav Srivastava/India/IBM@IBMIN
Cc:     oslc-automation <[email protected]>
Date:   02/08/2012 03:38 AM
Subject:        Re: [Oslc-Automation] Propose: Supported scenario and examples
            page on     Wiki?



Agree completely on this.   We have a skeleton of a
samples/examples/guidance page started and can start adding content at any
time for review.'

http://open-services.net/bin/view/Main/AutoSpecificationV1Samples

For the scenarios, I think they may already be out there from our previous
discussion, but could use editing for consistency of terminology.   Let's
discuss in the next workgroup meeting if anyone wants to take ownership of
this.

Regards,
Mike

Michael Fiedler
IBM Rational Software
[email protected]
919-254-4170



             Vaibhav
             Srivastava
             <vaibhav.srivasta                                          To
             [email protected]>            oslc-automation
             Sent by:                  <[email protected]>
             oslc-automation-b         ,
             ounces@open-servi                                          cc
             ces.net
                                                                   Subject
                                       [Oslc-Automation] Propose:
             02/07/2012 04:36          Supported scenario and examples
             AM                        page on           Wiki?












Hi All,

For the automation wiki page, I would like to propose 2 new pages which may
help the end consumers

1) Supported Scenario for v1
Since Automation specs involves multiple domains (Build, QM, DevOps..) it
might be worth mentioning at a high level what scenario to expect
functionally available using V1 specs. This would utilize the automation
terminology along with mapping the domains specific terms. For an end
consumer, this will be one stop for understand what to expect when they
implement automation V1 specs.

2) Example implementation for v1 specs
At a high level, this space will give a step by step explanation for the
provider and consumer for implementation. Explaining how to query, what to
expect from the automation plan, how to find the Automation Request and
leading to completion of the scenario with the Automation result.

Going forward, we could extend the same wiki pages to elaborate the
complete v2, v3 specs...

Thoughts?

Thanks
Vaibhav


_______________________________________________
Oslc-Automation mailing list
[email protected]
http://open-services.net/mailman/listinfo/oslc-automation_open-services.net






Reply via email to