User story : Requirements check

<<< Back to [[Final soa model design]]

AXXX (rather EasiFab or CXXXXX) - requirements check

As an SOA business architect / "product owner",

I want to check whether everything expected has been done (developed / tested? / deployed ??) and possibly metrics on its progress, so that I know what remains to do to meet the SOA requirements
and up to SLA requirements
- => manual process of informal requirements checking
- => vs auto checking : wsdl or more, ex that it is a SOAP endpoint or that delivered / deployed workflows match the Design phase partioning between platforms...
I want to be notified of ...

As a provider impl's development team member,

I want to be notified of ... if my impl doesn't meet requirements, so that I can patch it

As a platform operator,

I want to be notified of ... if my platform (monitoring-emitted SOA-level SLA events) doesn't meet requirements, so that I can improve it

=> requirements / expectations architecture

expectations are rules put in design phase (resp. impl or depl...), automated / using defaults / profiles or not, and checked later :

in depl (warning to be approved if any consumption without exchange in a given / all test),
impl (warning to be approved if any consumption without provider injection),
or even design (no consumption without provider set)

they come from :

they are checked by different archi components for each of :

(for design stuff ?) when anything changes in the model, including additional / requirements
(for impl stuff ?) after / in CI (Jenkins) or scheduled sanity check (Nuxeo)
(for runtime stuff !) reactively in MonitoringProxy / Jasmine and evaluated state updated to EasySOA
NOTE MKA Architectural requirement = validation must be available for EasySOA light developments, EasySOA Integration developments, External services