Re: Use cases and Blueprints

Margaret Chiosi <margaret.chiosi1@...>

Actually I would have thought integration meant ‘testing’ and functional meant architecture J

But as long as we define the different blueprints and the definition of them.


Thank You,

Margaret Chiosi

VP Open Ecosystem Team


Admin: Sophie Johnson


+1 (908) 541-3590


Futurewei Technologies, Inc.

Fixed Network Solution CC

400 Crossing Blvd

Bridgewater, NJ 08807

(cell) +1-732-216-5507



From: Seiler, Glenn [mailto:glenn.seiler@...]
Sent: Thursday, September 13, 2018 2:43 PM
To: Margaret Chiosi (A) <margaret.chiosi1@...>; main@...
Subject: RE: [Akraino Main] Use cases and Blueprints


I may have missed some threads, but I thought we were discussing

1)      Integration Blueprints (architecture)

2)      Functional Blueprints  (components)


I agree with some of the other comments that we risk spreading or diluting the definition of Blueprint to broadly and it can be very confusing.

I support the idea that blueprints are pretty specific, not just defining components that are integrated, but how they are intended to be used and deployed.

I’m not sure this would apply to an individual component (or functional) blueprint.




From: main@... [mailto:main@...] On Behalf Of Margaret Chiosi
Sent: Thursday, September 13, 2018 8:22 AM
To: main@...
Subject: Re: [Akraino Main] Use cases and Blueprints


I thought in email folks were ok with the following types of blueprint:
1. Architecture
2. components (Physical/virtual) supporting a specific 'use case'
3. Test

Join to automatically receive all group messages.