Blueprint overview/Introduction
< Target audience- anyone new to this Blue print and want to understand what this is about>
<Purpose- it should introduce what the blue print is about>about, use cases, business drivers and where it sits on the edge infrastructure>
<It should be readable by a semi technical audience , e.g. product marketing, business account executives etc>
Use Case
<use case 1>
<use case 2>
...
Business Drivers
Overall Architecture
<This could inform the non-technical audience, but now is more geared towards a more engaged, technical audience>
< Blue print's relation to Akraino generic architecture, how it relates to it >
< This section will use the Akraino architecture document as reference>
Platform Architecture
<Hardware components should be specified with model numbers, part numbers etc>
Software Platform Architecture
EDGE Interface
ETSI MEC Interaction
Virtual Infrastructure Management
Networking Technologies
SDN Controllers
Data Plane
...
<Software components with version/release numbers >
<EDGE Interface>
<ETSI MEC Interaction>
Hardware and Software Management
Hardware Dependencies
Software Dependencies
Deployment Architecture
Licensing
...