OSCL Requirements

[philchudley]

Hi All

Been trying out the Cloud Services and OSLC in EA version 11, and it works just fine

The data transferred for a requirement is defined in XML, is it possible to add tagged values to this structure? If so how?

If not, are tagged values likely to be supported in the future?

Cheers

[Ian Mitchell]

Sorry to interrupt this discussion, but do you have a way to demonstrate this new feature in action? What would be a compelling use case? Which other tool might we use ?

[Eve]

Phil,

I think at the moment it's just fields from the t_object table.

We'd love to hear feedback about how you want to use it. If that means allowing more customization, including tags or any other related table then we will see what we can do.

Ian,

Think of it on a similar level as XMI. The entire idea is about communication between tools but instead of exporting everything and importing into another tool it allows a client tool to work directly on the data provided by a server tool.

[philchudley]

Thanks Simon

Yes I would like to see some form of customisable fields for OSLC, a bit like the attribute customisation for the DOORS MDG or CSV

For example, EA knows what properties exist for a certain element (requirement + stereotype), and this could be used to populate a dialog of checkboxes to create, say, an OSCL specification (like CSV)

To summarise a method of customising OSCL in the same manner as CSV would be fantastic and a great selling point!

Shall I suggest this through the formal channels?

All the best