Statistics
| Revision:

root / branches / modelio3.6.x / src / main / resources / org / modelio / togaf / i18n / messages.properties @ 240

History | View | Annotate | Download (87.4 KB)

1
Mdac.TogafPropertyPage.Label=Togaf
2
Ui.Command.ArchitectureToJavaTransformation.Label=Transformation of Architecture model to Java implementation
3
Ui.Command.ArchitectureToJavaTransformation.Slot=Model transformation
4
Ui.Command.ArchitectureToJavaTransformation.Tooltip=Model transformation
5
Ui.Command.BusinessEntityCatalog.Label=Business Entities Catalog
6
Ui.Command.BusinessEntityCatalog.Slot=Document production|Catalogs (Modelio)
7
Ui.Command.BusinessEntityCatalog.Tooltip=Business Entities Catalog
8
Ui.Command.BusinessToExchangeDataTransformation.Label=Message generation from Business Entities
9
Ui.Command.BusinessToExchangeDataTransformation.Slot=Model transformation
10
Ui.Command.BusinessToExchangeDataTransformation.Tooltip=Message generation from Business Entities
11
Ui.Command.BusinessToPersistantTransformation.Label=Data Model generation from Business Entities
12
Ui.Command.BusinessToPersistantTransformation.Slot=Model transformation
13
Ui.Command.BusinessToPersistantTransformation.Tooltip=Data Model generation from Business Entities
14
Ui.Command.ComponentCatalog.Label=Component Catalog
15
Ui.Command.ComponentCatalog.Slot=Document production|Catalogs (Modelio)
16
Ui.Command.ComponentCatalog.Tooltip=Component Catalog
17
Ui.Command.InformationServiceCatalog.Label=Information Service Catalog
18
Ui.Command.InformationServiceCatalog.Slot=Document production|Catalogs (Modelio)
19
Ui.Command.InformationServiceCatalog.Tooltip=Information Service Catalog
20
Ui.Command.ProductActorRoleMatrix.Label=Actor - Role Matrix
21
Ui.Command.ProductActorRoleMatrix.Slot=Document production|Matrices
22
Ui.Command.ProductActorRoleMatrix.Tooltip=Actor - Role Matrix
23
Ui.Command.ProductApplicationInteractionMatrix.Label=Application - Interaction Matrix
24
Ui.Command.ProductApplicationInteractionMatrix.Slot=Document production|Matrices
25
Ui.Command.ProductApplicationInteractionMatrix.Tooltip=Application - Interaction Matrix
26
Ui.Command.ProductBusinessCatalog.Label=BusinessService - Function Catalog
27
Ui.Command.ProductBusinessCatalog.Slot=Document production|Catalogs
28
Ui.Command.ProductBusinessCatalog.Tooltip=Business Service - Function Catalog
29
Ui.Command.ProductBusinessInteractionMatrix.Label=Business - Interaction Matrix
30
Ui.Command.ProductBusinessInteractionMatrix.Slot=Document production|Matrices
31
Ui.Command.ProductBusinessInteractionMatrix.Tooltip=Business - Interaction Matrix
32
Ui.Command.ProductDataEntityBusinessFunctionMatrix.Label=Data Entity - Business Function Matrix
33
Ui.Command.ProductDataEntityBusinessFunctionMatrix.Slot=Document production|Matrices
34
Ui.Command.ProductDataEntityBusinessFunctionMatrix.Tooltip=Data Entity - Business Function Matrix
35
Ui.Command.ProductGoalCatalog.Label=Driver - Goal - Objective Catalog
36
Ui.Command.ProductGoalCatalog.Slot=Document production|Catalogs
37
Ui.Command.ProductGoalCatalog.Tooltip=Driver - Goal - Objective Catalog
38
Ui.Command.ProductLocationCatalog.Label=Location Catalog
39
Ui.Command.ProductLocationCatalog.Slot=Document production|Catalogs
40
Ui.Command.ProductLocationCatalog.Tooltip=Location Catalog
41
Ui.Command.ProductOrganizationCatalog.Label=Organization Catalog
42
Ui.Command.ProductOrganizationCatalog.Slot=Document production|Catalogs
43
Ui.Command.ProductOrganizationCatalog.Tooltip=Organization Catalog
44
Ui.Command.ProductProcessEventControlProductCatalog.Label=Process - Event - Control - Product Catalog
45
Ui.Command.ProductProcessEventControlProductCatalog.Slot=Document production|Catalogs
46
Ui.Command.ProductProcessEventControlProductCatalog.Tooltip=Process - Event - Control - Product Catalog
47
Ui.Command.ProductRoleCatalog.Label=Role - Actor Catalog
48
Ui.Command.ProductRoleCatalog.Slot=Document production|Catalogs
49
Ui.Command.ProductRoleCatalog.Tooltip=Role - Actor Catalog
50
Ui.Command.ProductRoleSystemMatrix.Label=Role - System Matrix
51
Ui.Command.ProductRoleSystemMatrix.Slot=Document production|Matrices
52
Ui.Command.ProductRoleSystemMatrix.Tooltip=Role - System Matrix
53
Ui.Command.ProductSystemDataMatrix.Label=Product - System - Data Matrix
54
Ui.Command.ProductSystemDataMatrix.Slot=Document production|Matrices
55
Ui.Command.ProductSystemDataMatrix.Tooltip=Product - System - Data Matrix
56
Ui.Command.ProductSystemFunctionMatrix.Label=System - Function Matrix
57
Ui.Command.ProductSystemFunctionMatrix.Slot=Document production|Matrices
58
Ui.Command.ProductSystemFunctionMatrix.Tooltip=System - Function Matrix
59
Ui.Command.ProductSystemOrganizationMatrix.Label=System - Organization Matrix
60
Ui.Command.ProductSystemOrganizationMatrix.Slot=Document production|Matrices
61
Ui.Command.ProductSystemOrganizationMatrix.Tooltip=Label=System - Organization Matrix
62
Ui.Command.ServiceDataCatalog.Label=Service Data Catalog
63
Ui.Command.ServiceDataCatalog.Slot=Document production|Catalogs (Modelio)
64
Ui.Command.ServiceDataCatalog.Tooltip=Service Data Catalog
65
Ui.Command.UseCasesCatalog.Label=Use Cases Catalog
66
Ui.Command.UseCasesCatalog.Slot=Document production|Catalogs (Modelio)
67
Ui.Command.UseCasesCatalog.Tooltip=Use Cases Catalog
68
Ui.Parameter.DisplayNote.Description=Display Information Notes in diagrams
69
Ui.Parameter.DisplayNote.Label=Information Notes in diagrams
70
Ui.Parameter.Mode.Description=TOGAF: Framework for Entreprise Architecture which provides a comprehensive approach to the design, planning, implementation, and governance of an enterprise information architecture./nSOA: Architectural style based on the concept of service, intended to simplify the interaction of brick architecture providing flexibility to the system./nBPM: Modeling the part of Enterprise Architecture related to corporate business, and the documents and diagrams that describe that architectural structure of business.
71
Ui.Parameter.Mode.Label=Point of view
72
Ui.Parameter.group=Interface
73
Ui.ModelSelectionGui.Shell=Modelio
74
Ui.ModelSelectionGui.Title=Point of view selection  
75
Ui.ModelSelectionGui.Message=
76
Ui.ModelSelectionGui.TogafLabel=TOGAF
77
Ui.ModelSelectionGui.TogafImage=/res/bpm/togaf32.png
78
Ui.ModelSelectionGui.TogafDescription=Framework for Entreprise Architecture which provides a comprehensive approach to the design, planning, implementation, and governance of an enterprise information architecture. 
79
Ui.ModelSelectionGui.SoaLabel=SOA Architect
80
Ui.ModelSelectionGui.SOAImage=/res/bpm/soa32.png
81
Ui.ModelSelectionGui.SOADescription=Architectural style based on the concept of service, intended to simplify the interaction of brick architecture providing flexibility to the system.
82
Ui.ModelSelectionGui.BPMLabel=BPM / Business Architecture
83
Ui.ModelSelectionGui.BPMImage=/res/bpm/bpm32.png
84
Ui.ModelSelectionGui.BPMDescription=Modeling the part of Enterprise Architecture related to corporate business, and the documents and diagrams that describe that architectural structure of business.
85
Ui.Command.CreateMatrix.Slot=Traceability Matrices
86
Ui.Command.CreateBusinessInteractionMatrix.Label=Business - Interaction Matrix
87
Ui.Command.CreateBusinessInteractionMatrix.Tooltip=Create Business - Interaction Matrix
88
Ui.Command.CreateActorRoleMatrix.Label=Actor - Role Matrix
89
Ui.Command.CreateActorRoleMatrix.Tooltip=Create Actor - Role Matrix
90
Ui.Command.CreateDataEntityBusinessFunctionMatrix.Label=DataEntity - BusinessFunction Matrix
91
Ui.Command.CreateDataEntityBusinessFunctionMatrix.Tooltip=Create DataEntity - BusinessFunction Matrix
92
Ui.Command.CreateSystemDataMatrix.Label=System - Data Matrix
93
Ui.Command.CreateSystemDataMatrix.Tooltip=Create System - Data Matrix
94
Ui.Command.CreateSystemOrganizationMatrix.Label=System - Organization Matrix
95
Ui.Command.CreateSystemOrganizationMatrix.Tooltip=Create System - Organization Matrix
96
Ui.Command.CreateRoleSystemMatrix.Label=Role - System Matrix
97
Ui.Command.CreateRoleSystemMatrix.Tooltip=Create Role - System Matrix
98
Ui.Command.CreateSystemFunctionMatrix.Label=System - Function Matrix
99
Ui.Command.CreateSystemFunctionMatrix.Tooltip=Create System - Function Matrix 
100
Ui.Command.CreateApplicationInteractionMatrix.Label=Application - Interaction Matrix
101
Ui.Command.CreateApplicationInteractionMatrix.Tooltip=Create Application - Interaction Matrix
102
module.start.error.title=Couldn''t start "{0}".
103
module.start.error.module = No license available for "{0}" module.\r\n\r\nDetail:\r\nNo valid feature found.\r\n\r\nFor more information, please contact Modeliosoft support team (support@modeliosoft.com).
104
Ui.Diagram.Drawing=Free drawing
105

    
106

    
107
PALETTE_Actor_Role=Actor - Role
108
PALETTE_Analyst=Analyst
109
PALETTE_Common=Common
110
PALETTE_Component=Component
111
PALETTE_Container=Container
112
PALETTE_Data=Data
113
PALETTE_Default=Default
114
PALETTE_Entity=Entity
115
PALETTE_Function=Function
116
PALETTE_Link=Link
117
PALETTE_Location=Location
118
PALETTE_Process=Process
119
PALETTE_Service=Service
120
PALETTE_ServiceData=ServiceData
121
PALETTE_Structure=Structure
122
PALETTE_NetworkNode=Network Node
123
PALETTE_System=System
124
PALETTE_BusinessElements=Business Elements
125
ApplicationArchitecture_COMMANDENAME=ApplicationArchitecture
126
ApplicationArchitecture_ERROR=Invalid owner element : Application Architecture
127
ApplicationArchitecture_NAME=Application Architecture
128
ApplicationArchitecture_Template=The application architecture is modeled under this domain. \nApplication components are the main elements modeled, with their provided or required IS services.\n\nDiagrams:\n- Solution Concept diagrams provide a high-level orientation of the solution that is envisaged in order to meet the objectives of the architecture engagement.\n- Application and User Location diagrams show the geographical distribution of applications.\n- Application and User Location diagrams show the geographical distribution of applications.\n- Enterprise Manageability diagrams show how one or more applications interact with application and technology components that support operational management of a solution.\n- Process/System Realization diagrams clearly depict the sequence of events when multiple applications are involved in executing a business process.\n- Project Context diagrams show the scope of a work package to be implemented as a part of a broader transformation roadmap.\n- Benefits diagrams show opportunities identified in an architecture definition, classified according to their relative size, benefit, and complexity. 
129
ApplicationArchitecture_TOOLTYPE=Application Architecture
130
ApplicationArchitectureAttribute_COMMANDENAME=ApplicationArchitectureAttribute
131
ApplicationArchitectureAttribute_ERROR=Invalid owner element : Application Attribute
132
ApplicationArchitectureAttribute_NAME=Application Attribute
133
ApplicationArchitectureAttribute_TOOLTYPE=Application Attribute
134
ApplicationArchitectureDomain_COMMANDENAME=ApplicationArchitectureDomain
135
ApplicationArchitectureDomain_ERROR=Invalid owner element : Application Domain
136
ApplicationArchitectureDomain_NAME=Application Domain
137
ApplicationArchitectureDomain_TOOLTYPE=Application Domain
138
ApplicationComponentOperation_COMMANDENAME=ApplicationComponentOperation
139
ApplicationComponentOperation_ERROR=Invalid owner element : Application Operation
140
ApplicationComponentOperation_NAME=Application Operation
141
ApplicationComponentOperation_TOOLTYPE=Application Operation
142
ApplicationLayer_COMMANDENAME=ApplicationLayer
143
ApplicationLayer_ERROR=Invalid owner element : Application Layer
144
ApplicationLayer_NAME=Application Layer
145
ApplicationLayer_Template=The application layer is related to the application models. The data architecture is in particular modeled under the \u0022data architecture\u0022 domain, where persistent data are defined. They can be derived from the business entities defined under the Business Layer/Business entities domain.\nThe application components and their architecture are defined under the \u0022Application Architecture\u0022 domain.
146
ApplicationLayer_TOOLTYPE=Application Layer
147
assigned_COMMANDENAME=Assigned
148
assigned_ERROR=Assigned : Actor/Package/Process -> Goal
149
assigned_NAME=Assigned
150
assigned_TOOLTYPE=Actor/Package/Process -> Goal
151
Assumes_COMMANDENAME=Assumes
152
Assumes_ERROR=Assumes : Actor -> Role
153
Assumes_NAME=Assumes
154
Assumes_TOOLTYPE=Actor -> Role
155
BusinessArchitecture_COMMANDENAME=BusinessArchitecture
156
BusinessArchitecture_ERROR=Invalid owner element : Business Architecture
157
BusinessArchitecture_NAME=Business Architecture
158
BusinessArchitecture_Template=In TOGAF, the Business Architecture defines the business strategy, governance, organization, and key business processes.\nAll these elements are modeled under this domain, with predefined subdomains.
159
BusinessArchitecture_TOOLTYPE=Business Architecture
160
BusinessAttribute_COMMANDENAME=BusinessAttribute
161
BusinessAttribute_ERROR=Invalid owner element : Attribute
162
BusinessAttribute_NAME=Attribute
163
BusinessAttribute_TOOLTYPE=Attribute
164
BusinessDataType_COMMANDENAME=BusinessDataType
165
BusinessDataType_ERROR=Invalid owner element : Business Data Type
166
BusinessDataType_NAME=Business Data Type
167
BusinessDataType_TOOLTYPE=Business Data Type
168
BusinessEntities_COMMANDENAME=BusinessEntities
169
BusinessEntities_ERROR=Invalid owner element : Business Entities
170
BusinessEntities_NAME=Business Entities
171
BusinessEntities_Template=Business Entities is related to TOGAF\u0027s Data Architecture. In this domain, data is modeled at a conceptual level. The focus is the notions that are handled in the business, their properties, associations lifecycles, etc. Information domains are structuring busines entities that are modeled using dedicated class diagrams.\nPersistency modeling is not the focus at this stage. You can use the \u0022Togaf\u0022 menu to automatically generate a persistency model within the Application Architecture, and/or to generate application components from the modeled Business Entities.
172
BusinessEntities_TOOLTYPE=Business Entities
173
BusinessEntity_COMMANDENAME=BusinessEntity
174
BusinessEntity_ERROR=Invalid owner element : Dusiness Entity
175
BusinessEntity_NAME=Business Entity
176
BusinessEntity_TOOLTYPE=Business Entity
177
BusinessInvariant_COMMANDENAME=BusinessInvariant
178
BusinessInvariant_ERROR=Invalid owner element : Invariant
179
BusinessInvariant_NAME=Invariant
180
BusinessInvariant_TOOLTYPE=Invariant
181
BusinessLayer_COMMANDENAME=BusinessLayer
182
BusinessLayer_ERROR=Invalid owner element : Business Layer
183
BusinessLayer_NAME=Business Layer
184
BusinessLayer_Template=The Business Layer domain contains the TOGAF Business architecture and Business Entities.\nIt is decomposed into the Business Architecture domain and the Business Entities domain, where the models are developped.
185
BusinessLayer_TOOLTYPE=Business Layer
186
BusinessOperation_COMMANDENAME=BusinessOperation
187
BusinessOperation_ERROR=Invalid owner element : Business Operation
188
BusinessOperation_NAME=Operation
189
BusinessOperation_TOOLTYPE=Operation
190
BusinessOrganizationDomain_COMMANDENAME=BusinessOrganizationDomain
191
BusinessOrganizationDomain_ERROR=Invalid owner element : Organization Domain
192
BusinessOrganizationDomain_NAME=Organization Domain
193
BusinessOrganizationDomain_TOOLTYPE=Organization Domain
194
Communicates_COMMANDENAME=Communicates
195
Communicates_ERROR=Communicates with : Role/Actor -> Role/Actor
196
Communicates_NAME=Communicates with
197
Communicates_TOOLTYPE=Role/Actor -> Role/Actor
198
ComponentRealization_COMMANDENAME=ComponentRealization
199
ComponentRealization_ERROR=Realizes : Component -> Service/Process/Use Case
200
ComponentRealization_NAME=Component Realization
201
ComponentRealization_TOOLTYPE=Component -> Service/Process/Use Case
202
Connexion_capacity_NAME=Capacity
203
Connexion_COMMANDENAME=Connexion
204
Connexion_ERROR=Connection : Hardware Technology Component/Instance -> Hardware Technology Component/Instance
205
Connexion_NAME=Connection
206
Connexion_protocol_NAME=Protocol
207
Connexion_TOOLTYPE=Hardware Tecnology Component/Instance -> Hardware Tecnology Component/Instance
208
ContractOf_COMMANDENAME=ContractOf
209
ContractOf_ERROR=Contract : Service -> Service Contract
210
ContractOf_NAME=Contract of
211
ContractOf_TOOLTYPE=Service -> Service Contract
212
Data_Template=The Data Architecture is in particular modeled under the \u0022Data Architecture\u0022 domain, where persistent data are defined. They can be derived from the Business Entities defined under the Business Layer/Business Entities domain.
213
DataBaseApplicationComponent_COMMANDENAME=DataBaseApplicationComponent
214
DataBaseApplicationComponent_ERROR=Invalid owner element : Database
215
DataBaseApplicationComponent_NAME=Database
216
DataBaseApplicationComponent_TOOLTYPE=Database
217
DeploymentInternet_COMMANDENAME=DeploymentInternet
218
DeploymentInternet_ERROR=Invalid owner element : Internet
219
DeploymentInternet_NAME=Internet
220
DeploymentInternet_TOOLTYPE=Internet
221
DeploymentNetworkNode_COMMANDENAME=DeploymentNetworkNode
222
DeploymentNetworkNode_ERROR=Invalid owner element : Network Node
223
DeploymentNetworkNode_NAME=Network Node
224
DeploymentNetworkNode_TOOLTYPE=Network Node
225
DeploymentRouter_COMMANDENAME=DeploymentRouter
226
DeploymentRouter_ERROR=Invalid owner element : Router
227
DeploymentRouter_NAME=Router
228
DeploymentRouter_TOOLTYPE=Router
229
DeploymentServer_COMMANDENAME=DeploymentServer
230
DeploymentServer_ERROR=Invalid owner element : Server
231
DeploymentServer_NAME=Server
232
DeploymentServer_TOOLTYPE=Server
233
DeploymentSwitch_COMMANDENAME=DeploymentSwitch
234
DeploymentSwitch_ERROR=Invalid owner element : Switch
235
DeploymentSwitch_NAME=Switch
236
DeploymentSwitch_TOOLTYPE=Switch
237
DeploymentWorkStation_COMMANDENAME=DeploymentWorkStation
238
DeploymentWorkStation_ERROR=Invalid owner element : Workstation
239
DeploymentWorkStation_NAME=Workstation
240
DeploymentWorkStation_TOOLTYPE=Workstation
241
EntityApplicationComponent_COMMANDENAME=EntityApplicationComponent
242
EntityApplicationComponent_ERROR=Invalid owner element : Entity Component
243
EntityApplicationComponent_NAME=Entity Component
244
EntityApplicationComponent_TOOLTYPE=Entity Component
245
EntityLifeCycle_COMMANDENAME=EntityLifeCycle
246
EntityLifeCycle_ERROR=Invalid owner element : Lifecycle
247
EntityLifeCycle_NAME=Lifecycle
248
EntityLifeCycle_TOOLTYPE=Lifecycle
249
Function_Template=The \u0022Business functions\u0022 domain is used to define business functions and business services.\n\nDiagrams:\n- Fonctional decomposition diagrams are used to summarize the capacities of an organization.\n- Value chain diagrams provide a high-level orientation view of an enterprise and how it interacts with the outside world.\n- Business Service/Information diagrams show the information needed to support one or more business services.\n- Goal/Objective/Service diagrams define the ways in which a service contributes to the achievement of a business vision or strategy. 
250
guarantee_COMMANDENAME=guarantee
251
guarantee_ERROR=Guarantee : Requirement -> Goal
252
guarantee_NAME=Guarantee
253
guarantee_TOOLTYPE=Requirement -> Goal
254
HardwareTechnologyComponent_COMMANDENAME=HardwareTechnologyComponent
255
HardwareTechnologyComponent_ERROR=Invalid owner element : Technology Component
256
HardwareTechnologyComponent_NAME=Technology Component
257
HardwareTechnologyComponent_TOOLTYPE=Technology Component
258
HeadquarterLocation_COMMANDENAME=HeadquarterLocation
259
HeadquarterLocation_ERROR=Invalid owner element : Headquarter
260
HeadquarterLocation_NAME=Headquarter
261
HeadquarterLocation_TOOLTYPE=Headquarter
262
implement_COMMANDENAME=Implement
263
implement_ERROR=Implement : Process/Class -> Business Rule
264
implement_NAME=Implement
265
implement_TOOLTYPE=Process/Class -> Business Rule
266
InformationDomain_COMMANDENAME=InformationDomain
267
InformationDomain_ERROR=Invalid owner element : Information Domain
268
InformationDomain_NAME=Information Domain
269
InformationDomain_TOOLTYPE=Information Domain
270
Initiator_COMMANDENAME=Initiator
271
Initiator_ERROR=Initiator of : Role/Actor/Organization Unit -> Process
272
Initiator_NAME=Initiator of
273
Initiator_TOOLTYPE=Role/Actor/Organization Unit -> Process
274
InteractionApplicationComponent_COMMANDENAME=InteractionApplicationComponent
275
InteractionApplicationComponent_ERROR=Invalid owner element : Interaction Component
276
InteractionApplicationComponent_NAME=Interaction Component
277
InteractionApplicationComponent_TOOLTYPE=Interaction Component
278
IntermediaryApplicationComponent_COMMANDENAME=IntermediaryApplicationComponent
279
IntermediaryApplicationComponent_ERROR=Invalid owner element : Intermediary Component
280
IntermediaryApplicationComponent_NAME=Intermediary Component
281
IntermediaryApplicationComponent_TOOLTYPE=Intermediary Component
282
IOFlow_COMMANDENAME=IOFlow
283
IOFlow_ERROR=Flow : Any active element<-->Product/Entity/Event
284
IOFlow_habilitation_NAME=Habilitation
285
IOFlow_NAME=Flow
286
IOFlow_TOOLTYPE=Any active element<-->Product/Entity/Event
287
Layer_COMMANDENAME=Layer
288
Layer_ERROR=Invalid owner element : Layer
289
Layer_NAME=Layer
290
Layer_TOOLTYPE=Layer
291
Locations_Template=This domains gathers the locations of the company. Headquarter and ocations are defined. Then, it will be possible to deploy roles, actors, devices (servers, network, ..), and application components on these locations.
292
LogicalDataModel_COMMANDENAME=LogicalDataModel
293
LogicalDataModel_ERROR=Invalid owner element : Data Architecture
294
LogicalDataModel_NAME=Data Architecture
295
LogicalDataModel_TOOLTYPE=Data Architecture
296
measure_COMMANDENAME=Measure
297
measure_ERROR=Measure : Model Element -> Goal
298
Measure_NAME=Measure
299
measure_NAME=Measure
300
measure_TOOLTYPE=Model Element -> Goal
301
Migration_COMMANDENAME=Migrate
302
Migration_ERROR=Invalid owner element : Migrate
303
Migration_NAME=Migrate
304
Migration_TOOLTYPE=Migrate
305
Name_NAME=Name
306
NetworkLink_COMMANDENAME=NetworkLink
307
NetworkLink_ERROR=Network Link : Technology Architecture Element/Technology Architecture Element
308
NetworkLink_NAME=Network Link
309
NetworkLink_TOOLTYPE=Network Link : Technology Architecture Element/Technology Architecture Element
310
Organization_Template=Under the Organization domain, we will define the organization units of the enterprise, its roles and actors. We recommend to focus more on role modeling than on actor modeling, since the model will be of a higher level, and more stable.\n\nDiagrams:\nUse Organization role diagram to express the definition of participants and their responsabilities.\nUse Organization decomposition diagram to describe the links between actor, roles, and location (which shall be already defined in the \u0022Locations\u0022 domain) within an organization tree
311
OrganizationParticipant_COMMANDENAME=OrganizationParticipant
312
OrganizationParticipant_ERROR=Invalid owner element : Organization Participant
313
OrganizationParticipant_NAME=Organization Participant
314
OrganizationParticipant_TOOLTYPE=Organization Participant
315
Owner_COMMANDENAME=Owner
316
Owner_ERROR=Owner of : Role/Actor/Organization Unit -> Process/Service
317
Owner_NAME=Owner of
318
Owner_TOOLTYPE=Role/Actor/Organization Unit -> Process/Service
319
Part_COMMANDENAME=Part
320
Part_ERROR=Invalid owner element : Part
321
Part_NAME=Part
322
Part_TOOLTYPE=Function <--> Function
323
Participates_COMMANDENAME=Participates
324
Participates_ERROR=Participates in : Role/Actor/Organization Unit -> Process/Service/Service Operation
325
Participates_NAME=Participates in
326
Participates_TOOLTYPE=Role/Actor/Organization Unit -> Process/Service/Service Operation
327
PostCondition_COMMANDENAME=PostCondition
328
PostCondition_ERROR=Invalid owner element : Postcondition
329
PostCondition_NAME=Postcondition
330
PostCondition_TOOLTYPE=Postcondition
331
PreCondition_COMMANDENAME=PreCondition
332
PreCondition_ERROR=Invalid owner element : Precondition
333
PreCondition_NAME=Precondition
334
PreCondition_TOOLTYPE=Precondition
335
ProcessApplicationComponent_COMMANDENAME=ProcessApplicationComponent
336
ProcessApplicationComponent_ERROR=Invalid owner element : Process Component
337
ProcessApplicationComponent_NAME=Process Component
338
ProcessApplicationComponent_TOOLTYPE=Process Component
339
Processes_Template=The process domain is the place where business processes are defined and modeled. Business Events or products can be defined there.\n\nDiagrams:\nUse \u0022Event diagrams\u0022 to provide an overview of the different business processes, and do a detailed business process model under each process through process flow diagrams.
340
Property_Type_NAME=Type
341
ProvidedServiceAccess_COMMANDENAME=ProvidedServiceAccess
342
ProvidedServiceAccess_ERROR=Invalid owner element : Provided
343
ProvidedServiceAccess_NAME=Provided
344
ProvidedServiceAccess_TOOLTYPE=Provided
345
PublicApplicationComponent_COMMANDENAME=PublicApplicationComponent
346
PublicApplicationComponent_ERROR=Invalid owner element : Public Component
347
PublicApplicationComponent_NAME=Public Component
348
PublicApplicationComponent_TOOLTYPE=Public Component
349
refine_COMMANDENAME=Refine
350
refine_ERROR=Refine : Model Element/Requirement -> Requirement
351
refine_NAME=Refine
352
refine_TOOLTYPE=Model Element/Requirement -> Requirement
353
RequiredServiceAccess_COMMANDENAME=RequiredServiceAccess
354
RequiredServiceAccess_ERROR=Invalid owner element : Required
355
RequiredServiceAccess_NAME=Required
356
RequiredServiceAccess_TOOLTYPE=Required
357
Responsible_COMMANDENAME=Responsible
358
Responsible_ERROR=Responsible of : Role/Actor -> Role/Actor/Organization Unit
359
Responsible_NAME=Responsible of
360
Responsible_TOOLTYPE=Role/Actor -> Role/Actor/Organization Unit
361
satisfy_COMMANDENAME=Satisfy
362
satisfy_ERROR=Satisfy : Model Element -> Requirement
363
satisfy_NAME=Satisfy
364
satisfy_TOOLTYPE=Model Element -> Requirement
365
Service_Template=The \u0022Service Data\u0022 domain contains the model of messages and message fragments. These messages constitute the information exchanged between IS services. Modelio can generate XSD schema from this model. Messeges will be used as types service parameters.
366
ServiceAccess_COMMANDENAME=ServiceAccess
367
ServiceAccess_ERROR=Invalid owner element : Service Access
368
ServiceAccess_NAME=Service Access
369
ServiceAccess_TOOLTYPE=Service Access
370
ServiceApplicationComponent_COMMANDENAME=ServiceApplicationComponent
371
ServiceApplicationComponent_ERROR=Invalid owner element : Service Component
372
ServiceApplicationComponent_NAME=Service Component
373
ServiceApplicationComponent_TOOLTYPE=Service Component
374
ServiceData_COMMANDENAME=ServiceData
375
ServiceData_ERROR=Invalid owner element : Message
376
ServiceData_NAME=Message
377
ServiceData_TOOLTYPE=Message
378
ServiceDataDiagram_COMMANDENAME=ServiceDataDiagram
379
ServiceDataDiagram_ERROR=Invalid owner element : Logical Data diagram
380
ServiceDataDiagram_NAME=Logical Data diagram
381
ServiceDataDiagram_TOOLTYPE=Logical Data diagram
382
ServiceDataFragment_COMMANDENAME=ServiceDataFragment
383
ServiceDataFragment_ERROR=Invalid owner element : Message Fragment
384
ServiceDataFragment_NAME=Message Fragment
385
ServiceDataFragment_TOOLTYPE=Message Fragment
386
ServiceProcessSupport_COMMANDENAME=ServiceProcessSupport
387
ServiceProcessSupport_ERROR=Supports : Service/Service Access/Process/Component -> Service/Process
388
ServiceProcessSupport_NAME=Supports
389
ServiceProcessSupport_TOOLTYPE=Service/Service Access/Process/Component -> Service/Process
390
SoftwareDistribution_COMMANDENAME=SoftwareDistribution
391
SoftwareDistribution_NAME=Software Distribution diagram
392
SoftwareDistribution_TOOLTYPE=Software Distribution diagram
393
SoftwareDistributionDiagram_NOTE=\nThe purpose of Software Distribution diagrams is to define TOGAF Software Distribution
394
SoftwareDistributionDiagram_SHORTNOTE=The purpose of Software Distribution diagrams is to define TOGAF Software Distribution
395
SoftwareEngineering_COMMANDENAME=SoftwareEngineering
396
SoftwareEngineering_NAME=Software Engineering diagram
397
SoftwareEngineering_TOOLTYPE=Software Engineering diagram
398
SoftwareEngineeringDiagram_NOTE=\nThe purpose of Software Engineering diagrams is to define TOGAF Software Engineering
399
SoftwareEngineeringDiagram_SHORTNOTE=The purpose of Software Engineering diagrams is to define TOGAF Software Engineering
400
SofwareDistributionDiagram_COMMANDENAME=SofwareDistributionDiagram
401
SofwareDistributionDiagram_ERROR=Invalid owner element : Software Distribution diagram
402
SofwareDistributionDiagram_NAME=Software Distribution diagram
403
SofwareDistributionDiagram_TOOLTYPE=Software Distribution diagram
404
SystemApplicationComponent_COMMANDENAME=SystemApplicationComponent
405
SystemApplicationComponent_ERROR=Invalid owner element : System
406
SystemApplicationComponent_NAME=System
407
SystemApplicationComponent_TOOLTYPE=System
408
Systeme_Template=System Uses Cases are modeled here.  Roles or actos can be related to Use case. Application component that realize the Use Case can also be shown with a \u0022component realization dependency.
409
TechnologyArchitecture_COMMANDENAME=TechnologyArchitecture
410
TechnologyArchitecture_ERROR=Invalid owner element : Technology Architecture
411
TechnologyArchitecture_NAME=Technology Architecture
412
TechnologyArchitecture_Template=Devices or technology artifacts can be created under the technology architecture. Elements deployed under the devices (typically servers and workstations) will be modeled under this domain.\n\nDiagrams:\n- Environments and Locations diagrams depict which locations host which applications, identifies what technologies and/or applications are used at which locations, and finally identifies the locations from which business users typically interact with the applications.\n- Software Distribution diagrams show how application software is structured and distributed across the estate.\n- Platform Decomposition diagrams depict the technology platform that supports the operations of the Information Systems Architecture. \n- Network computing hardware diagrams show the as deployed logical view of logical application components in a distributed network computing environment.\n- Processing diagrams focus on deployable units of code/configuration and how these are deployed onto the technology platform.
413
TechnologyArchitecture_TOOLTYPE=Technology Architecture
414
TechnologyArchitectureDomain_COMMANDENAME=TechnologyArchitectureDomain
415
TechnologyArchitectureDomain_ERROR=Invalid owner element : Technology Domain
416
TechnologyArchitectureDomain_NAME=Technology Domain
417
TechnologyArchitectureDomain_TOOLTYPE=Technology Domain
418
TechnologyArtifact_COMMANDENAME=TechnologyArtifact
419
TechnologyArtifact_ERROR=Invalid owner element : Technology Artifact
420
TechnologyArtifact_NAME=Technology Artifact
421
TechnologyArtifact_TOOLTYPE=Technology Artifact
422
TogafActor_COMMANDENAME=TogafActor
423
TogafActor_ERROR=Invalid owner element : Actor
424
TogafActor_NAME=Actor
425
TogafActor_TOOLTYPE=Actor
426
TogafApplication_COMMANDENAME=TogafApplication
427
TogafApplication_ERROR=Invalid owner element : Application
428
TogafApplication_NAME=Application
429
TogafApplication_TOOLTYPE=Application
430
TogafApplicationAndUserLocationDiagram_COMMANDENAME=TogafApplicationAndUserLocationDiagram
431
TogafApplicationAndUserLocationDiagram_ERROR=Invalid owner element : Application and User Location diagram
432
TogafApplicationAndUserLocationDiagram_NAME=Application and User Location diagram
433
TogafApplicationAndUserLocationDiagram_TOOLTYPE=Application and User Location diagram
434
TogafApplicationCommunicationDiagram_COMMANDENAME=TogafApplicationCommunicationDiagram
435
TogafApplicationCommunicationDiagram_ERROR=Invalid owner element : Application Communication diagram
436
TogafApplicationCommunicationDiagram_NAME=Application Communication diagram
437
TogafApplicationCommunicationDiagram_TOOLTYPE=Application Communication diagram
438
TogafApplicationComponent_benefits_NAME=Benefits
439
TogafApplicationComponent_COMMANDENAME=TogafApplicationComponent
440
TogafApplicationComponent_complexity_NAME=Complexity
441
TogafApplicationComponent_ERROR=Invalid owner element : Application Component
442
TogafApplicationComponent_NAME=Application component
443
TogafApplicationComponent_size_NAME=Size
444
TogafApplicationComponent_TogafApplicationComponent_level_NAME=Level
445
TogafApplicationComponent_TOOLTYPE=Application Component
446
TogafApplicationComponentInstance_capacity_NAME=Capacity
447
TogafApplicationComponentInstance_COMMANDENAME=TogafApplicationComponentInstance
448
TogafApplicationComponentInstance_ERROR=Invalid owner element : Application Instance
449
TogafApplicationComponentInstance_NAME=Application Instance
450
TogafApplicationComponentInstance_occurencesNumber_NAME=Occurences Number
451
TogafApplicationComponentInstance_TOOLTYPE=Application Instance
452
TogafApplicationMigrationDiagram_COMMANDENAME=TogafApplicationMigrationDiagram
453
TogafApplicationMigrationDiagram_ERROR=Invalid owner element : Application Migration diagram
454
TogafApplicationMigrationDiagram_NAME=Application Migration diagram
455
TogafApplicationMigrationDiagram_NOTE=\nThe Application Migration diagram identifies application migration from baseline to target application components. It enables a more accurate estimation of migration costs by showing precisely which applications and interfaces need to be mapped between migration stages.\nUnder Modelio : One strategy is to model the global Information system as a system application component for each of its state. Under the context of each version of the system, instances of application components will be created (just drag & drop application components under the system component). This allows showing several instances of identical components deployed in several versions of the IS. Between these instances, \u0022migration\u0022 dependencies are drawn. The model can be more accurate, and focused for example on different versions of services on different occurrences of application components.
456
TogafApplicationMigrationDiagram_SHORTNOTE=The Application Migration diagram identifies application migration from baseline to target application components.
457
TogafApplicationMigrationDiagram_TOOLTYPE=Application Migration diagram
458
TogafBenefitsDiagram_COMMANDENAME=TogafBenefitsDiagram
459
TogafBenefitsDiagram_ERROR=Invalid owner element : Benefits diagram
460
TogafBenefitsDiagram_NAME=Benefits diagram
461
TogafBenefitsDiagram_NOTE=\nThe Benefits diagram shows opportunities identified in an architecture definition, classified according to their relative size, benefit, and complexity. This diagram can be used by stakeholders to make selection, prioritization, and sequencing decisions on identified opportunities.\nBenefit diagrams are similar to application communication diagrams. They are annotated with notes, to document the benefits of the designed application components. Use also the properties : SIze, Benefits, and Complexity of application components.
462
TogafBenefitsDiagram_SHORTNOTE=The Benefits diagram shows opportunities identified in an architecture definition, classified according to their relative size, benefit, and complexity. 
463
TogafBenefitsDiagram_TOOLTYPE=Benefits diagram
464
TogafBus_COMMANDENAME=TogafBus
465
TogafBus_ERROR=Invalid owner element : Bus
466
TogafBus_NAME=Bus
467
TogafBus_TOOLTYPE=Bus
468
TogafBusinessCapability_COMMANDENAME=TogafBusinessCapability
469
TogafBusinessCapability_ERROR=Invalid owner element : Business Capability
470
TogafBusinessCapability_NAME=Business Capability
471
TogafBusinessCapability_TOOLTYPE=Business Capability
472
TogafBusinessFootPrintDiagram_COMMANDENAME=TogafBusinessFootPrintDiagram
473
TogafBusinessFootPrintDiagram_ERROR=Invalid owner element : functional decomposition diagram
474
TogafBusinessFootPrintDiagram_NAME=Business Footprint diagram
475
TogafBusinessFootPrintDiagram_NOTE=\nA Business Footprint diagram describes the links between business goals, organizational units, business functions, and services, and maps these functions to the technical components delivering the required capability.\nA Business Footprint diagram provides a clear traceability between a technical component and the business goal that it satisfies, whilst also demonstrating ownership of the services identified.\nA Business Footprint diagram demonstrates only the key facts linking organization unit functions to delivery services and is utilized as a communication platform for senior-level (CxO) stakeholders.\nUnder Modelio : select in the explorer the elements (Goals, Organization Units, Business Functions, Business Services, Applications Components) that are under focus and shall be already defined.  Drag & drop them, create \u0022trace\u0022, \u0022participates in\u0022 , \u0022supports\u0022 and \u0022component realization\u0022 dependencies.
476
TogafBusinessFootPrintDiagram_SHORTNOTE=A Business Footprint diagram describes the links between business goals, organizational units, business functions, and services, and maps these functions to the technical components delivering the required capability.
477
TogafBusinessFootPrintDiagram_TOOLTYPE=Business Footprint diagram
478
TogafBusinessOperation_COMMANDENAME=TogafBusinessOperation
479
TogafBusinessOperation_ERROR=Invalid owner element : Operation
480
TogafBusinessOperation_NAME=Operation
481
TogafBusinessOperation_TOOLTYPE=Operation
482
TogafBusinessService_COMMANDENAME=TogafBusinessService
483
TogafBusinessService_ERROR=Invalid owner element : Business Service
484
TogafBusinessService_NAME=Business Service
485
TogafBusinessService_TOOLTYPE=Business Service
486
TogafBusinessServiceInformationDiagram_COMMANDENAME=TogafBusinessServiceInformationDiagram
487
TogafBusinessServiceInformationDiagram_ERROR=Invalid owner element : Business Service Information diagram
488
TogafBusinessServiceInformationDiagram_NAME=Business Service Information diagram
489
TogafBusinessServiceInformationDiagram_NOTE=\nThe Business Service/Information diagram shows the information needed to support one or more business services. The Business Service/Information diagram shows what data is consumed by or produced by a business service and may also show the source of information. The Business Service/Information diagram shows an initial representation of the information present within the architecture and therefore forms a basis for elaboration and refinement within Phase C (Data Architecture).\nHints : by using \u0022flow\u0022 dependencies between  business services and Business Entities, this diagram represents which kind of entity is used or produced by the services. \nUnder Modelio : drag and drop business services and Business Entities from the explorer, and draw \u0022flow\u0022 dependencies between them to express inputs or outputs. Flow properties provide the means to specify the input or output orientation.
490
TogafBusinessServiceInformationDiagram_SHORTNOTE=\nThe Business Service/Information diagram shows the information needed to support one or more business services.
491
TogafBusinessServiceInformationDiagram_TOOLTYPE=Business Service Information diagram
492
TogafBusinessUseCaseDiagram_COMMANDENAME=TogafBusinessUseCaseDiagram
493
TogafBusinessUseCaseDiagram_ERROR=Invalid owner element : Business Use Case diagram
494
TogafBusinessUseCaseDiagram_NAME=Business Use Case diagram
495
TogafBusinessUseCaseDiagram_TOOLTYPE=Business Use Case diagram
496
TogafClassDiagram_COMMANDENAME=TogafClassDiagram
497
TogafClassDiagram_ERROR=Invalid owner element : Class diagram
498
TogafClassDiagram_NAME=Class diagram
499
TogafClassDiagram_TOOLTYPE=Class diagram
500
TogafClassHierachyDiagram_COMMANDENAME=TogafClassHierachyDiagram
501
TogafClassHierachyDiagram_ERROR=Invalid owner element : Class Hierarchy diagram
502
TogafClassHierachyDiagram_NAME=Class Hierarchy diagram
503
TogafClassHierachyDiagram_NOTE=\nThe purpose of the Class Hierarchy diagram is to show the technical stakeholders a perspective of the class hierarchy. The advantage of this diagram is that it allows the stakeholders a technical utilization/usage diagram of the data entity. This diagram gives the stakeholders an idea of who is using the data, how, why, and when. A possible variant can be to use this diagram in auditing.\nClass Hierarchy diagram is a kind of class diagram, focused on the hierarchy.
504
TogafClassHierachyDiagram_SHORTNOTE=The purpose of the Class Hierarchy diagram is to show the technical stakeholders a perspective of the class hierarchy. 
505
TogafClassHierachyDiagram_TOOLTYPE=Class Hierarchy diagram
506
TogafCommunicationEngineeringDiagrams_COMMANDENAME=TogafCommunicationEngineeringDiagrams
507
TogafCommunicationEngineeringDiagrams_ERROR=Invalid owner element : Communication Engineering diagram
508
TogafCommunicationEngineeringDiagrams_NAME=Communication Engineering diagram
509
TogafCommunicationEngineeringDiagrams_NOTE=\nThe Communications Engineering diagram describes the means of communication, the method of sending and receiving information between these assets in the Technology Architecture; insofar as the selection of package solutions in the preceding architectures put specific requirements on the communications between the applications. The Communications Engineering diagram will take logical connections between client and server components and identify network boundaries and network infrastructure required to physically implement those connections. It does not describe the information format or content, but will address protocol and capacity issues.\nSee NewtorkComputingHardware Diagram: the focus is set here on communications.
510
TogafCommunicationEngineeringDiagrams_SHORTNOTE=The Communications Engineering diagram describes the means of communication, the method of sending and receiving information between these assets in the Technology Architecture; insofar as the selection of package solutions in the preceding architectures put specific requirements on the communications between the applications. 
511
TogafCommunicationEngineeringDiagrams_TOOLTYPE=Communication Engineering diagram
512
TogafConsumes_COMMANDENAME=TogafConsumes
513
TogafConsumes_ERROR=Consumes : Role/Actor/Organization Unit -> Operation/Service/Component
514
TogafConsumes_habilitation_NAME=Habilitation
515
TogafConsumes_NAME=Consumes
516
TogafConsumes_TOOLTYPE=Role/Actor/Organization Unit -> Operation/Service/Component
517
TogafDataDisseminationDiagram_COMMANDENAME=TogafDataDisseminationDiagram
518
TogafDataDisseminationDiagram_ERROR=Invalid owner element : Data Dissemination diagram
519
TogafDataDisseminationDiagram_NAME=Data Dissemination diagram
520
TogafDataDisseminationDiagram_NOTE=\nThe purpose of the Data Dissemination diagram is to show the relationship between data entities, business services, and application components. The diagram shows how the logical entities are to be physically realized by application components. This allows effective sizing to be carried out and the IT footprint to be refined. Moreover, by assigning business value to data, an indication of the business criticality of application components can be gained. Additionally, the diagram may show data replication and system ownership of the master reference for data. In this instance, it can show two copies and the master-copy relationship between them. This diagram can include services; that is, services encapsulate data and they reside in an application, or services that reside on an application and access data encapsulated within the application\nUnder Modelio : Data dissemination diagram is a kind of architecture diagram, where data entities are connected to application components. First, drag & drop application components from the Application Architecture, and then drag and drop Business Entities, either within the application components to show their localization, or beside them, with dependency links.
521
TogafDataDisseminationDiagram_SHORTNOTE=The purpose of the Data Dissemination diagram is to show the relationship between data entities, business services, and application components. 
522
TogafDataDisseminationDiagram_TOOLTYPE=Data Dissemination diagram
523
TogafDataLifeCycleDiagram_COMMANDENAME=TogafDataLifeCycleDiagram
524
TogafDataLifeCycleDiagram_ERROR=Invalid owner element : Data Lifecycle diagram
525
TogafDataLifeCycleDiagram_NAME=Data Lifecycle diagram
526
TogafDataLifeCycleDiagram_TOOLTYPE=Data Lifecycle diagram
527
TogafDataMigrationDiagram_COMMANDENAME=TogafDataMigrationDiagram
528
TogafDataMigrationDiagram_ERROR=Invalid owner element : data Migration diagram
529
TogafDataMigrationDiagram_NAME=Data Migration diagram
530
TogafDataMigrationDiagram_NOTE=\nThe purpose of the Data Migration diagram is to show the flow of data from the source to the target applications. The diagram will provide a visual representation of the spread of sources/targets and serve as a tool for data auditing and establishing traceability. This diagram can be elaborated or enhanced as detailed as necessary. For example, the diagram can contain just an overall layout of migration landscape or could go into individual application metadata element level of detail.\nHints : Data migration can be expressed at the conceptual level, logical or physical. It can also use application communication diagrams to express the data migration. The \u0022migrate\u0022 dependency is the key element to formalize migration.\nUnder Modelio : Use the previous data model (which should be in a separated information domain), drag and drop previous and new entities, and use the \u0022migrates\u0022 dependency to express how previous data is translated into new entities.
531
TogafDataMigrationDiagram_SHORTNOTE=The purpose of the Data Migration diagram is to show the flow of data from the source to the target applications.
532
TogafDataMigrationDiagram_TOOLTYPE=Data Migration diagram
533
TogafDataSecurityDiagram_COMMANDENAME=TogafDataSecurityDiagram
534
TogafDataSecurityDiagram_ERROR=Invalid owner element : Data Security diagram
535
TogafDataSecurityDiagram_NAME=Data Security diagram
536
TogafDataSecurityDiagram_NOTE=\nData is considered as an asset to the enterprise and data security simply means ensuring that enterprise data is not compromised and that access to it is suitably controlled. The purpose of the Data Security diagram is to depict which actor (person, organization, or system) can access which enterprise data. This relationship can be shown in a matrix form between two objects or can be shown as a mapping. The diagram can also be used to demonstrate compliance with data privacy laws and other applicable regulations (HIPAA, SOX, etc). This diagram should also consider any trust implications where an enterprise\u0027s partners or other parties may have access to the company\u0027s systems, such as an outsourced situation where information may be managed by other people and may even be hosted in a different country.\nHints : Large diagrams can become hard to read. It is recommended to do data security diagrams per business entity, and/or per participant (role typically).\nUnder Modelio : drag and drop data (Business Entities, data entities) you want to show, drag and drop roles or actor involved with these entities and express using and valuating \u0022flow\u0022 dependencies the access mode of each participant to each entity.
537
TogafDataSecurityDiagram_SHORTNOTE=Data is considered as an asset to the enterprise and data security simply means ensuring that enterprise data is not compromised and that access to it is suitably controlled. 
538
TogafDataSecurityDiagram_TOOLTYPE=Data Security diagram
539
TogafDiagram_COMMANDENAME=TogafDiagram
540
TogafDiagram_ERROR=Invalid owner element : TOGAF diagram
541
TogafDiagram_NAME=TOGAF diagram
542
TogafDiagram_TOOLTYPE=Create a TOGAF diagram
543
TogafElement_category_NAME=Category
544
TogafElement_description_NAME=Description
545
TogafElement_name_NAME=Name
546
TogafElement_owner_NAME=Owner
547
TogafElement_reference_NAME=Reference
548
TogafElement_reference_NAME=Reference
549
TogafElement_source_NAME=Source
550
TogafEnterpriseManageabilityDiagram_COMMANDENAME=TogafEnterpriseManageabilityDiagram
551
TogafEnterpriseManageabilityDiagram_ERROR=Invalid owner element : Enterprise Manageability diagram
552
TogafEnterpriseManageabilityDiagram_NAME=Enterprise Manageability diagram
553
TogafEnterpriseManageabilityDiagram_NOTE=\nThe Enterprise Manageability diagram shows how one or more applications interact with application and technology components that support operational management of a solution. This diagram is really a filter on the Application Communication diagram, specifically for enterprise management class software. Analysis can reveal duplication and gaps, and opportunities in the IT service management operation of an organization. It would identify temporary applications, staging areas, and the infrastructure required to support migrations (for example, parallel run environments, etc).\nUnder Modelio : The usage is similar to Application communication diagrams, where some application components and their properties are dragged and dropped from the explorer. The \u0022migrates\u0022 dependency is frequently used there.
554
TogafEnterpriseManageabilityDiagram_SHORTNOTE=The Enterprise Manageability diagram shows how one or more applications interact with application and technology components that support operational management of a solution.
555
TogafEnterpriseManageabilityDiagram_TOOLTYPE=Enterprise Manageability diagram
556
TogafEnterpriseSystem_COMMANDENAME=TogafEnterpriseSystem
557
TogafEnterpriseSystem_ERROR=Invalid owner element : Enterprise System
558
TogafEnterpriseSystem_NAME=Enterprise System
559
TogafEnterpriseSystem_TOOLTYPE=Enterprise System
560
TogafEnumeration_COMMANDENAME=TogafEnumeration
561
TogafEnumeration_ERROR=Invalid owner element : Enumeration
562
TogafEnumeration_NAME=Enumeration
563
TogafEnumeration_TOOLTYPE=Enumeration 
564
TogafEnvironmentAndLocationsDiagram_COMMANDENAME=TogafEnvironmentAndLocationsDiagram
565
TogafEnvironmentAndLocationsDiagram_ERROR=Invalid owner element : Environment and Locations diagram
566
TogafEnvironmentAndLocationsDiagram_NAME=Environment and Locations diagram
567
TogafEnvironmentAndLocationsDiagram_NOTE=\nEnvironments and Locations diagram depicts which locations host which applications, identifies what technologies and/or applications are used at which locations, and finally identifies the locations from which business users typically interact with the applications. This diagram should also show the existence and location of different deployment environments, including non-production environments, such as development and pre production.\nUnder Modelio : Drag & drop the locations of the enterprise, and then drag and drop the material (typically the servers) under the locations, and then drag & drop the application components, or software elements under the material. Typically, this diagram represents where is located each server, and on which server is executed which application.
568
TogafEnvironmentAndLocationsDiagram_SHORTNOTE=Environments and Locations diagram depicts which locations host which applications, identifies what technologies and/or applications are used at which locations, and finally identifies the locations from which business users typically interact with the applications. 
569
TogafEnvironmentAndLocationsDiagram_TOOLTYPE=Environment and Locations diagram
570
TogafEvent_COMMANDENAME=TogafEvent
571
TogafEvent_ERROR=Invalid owner element : Event
572
TogafEvent_NAME=Event
573
TogafEvent_TOOLTYPE=Event
574
TogafEventDiagram_COMMANDENAME=TogafEventDiagram
575
TogafEventDiagram_ERROR=Invalid owner element : Event diagram
576
TogafEventDiagram_NAME=Event diagram
577
TogafEventDiagram_TOOLTYPE=Event diagram
578
TogafExternalActor_COMMANDENAME=TogafExternalActor
579
TogafExternalActor_ERROR=Invalid owner element : External Actor
580
TogafExternalActor_NAME=External Actor
581
TogafExternalActor_TOOLTYPE=External Actor
582
TogafExternalRole_COMMANDENAME=TogafExternalRole
583
TogafExternalRole_ERROR=Invalid owner element : External Role
584
TogafExternalRole_NAME=External Role
585
TogafExternalRole_TOOLTYPE=External Role
586
TogafFunction_changesNeeded_NAME=Changes Needed
587
TogafFunction_COMMANDENAME=TogafFunction
588
TogafFunction_ERROR=Invalid owner element : Function
589
TogafFunction_increments_NAME=Increments
590
TogafFunction_NAME=Function
591
TogafFunction_TOOLTYPE=Function
592
TogafFunction_valueFactor_NAME=Value Factor
593
TogafFunctionalDecompositionDiagram_COMMANDENAME=TogafFunctionalDecompositionDiagram
594
TogafFunctionalDecompositionDiagram_ERROR=Invalid owner element : Togaf Functional Decomposition diagram
595
TogafFunctionalDecompositionDiagram_NAME=Functional Decomposition diagram
596
TogafFunctionalDecompositionDiagram_TOOLTYPE=Togaf Functional Decomposition diagram
597
TogafFunctionSequence_COMMANDENAME=TogafFunctionSequence
598
TogafFunctionSequence_ERROR=Sequence : Function -> Function
599
TogafFunctionSequence_NAME=Sequence
600
TogafFunctionSequence_TOOLTYPE=Function -> Function
601
TogafGoalObjectiveServiceDiagram_COMMANDENAME=TogafGoalObjectiveServiceDiagram
602
TogafGoalObjectiveServiceDiagram_ERROR=Invalid owner element : Driver/Goal/Objectives diagram
603
TogafGoalObjectiveServiceDiagram_NAME=Driver/Goal/Objectives diagram
604
TogafGoalObjectiveServiceDiagram_NOTE=\nThe purpose of a Goal/Objective/Service diagram is to define the ways in which a service contributes to the achievement of a business vision or strategy. \nServices are associated with the drivers, goals, objectives, and measures that they support, allowing the enterprise to understand which services contribute to similar aspects of business performance. The Goal/Objective/Service diagram also provides qualitative input on what constitutes high performance for a particular service.\nUnder Modelio: drag & drop business services and goals, and define \u0022trace\u0022 dependencies between services and goals where appropriate.
605
TogafGoalObjectiveServiceDiagram_SHORTNOTE=\nThe purpose of a Goal/Objective/Service diagram is to define the ways in which a service contributes to the achievement of a business vision or strategy.
606
TogafGoalObjectiveServiceDiagram_TOOLTYPE=Driver/Goal/Objectives diagram
607
TogafInternalActor_COMMANDENAME=TogafInternalActor
608
TogafInternalActor_ERROR=Invalid owner element : Internal Actor
609
TogafInternalActor_NAME=Internal Actor
610
TogafInternalActor_TOOLTYPE=Internal Actor
611
TogafInternalRole_COMMANDENAME=TogafInternalRole
612
TogafInternalRole_ERROR=Invalid owner element : Internal Role
613
TogafInternalRole_NAME=Internal Role
614
TogafInternalRole_TOOLTYPE=Internal Role
615
TogafISService_COMMANDENAME=TogafISService
616
TogafISService_ERROR=Invalid owner element : IS Service
617
TogafISService_NAME=IS Service
618
TogafISService_TOOLTYPE=IS Service
619
TogafISServiceOperation_COMMANDENAME=TogafISServiceOperation
620
TogafISServiceOperation_ERROR=Invalid owner element : IS Service Operation
621
TogafISServiceOperation_NAME=IS Service Operation
622
TogafISServiceOperation_TOOLTYPE=IS Service Operation
623
TogafLocalization_COMMANDENAME=TogafLocalization
624
TogafLocalization_ERROR=Localization : Role/Actor/Organization Unit -> Location
625
TogafLocalization_NAME=Localization
626
TogafLocalization_TOOLTYPE=Role/Actor/Organization Unit -> Location
627
TogafLocation_category_NAME=Category
628
TogafLocation_COMMANDENAME=TogafLocation
629
TogafLocation_ERROR=Invalid owner element : Location
630
TogafLocation_NAME=Location
631
TogafLocation_TOOLTYPE=Location
632
TogafLocationDiagram_COMMANDENAME=TogafLocationDiagram
633
TogafLocationDiagram_ERROR=Invalid owner element : Location diagram
634
TogafLocationDiagram_NAME=Location diagram
635
TogafLocationDiagram_TOOLTYPE=Location diagram
636
TogafMatrixDiagram_COMMANDENAME=TogafMatrixDiagram
637
TogafMatrixDiagram_ERROR=Invalid owner element : Traceability diagram
638
TogafMatrixDiagram_NAME=Traceability diagram
639
TogafMatrixDiagram_TOOLTYPE=Traceability diagram
640
TogafNewtorkComputingHardwareDiagram_COMMANDENAME=TogafNewtorkComputingHardwareDiagram
641
TogafNewtorkComputingHardwareDiagram_ERROR=Invalid owner element : Network Computing Hardware diagram
642
TogafNewtorkComputingHardwareDiagram_NAME=Network Computing Hardware diagram
643
TogafNewtorkComputingHardwareDiagram_TOOLTYPE=Network Computing Hardware diagram
644
TogafOrganizationDecompositionDiagram_COMMANDENAME=TogafOrganizationDecompositionDiagram
645
TogafOrganizationDecompositionDiagram_ERROR=Invalid owner element : Organization Decomposition diagram
646
TogafOrganizationDecompositionDiagram_NAME=Organization Decomposition diagram
647
TogafOrganizationDecompositionDiagram_TOOLTYPE=Organization Decomposition diagram
648
TogafOrganizationRoleDiagram_COMMANDENAME=OrganizationRoleDiagram
649
TogafOrganizationRoleDiagram_ERROR=Invalid owner element : Organization Role diagram
650
TogafOrganizationRoleDiagram_NAME=Organization Role diagram
651
TogafOrganizationRoleDiagram_NOTE=\nDiagram dedicated to the definition of participants and their responsibilities. Roles and actors are modeled here. This is an extension to TOGAF: the organization is presented in terms of connections between roles and responsibilities.\nUnder Modelio: Define the roles of the Organization, define Organization Units, define the dependencies between roles (communication, hierarchy, responsibilities). The assigned goals can also be shown here.
652
TogafOrganizationRoleDiagram_SHORTNOTE=Diagram dedicated to the definition of participants and their responsibilities. Roles and actors are modeled here. 
653
TogafOrganizationRoleDiagram_TOOLTYPE=Organization Role diagram
654
TogafOrganizationUnit_COMMANDENAME=TogafOrganizationUnit
655
TogafOrganizationUnit_ERROR=Invalid owner element : Organization Unit
656
TogafOrganizationUnit_NAME=Organization Unit
657
TogafOrganizationUnit_TOOLTYPE=Organization Unit
658
TogafParticipantAllocation_COMMANDENAME=TogafParticipantAllocation
659
TogafParticipantAllocation_ERROR=Allocated to : Role/Actor -> Organization Unit
660
TogafParticipantAllocation_NAME=Allocated
661
TogafParticipantAllocation_TOOLTYPE=Role/Actor -> Organization Unit
662
TogafParticipantDecomposition_COMMANDENAME=TogafParticipantDecomposition
663
TogafParticipantDecomposition_ERROR=Composed of : Role/Actor -> Role/Actor
664
TogafParticipantDecomposition_NAME=Composed of
665
TogafParticipantDecomposition_TOOLTYPE=Role/Actor -> Role/Actor
666
TogafPlatformDecompositionDiagram_COMMANDENAME=TogafPlatformDecompositionDiagram
667
TogafPlatformDecompositionDiagram_ERROR=Invalid owner element : Platform Decomposition diagram
668
TogafPlatformDecompositionDiagram_NAME=Platform decomposition diagram
669
TogafPlatformDecompositionDiagram_NOTE=\nThe Platform Decomposition diagram depicts the technology platform that supports the operations of the Information Systems Architecture. The diagram covers all aspects of the infrastructure platform and provides an overview of the enterprise\u0027s technology platform. The diagram can be expanded to map the technology platform to appropriate application components within a specific functional or process area. This diagram may show details of specification, such as product versions, number of CPUs, etc., or simply could be an informal eye-char t providing an overview of the technical environment. The diagram should clearly show the enterprise applications and the technology platform for each application area can further be decomposed as follows for Hardware and Software: Logical Technology Components (with attributes), Physical Technology Components (with attributes). Depending upon the scope of the enterprise architecture work, additional technology crossplatform information (e.g., communications, telco, and video information) may be addressed. It is a specific focus on network computing diagrams.\nSee also network computing diagrams.
670
TogafPlatformDecompositionDiagram_SHORTNOTE=The Platform Decomposition diagram depicts the technology platform that supports the operations of the Information Systems Architecture. 
671
TogafPlatformDecompositionDiagram_TOOLTYPE=Platform Decomposition diagram
672
TogafProcess_COMMANDENAME=TogafProcess
673
TogafProcess_criticality_NAME=Criticality
674
TogafProcess_duration_NAME=Duration
675
TogafProcess_ERROR=Invalid owner element : Business Process
676
TogafProcess_isAutomated_NAME=Is Automated
677
TogafProcess_kind_NAME=Kind
678
TogafProcess_KPI_NAME=KPI
679
TogafProcess_NAME=Business Process
680
TogafProcess_TOOLTYPE=Business Process
681
TogafProcess_used_resources_NAME=Used Resources
682
TogafProcess_volumetrics_NAME=Frequency
683
TogafProcessFlowDiagram_COMMANDENAME=TogafProcessFlowDiagram
684
TogafProcessFlowDiagram_ERROR=Invalid owner element : Process Flow diagram
685
TogafProcessFlowDiagram_NAME=Process Flow diagram
686
TogafProcessFlowDiagram_TOOLTYPE=Process Flow diagram
687
TogafProcessingDiagram_COMMANDENAME=TogafProcessingDiagram
688
TogafProcessingDiagram_ERROR=Invalid owner element : Processing diagram
689
TogafProcessingDiagram_NAME=Processing diagram
690
TogafProcessingDiagram_NOTE=\nThe Processing diagram focuses on deployable units of code/configuration and how these are deployed onto the technology platform. A deployment unit represents grouping of business function, service, or application components. The Processing diagram addresses the following:\n- Which set of application components need to be grouped to form a deployment unit\n- How one deployment unit connects/interacts with another (LAN, WAN, and the applicable protocols)\n- How application configuration and usage patterns generate load or capacity requirements for different technology components\nSee NewtorkComputingHardware Diagram. Processing diagram will use deployment in a more generic way, in order to present deployment units. Deployment units can be presented as component instances where application components are deployed, or as physical utility component that will host the deployed application component (for example: an application server).\nAssociations between these deployment units will represent the connection (as for example network), information flows will indicate the nature of information exchanged. \nOn these diagrams, indications about capacity requirements are provided.\nUnder Modelio : Drag & drop application components to deploy them into the deployable units of configuration, which are themself specific kinds of application components, at a logical technology level.
691
TogafProcessingDiagram_SHORTNOTE=The Processing diagram focuses on deployable units of code/configuration and how these are deployed onto the technology platform.
692
TogafProcessingDiagram_TOOLTYPE=Processing diagram
693
TogafProcessSystemRealizationDiagram_COMMANDENAME=TogafProcessSystemRealizationDiagram
694
TogafProcessSystemRealizationDiagram_ERROR=Invalid owner element : Process System Realization diagram
695
TogafProcessSystemRealizationDiagram_NAME=Process System Realization diagram
696
TogafProcessSystemRealizationDiagram_NOTE=\nThe purpose of the Process/System Realization diagram is to clearly depict the sequence of events when multiple applications are involved in executing a business process. It enhances the Application Communication diagram by augmenting it with any sequencing constraints, and hand-off points between batch and real-time processing. It would identify complex sequences that could be simplified, and identify possible rationalization points in the architecture in order to provide more timely information to business users. It may also identify process efficiency improvements that may reduce interaction traffic between applications.\nUnder Modelio : Drag & drop the processes that you want to illustrate, drag & drop the Application components that are involved, and draw \u0022component realization\u0022 dependencies. Indications of role or order can be made using information flows (as in the example), or notes attached to elements. 
697
TogafProcessSystemRealizationDiagram_SHORTNOTE=\nThe purpose of the Process/System Realization diagram is to clearly depict the sequence of events when multiple applications are involved in executing a business process. 
698
TogafProcessSystemRealizationDiagram_TOOLTYPE=Process System Realization diagram
699
TogafProduct_COMMANDENAME=TogafProduct
700
TogafProduct_ERROR=Invalid owner element : Product
701
TogafProduct_NAME=Product
702
TogafProduct_TOOLTYPE=Product
703
TogafProductLifeCycleDiagram_COMMANDENAME=TogafProductLifeCycleDiagram
704
TogafProductLifeCycleDiagram_ERROR=Invalid owner element : Product Lifecycle diagram
705
TogafProductLifeCycleDiagram_NAME=Product Lifecycle diagram
706
TogafProductLifeCycleDiagram_TOOLTYPE=Product Lifecycle diagram
707
TogafProjectContextDiagram_COMMANDENAME=TogafProjectContextDiagram
708
TogafProjectContextDiagram_ERROR=Invalid owner element : Project Context diagram
709
TogafProjectContextDiagram_NAME=Project Context diagram
710
TogafProjectContextDiagram_NOTE=\nA Project Context diagram shows the scope of a work package to be implemented as a part of a broader transformation roadmap. The Project Context diagram links a work package to the organizations, functions, services, processes, applications, data, and technology that will be added, removed, or impacted by the project. The Project Context diagram is also a valuable tool for project portfolio management and project mobilization.\nUnder Modelio : Drag & drop the essential application component of the project, the main requirements, the related business processes, business interfaces, business functions, and express what requirement are satisfied by the project, which business processes are implemented, which functions are related, and which roles will use the targeted components. Relationships to other parts of the IS can also be expressed.
711
TogafProjectContextDiagram_SHORTNOTE=A Project Context diagram shows the scope of a work package to be implemented as a part of a broader transformation roadmap. 
712
TogafProjectContextDiagram_TOOLTYPE=Project Context diagram
713
TogafRole_COMMANDENAME=TogafRole
714
TogafRole_ERROR=Invalid owner element : External Role
715
TogafRole_NAME=External Role
716
TogafRole_SkillsRequirements_NAME=Skills Requirements
717
TogafRole_TOOLTYPE=External Role
718
TogafService_businessImportance_NAME=Business Importance
719
TogafService_COMMANDENAME=TogafService
720
TogafService_contract_NAME=Contract
721
TogafService_ERROR=Invalid owner element : Service
722
TogafService_growth_NAME=Growth
723
TogafService_growthPeriod_NAME=Growth Period
724
TogafService_NAME=Service
725
TogafService_peakProfileLongTerm_NAME=Peak Profile Long Term
726
TogafService_peakProfileShortTerm_NAME=Peak Profile Short Term
727
TogafService_QOS_NAME=QOS
728
TogafService_RACI_NAME=RACI
729
TogafService_serviceTimes_NAME=Service Times
730
TogafService_SLA_NAME=SLA
731
TogafService_TOOLTYPE=Service
732
TogafService_troughput_NAME=Troughput
733
TogafService_troughputPeriod_NAME=Troughput Period
734
TogafService_type_NAME=Type
735
TogafServiceContract_COMMANDENAME=TogafServiceContract
736
TogafServiceContract_ERROR=Invalid owner element : Service Contract
737
TogafServiceContract_NAME=Service Contract
738
TogafServiceContract_TOOLTYPE=Service Contract
739
TogafServiceOperation_COMMANDENAME=TogafServiceOperation
740
TogafServiceOperation_ERROR=Invalid owner element : Service Operation
741
TogafServiceOperation_NAME=Service Operation
742
TogafServiceOperation_TOOLTYPE=Service Operation
743
TogafSofwareDistributionDiagram_NOTE=\nThe Software Distribution diagram shows how application software is structured and distributed across the estate. It is useful in systems upgrade or application consolidation projects. This diagram shows how physical applications are distributed across physical technology and the location of that technology. This enables a clear view of how the software is hosted, but also enables managed operations staff to understand how that application software is maintained once installed.\nSame principle as network computing diagram, but the focus here is on software, and physical environments.
744
TogafSofwareDistributionDiagram_SHORTNOTE=The Software Distribution diagram shows how application software is structured and distributed across the estate. 
745
TogafSolutionConceptDiagram_COMMANDENAME=TogafSolutionConceptDiagram
746
TogafSolutionConceptDiagram_ERROR=Invalid owner element : Solution Concept diagram
747
TogafSolutionConceptDiagram_NAME=Solution Concept diagram
748
TogafSolutionConceptDiagram_NOTE=\nA Solution Concept diagram provides a high-level orientation of the solution that is envisaged in order to meet the objectives of the architecture engagement. In contrast to the more formal and detailed architecture diagrams developed in the following phases, the solution concept represents a pencil sketch of the expected solution at the outset of the engagement. This diagram may embody key objectives, requirements, and constraints for the engagement and also highlight work areas to be investigated in more detail with formal architecture modeling. The purpose of this diagram is to quickly on-board and align stakeholders for a particular change initiative, so that all participants understand what the architecture engagement is seeking to achieve and how it is expected that a particular solution approach will meet the needs of the enterprise.\nHints : Present only the main application components of the solution, and summarize their connections using the \u0022access\u0022 dependency. Connect them to existing applications when necessary. Connect them to requirements, processes or functions, themselves connected to goals. Also express (\u0022consumes\u0022 dependency) which role uses which component.\nUnder Modelio : Create of drag & drop the components. Drag & drop the relevant requirements, goals, processes, functions or business services. Unmask or create the appropriate dependencies (consumes, satisfy, assigned, ...)
749
TogafSolutionConceptDiagram_SHORTNOTE=A Solution Concept diagram provides a high-level orientation of the solution that is envisaged in order to meet the objectives of the architecture engagement. 
750
TogafSolutionConceptDiagram_TOOLTYPE=Solution Concept diagram
751
TogafSystemFederation_COMMANDENAME=TogafSystemFederation
752
TogafSystemFederation_ERROR=Invalid owner element : System Federation
753
TogafSystemFederation_NAME=System Federation
754
TogafSystemFederation_TOOLTYPE=System Federation
755
TogafSystemUseCaseDiagram_COMMANDENAME=TogafSystemUseCaseDiagram
756
TogafSystemUseCaseDiagram_ERROR=Invalid owner element : System Use Case diagram
757
TogafSystemUseCaseDiagram_NAME=System Use Case diagram
758
TogafSystemUseCaseDiagram_TOOLTYPE=System Use Case diagram
759
TogafUseCaseDiagram_COMMANDENAME=TogafUseCaseDiagram
760
TogafUseCaseDiagram_ERROR=Invalid owner element : Use Case diagram
761
TogafUseCaseDiagram_NAME=Use Case diagram
762
TogafUseCaseDiagram_TOOLTYPE=Use Case diagram
763
TogafValueChainDiagram_COMMANDENAME=TogafValueChainDiagram
764
TogafValueChainDiagram_ERROR=Invalid owner element : Value Chain diagram
765
TogafValueChainDiagram_NAME=Value Chain diagram
766
TogafValueChainDiagram_TOOLTYPE=Value Chain diagram
767
TraceabilityDiagram_COMMANDENAME=TraceabilityDiagram
768
TraceabilityDiagram_ERROR=Invalid owner element : traceability
769
TraceabilityDiagram_NAME=Traceability
770
TraceabilityDiagram_TOOLTYPE=Traceability
771
UMLAssociation_COMMANDENAME=UMLAssociation
772
UMLAssociation_ERROR=Invalid owner element : Association 
773
UMLAssociation_NAME=Association
774
UMLAssociation_TOOLTYPE=Association
775
UMLComposition_COMMANDENAME=UMLComposition
776
UMLComposition_ERROR=Invalid owner element : Composition 
777
UMLComposition_NAME=Composition
778
UMLComposition_TOOLTYPE=Composition
779
UMLConnector_COMMANDENAME=UMLConnector
780
UMLConnector_ERROR=Invalid owner element : Connector
781
UMLConnector_NAME=Connector
782
UMLConnector_TOOLTYPE=Connector
783
UMLDependency_COMMANDENAME=UMLDependency
784
UMLDependency_ERROR=Invalid owner element : Dependency
785
UMLDependency_NAME=Dependency
786
UMLDependency_TOOLTYPE=Dependency
787
UMLElementImport_COMMANDENAME=UMLElementImport
788
UMLElementImport_ERROR=Invalid owner element : Element Import
789
UMLElementImport_NAME=Element Import
790
UMLElementImport_TOOLTYPE=Element Import
791
UMLEnumerationLitteral_COMMANDENAME=UMLEnumerationLitteral
792
UMLEnumerationLitteral_ERROR=Invalid owner element : Enumeration required
793
UMLEnumerationLitteral_NAME=Enumeration Literal
794
UMLEnumerationLitteral_TOOLTYPE=Enumeration Literal
795
UMLGeneralization_COMMANDENAME=UMLGeneralization
796
UMLGeneralization_ERROR=Invalid owner element : Generalization 
797
UMLGeneralization_NAME=Generalization
798
UMLGeneralization_TOOLTYPE=Generalization
799
UMLInformationFLow_COMMANDENAME=UMLInformationFLow 
800
UMLInformationFLow_ERROR=Invalid owner element : Information Flow
801
UMLInformationFLow_NAME=Information Flow
802
UMLInformationFLow_TOOLTYPE=Information Flow
803
UMLNote_COMMANDENAME=UMLNote
804
UMLNote_ERROR=Invalid owner element : Note
805
UMLNote_NAME=Note
806
UMLNote_TOOLTYPE=Note
807
UMLPackageImport_COMMANDENAME=UMLPackageImport
808
UMLPackageImport_ERROR=Element parent invalide : Package Import
809
UMLPackageImport_NAME=Package Import
810
UMLPackageImport_TOOLTYPE=Package Import
811
UMLTracability_COMMANDENAME=UMLTracability
812
UMLTracability_ERROR=Invalid owner element : Traceability
813
UMLTracability_NAME=Traceability
814
UMLTracability_TOOLTYPE=Traceability
815
UtilityApplicationComponent_COMMANDENAME=UtilityApplicationComponent
816
UtilityApplicationComponent_ERROR=Invalid owner element : Utility Component
817
UtilityApplicationComponent_NAME=Utility Component
818
UtilityApplicationComponent_TOOLTYPE=Utility Component
819
verify_COMMANDENAME=Verify
820
verify_ERROR=Verify : Model Element -> Requirement
821
verify_NAME=Verify
822
verify_TOOLTYPE=Model Element -> Requirement
823
ELEMENT_CREATION_SLOT=
824
System_Application_Component=System/Application
825
Service_Application_Component=Service Component
826
TogafApplicationCollaboration_NAME=Application Collaboration
827
TogafApplicationCollaboration_COMMANDENAME=TogafApplicationCollaboration
828
TogafApplicationCollaboration_TOOLTYPE=Application Collaboration
829
TogafApplicationCollaboration_ERROR=Invalid owner element : Application Collaboration
830
TogafBusinessCollaboration_NAME=Business Collaboration
831
TogafBusinessCollaboration_COMMANDENAME=TogafBusinessCollaboration
832
TogafBusinessCollaboration_TOOLTYPE=Business Collaboration
833
TogafBusinessCollaboration_ERROR=Invalid owner element : Business Collaboration
834

    
835
TogafSystemUseCaseDiagram_NOTE=\nA Use-Case diagram displays the relationships between consumers and providers of services.  Services are consumed by actors or other component services and the Use-Case diagram provides added richness in describing service components functionalities by illustrating how and when these functionalities are used. The purpose of the Use-Case diagram is to help describing and validating the interaction between actors and their roles with applications. As the architecture progresses, the use-case can evolve from functional information to include technical realization details. Architectural use-cases can also be re-used in more detailed systems design work.\nUnder Modelio : Create use cases, drag and drop roles and actors, drag and drop service components, and draw communication links between roles and use cases, and component realization links between components and use cases.
836
TogafSystemUseCaseDiagram_SHORTNOTE=A Use-Case diagram displays the relationships between consumers and providers of Services. 
837
TogafApplicationAndUserLocationDiagram_NOTE=The application and user location diagram shows the geographical distribution of applications.
838
TogafApplicationAndUserLocationDiagram_SHORTNOTE=The application and user location diagram shows the geographical distribution of applications. 
839
TogafApplicationCommunicationDiagram_NOTE=\nThe purpose of the SOA Architecture diagram is to depict the assembly of and communication between service components. It shows service components and interfaces between components. Communication should be logical and should only show intermediary technology where it is architecturally relevant.\nHints : Use service components to present as much as possible an SOA oriented architecture. Service components have different kinds that allows structuring them into layers, the main one being : GUI (interaction), Process, Entity. An Application Architecture may be hybrid due to the legacy system or external applications : \u0022Application\u0022 or \u0022DataBase\u0022 components serve this purpose, and can be mixed with SOA oriented service components. service components are connected via required or provided services which are connected through connectors. Provided/Required services are typed by services that are generally modeled elsewhere (such as within a component that manages this service).
840
TogafApplicationCommunicationDiagram_SHORTNOTE=The purpose of the Application Communication diagram is to depict all models and mappings related to communication between applications in the metamodel entity. 
841
ServiceDataDiagram_NOTE=\n Messages need a dedicated model and definition. The constitution of messages is modeled in this kind of diagram\nHints : message diagrams are most of the time deduced from the class diagrams of business entities, and the information exchange needs between services. They are the parameters of the service operations. The messages model is an extract of the business entities information needed by services. Think about extendibility and reusability, so that service evolution does not require redefining or creating new variants of messages. Messages become frequently XML documents : they have a message as a root, decomposed into message fragments.\nUnder Modelio : create a simple class diagram, having messages as roots, and being decomposed (composition association) into message fragments. 
842
ServiceDataDiagram_SHORTNOTE= Messages need a dedicated model and definition.
843
TogafNewtorkComputingHardwareDiagram_NOTE=\nStarting with the transformation to client-server systems from mainframes and later with the advent of e-Business and J2EE, large enterprises moved predominantly into a highly network based distributed network computing environment with firewalls and demilitarized zones. Currently, most of the applications have a web front-end and, looking at the deployment architecture of these applications, it is very common to find three distinct layers in the network landscape; namely a web presentation layer, a business logic or Application Layer, and a backend data store layer. It is a common practice for applications to be deployed and hosted in a shared and common infrastructure environment. So it becomes highly critical to document the mapping between logical applications and the technology components (e.g., server) that supports the application both in the development and production environments. The purpose of this diagram is to show the \u0022as deployed\u0022 logical view of logical service components in a distributed network computing environment.\nUnder Modelio: Create workstations, servers and connect them using network devices and association. Then, deploy service components by drag & dropping them to workstations and servers. You can also link roles or actors to their environment.
844
TogafNewtorkComputingHardwareDiagram_SHORTNOTE=Representation of the deployment of service components to computing devices (i.e. servers, workstations, \u2026).
845
TogafClassDiagram_NOTE=\nThe key purpose of the Class diagram is to depict the relationships among the critical data entities (or classes) within the enterprise. This diagram is developed to clearly present the relationships and to help understand the lower-level data models for the enterprise.\nHints : this diagram is at a high level of representation (conceptual). We are here interested in modeling the main Business Entities, their properties and relationships. The persistency model (typically for RDB) will be inferred later at the Application Layer.\nUnder Modelio : This is a class diagram, where the main notion is the \u0022Business Entity\u0022.
846
TogafClassDiagram_SHORTNOTE=The key purpose of the Class diagram is to depict the relationships among the critical data entities (or classes) within the enterprise. 
847
TogafDataLifeCycleDiagram_NOTE=\nThe Entity Lifecycle diagram is an essential part of managing business data throughout its lifecycle from conception until disposal within the constraints of the business process. The data is considered as an entity in its own right, decoupled from business process and activity. Each change in state is represented on the diagram which may include the event or rules that trigger that change in state. The separation of data from process allows common data requirements to be identified which enables resource sharing to be achieved more effectively.\n- Hints: Identify the possible states of the entity (for example, a document can be \u0022underCreation\u0022, \u0022underRevision\u0022, \u0022approved\u0022, etc.), and define the possible transitions between each states. A state must be a stable situation of a data : when no action is executed on it, the data is always in one of the identified states.
848
TogafDataLifeCycleDiagram_SHORTNOTE=The Entity Lifecycle diagram is an essential part of managing business entities throughout its lifecycle from conception until disposal within the constraints of the business process. 
849
TogafProcessFlowDiagram_NOTE=\nBusiness Process modeling is done using business process diagrams.\nThe purpose of the business process diagram is to depict all models and mappings related to a process. Business process diagrams show sequential flows of control between activities and may utilize swim-lane techniques to represent ownership and realization of process steps. For example, the application that supports a process step may be shown as a swim-lane. In addition to showing a sequence of activities, business process diagrams can also be used to detail the controls that apply to a process, the events that trigger or result from completion of a process, and also the products that are generated from process execution. Business process diagrams are useful in elaborating the architecture with subject specialists, as they allow the specialist to describe how the job is done for a particular function. Through this process, each process step can become a more fine-grained function and can then in turn be elaborated as a process.\nUnder Modelio : Business process diagrams are modeled using BPMN. Pools and lanes can be assigned to existing actors or organization units. Business Entities can be used to type data objects, and their states (from their entity lifecycle diagrams) can be shown during the processing.
850
TogafProcessFlowDiagram_SHORTNOTE=Business Process modeling is done using business process diagrams.\nThe purpose of the business process diagram is to depict all models and mappings related to a process. 
851
TogafFunctionalDecompositionDiagram_NOTE=\nThe purpose of the Functional Decomposition diagram is to show on a single page the capabilities of an organization that are relevant to the consideration of an architecture. By examining the capabilities of an organization from a functional perspective, it is possible to quickly develop models of what the organization does without being dragged into extended debate on how the organization does it. Once a basic Functional Decomposition diagram has been developed, it becomes possible to layer heat-maps on top of this diagram to show scope and decisions. For example, the capabilities to be implemented in different phases of a change program.\nUnder Modelio : Dedicated dependencies can be used to enrich the model, for example to indicate which application components support which function, which role uses which function, etc. Function decomposition can be expressed by \u0022containment\u0022 (just create a function in another function), or by using the \u0022part\u0022 dependency.
852
TogafFunctionalDecompositionDiagram_SHORTNOTE=The purpose of the Functional Decomposition diagram is to show on a single page the capabilities of an organization that are relevant to the consideration of an architecture. 
853
TogafProductLifeCycleDiagram_NOTE=\nThe purpose of the Product Lifecycle diagram is to assist in understanding the lifecycles of key entities within the enterprise. Understanding product lifecycles is becoming increasingly important with respect to environmental concerns, legislation, and regulation where products must be tracked from manufacture to disposal. Equally, organizations that create products that involve personal or sensitive information must have a detailed understanding of the product lifecycle during the development of Business Architecture in order to ensure rigor in design of controls, processes, and procedures. Examples of this would include credit cards, debit cards, store/loyalty cards, smart cards, user identity credentials (identity cards, passports, etc.).\nUnder Modelio: Product LifeCycleDiagrams are state machine diagrams on BusinessEntities.
854
TogafProductLifeCycleDiagram_SHORTNOTE=The purpose of the Product Lifecycle diagram is to assist in understanding the lifecycles of key entities within the enterprise.
855
TogafBusinessUseCaseDiagram_NOTE=\nA Business Use-Case diagram displays the relationships between consumers and providers of business services. Business services are consumed by actors or other business services and the Business Use-Case diagram provides added richness in describing business capability by illustrating how and when that capability is used. The purpose of the Business Use-Case diagram is to help to describe and validate the interaction between actors and their roles to processes and functions. As the architecture progresses, the use-case can evolve from the business level to include data, application, and technology details. Architectural business use-cases can also be re-used in systems design work.
856
TogafBusinessUseCaseDiagram_SHORTNOTE=A Business Use-Case diagram displays the relationships between consumers and providers of business services.
857
TogafOrganizationDecompositionDiagram_NOTE=\nAn Organization diagram describes the links between actors, and locations within an organization tree. An organization map (organization diagram) should provide a chain of command of owners and decision makers in the organization. Although it is not the intent of the Organization diagram to link goals to organization, it should be possible to intuitively link the goals to the stakeholders from the Organization diagram.\nThis diagram can also describe the definition of actors and their responsibilities : the organization is presented in terms of connections between actors, or between actors and organization units showing hierarchical links, communications and responsibilities.\nMissions and responsibilities within an organization can also be emphasized by presenting the main information flows circulating between the major participants of the enterprise. This presents which information is received, processes or emitted by who in the organization, showing thus the responsibilities of organizational elements.\nUnder Modelio : organization units can be deployed under locations (drag & drop organization units from the explorer to locations in the diagram). \u0022localization\u0022 dependencies express where roles or actors are localized. As in every diagram, goals can be dragged and dropped, and traced to organizations roles.
858
TogafOrganizationDecompositionDiagram_SHORTNOTE=An Organization diagram describes the links between actors, and locations within an organization tree. 
859
TogafEventDiagram_NOTE=The purpose of the process map diagram is to depict the relationship between events and process. Certain events such as arrival of certain information (e.g., customer submits sales order) or a certain point in time (e.g., end of fiscal quarter)  cause work and certain actions need to be undertaken within the business. These are often referred to as business events or simply events and are considered as triggers for a process. It is important to note that the event has to trigger a process and generate a business response or result.\nUnder Modelio:  Events are connected to processes using \u0022flow\u0022 dependencies, roles can be initiator or participant to processes, products can be connected to processes through the \u0022flow\u0022 dependencies.
860
TogafEventDiagram_SHORTNOTE=The purpose of the process map diagram is to depict the relationship between events and process, and to show an overview of the business processes.
861
TogafValueChainDiagram_NOTE=\nA Value Chain diagram provides a high-level orientation view of an enterprise and how it interacts with the outside world. In contrast to the more formal Functional Decomposition diagram, the Value Chain diagram focuses on presentational impact. The purpose of this diagram is to quickly on-board and align stakeholders for a particular change initiative, so that all participants understand the high-level functional and organizational context of the architecture engagement. A usual practice consists in showing a simplified business process diagram, and for each task defining its value factors and changes needed.\nUnder Modelio : Use sequence dependencies between functions to express value chains. The \u0022 Value factors\u0022 and \u0022changes needed\u0022 types of notes are expressing this key information.
862
TogafValueChainDiagram_SHORTNOTE=A Value Chain diagram provides a high-level orientation view of an enterprise and how it interacts with the outside world. 
863
TogafLocationDiagram_NOTE=This kind of diagram helps in formalizing the locations of an enterprise, and the distribution of platforms and business services on it.
864
TogafLocationDiagram_SHORTNOTE=This kind of diagram helps in formalizing the locations of an enterprise, and the distribution of platforms and business services on it.
865
TogafMatrixDiagram_NOTE=\nThe purpose of Matrix diagrams is to define dependencies that will produce the Excell Matrices. Matrix diagrams are also useful to define general purpose traceabilities between elements.\nUnder Modelio: Drag and drop in the diagram the origin and destination elements, and trace the appropriate links.
866
TogafMatrixDiagram_SHORTNOTE=The purpose of Matrix diagrams is to define dependencies that will produce the Excell Matrices. Matrix diagrams are also useful to define general purpose traceabilities between elements.
867
TogafUseCaseDiagram_NOTE=\nA Use-Case diagram displays the relationships between consumers and providers of services.  Services are consumed by actors or other component services and the Use-Case diagram provides added richness in describing service components functionalities by illustrating how and when these functionalities are used. The purpose of the Use-Case diagram is to help describing and validating the interaction between actors and their roles with applications. As the architecture progresses, the use-case can evolve from functional information to include technical realization details. Architectural use-cases can also be re-used in more detailed systems design work.\nUnder Modelio : Create use cases, drag and drop roles and actors, drag and drop service components, and draw communication links between roles and use cases, and component realization links between components and use cases.
868
TogafUseCaseDiagram_SHORTNOTE=A Use-Case diagram displays the relationships between consumers and providers of Services. 
869

    
870
migration_success_title=Migration Success
871
migration_success_message=Your project is now ready to be migrated to Modelio 3.7
872
migration_failled_title=Migration Failed
873
migration_failled_lock= The Migration has failed due to a read only element of the model.If your project is an SVN model, please take locks on all the model. \n\n.More informations : \n  {0}
874