What Yuan is asking are software requirements, which is why we are creating a
software architect coordinator role.
I do agree that is a missing link with the project and needs to coordinate with
the use case and target architecture subcommittees.
Mazin
On Nov 9, 2017, at 7:47 AM, Alla Goldner
Hi Yuan,
We can definitely consider this, though I believe that the specific information
you require below belongs to the next level of details. Perhaps even more
points will be raised when we present it.
And, as I said, this is “endorsement” not “approval”, and definitely needs
future
Hello
As we are discussing branching topics for the TSC Call today, I would like to
share some vision from a service provider perspective.
We intend to use Amsterdam Release for internal POC and first trial to
demonstrate the capabilities to operational teams, to educate...While I know
some
Hi Alla,
Thank for your reply, it's clear to me. I does not object we bring the
requirements to TSC for approval but from my view, the requirements need next
level of detials before it goes to component design. The requirements looks too
generic for different project teams reaching
Sorry I have not been able to get this out for a couple of days.
# opened Requestor Subject Status Owner last update Last
Updated By status
40696 5/10/17 phrobb (Phil Robb) Fwd: Need of Swagger for ONAP open
KennyPaul 11/1/17 KennyPaul Meeting held
