6 Here is master list of all roles involved in ECOMP with DCAE:
10 - Component developer/expert - components are also referred to as
11 micro-services but include collectors, analytics
27 Person who knows the high-level technical requirements for DCAE's
28 upcoming release cycle and dictates the development needs. This person
29 is responsible for the service assurance flows. This person expresses
30 the nodes and connections of a flow at a high level in a new graph or an
31 existing graph and assigns nodes to component developer/experts to be
34 This person must know:
36 - What newly added flows should look like at a high level
38 - What changes that are needed to existing flows
40 - Target environments/sites/locations that need the flows at what SLA
42 - Data requirements e.g. volume, rate, format, retention
44 This person creates a top-level representation of the flow and assigns
45 the pieces to developers or experts for implementation.
48 Component developer/expert
49 --------------------------
51 Person who is responsible for defining an assigned node's subgraph.
54 - A developer who might be onboarding a new component or a new version
55 of an existing component to fulfill the system engineer's
58 - A domain expert who selects a suitable existing component, wires and
59 configures. This expert knows the intricacies of a class of
60 components (e.g. Acumos machine learning).
67 - The target DCAE runtime and can develop a component to successfully
70 - The DCAE onboarding process for components including the development
73 - Best practices of data flow management (data provenance?)
75 - Lifecycle of DCAE components specifically impact of changes to
76 existing running instances globally
78 - The resource requirement of the developed component
85 - The target DCAE runtime
87 - The technical capabilities of a set of components in order to best
90 - The technical needs of the set of components in order to properly
97 Person who is responsible for connecting remote nodes to flows and
98 configuring all nodes in a flow in the context of the flow and in the
99 context of the greater graph. An example of the former is connecting a
100 flow with a collector to a black boxed vMME. An example of the latter
101 is assigning the threshold to a threshold-crossing-analytics component
102 when it is connected to a specific VES collector who is connected to a
107 - The VNFs to monitor and the technical details to correctly connect
110 - Enough about the capability of a component and understands the
111 characteristics and requirements of a flow to properly
112 assign designer_editable configuration parameters
114 This person has the ability to promote flows through the development
115 process (i.e. FTL to IST to ETE) and will coordinate with testers to
116 make sure the progression happens.
121 Person who is responsible for testing a promoted new flow or newly
122 edited flow. Once the designer has promoted a flow to a tester's
123 environment, the tester will have ready access to the deployment
124 artifacts necessary to apply the runtime changes that will reflect the
125 flow design and verify the resulting functionality matches to the system
126 engineer's expectations.
128 Person knows and owns a DCAE runtime.
130 Read access to the design tool would be useful for troubleshooting.
136 Person who is responsible that DCAE both platform and service assurance
137 flows are all operational in production environments and locations.
138 Once a flow has been fully certified, the required deployment artifact
139 is provided to operations and operations is responsible for applying the
140 runtime changes to reflect the flow design.
142 Person knows and owns a DCAE runtime.
144 Read access to the design tool would be useful for troubleshooting.
152 Person who are accountable to the business of the successful delivery of
153 a set of service assurance flows. Read access to the design tool
154 specifically high level reports are useful to understand if goals are
155 being met and to better measure project success.
161 Person who is responsible for the development of the DCAE platform which
162 ranges from onboarding, design, and runtime. In the scope of onboarding
163 and design, they are also responsible (unless there's an internal
164 operational team) for the operational concerns which means the tooling
165 built in this effort will need to be continually supported.
166 Their **users** are all the above. The design tool is intended to span
167 across multiple environments thus must run where all the required