The Access Relationship represents the ability of behavior and active structure elements to observe or act upon passive structure elements.
+
+
Category:
+
Dependency.
+
+
Examples:
+
Create a new object, Read data from an object, Write or modify object data, Delete an object.
+ The “Create Invoice” sub-process writes/creates the “Invoice” business object; the “Send Invoice” sub-process reads that object
+
+
+
\ No newline at end of file
diff --git a/hints/aggregation.html b/hints/aggregation.html
new file mode 100644
index 0000000000000000000000000000000000000000..1249959f4481cc1a281f855db99ae4d0dad0c510
--- /dev/null
+++ b/hints/aggregation.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Aggregation Relationship
+
+
+
+
The Aggregation Relationship represents that an element combines one or more other concepts.
+
+
Category:
+
Structural.
+
+
Examples:
+
A Car Insurance Business Product aggregates a Business Contract and some Business Services. "Customer File" aggregates an "Insurance Policy" and "Insurance Claim".
+
+
\ No newline at end of file
diff --git a/hints/application_collaboration.html b/hints/application_collaboration.html
new file mode 100644
index 0000000000000000000000000000000000000000..e83669bbb005b0bc3d346e776b02a7297f4eec03
--- /dev/null
+++ b/hints/application_collaboration.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Application Collaboration
+
+
+
+
An Application Collaboration represents an aggregate of two or more application internal active structure elements that work together to perform collective application behavior.
+
+
Category:
+
Application. Active Structure.
+
+
Examples:
+
Two Application Components collaborate in transaction administration: an Accounting component and a Billing component. This collaboration performs the task "Administrate transactions".
+
+
\ No newline at end of file
diff --git a/hints/application_component.html b/hints/application_component.html
new file mode 100644
index 0000000000000000000000000000000000000000..80136c063ae9e03e6ef2fec3108e9762d2310df7
--- /dev/null
+++ b/hints/application_component.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Application Component
+
+
+
+
An Application Component represents an encapsulation of application functionality aligned to implementation structure, which is modular and replaceable.
+
+
Category:
+
Application. Active Structure.
+
+
Examples:
+
CRM System, Web portal, Financial Application, Customer Data Access.
+
+
\ No newline at end of file
diff --git a/hints/application_event.html b/hints/application_event.html
new file mode 100644
index 0000000000000000000000000000000000000000..866f15333f522e3f71b336655cf53e8fe218a7e8
--- /dev/null
+++ b/hints/application_event.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Application Event
+
+
+
+
An Application Event represents an application state change.
+
+
Category:
+
Application. Behavioural.
+
+
Examples:
+
Claim received, Request for quotation.
+
+
\ No newline at end of file
diff --git a/hints/application_function.html b/hints/application_function.html
new file mode 100644
index 0000000000000000000000000000000000000000..fc7febfcebcccfafdf694b468a6ecdbc9e6352a8
--- /dev/null
+++ b/hints/application_function.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Application Function
+
+
+
+
An Application Function represents automated behavior that can be performed by an application component.
+
+
\ No newline at end of file
diff --git a/hints/application_interaction.html b/hints/application_interaction.html
new file mode 100644
index 0000000000000000000000000000000000000000..baa4f050cc5341c9bda817a555cb6891aff23587
--- /dev/null
+++ b/hints/application_interaction.html
@@ -0,0 +1,19 @@
+
+
+
+
+
+ Application Interaction
+
+
+
+
+
An Application Interaction represents a unit of collective application behavior performed by (a collaboration of) two or more application components.
+
+
Category:
+
Application. Behavioural.
+
+
Examples:
+
Administrate transactions, Client profile creation, Update customer records
+
+
\ No newline at end of file
diff --git a/hints/application_interface.html b/hints/application_interface.html
new file mode 100644
index 0000000000000000000000000000000000000000..d9550e6d84ecda8db4818620ad7acc90837bf510
--- /dev/null
+++ b/hints/application_interface.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Application Interface
+
+
+
+
An Application Interface represents a point of access where application services are made available to a user, another application component, or a node.
+
+
Category:
+
Application. Active Structure.
+
+
Examples:
+
Transaction data exchange, Web services
+
+
\ No newline at end of file
diff --git a/hints/application_process.html b/hints/application_process.html
new file mode 100644
index 0000000000000000000000000000000000000000..464e016a8d4c378b115d2527d108591b39730e07
--- /dev/null
+++ b/hints/application_process.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Application Process
+
+
+
+
An Application Process represents a sequence of application behaviors that achieves a specific result.
+
+
Category:
+
Application. Behavioural.
+
+
Examples:
+
Claims adjudication process, General ledger update job.
+
+
\ No newline at end of file
diff --git a/hints/application_service.html b/hints/application_service.html
new file mode 100644
index 0000000000000000000000000000000000000000..94774fb5865e993b9ce497c4da2898235d6cc430
--- /dev/null
+++ b/hints/application_service.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Application Service
+
+
+
+
An Application Service represents an explicitly defined exposed application behavior.
+
+
\ No newline at end of file
diff --git a/hints/assignment.html b/hints/assignment.html
new file mode 100644
index 0000000000000000000000000000000000000000..7f16fd81009a43e6c70ec4d9a8d5d283951a1b88
--- /dev/null
+++ b/hints/assignment.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Assignment Relationship
+
+
+
+
The Assignment Relationship represents the allocation of responsibility, performance of behavior, storage, or execution.
+
+
Category:
+
Structural.
+
+
Examples:
+
A Business Actor assigned to a Business Role. A Business Role assigned to a Business Process or Function. An Application Component assigned to an Application Function.
+
+
\ No newline at end of file
diff --git a/hints/association.html b/hints/association.html
new file mode 100644
index 0000000000000000000000000000000000000000..b319238c17ad5d19d992439ffd0d7e986548fea8
--- /dev/null
+++ b/hints/association.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Association Relationship
+
+
+
+
The Association Relationship represents an unspecified relationship, or one that is not represented by another ArchiMate relationship.
+
+
Category:
+
Dependency.
+
+
Examples:
+
Some Business Objects and a Business Contract are all associated with each other.
+
+
\ No newline at end of file
diff --git a/hints/business_actor.html b/hints/business_actor.html
new file mode 100644
index 0000000000000000000000000000000000000000..13b641ba47306455c0743c43a1a5cacb9db11c84
--- /dev/null
+++ b/hints/business_actor.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Business Actor
+
+
+
+
A Business Actor represents a business entity that is capable of performing behavior.
+
+
Category:
+
Business. Active Structure.
+
+
Examples:
+
A Customer, Marketing & Communications department, Director of Finance, Secretary, Admissions Department, Product Development.
+
+
\ No newline at end of file
diff --git a/hints/business_collaboration.html b/hints/business_collaboration.html
new file mode 100644
index 0000000000000000000000000000000000000000..3b2ea3e51e63930ca0cbe6afa04c2c099c283680
--- /dev/null
+++ b/hints/business_collaboration.html
@@ -0,0 +1,19 @@
+
+
+
+
+
+ Business Collaboration
+
+
+
+
A Business Collaboration represents an aggregate of two or more business internal active structure elements that work together to perform collective behavior.
+
+
+
Category:
+
Business. Active Structure.
+
+
Examples:
+
The Business Roles of Sales Department and Advertising may form a temporary Business Collaboration in order to push a product to market. The Business Roles of Home Insurance Seller and Travel Insurance Seller may form a temporary Business Collaboration in order to form combined Insurance Selling service.
+
+
\ No newline at end of file
diff --git a/hints/business_event.html b/hints/business_event.html
new file mode 100644
index 0000000000000000000000000000000000000000..bfd0d905249a0cf87a4a65ec0505d1c9311b4c7e
--- /dev/null
+++ b/hints/business_event.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Business Event
+
+
+
+
A Business Event represents a business-related state change.
+
+
Category:
+
Business. Behavioural.
+
+
Examples:
+
Request for Insurance, Claim Received, Application Form Received, Send Product Portfolio.
+
+
\ No newline at end of file
diff --git a/hints/business_function.html b/hints/business_function.html
new file mode 100644
index 0000000000000000000000000000000000000000..b633f85f838b921a6613e438ebf14684afea9482
--- /dev/null
+++ b/hints/business_function.html
@@ -0,0 +1,19 @@
+
+
+
+
+
+ Business Function
+
+
+
+
A Business Function represents a collection of business behavior based on a chosen set of criteria such as required business resources and/or competencies, and is managed or performed as a whole.
+
+
+
\ No newline at end of file
diff --git a/hints/business_interaction.html b/hints/business_interaction.html
new file mode 100644
index 0000000000000000000000000000000000000000..f02f96cf49b6c6be38188286ca1099d56886e235
--- /dev/null
+++ b/hints/business_interaction.html
@@ -0,0 +1,19 @@
+
+
+
+
+
+ Business Interaction
+
+
+
+
A Business Interaction represents a unit of collective business behavior performed by (a collaboration of) two or more business actors, business roles, or business collaborations.
+
+
Category:
+
Business. Behavioural.
+
+
Examples:
+
Formalise Request, Check and Sign Contract, Take out Combined Insurance.
+
+
+
\ No newline at end of file
diff --git a/hints/business_interface.html b/hints/business_interface.html
new file mode 100644
index 0000000000000000000000000000000000000000..338bf6e70601e0b4a1627391e24e5cbad225e440
--- /dev/null
+++ b/hints/business_interface.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Business Interface
+
+
+
+
A Business Interface represents a point of access where business services are made available to the environment.
+
+
Category:
+
Business. Active Structure.
+
+
Examples:
+
Telephone, Email, Call centre, Web Chat, Help Desk.
+
+
\ No newline at end of file
diff --git a/hints/business_process.html b/hints/business_process.html
new file mode 100644
index 0000000000000000000000000000000000000000..361ee295f36a1057db881218ea9c549b382519b8
--- /dev/null
+++ b/hints/business_process.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Business Process
+
+
+
+
A Business Process represents a sequence of business behaviors that achieves a specific result such as a defined set of products or business services.
+
+
\ No newline at end of file
diff --git a/hints/business_role.html b/hints/business_role.html
new file mode 100644
index 0000000000000000000000000000000000000000..4ddd1114a59ea12ca6784882a839051b936bb270
--- /dev/null
+++ b/hints/business_role.html
@@ -0,0 +1,19 @@
+
+
+
+
+
+ Business Role
+
+
+
+
A Business Role represents the responsibility for performing specific behavior, to which an actor can be assigned, or the part an actor plays in a particular action or event.
+
+
+
\ No newline at end of file
diff --git a/hints/business_service.html b/hints/business_service.html
new file mode 100644
index 0000000000000000000000000000000000000000..1d01066f75e2d3974173d16566a7e1822f841a80
--- /dev/null
+++ b/hints/business_service.html
@@ -0,0 +1,17 @@
+
+
+
+
+
+ Business Service
+
+
+
A Business Service represents explicitly defined behavior that a business role, business actor, or business collaboration exposes to its environment.
+
+
Category:
+
Business. Behavioural.
+
+
Examples:
+
Customer Information Service, Claims Payment Service, Enrolment Service.
+
+
\ No newline at end of file
diff --git a/hints/canvas_block.html b/hints/canvas_block.html
new file mode 100644
index 0000000000000000000000000000000000000000..700009c64056b3abc86029c4b73c007afc0d4e53
--- /dev/null
+++ b/hints/canvas_block.html
@@ -0,0 +1,13 @@
+
+
+
+
+
+ Canvas Block
+
+
+
+
A Block Object is a container area that can contain text and an icon. You can also provide your own Help Hints. You can lock the Block if you want to make it read-only.
+
A typical scenario is to create a number of container Blocks on the Canvas, arrange them into the desired framework, lock them, and then save the Canvas as a template.
+
+
\ No newline at end of file
diff --git a/hints/canvas_connection.html b/hints/canvas_connection.html
new file mode 100644
index 0000000000000000000000000000000000000000..e4f3c9ccc615c36cd5b93cb7ffcd65902b6af172
--- /dev/null
+++ b/hints/canvas_connection.html
@@ -0,0 +1,13 @@
+
+
+
+
+
+ Canvas Connection
+
+
+
+
A connection between two objects with no explicit semantic meaning.
+
You can lock the Connection if you want to make it read-only.
+
+
\ No newline at end of file
diff --git a/hints/canvas_diagram.html b/hints/canvas_diagram.html
new file mode 100644
index 0000000000000000000000000000000000000000..747101b62e99290d6014662e124dabbdedfe5d43
--- /dev/null
+++ b/hints/canvas_diagram.html
@@ -0,0 +1,14 @@
+
+
+
+
+
+ Canvas
+
+
+
+
A Canvas to hold Blocks, Images, Stickies and Connections. You can also provide your own Help Hints.
+
A typical scenario is to create a number of container Blocks and Stickies on the Canvas, arrange them into the desired framework, lock them, and then save the Canvas as a template.
+
You can drag and drop image files from the desktop to create Images on the Canvas.
+
+
\ No newline at end of file
diff --git a/hints/canvas_image.html b/hints/canvas_image.html
new file mode 100644
index 0000000000000000000000000000000000000000..7fe0e579f3a5043f98d0e0f75d808296a01b11ca
--- /dev/null
+++ b/hints/canvas_image.html
@@ -0,0 +1,13 @@
+
+
+
+
+
+ Canvas Image
+
+
+
+
A Canvas Image. Choose your own image to add to the area.
+
You can lock the Image if you want to make it read-only.
+
+
\ No newline at end of file
diff --git a/hints/canvas_sticky.html b/hints/canvas_sticky.html
new file mode 100644
index 0000000000000000000000000000000000000000..93bd562552e963ab59af790b2c627acfaa936057
--- /dev/null
+++ b/hints/canvas_sticky.html
@@ -0,0 +1,14 @@
+
+
+
+
+
+ Canvas Sticky
+
+
+
+
A Sticky element for the Canvas.
+
Add text and an icon to the Sticky. You can lock the Sticky if you want to make it read-only.
+
Any Notes will appear in the tooltip for the Sticky.
+
+
\ No newline at end of file
diff --git a/hints/capability.html b/hints/capability.html
new file mode 100644
index 0000000000000000000000000000000000000000..074fefec8b25a2c4997b6237b7cae757e2a11003
--- /dev/null
+++ b/hints/capability.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Capability
+
+
+
+
A Capability represents an ability that an active structure element, such as an organization, person, or system, possesses.
+
+
Category:
+
Strategy. Behaviour.
+
+
Examples:
+
Digital Customer Management, Data Analysis, Product Management, Productise Open Source Software.
+
+
\ No newline at end of file
diff --git a/hints/communication_network.html b/hints/communication_network.html
new file mode 100644
index 0000000000000000000000000000000000000000..ef2f2f7f5896f4954a074ef4ab1f54c0460917ad
--- /dev/null
+++ b/hints/communication_network.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Communication Network
+
+
+
+
A Communication Network represents a set of structures that connects devices or system software for transmission, routing, and reception of data.
+
+
Category:
+
Technology. Active Structure.
+
+
Examples:
+
LAN. Wireless. Wide Area Network.
+
+
\ No newline at end of file
diff --git a/hints/composition.html b/hints/composition.html
new file mode 100644
index 0000000000000000000000000000000000000000..7849207d46aba7583259200d270f795c44ee5031
--- /dev/null
+++ b/hints/composition.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Composition Relationship
+
+
+
+
The Composition relationship represents that an element consists of one or more other concepts.
+
+
Category:
+
Structural.
+
+
Examples:
+
An Application Component may be composed of two or more sub-components.
+
+
\ No newline at end of file
diff --git a/hints/connection.html b/hints/connection.html
new file mode 100644
index 0000000000000000000000000000000000000000..4bdd799483070a106fb84439c08b56027e80029a
--- /dev/null
+++ b/hints/connection.html
@@ -0,0 +1,12 @@
+
+
+
+
+
+ Connection
+
+
+
+
A plain connection between two objects with no explicit semantic meaning.
+
+
\ No newline at end of file
diff --git a/hints/constraint.html b/hints/constraint.html
new file mode 100644
index 0000000000000000000000000000000000000000..6d0b5375230816598e25c5f2dd3b376cf3b0d232
--- /dev/null
+++ b/hints/constraint.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Constraint
+
+
+
+
A Constraint represents a limitation on aspects of the architecture, its implementation process, or its realization.
+
+
Category:
+
Motivation
+
+
Examples:
+
"Application should be realised in Java", "Cost should be below budget", "iPad only version", "Must use MIT license"
+
+
\ No newline at end of file
diff --git a/hints/contract.html b/hints/contract.html
new file mode 100644
index 0000000000000000000000000000000000000000..439bf8a0c1a9ae686e3e898e9d461a5a5ac70364
--- /dev/null
+++ b/hints/contract.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Contract
+
+
+
+
A Contract represents a formal or informal specification of an agreement between a provider and a consumer that specifies the rights and obligations associated with a product and establishes functional and non-functional parameters for interaction.
+
+
Category:
+
Business. Passive Structure.
+
+
Examples:
+
Travel Insurance Policy.
+
+
\ No newline at end of file
diff --git a/hints/course_of_action.html b/hints/course_of_action.html
new file mode 100644
index 0000000000000000000000000000000000000000..fb2d84b3904d12b88714095e74f79ef56a4de02d
--- /dev/null
+++ b/hints/course_of_action.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Course of Action
+
+
+
+
A Course of Action represents an approach or plan for configuring some capabilities and resources of the enterprise, undertaken to achieve a goal.
+
+
Category:
+
Strategy. Behaviour.
+
+
Examples:
+
Acquire company, Merge organizations, Provide repository support.
+
+
\ No newline at end of file
diff --git a/hints/data_object.html b/hints/data_object.html
new file mode 100644
index 0000000000000000000000000000000000000000..47db28a4693d09ae46e2946fccffc39c5bdc5ace
--- /dev/null
+++ b/hints/data_object.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Data Object
+
+
+
+
A Data Object represents data structured for automated processing.
+
+
\ No newline at end of file
diff --git a/hints/deliverable.html b/hints/deliverable.html
new file mode 100644
index 0000000000000000000000000000000000000000..adb37ffba7335f228a66f1ac2bd42f06dc125f58
--- /dev/null
+++ b/hints/deliverable.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Deliverable
+
+
+
+
A Deliverable represents a precisely-defined result of a work package.
+
+
Category:
+
Implementation and Migration
+
+
Examples:
+
Software, Hardware, CRM System, Report, Paper
+
+
\ No newline at end of file
diff --git a/hints/device.html b/hints/device.html
new file mode 100644
index 0000000000000000000000000000000000000000..1aec3a94c8b26f1bff6c4c2f74acc8158b2a0ec1
--- /dev/null
+++ b/hints/device.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Device
+
+
+
+
A Device represents a physical IT resource upon which system software and artifacts may be stored or deployed for execution.
+
+
Category:
+
Technology. Active Structure.
+
+
Examples:
+
File Server, Router, Mainframe, Desktop PC, IBM System Z.
+
+
\ No newline at end of file
diff --git a/hints/diagram_image.html b/hints/diagram_image.html
new file mode 100644
index 0000000000000000000000000000000000000000..7d9d3a82dd2a219d74fd6d8b1e2af7740b0c18b6
--- /dev/null
+++ b/hints/diagram_image.html
@@ -0,0 +1,12 @@
+
+
+
+
+
+ Image
+
+
+
+
A diagram image.
+
+
\ No newline at end of file
diff --git a/hints/distribution_network.html b/hints/distribution_network.html
new file mode 100644
index 0000000000000000000000000000000000000000..1f771adf297ec2797518c71f9e5880a0fe6a5177
--- /dev/null
+++ b/hints/distribution_network.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Distribution Network
+
+
+
+
A Distribution Network represents a physical network used to transport materials or energy.
+
+
Category:
+
Physical. Active Structure.
+
+
Examples:
+
Local Trucking, Overseas Shipping.
+
+
\ No newline at end of file
diff --git a/hints/driver.html b/hints/driver.html
new file mode 100644
index 0000000000000000000000000000000000000000..cb511ee61f8bbe242ff4feb6fd92d6d6a88f5436
--- /dev/null
+++ b/hints/driver.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Driver
+
+
+
+
A Driver represents an external or internal condition that motivates an organization to define its goals and implement the changes necessary to achieve them.
+
+
Category:
+
Motivation
+
+
Examples:
+
"Customer satisfaction", "Compliance to legislation", "Profitability", "Economic changes", "Changing legislation"
+
+
\ No newline at end of file
diff --git a/hints/equipment.html b/hints/equipment.html
new file mode 100644
index 0000000000000000000000000000000000000000..d452a9925999d4140e44c2bf78ea41eaf6b81f53
--- /dev/null
+++ b/hints/equipment.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Equipment
+
+
+
+
Equipment represents one or more physical machines, tools, or instruments that can create, use, store, move, or transform materials.
+
+
Category:
+
Physical. Active Structure.
+
+
Examples:
+
MRI scanner, Assembly line.
+
+
\ No newline at end of file
diff --git a/hints/facility.html b/hints/facility.html
new file mode 100644
index 0000000000000000000000000000000000000000..46931b59cb3f994f78adcd15d57efb7af406b6ba
--- /dev/null
+++ b/hints/facility.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Facility
+
+
+
+
A Facility represents a physical structure or environment.
+
+
\ No newline at end of file
diff --git a/hints/flow.html b/hints/flow.html
new file mode 100644
index 0000000000000000000000000000000000000000..cef62b282bec270027a2fc31a000fecd055bfdb3
--- /dev/null
+++ b/hints/flow.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Flow Relationship
+
+
+
+
The Flow Relationship represents transfer (e.g. of information, goods or money) from one element to another.
+
+
Category:
+
Dynamic.
+
+
Examples:
+
A "Claim assessment" Business Function forwards decisions about the claim to the "Claim settlement" Business Function.
+
+
\ No newline at end of file
diff --git a/hints/folder.html b/hints/folder.html
new file mode 100644
index 0000000000000000000000000000000000000000..bb682f6c37021e58a5624a2c2d130f5179dcc3a0
--- /dev/null
+++ b/hints/folder.html
@@ -0,0 +1,13 @@
+
+
+
+
+
+ Folder
+
+
+
+
A folder to contain elements.
+
Note that the root folders cannot be deleted.
+
+
\ No newline at end of file
diff --git a/hints/gap.html b/hints/gap.html
new file mode 100644
index 0000000000000000000000000000000000000000..cab679085133eca1d71fc49799f50f5797e382ed
--- /dev/null
+++ b/hints/gap.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Gap
+
+
+
+
A Gap represents a statement of difference between two plateaus.
+
+
Category:
+
Implementation and Migration
+
+
Examples:
+
"Gap between the Baseline and Target infrastructure", "Knowledge of how to address customer needs".
+
+
\ No newline at end of file
diff --git a/hints/goal.html b/hints/goal.html
new file mode 100644
index 0000000000000000000000000000000000000000..d47ac0e7b8e137aa7c50d45f63ab2d9b9ada2b02
--- /dev/null
+++ b/hints/goal.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Goal
+
+
+
+
A Goal represents a high-level statement of intent, direction, or desired end state for an organization and its stakeholders.
+
+
Category:
+
Motivation
+
+
Examples:
+
Increase profit, reduce waiting times at the helpdesk, introduce on-line portfolio management, more sales
+
+
\ No newline at end of file
diff --git a/hints/group.html b/hints/group.html
new file mode 100644
index 0000000000000000000000000000000000000000..cc068a8cf03d361157cc4f47c8bbb9f37de218c7
--- /dev/null
+++ b/hints/group.html
@@ -0,0 +1,17 @@
+
+
+
+
+
+ Group
+
+
+
+
The Group box denotes a collection of objects that belong together but are not aggregated or composed as with the Grouping element.
+
+
The Group provides a convenient visual collection of elements, without any semantic relationships.
+
+
Examples:
+
Group Roles and Actors, Business Layers, Application Layers.
+
+
\ No newline at end of file
diff --git a/hints/grouping.html b/hints/grouping.html
new file mode 100644
index 0000000000000000000000000000000000000000..453dea68d159dc38202b47f03809b475bd6bd54b
--- /dev/null
+++ b/hints/grouping.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Grouping
+
+
+
+
The Grouping element aggregates or composes concepts that belong together based on some common characteristic.
+
+
Category:
+
Other. Composite.
+
+
Examples:
+
Aggregate two Processes and an Object that together Realize a Service
+
+
\ No newline at end of file
diff --git a/hints/implementation_event.html b/hints/implementation_event.html
new file mode 100644
index 0000000000000000000000000000000000000000..37dfe7c5c17037f97afc31db1d6371ff44fe1d13
--- /dev/null
+++ b/hints/implementation_event.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Implementation Event
+
+
+
+
An Implementation Event represents a state change related to implementation or migration.
+
+
Category:
+
Implementation and Migration
+
+
Examples:
+
"Release to production", "Project initiation phase completed".
+
+
\ No newline at end of file
diff --git a/hints/influence.html b/hints/influence.html
new file mode 100644
index 0000000000000000000000000000000000000000..a609d1d8f8f236662cbd9ec5e51e7592f93d9b89
--- /dev/null
+++ b/hints/influence.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Influence Relationship
+
+
+
+
The Influence Relationship represents that an element affects the implementation or achievement of some motivation element.
+
+
Category:
+
Dependency.
+
+
Examples:
+
The degree in which the goal to increase customer satisfaction is realized may be represented by the percentage of satisfied customers that participate in a market interview.
+
+
\ No newline at end of file
diff --git a/hints/junction.html b/hints/junction.html
new file mode 100644
index 0000000000000000000000000000000000000000..f39c91da7700740b8dc0a42f7ff4c7790a215b37
--- /dev/null
+++ b/hints/junction.html
@@ -0,0 +1,20 @@
+
+
+
+
+
+ Junction
+
+
+
+
A Junction is used to connect relationships of the same type.
+
+
There are two types - And and Or.
+
+
Category:
+
Other.
+
+
Examples:
+
An "assess application" Business Process can lead to a choice Junction (split) to accept or reject the client application and route to alternative processes for each case.
+
+
\ No newline at end of file
diff --git a/hints/legend.html b/hints/legend.html
new file mode 100644
index 0000000000000000000000000000000000000000..f25333ebe081d90ff3281fb80d0344f2c3b1a614
--- /dev/null
+++ b/hints/legend.html
@@ -0,0 +1,12 @@
+
+
+
+
+
+ Legend
+
+
+
+
A Legend can be included in an ArchiMate View to show all icons and names of the concepts within it.
+
+
\ No newline at end of file
diff --git a/hints/location.html b/hints/location.html
new file mode 100644
index 0000000000000000000000000000000000000000..386e4d896a7fbff25679f6b489b7a75419bc0db8
--- /dev/null
+++ b/hints/location.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Location
+
+
+
+
A Location represents a conceptual or physical place or position where concepts are located (e.g., structure elements) or performed (e.g., behavior elements).
+
+
Category:
+
Other. Composite.
+
+
Examples:
+
Main Office, Local Office, Room.
+
+
\ No newline at end of file
diff --git a/hints/material.html b/hints/material.html
new file mode 100644
index 0000000000000000000000000000000000000000..80a36073b371357e1d82d6062aa9916962f6a66c
--- /dev/null
+++ b/hints/material.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Material
+
+
+
+
Material represents tangible physical matter or energy.
+
+
Category:
+
Physical. Passive Structure.
+
+
Examples:
+
Plastic Case, Internal Antenna, Speedometer.
+
+
\ No newline at end of file
diff --git a/hints/meaning.html b/hints/meaning.html
new file mode 100644
index 0000000000000000000000000000000000000000..fbddfeb0d33aa6c60a43ce5be59db97051dc05e5
--- /dev/null
+++ b/hints/meaning.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Meaning
+
+
+
+
Meaning represents the knowledge or expertise present in, or the interpretation given to, a concept in a particular context.
A Node represents a computational or physical resource that hosts, manipulates, or interacts with other computational or physical resources.
+
+
Category:
+
Technology. Active Structure.
+
+
Examples:
+
Mainframe, Unix Server Farm, Application Server, Firewall.
+
+
\ No newline at end of file
diff --git a/hints/note.html b/hints/note.html
new file mode 100644
index 0000000000000000000000000000000000000000..319ab02b4889f68b38fc8dc1392b8c1165db057d
--- /dev/null
+++ b/hints/note.html
@@ -0,0 +1,13 @@
+
+
+
+
+
+ Note
+
+
+
+
A Note is simply a place to add user annotations to a diagram.
+
A Note has no semantic meaning in the ArchiMate language.
+
+
\ No newline at end of file
diff --git a/hints/outcome.html b/hints/outcome.html
new file mode 100644
index 0000000000000000000000000000000000000000..d82a805c1384f001466d7823298980a2f74441c6
--- /dev/null
+++ b/hints/outcome.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Outcome
+
+
+
+
An Outcome represents an end result, effect, or consequence of a certain state of affairs.
+
+
Category:
+
Motivation
+
+
Examples:
+
"First-place ranking achieved", "Key supplier partnerships in place", "2015 quarterly profits rose 10%"
+
+
\ No newline at end of file
diff --git a/hints/path.html b/hints/path.html
new file mode 100644
index 0000000000000000000000000000000000000000..8507c39cf29b5b0d44199f0cc2544de05d50590a
--- /dev/null
+++ b/hints/path.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Path
+
+
+
+
A Path represents a link between two or more technology internal active structure elements, through which these elements can exchange data, energy, or material.
+
+
Category:
+
Technology. Active Structure.
+
+
Examples:
+
Message Queuing, Data Replication Path.
+
+
\ No newline at end of file
diff --git a/hints/plateau.html b/hints/plateau.html
new file mode 100644
index 0000000000000000000000000000000000000000..82bdd6199dc7f3fffda4b582f6e39b3c67d8cd11
--- /dev/null
+++ b/hints/plateau.html
@@ -0,0 +1,20 @@
+
+
+
+
+
+ Plateau
+
+
+
+
+
+
A Plateau represents a relatively stable state of the architecture that exists during a limited period of time.
+
+
Category:
+
Implementation and Migration
+
+
Examples:
+
Baseline, Transition 1, Strategic Plan complete, Services in place.
+
+
\ No newline at end of file
diff --git a/hints/principle.html b/hints/principle.html
new file mode 100644
index 0000000000000000000000000000000000000000..4085e11799a3884978a6e294ac37cf9496644796
--- /dev/null
+++ b/hints/principle.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Principle
+
+
+
+
A Principle represents a statement of intent defining a general property that applies to any system in a certain context in the architecture.
+
+
Category:
+
Motivation
+
+
Examples:
+
"Systems should be customer facing", "Customers should have a great experience", "Colleagues should be informed", "Open Source Software should be used"
+
+
\ No newline at end of file
diff --git a/hints/product.html b/hints/product.html
new file mode 100644
index 0000000000000000000000000000000000000000..35aa902e1a7d5647b358548605259615cfc67170
--- /dev/null
+++ b/hints/product.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Product
+
+
+
+
A Product represents a coherent collection of services and/or passive structure elements, accompanied by a contract, which is offered as a whole to (internal or external) customers.
+
+
Category:
+
Business. Composite.
+
+
Examples:
+
A Travel Insurance Product consisting of Insurance Services and a Contract.
+
+
\ No newline at end of file
diff --git a/hints/realization.html b/hints/realization.html
new file mode 100644
index 0000000000000000000000000000000000000000..96dd61834496169ef6d33952edde48d345b74149
--- /dev/null
+++ b/hints/realization.html
@@ -0,0 +1,19 @@
+
+
+
+
+
+ Realization Relationship
+
+
+
+
The Realization Relationship represents that an element plays a critical role in the creation, achievement, sustenance, or operation of a more abstract element.
+
+
+
Category:
+
Structural.
+
+
Examples:
+
An Application Component, "Financial Application", realizes a "Billing" Service. A "Billing" Data Object realizes the Business Object, "Invoice".
+
+
\ No newline at end of file
diff --git a/hints/representation.html b/hints/representation.html
new file mode 100644
index 0000000000000000000000000000000000000000..b57cca2dffdb69cd8174e8f2874e93a4afbf1f2c
--- /dev/null
+++ b/hints/representation.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Representation
+
+
+
+
A Representation represents a perceptible form of the information carried by a business object.
+
+
Category:
+
Business. Passive Structure.
+
+
Examples:
+
Paper Bill, Request Form, Claim Form, Online Form.
+
+
\ No newline at end of file
diff --git a/hints/requirement.html b/hints/requirement.html
new file mode 100644
index 0000000000000000000000000000000000000000..edc01f70b50d92d6a9d22bceaa260791db34a7c6
--- /dev/null
+++ b/hints/requirement.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Requirement
+
+
+
+
A Requirement represents a statement of need defining a property that applies to a specific system as described by the architecture.
+
+
Category:
+
Motivation
+
+
Examples:
+
"Assign personal assistant", "Provide on-line portfolio service", "Provide on-line information service", "Use open source software"
+
+
\ No newline at end of file
diff --git a/hints/resource.html b/hints/resource.html
new file mode 100644
index 0000000000000000000000000000000000000000..408d39b79b577d955ce65a94bda208edd29b2016
--- /dev/null
+++ b/hints/resource.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Resource
+
+
+
+
A Resource represents an asset owned or controlled by an individual or organization.
+
+
\ No newline at end of file
diff --git a/hints/sketch_sticky.html b/hints/sketch_sticky.html
new file mode 100644
index 0000000000000000000000000000000000000000..a3137c6df6a3a4695955a9594869565c2b9979b0
--- /dev/null
+++ b/hints/sketch_sticky.html
@@ -0,0 +1,11 @@
+
+
+
+
+
+ Sticky
+
+
+
A "Sticky" figure for your Sketch.
+
+
\ No newline at end of file
diff --git a/hints/specialization.html b/hints/specialization.html
new file mode 100644
index 0000000000000000000000000000000000000000..ed86259fc5d7da0a44a9f8042ee990d7afda3375
--- /dev/null
+++ b/hints/specialization.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Specialization Relationship
+
+
+
+
The Specialization Relationship Represents that an element is a particular kind of another element.
+
+
Category:
+
Other.
+
+
Examples:
+
A "Take out travel insurance" and a "Take out luggage insurance" process are a specialization of a more generic "Take out insurance" process.
+
+
\ No newline at end of file
diff --git a/hints/stakeholder.html b/hints/stakeholder.html
new file mode 100644
index 0000000000000000000000000000000000000000..f4bd5d36f38917bcaa5daeddb3223bbc9d85e67f
--- /dev/null
+++ b/hints/stakeholder.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Stakeholder
+
+
+
+
A Stakeholder represents the role of an individual, team, or organization (or classes thereof) that represents their interests in the effects of the architecture.
+
+
Category:
+
Motivation
+
+
Examples:
+
CEO, the board of directors, shareholders, customers, business, and application architects
System Software represents software that provides or contributes to an environment for storing, executing, and using software or data deployed within it.
+
+
Category:
+
Technology. Active Structure.
+
+
Examples:
+
DBMS, DB2 System Software, Message Queuing, Operating System, J2EE Application Server
+
+
\ No newline at end of file
diff --git a/hints/technology_collaboration.html b/hints/technology_collaboration.html
new file mode 100644
index 0000000000000000000000000000000000000000..8e0a35270203168cc5d668a9952d12fbab44516f
--- /dev/null
+++ b/hints/technology_collaboration.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Technology Collaboration
+
+
+
+
A Technology Collaboration represents an aggregate of two or more technology internal active structure elements that work together to perform collective technology behavior.
+
+
Category:
+
Technology. Active Structure.
+
+
Examples:
+
E-Commerce Hosting.
+
+
\ No newline at end of file
diff --git a/hints/technology_event.html b/hints/technology_event.html
new file mode 100644
index 0000000000000000000000000000000000000000..2e6009b68a10c95583baf17932d4b927569ac035
--- /dev/null
+++ b/hints/technology_event.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Technology Event
+
+
+
+
A Technology Event represents a technology state change.
+
+
Category:
+
Technology. Behavioural.
+
+
Examples:
+
Message received, Database update.
+
+
\ No newline at end of file
diff --git a/hints/technology_function.html b/hints/technology_function.html
new file mode 100644
index 0000000000000000000000000000000000000000..3d425d7e33f58a460dea5f919772b2cd51d18716
--- /dev/null
+++ b/hints/technology_function.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Technology Function
+
+
+
+
A Technology Function represents a collection of technology behavior that can be performed by a technology internal active structure element.
+
+
Category:
+
Technology. Behavioural.
+
+
Examples:
+
Providing Data Access, Managing Data.
+
+
\ No newline at end of file
diff --git a/hints/technology_interaction.html b/hints/technology_interaction.html
new file mode 100644
index 0000000000000000000000000000000000000000..457060d3c58e23b693f53d0cb992750cc708e7c7
--- /dev/null
+++ b/hints/technology_interaction.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Technology Interaction
+
+
+
+
A Technology Interaction represents a unit of collective technology behavior performed by (a collaboration of) two or more technology internal active structure elements.
+
+
Category:
+
Technology. Behavioural.
+
+
Examples:
+
Client profile creation, Update customer records.
+
+
\ No newline at end of file
diff --git a/hints/technology_interface.html b/hints/technology_interface.html
new file mode 100644
index 0000000000000000000000000000000000000000..8f4136263b74ff30cd0491b53d6607f2862cf56c
--- /dev/null
+++ b/hints/technology_interface.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Technology Interface
+
+
+
+
A Technology Interface represents a point of access where technology services offered by a technology internal active structure element can be accessed.
+
+
Category:
+
Technology. Active Structure.
+
+
Examples:
+
Client software, Management Interface.
+
+
\ No newline at end of file
diff --git a/hints/technology_process.html b/hints/technology_process.html
new file mode 100644
index 0000000000000000000000000000000000000000..5a657c304ff6277d6db98d7ea750a021ca9c9d40
--- /dev/null
+++ b/hints/technology_process.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Technology Process
+
+
+
+
A Technology Process represents a sequence of technology behaviors that achieves a specific result.
+
+
Category:
+
Technology. Behavioural.
+
+
Examples:
+
Boot up system, Replicate database
+
+
\ No newline at end of file
diff --git a/hints/technology_service.html b/hints/technology_service.html
new file mode 100644
index 0000000000000000000000000000000000000000..1c1985bcfbc25f5328cf9980308a453a5ef1ad13
--- /dev/null
+++ b/hints/technology_service.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Technology Service
+
+
+
+
A Technology Service represents an explicitly defined exposed technology behavior.
+
+
\ No newline at end of file
diff --git a/hints/view.html b/hints/view.html
new file mode 100644
index 0000000000000000000000000000000000000000..371c7607caf0610458ae901abb3afce02df0956f
--- /dev/null
+++ b/hints/view.html
@@ -0,0 +1,14 @@
+
+
+
+
+
+ View
+
+
+
+
A View is a part of an Architecture Description that addresses a set of related concerns and is tailored for specific stakeholders.
+
A View is specified by means of a Viewpoint, which prescribes the concepts, models, analysis techniques, and visualizations that are provided by the View.
+
The same elements from the Model Tree can be re-used multiple times in the same or different View.
+
+
\ No newline at end of file
diff --git a/hints/view_ref.html b/hints/view_ref.html
new file mode 100644
index 0000000000000000000000000000000000000000..1b7597ef5b95358d10fb5d4be8f6786cc99dd6ad
--- /dev/null
+++ b/hints/view_ref.html
@@ -0,0 +1,13 @@
+
+
+
+
+
+ View Reference
+
+
+
+
A View Reference is simply a shortcut to another View in the same model.
+
Add a View Reference to a View if you wish to create a link to another View of the model. Double-click on it to jump to the View it references.
+
+
\ No newline at end of file
diff --git a/hints/vp_application_cooperation.html b/hints/vp_application_cooperation.html
new file mode 100644
index 0000000000000000000000000000000000000000..201f5c503e1aa9b3de5b9e78592560673eb1a70b
--- /dev/null
+++ b/hints/vp_application_cooperation.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Application Cooperation Viewpoint
+
+
+
+
The Application Cooperation viewpoint describes the relationships between applications components in terms of the information flows between them, or in terms of the services they offer and use. This viewpoint is typically used to create an overview of the application landscape of an organization. This viewpoint is also used to express the (internal) cooperation or orchestration of services that together support the execution of a business process.
+
+
Stakeholders:
+
Enterprise, process, application, and domain architects
+
+
Concerns:
+
Relationships and dependencies between applications, orchestration/choreography of services, consistency and completeness, reduction of complexity
+
+
Purpose:
+
Designing
+
+
Scope:
+
Multiple layer/Multiple aspect
+
+
\ No newline at end of file
diff --git a/hints/vp_application_structure.html b/hints/vp_application_structure.html
new file mode 100644
index 0000000000000000000000000000000000000000..64f13fb9b9488a9aeb2a1fac45e7aaf7a80a4ade
--- /dev/null
+++ b/hints/vp_application_structure.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Application Structure Viewpoint
+
+
+
+
The Application Structure viewpoint shows the structure of one or more applications or components. This viewpoint is useful in designing or understanding the main structure of applications or components and the associated data; e.g., to break down the structure of the system under construction, or to identify legacy application components that are suitable for migration/integration.
+
+
Stakeholders:
+
Application and solution architects
+
+
Concerns:
+
Application structure, consistency and completeness, reduction of complexity
+
+
Purpose:
+
Designing
+
+
Scope:
+
Single layer/Multiple aspect
+
+
\ No newline at end of file
diff --git a/hints/vp_application_usage.html b/hints/vp_application_usage.html
new file mode 100644
index 0000000000000000000000000000000000000000..736ca84176a2800cd08be4d9c65b94b85fc4f240
--- /dev/null
+++ b/hints/vp_application_usage.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Application Usage Viewpoint
+
+
+
+
The Application Usage viewpoint describes how applications are used to support one or more business processes, and how they are used by other applications. It can be used in designing an application by identifying the services needed by business processes and other applications, or in designing business processes by describing the services that are available. Furthermore, since it identifies the dependencies of business processes upon applications, it may be useful to operational managers responsible for these processes.
+
+
Stakeholders:
+
Enterprise, process, and application architects, operational managers
+
+
Concerns:
+
Consistency and completeness, reduction of complexity
+
+
Purpose:
+
Designing, deciding
+
+
Scope:
+
Multiple layer/Multiple aspect
+
+
\ No newline at end of file
diff --git a/hints/vp_business_process_cooperation.html b/hints/vp_business_process_cooperation.html
new file mode 100644
index 0000000000000000000000000000000000000000..d0c8b6de640081dc912cf47d8e3658c9dd91b37a
--- /dev/null
+++ b/hints/vp_business_process_cooperation.html
@@ -0,0 +1,31 @@
+
+
+
+
+
+ Business Process Cooperation Viewpoint
+
+
+
+
The Business Process Cooperation viewpoint is used to show the relationships of one or more business processes with each other and/or with their environment. It can both be used to create a high-level design of business processes within their context and to provide an operational manager responsible for one or more such processes with insight into their dependencies. Important aspects of business process cooperation are:
+
+
Causal relationships between the main business processes of the enterprise
+
Mapping of business processes onto business functions
+
Realization of services by business processes
+
Use of shared data
+
+
Each of these can be regarded as a "sub-viewpoint" of the business process cooperation viewpoint.
+
+
Stakeholders:
+
Process and domain architects, operational managers
+
+
Concerns:
+
Dependencies between business processes, consistency and completeness, responsibilities
+
+
Purpose:
+
Designing, deciding
+
+
Scope:
+
Multiple layer/Multiple aspect
+
+
\ No newline at end of file
diff --git a/hints/vp_capability.html b/hints/vp_capability.html
new file mode 100644
index 0000000000000000000000000000000000000000..bcbac819331629da3ac0dd9a3fded0bb22fa81a8
--- /dev/null
+++ b/hints/vp_capability.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Capability Viewpoint
+
+
+
+
The Capability map viewpoint allows the business architect to create a structured overview of the capabilities of the enterprise. A capability map typically shows two or three levels of capabilities across the entire enterprise. It can, for example, be used as a heat map to identify areas of investment. In some cases, a capability map may also show specific outcomes delivered by these capabilities.
+
+
Stakeholders:
+
Business managers, enterprise and business architects
+
+
Concerns:
+
Architecture strategy and tactics, motivation
+
+
Purpose:
+
Designing, deciding
+
+
Scope:
+
Strategy
+
+
\ No newline at end of file
diff --git a/hints/vp_goal_realization.html b/hints/vp_goal_realization.html
new file mode 100644
index 0000000000000000000000000000000000000000..489611ffb64d83c39a7a8da82bf362aa079b7ff6
--- /dev/null
+++ b/hints/vp_goal_realization.html
@@ -0,0 +1,26 @@
+
+
+
+
+
+ Goal Realization Viewpoint
+
+
+
+
The Goal Realization viewpoint allows a designer to model the refinement of (high-level) goals into more tangible goals, and the refinement of tangible goals into requirements or constraints that describe the properties that are needed to realize the goals. The refinement of goals into sub-goals is modeled using the aggregation relationship. The refinement of goals into requirements is modeled using the realization relationship.
+
+
In addition, the principles may be modeled that guide the refinement of goals into requirements.
+
+
Stakeholders:
+
Stakeholders, business managers, enterprise and ICT architects, business analysts, requirements managers
+
+
Concerns:
+
Architecture mission, strategy and tactics, motivation
+
+
Purpose:
+
Designing, deciding
+
+
Scope:
+
Motivation
+
+
\ No newline at end of file
diff --git a/hints/vp_implementation_deployment.html b/hints/vp_implementation_deployment.html
new file mode 100644
index 0000000000000000000000000000000000000000..c92c23201ff567b1242a994bfd76e2fa328ab6be
--- /dev/null
+++ b/hints/vp_implementation_deployment.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Implementation and Deployment Viewpoint
+
+
+
+
The Implementation and Deployment viewpoint shows how one or more applications are realized on the infrastructure. This comprises the mapping of applications and components onto artifacts, and the mapping of the information used by these applications and components onto the underlying storage infrastructure.
+
+
Stakeholders:
+
Application and domain architects
+
+
Concerns:
+
Structure of application platforms and how they relate to supporting technology
+
+
Purpose:
+
Designing, deciding
+
+
Scope:
+
Multiple layer/Multiple aspect
+
+
\ No newline at end of file
diff --git a/hints/vp_implementation_migration.html b/hints/vp_implementation_migration.html
new file mode 100644
index 0000000000000000000000000000000000000000..03dbed019cc9b8a53b53b8b15865b69eae02208d
--- /dev/null
+++ b/hints/vp_implementation_migration.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+ Implementation and Migration Viewpoint
+
+
+
+
The Implementation and Migration viewpoint is used to relate programs and projects to the parts of the architecture that they implement. This view allows modeling of the scope of programs, projects, project activities in terms of the plateaus that are realized or the individual architecture elements that are affected. In addition, the way the elements are affected may be indicated by annotating the relationships.
+
+
Furthermore, this viewpoint can be used in combination with the programs and projects viewpoint to support portfolio management:
+
+
The programs and projects viewpoint is suited to relate business goals to programs and projects. For example, this makes it possible to analyze at a high level whether all business goals are covered sufficiently by the current portfolio(s).
+
The implementation and migration viewpoint is suited to relate business goals (and requirements) via programs and projects to (parts of) the architecture. For example, this makes it possible to analyze potential overlap between project activities or to analyze the consistency between project dependencies and dependencies among plateaus or architecture elements.
+
+
+
Stakeholders:
+
(Operational) managers, enterprise and ICT architects, employees, shareholders
+
+
Concerns:
+
Architecture vision and policies, motivation
+
+
Purpose:
+
Deciding, informing
+
+
Scope:
+
Multiple layer/Multiple aspect
+
+
\ No newline at end of file
diff --git a/hints/vp_information_structure.html b/hints/vp_information_structure.html
new file mode 100644
index 0000000000000000000000000000000000000000..61defe2dd5bb7705c4af9ced2cf04bf8addadb3a
--- /dev/null
+++ b/hints/vp_information_structure.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Information Structure Viewpoint
+
+
+
+
The Information Structure viewpoint is comparable to the traditional information models created in the development of almost any information system. It shows the structure of the information used in the enterprise or in a specific business process or application, in terms of data types or (object-oriented) class structures. Furthermore, it may show how the information at the business level is represented at the application level in the form of the data structures used there, and how these are then mapped onto the underlying technology infrastructure; e.g., by means of a database schema.
+
+
Stakeholders:
+
Domain and information architects
+
+
Concerns:
+
Structure and dependencies of the used data and information, consistency and completeness
+
+
Purpose:
+
Designing
+
+
Scope:
+
Multiple layer/Single aspect
+
+
\ No newline at end of file
diff --git a/hints/vp_layered.html b/hints/vp_layered.html
new file mode 100644
index 0000000000000000000000000000000000000000..4034e324137da5fb0449919e5ccc7c02043b5fae
--- /dev/null
+++ b/hints/vp_layered.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+ Layered Viewpoint
+
+
+
+
The Layered viewpoint pictures several layers and aspects of an Enterprise Architecture in one diagram.
+
+
There are two categories of layers, namely dedicated layers and service layers. The layers are the result of the use of the "grouping" relationship for a natural partitioning of the entire set of objects and relationships that belong to a model. The technology, application, process, and actor/role layers belong to the first category. The structural principle behind a fully layered viewpoint is that each dedicated layer exposes, by means of the "realization" relationship, a layer of services, which are further on "serving" the next dedicated layer.
+
+
Thus, we can easily separate the internal structure and organization of a dedicated layer from its externally observable behavior expressed as the service layer that the dedicated layer realizes.
+
+
The main goal of the layered viewpoint is to provide an overview in one diagram. Furthermore, this viewpoint can be used as support for impact of change analysis and performance analysis or for extending the service portfolio.
+
+
Stakeholders:
+
Enterprise, process, application, infrastructure, and domain architects
+
+
Concerns:
+
Consistency, reduction of complexity, impact of change, flexibility
+
+
Purpose:
+
Designing, deciding, informing
+
+
Scope:
+
Multiple layer/Multiple aspect
+
+
\ No newline at end of file
diff --git a/hints/vp_migration.html b/hints/vp_migration.html
new file mode 100644
index 0000000000000000000000000000000000000000..cfa456724f29a019eed27421a109bdbd9706775e
--- /dev/null
+++ b/hints/vp_migration.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Migration Viewpoint
+
+
+
+
The Migration viewpoint entails models and concepts that can be used for specifying the transition from an existing architecture to a desired architecture. Since the plateau and gap elements have been quite extensively presented in Section 13.2, here the migration viewpoint is only briefly described and positioned by means of the table below.
+
+
Stakeholders:
+
Enterprise architects, process architects, application architects, infrastructure architects and domain architects, employees, shareholders
+
+
Concerns:
+
History of models
+
+
Purpose:
+
Designing, deciding, informing
+
+
Scope:
+
Implementation and Migration
+
+
\ No newline at end of file
diff --git a/hints/vp_motivation.html b/hints/vp_motivation.html
new file mode 100644
index 0000000000000000000000000000000000000000..c8fa9b9ecc94405f919c1f52a1a449d7eae0e175
--- /dev/null
+++ b/hints/vp_motivation.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Motivation Viewpoint
+
+
+
+
The Motivation viewpoint allows the designer or analyst to model the motivation aspect, without focusing on certain elements within this aspect. For example, this viewpoint can be used to present a complete or partial overview of the motivation aspect by relating stakeholders, their primary goals, the principles that are applied, and the main requirements on services, processes, applications, and objects.
+
+
Stakeholders:
+
Enterprise and ICT architects, business analysts, requirements managers
+
+
Concerns:
+
Architecture strategy and tactics, motivation
+
+
Purpose:
+
Designing, deciding, informing
+
+
Scope:
+
Motivation
+
+
\ No newline at end of file
diff --git a/hints/vp_organization.html b/hints/vp_organization.html
new file mode 100644
index 0000000000000000000000000000000000000000..a79576b2d1b8689da37a4f726002543574854a93
--- /dev/null
+++ b/hints/vp_organization.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Organization Viewpoint
+
+
+
+
The Organization viewpoint focuses on the (internal) organization of a company, department, network of companies, or of another organizational entity. It is possible to present models in this viewpoint as nested block diagrams, but also in a more traditional way, such as organizational charts. The Organization viewpoint is very useful in identifying competencies, authority, and responsibilities in an organization.
+
+
Stakeholders:
+
Enterprise, process and domain architects, managers, employees, shareholders
+
+
Concerns:
+
Identification of competencies, authority, and responsibilities
+
+
Purpose:
+
Designing, deciding, informing
+
+
Scope:
+
Single layer/Single aspect
+
+
\ No newline at end of file
diff --git a/hints/vp_outcome_realization.html b/hints/vp_outcome_realization.html
new file mode 100644
index 0000000000000000000000000000000000000000..1a9040d0228d3f6fbf4c0f614e50e22b62c22b77
--- /dev/null
+++ b/hints/vp_outcome_realization.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Outcome Realization Viewpoint
+
+
+
+
The Outcome Realization viewpoint is used to show how the highest-level, business-oriented results are produced by the capabilities and underlying core elements.
+
+
Stakeholders:
+
Business managers, enterprise and business architects
+
+
Concerns:
+
Business-oriented results
+
+
Purpose:
+
Designing, deciding
+
+
Scope:
+
Strategy
+
+
\ No newline at end of file
diff --git a/hints/vp_physical.html b/hints/vp_physical.html
new file mode 100644
index 0000000000000000000000000000000000000000..8b9301eafbf3560c262544779ac870cbe35d2c53
--- /dev/null
+++ b/hints/vp_physical.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Physical Viewpoint
+
+
+
+
The Physical viewpoint contains equipment (one or more physical machines, tools, or instruments) that can create, use, store, move, or transform materials, how the equipment is connected via the distribution network, and what other active elements are assigned to the equipment.
+
+
Stakeholders:
+
Infrastructure architects, operational managers
+
+
Concerns:
+
Relationships and dependencies of the physical environment and how this relates to IT infrastructure
+
+
Purpose:
+
Designing
+
+
Scope:
+
Multiple layer/Multiple aspect
+
+
\ No newline at end of file
diff --git a/hints/vp_product.html b/hints/vp_product.html
new file mode 100644
index 0000000000000000000000000000000000000000..e1c3df24f69ddb00ba5d055fd120a14d97ce2597
--- /dev/null
+++ b/hints/vp_product.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Product Viewpoint
+
+
+
+
The Product viewpoint depicts the value that these products offer to the customers or other external parties involved and shows the composition of one or more products in terms of the constituting (business, application, or technology) services, and the associated contract(s) or other agreements. It may also be used to show the interfaces (channels) through which this product is offered, and the events associated with the product. A product viewpoint is typically used in product development to design a product by composing existing services or by identifying which new services have to be created for this product, given the value a customer expects from it. It may then serve as input for business process architects and others that need to design the processes and ICT realizing these products.
+
+
Stakeholders:
+
Product developers, product managers, process and domain architects
+
+
Concerns:
+
Product development, value offered by the products of the enterprise
+
+
Purpose:
+
Designing, deciding
+
+
Scope:
+
Multiple layer/Multiple aspect
+
+
\ No newline at end of file
diff --git a/hints/vp_project.html b/hints/vp_project.html
new file mode 100644
index 0000000000000000000000000000000000000000..3ce76c10c40c1dc3bcba717849a46e6ee2ba8598
--- /dev/null
+++ b/hints/vp_project.html
@@ -0,0 +1,31 @@
+
+
+
+
+
+ Project Viewpoint
+
+
+
+
A Project viewpoint is primarily used to model the management of architecture change. The “architecture” of the migration process from an old situation (current state Enterprise Architecture) to a new desired situation (target state Enterprise Architecture) has significant consequences on the medium and long-term growth strategy and the subsequent decision-making process. Some of the issues that should be taken into account by the models designed in this viewpoint are:
+
+
Developing a fully-fledged organization-wide Enterprise Architecture is a task that may require several years.
+
All systems and services must remain operational regardless of the presumed modifications and changes of the Enterprise Architecture during the change process.
+
The change process may have to deal with immature technology standards (e.g., messaging, security, data, etc.).
+
The change has serious consequences for the personnel, culture, way of working, and organization.
+
+
Furthermore, there are several other governance aspects that might constrain the transformation process, such as internal and external cooperation, project portfolio management, project management (deliverables, goals, etc.), plateau planning, financial and legal aspects, etc.
+
+
Stakeholders:
+
(Operational) managers, enterprise and ICT architects, employees, shareholders
+
+
Concerns:
+
Architecture vision and policies, motivation
+
+
Purpose:
+
Deciding, informing
+
+
Scope:
+
Implementation and Migration
+
+
\ No newline at end of file
diff --git a/hints/vp_requirements_realization.html b/hints/vp_requirements_realization.html
new file mode 100644
index 0000000000000000000000000000000000000000..cf1d05435908d04fddf132817b33091e1fc4a6e8
--- /dev/null
+++ b/hints/vp_requirements_realization.html
@@ -0,0 +1,26 @@
+
+
+
+
+
+ Requirements Realization Viewpoint
+
+
+
+
The Requirements Realization viewpoint allows the designer to model the realization of requirements by the core elements, such as business actors, business services, business processes, application services, application components, etc. Typically, the requirements result from the goal refinement viewpoint.
+
+
In addition, this viewpoint can be used to refine requirements into more detailed requirements. The aggregation relationship is used for this purpose.
+
+
Stakeholders:
+
Enterprise and ICT architects, business analysts, requirements managers
+
+
Concerns:
+
Architecture strategy and tactics, motivation
+
+
Purpose:
+
Designing, deciding, informing
+
+
Scope:
+
Motivation
+
+
\ No newline at end of file
diff --git a/hints/vp_resource.html b/hints/vp_resource.html
new file mode 100644
index 0000000000000000000000000000000000000000..7111fc67f303e42876ea0b39d197dd71d7d646f7
--- /dev/null
+++ b/hints/vp_resource.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Resource Map Viewpoint
+
+
+
+
The Resource map viewpoint allows the business architect to create a structured overview of the resources of the enterprise. A resource map typically shows two or three levels of resources across the entire enterprise. It can, for example, be used as a heat map to identify areas of investment. In some cases, a resource map may also show relationships between resources and the capabilities they are assigned to.
+
+
Stakeholders:
+
Business managers, enterprise and business architects
+
+
Concerns:
+
Architecture strategy and tactics, motivation
+
+
Purpose:
+
Designing, deciding
+
+
Scope:
+
Strategy
+
+
\ No newline at end of file
diff --git a/hints/vp_service_realization.html b/hints/vp_service_realization.html
new file mode 100644
index 0000000000000000000000000000000000000000..6255f10fbebcf129c4140b60cc06bdb300a371c2
--- /dev/null
+++ b/hints/vp_service_realization.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Service Realization Viewpoint
+
+
+
+
The Service Realization viewpoint is used to show how one or more business services are realized by the underlying processes (and sometimes by application components). Thus, it forms the bridge between the business products viewpoint and the business process view. It provides a "view from the outside" on one or more business processes.
+
+
Stakeholders:
+
Process and domain architects, product and operational managers
+
+
Concerns:
+
Added-value of business processes, consistency and completeness, responsibilities
+
+
Purpose:
+
Designing, deciding
+
+
Scope:
+
Multiple layer/Multiple aspect
+
+
\ No newline at end of file
diff --git a/hints/vp_stakeholder.html b/hints/vp_stakeholder.html
new file mode 100644
index 0000000000000000000000000000000000000000..3530e2179b34c432b2413078ca8e2466fe6a58cd
--- /dev/null
+++ b/hints/vp_stakeholder.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Stakeholder Viewpoint
+
+
+
+
The Stakeholder viewpoint allows the analyst to model the stakeholders, the internal and external drivers for change, and the assessments (in terms of strengths, weaknesses, opportunities, and threats) of these drivers. Also, the links to the initial (high-level) goals that address these concerns and assessments may be described. These goals form the basis for the requirements engineering process, including goal refinement, contribution and conflict analysis, and the derivation of requirements that realize the goals.
+
+
Stakeholders:
+
Stakeholders, business managers, enterprise and ICT architects, business analysts, requirements managers
+
+
Concerns:
+
Architecture mission and strategy, motivation
+
+
Purpose:
+
Designing, deciding, informing
+
+
Scope:
+
Motivation
+
+
\ No newline at end of file
diff --git a/hints/vp_strategy.html b/hints/vp_strategy.html
new file mode 100644
index 0000000000000000000000000000000000000000..36fe1cdc6b819f08b6be9944d4c13a205a9c2157
--- /dev/null
+++ b/hints/vp_strategy.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Strategy Viewpoint
+
+
+
+
The Strategy viewpoint allows the business architect to model a high-level, strategic overview of the strategies (courses of action) of the enterprise, the capabilities and resources supporting those, and the envisaged outcomes.
+
+
Stakeholders:
+
CxOs, business managers, enterprise and business architects
+
+
Concerns:
+
Strategy development
+
+
Purpose:
+
Designing, deciding
+
+
Scope:
+
Strategy
+
+
\ No newline at end of file
diff --git a/hints/vp_technology.html b/hints/vp_technology.html
new file mode 100644
index 0000000000000000000000000000000000000000..0152b85c9f98cd73df948c8a72302cdbc97e3fee
--- /dev/null
+++ b/hints/vp_technology.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Technology Viewpoint
+
+
+
+
The Technology viewpoint contains the software and hardware technology elements supporting the Application Layer, such as physical devices, networks, or system software (e.g., operating systems, databases, and middleware).
+
+
Stakeholders:
+
Infrastructure architects, operational managers
+
+
Concerns:
+
Stability, security, dependencies, costs of the infrastructure
+
+
Purpose:
+
Designing
+
+
Scope:
+
Single layer/Multiple aspect
+
+
\ No newline at end of file
diff --git a/hints/vp_technology_usage.html b/hints/vp_technology_usage.html
new file mode 100644
index 0000000000000000000000000000000000000000..471c0ae82ed216c2a8e64b63523cdd0faa861883
--- /dev/null
+++ b/hints/vp_technology_usage.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Technology Usage Viewpoint
+
+
+
+
The Technology Usage viewpoint shows how applications are supported by the software and hardware technology: the technology services are delivered by the devices; system software and networks are provided to the applications. This viewpoint plays an important role in the analysis of performance and scalability, since it relates the physical infrastructure to the logical world of applications. It is very useful in determining the performance and quality requirements on the infrastructure based on the demands of the various applications that use it.
+
+
\ No newline at end of file
diff --git a/hints/vp_value_stream.html b/hints/vp_value_stream.html
new file mode 100644
index 0000000000000000000000000000000000000000..97b87f81848e60c1205ee0396a85c15f5109217a
--- /dev/null
+++ b/hints/vp_value_stream.html
@@ -0,0 +1,24 @@
+
+
+
+
+
+ Value Stream Viewpoint
+
+
+
+
The Value Stream viewpoint allows the Business Architect to create a structured overview of a value stream, the capabilities supporting the stages in that value stream, the value created, and the stakeholders involved.
+
+
Stakeholders:
+
Business managers, enterprise and business architects
+
+
Concerns:
+
Architecture strategy and tactics, motivation
+
+
Purpose:
+
Designing, deciding
+
+
Scope:
+
Strategy
+
+
\ No newline at end of file
diff --git a/hints/workpackage.html b/hints/workpackage.html
new file mode 100644
index 0000000000000000000000000000000000000000..cd6767dee28707770a72543c5febd1052afea994
--- /dev/null
+++ b/hints/workpackage.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+ Work Package
+
+
+
+
A Work Package represents a series of actions identified and designed to achieve specific results within specified time and resource constraints.
+
+
Category:
+
Implementation and Migration
+
+
Examples:
+
"Program to sustain implementation", "Project to secure funding", "Project for CRM system integration"
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-007aba06ff3513ecad523f57ad41d69b.html b/id-iso15288-model/elements/id-007aba06ff3513ecad523f57ad41d69b.html
new file mode 100644
index 0000000000000000000000000000000000000000..b8c97e10b910d4822806cde4637323967a4c2c0f
--- /dev/null
+++ b/id-iso15288-model/elements/id-007aba06ff3513ecad523f57ad41d69b.html
@@ -0,0 +1,209 @@
+
+
+
+
+ Transition
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Transition
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.4.10.1] The purpose of the Transition process is to establish a capability for a system to provide services specified by stakeholder requirements in the operational environment. See detailed description in the INCOSE Handbook v.5, page 143
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-0403deb32f4b47eac18bb4e41baba7f5.html b/id-iso15288-model/elements/id-0403deb32f4b47eac18bb4e41baba7f5.html
new file mode 100644
index 0000000000000000000000000000000000000000..1c9723fcb60ece866d36c19367bfd74cf98bcaf2
--- /dev/null
+++ b/id-iso15288-model/elements/id-0403deb32f4b47eac18bb4e41baba7f5.html
@@ -0,0 +1,190 @@
+
+
+
+
+ Quality Management
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Quality Management
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.2.5.1] The purpose of the Quality Management process is to assure that products, services and implementations of the quality management process meet organizational and project quality objectives and achieve customer satisfaction. See detailed description in the INCOSE Handbook v.5, page 63
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-0483539444bc9db5831ac711247d74b9.html b/id-iso15288-model/elements/id-0483539444bc9db5831ac711247d74b9.html
new file mode 100644
index 0000000000000000000000000000000000000000..1f33fe118f3faf37ea3a2f23ca2225e42d6f0cdc
--- /dev/null
+++ b/id-iso15288-model/elements/id-0483539444bc9db5831ac711247d74b9.html
@@ -0,0 +1,123 @@
+
+
+
+
+ Life cycle models
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Life cycle models
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Framework of processes and activities concerned with the life cycle that can be organized into stages, acting as a common reference for communication and understanding. (ISO/IEC/IEEE 15288, 2023)
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-0560d160211817bffac04a73d00c5916.html b/id-iso15288-model/elements/id-0560d160211817bffac04a73d00c5916.html
new file mode 100644
index 0000000000000000000000000000000000000000..67a34a0465f22cb6b2a145ce6fd206355f02f7e2
--- /dev/null
+++ b/id-iso15288-model/elements/id-0560d160211817bffac04a73d00c5916.html
@@ -0,0 +1,125 @@
+
+
+
+
+ Measurement needs
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Measurement needs
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Measurement needs from all applicable life cycle processes, including: critical performance measurement needs, organizational measurement needs, and project measurement needs.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-0eb662bc148dd139cd1cc4ab31e825a3.html b/id-iso15288-model/elements/id-0eb662bc148dd139cd1cc4ab31e825a3.html
new file mode 100644
index 0000000000000000000000000000000000000000..db6759aff431edb87474f06bb1ee01caa86db94d
--- /dev/null
+++ b/id-iso15288-model/elements/id-0eb662bc148dd139cd1cc4ab31e825a3.html
@@ -0,0 +1,115 @@
+
+
+
+
+ Request for supply
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Request for supply
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Acquirer’s request for information and commitments needed from the supplier that are required to be included in the potential supplier’s proposal. It announces the acquirer’s intention to potential bidders to acquire a specified system or system element (product or service). (Adapted from ISO/IEC/IEEE 15289, 2019)
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-114fb50d5859c1ec8e628f630b704ec9.html b/id-iso15288-model/elements/id-114fb50d5859c1ec8e628f630b704ec9.html
new file mode 100644
index 0000000000000000000000000000000000000000..b9952abf55490e9ccd4aa73f89ea4171231bc29d
--- /dev/null
+++ b/id-iso15288-model/elements/id-114fb50d5859c1ec8e628f630b704ec9.html
@@ -0,0 +1,147 @@
+
+
+
+
+ System architecture description
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ System architecture description
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
The fundamental conception of a system-of-interest in terms of its purpose, system qualities (such as feasibility, performance, safety, and interoperability), constraints, and design decisions and rationale. Identification of the architecture’s stakeholders and the stakeholders’ architecture-related concerns. (Adapted from ISO/IEC/IEEE 15289, 2019)
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-11a861754d4769dbaaec043cee59811f.html b/id-iso15288-model/elements/id-11a861754d4769dbaaec043cee59811f.html
new file mode 100644
index 0000000000000000000000000000000000000000..8135dafd7d935c10bb07ce61d4214c4694b143f9
--- /dev/null
+++ b/id-iso15288-model/elements/id-11a861754d4769dbaaec043cee59811f.html
@@ -0,0 +1,145 @@
+
+
+
+
+ Measurement
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Measurement
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.3.7.1] The purpose of the Measurement process is to collect, analyze, and report objective data and information to support effective management and demonstrate the quality of the products, services, and processes. See detailed description in the INCOSE Handbook v.5, page 93
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-13367ce0d2281f0706a83414d1175c33.html b/id-iso15288-model/elements/id-13367ce0d2281f0706a83414d1175c33.html
new file mode 100644
index 0000000000000000000000000000000000000000..7aa3d3d4b7778102790e91205b0f190eb3a66447
--- /dev/null
+++ b/id-iso15288-model/elements/id-13367ce0d2281f0706a83414d1175c33.html
@@ -0,0 +1,107 @@
+
+
+
+
+ Deliver and support the product or service
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Deliver and support the product or service
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
See detailed description in the INCOSE Handbook v.5, page 49
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-17b4ab2392cbf7d0bce2f7fe0ecf4b4e.html b/id-iso15288-model/elements/id-17b4ab2392cbf7d0bce2f7fe0ecf4b4e.html
new file mode 100644
index 0000000000000000000000000000000000000000..da543e40c2d40bf5c5a7a46420b06f00cbde2dc3
--- /dev/null
+++ b/id-iso15288-model/elements/id-17b4ab2392cbf7d0bce2f7fe0ecf4b4e.html
@@ -0,0 +1,230 @@
+
+
+
+
+ Constraints on solution
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Constraints on solution
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Externally imposed limitation on the system, its design, or implementation or on the process used to develop or modify a system. (ISO/IEC/IEEE 29148, 2018).
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-19c7d399d95318384962182224a27c22.html b/id-iso15288-model/elements/id-19c7d399d95318384962182224a27c22.html
new file mode 100644
index 0000000000000000000000000000000000000000..c5baf2e7484916bfe1fe610ef6c8c05a5cc4bb5c
--- /dev/null
+++ b/id-iso15288-model/elements/id-19c7d399d95318384962182224a27c22.html
@@ -0,0 +1,249 @@
+
+
+
+
+ Validation
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Validation
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.4.11.1] The purpose of the Validation process is to provide objective evidence that the system, when in use, fulfills its business or mission objectives and stakeholder requirements, achieving its intended use in its intended operational environment. See detailed description in the INCOSE Handbook v.5, page 146
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-1d8aa079dfdc10122a6a36304b19d24d.html b/id-iso15288-model/elements/id-1d8aa079dfdc10122a6a36304b19d24d.html
new file mode 100644
index 0000000000000000000000000000000000000000..1bdd55e875b5ff36ef616709765a684fda39a177
--- /dev/null
+++ b/id-iso15288-model/elements/id-1d8aa079dfdc10122a6a36304b19d24d.html
@@ -0,0 +1,227 @@
+
+
+
+
+ Life cycle concepts
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Life cycle concepts
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Articulation and refinement of the various life cycle concepts consistent with the stakeholder needs. Typical concepts include: acquisition concept; deployment concept; operational concept (OpsCon); support concept; retirement concept.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-1eba94e478b18a0f0d9d0f5f2be33103.html b/id-iso15288-model/elements/id-1eba94e478b18a0f0d9d0f5f2be33103.html
new file mode 100644
index 0000000000000000000000000000000000000000..4f452b2ae3b36889ce94ba937061e47b8db13084
--- /dev/null
+++ b/id-iso15288-model/elements/id-1eba94e478b18a0f0d9d0f5f2be33103.html
@@ -0,0 +1,234 @@
+
+
+
+
+ Integration
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Integration
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.4.8.1] The purpose of the Integration process is to synthesize a set of system elements into a realized system (product or service) that satisfies system requirements* architecture, and design. See detailed description in the INCOSE Handbook v.5, page 134
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-26b0686349f25d7329a5dd4321c27b2c.html b/id-iso15288-model/elements/id-26b0686349f25d7329a5dd4321c27b2c.html
new file mode 100644
index 0000000000000000000000000000000000000000..cea5440f0c71556cb0629889c4772ba6ae15c757
--- /dev/null
+++ b/id-iso15288-model/elements/id-26b0686349f25d7329a5dd4321c27b2c.html
@@ -0,0 +1,180 @@
+
+
+
+
+ Quality Assurance
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Quality Assurance
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.3.8.1] The purpose of the Quality Assurance process is to help ensure the effective application of the organization's Quality Management process to the project. See detailed description in the INCOSE Handbook v.5, page 98
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-30d9ca1d2d5a7e0e7f3d82541fc9bf0b.html b/id-iso15288-model/elements/id-30d9ca1d2d5a7e0e7f3d82541fc9bf0b.html
new file mode 100644
index 0000000000000000000000000000000000000000..27770421ce4e4ed3d1fc0f2cc71d55da068f69a2
--- /dev/null
+++ b/id-iso15288-model/elements/id-30d9ca1d2d5a7e0e7f3d82541fc9bf0b.html
@@ -0,0 +1,160 @@
+
+
+
+
+ Information Management
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Information Management
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.3.6.1] The purpose of the Information Management process is to generate, obtain, confirm, transform, retain, retrieve, disseminate and dispose of information, to designated stakeholders. Information management plans, executes, and controls the provision of information to designated stakeholders that is unambiguous, complete, verifiable, consistent, modifiable, traceable, and presentable. Information includes technical, project, organizational, agreement, and user information. Information is often derived from data records of the organization, system, process, or project. See detailed description in the INCOSE Handbook v.5, page 91
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-3120ed28b518abd0a575282e0a4f9966.html b/id-iso15288-model/elements/id-3120ed28b518abd0a575282e0a4f9966.html
new file mode 100644
index 0000000000000000000000000000000000000000..cb60fc126b32b8b7264b7e39c5ce8e40db6498fb
--- /dev/null
+++ b/id-iso15288-model/elements/id-3120ed28b518abd0a575282e0a4f9966.html
@@ -0,0 +1,205 @@
+
+
+
+
+ Life Cycle Model Management
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Life Cycle Model Management
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.2.1.1] The purpose of the Life Cycle Model Management process is to define, maintain, and assure availability of policies, life cycle processes, life cycle models, and procedures for use by the organization with respect to the scope of [ISO/IEC/IEEE 15288:2023]. See detailed description in the INCOSE Handbook v.5, page 51
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-3249c77ccac6f9f3103edb3f40642df8.html b/id-iso15288-model/elements/id-3249c77ccac6f9f3103edb3f40642df8.html
new file mode 100644
index 0000000000000000000000000000000000000000..de125d54dc81fbd2486a8093d9e24f38fae4a8f9
--- /dev/null
+++ b/id-iso15288-model/elements/id-3249c77ccac6f9f3103edb3f40642df8.html
@@ -0,0 +1,107 @@
+
+
+
+
+ Project direction
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Project direction
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Organizational direction to the project. Includes sustainment of projects meeting objectives and redirection or termination of projects not meeting objectives.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-36ad52dff0937b9d207742513c97587a.html b/id-iso15288-model/elements/id-36ad52dff0937b9d207742513c97587a.html
new file mode 100644
index 0000000000000000000000000000000000000000..c2ac15acfabf8e51fe5eeb751fad11264501fa05
--- /dev/null
+++ b/id-iso15288-model/elements/id-36ad52dff0937b9d207742513c97587a.html
@@ -0,0 +1,131 @@
+
+
+
+
+ Project status report or dashboard
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Project status report or dashboard
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
A linked list of a project’s milestones, activities, and deliverables with intended start and finish dates May include a top-level milestone schedule and multiple levels (also called tiers) of schedules of increasing detail and task descriptions with completion criteria and work authorizations.
Action to eliminate the cause or reduce the likelihood of recurrence of a detected project nonconformity or other undesirable situation. (Adapted from ISO/IEC 19770–1, 2017)
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-3bdf4cc6b682a2386e72a8b4b376efad.html b/id-iso15288-model/elements/id-3bdf4cc6b682a2386e72a8b4b376efad.html
new file mode 100644
index 0000000000000000000000000000000000000000..136fa90095c005e42c1da3e50fdec8a9a2773a83
--- /dev/null
+++ b/id-iso15288-model/elements/id-3bdf4cc6b682a2386e72a8b4b376efad.html
@@ -0,0 +1,115 @@
+
+
+
+
+ Problem or opportunity statement
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Problem or opportunity statement
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Description of the problem or opportunity. Should be derived from the organization strategy and provide enough detail to understand the gap or new capability that is being considered
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-45c4df4f31975f60ed5e08b081a3a265.html b/id-iso15288-model/elements/id-45c4df4f31975f60ed5e08b081a3a265.html
new file mode 100644
index 0000000000000000000000000000000000000000..37994ad036a483b164467824dabc66c48065c9d3
--- /dev/null
+++ b/id-iso15288-model/elements/id-45c4df4f31975f60ed5e08b081a3a265.html
@@ -0,0 +1,131 @@
+
+
+
+
+ System element description
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ System element description
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Applies the system architecture description to the low-level system configuration items and elements. It is at a level of detail to permit design, implementation, and test. (Adapted from ISO/IEC/IEEE 15289, 2019)
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-476f23fa242a1d340510aed1bb3cdc4c.html b/id-iso15288-model/elements/id-476f23fa242a1d340510aed1bb3cdc4c.html
new file mode 100644
index 0000000000000000000000000000000000000000..8a4e3d142e7295273298631ea26533173d8e3fe0
--- /dev/null
+++ b/id-iso15288-model/elements/id-476f23fa242a1d340510aed1bb3cdc4c.html
@@ -0,0 +1,147 @@
+
+
+
+
+ System architecture rationale
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ System architecture rationale
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Rationale for architecture selection, technological/technical system element selection, and allocation between system requirements and architectural entities.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-489949d363237a2f7adbd891701f9cc7.html b/id-iso15288-model/elements/id-489949d363237a2f7adbd891701f9cc7.html
new file mode 100644
index 0000000000000000000000000000000000000000..f91ba84b8542f01e3fff9343771ba4eaa889af65
--- /dev/null
+++ b/id-iso15288-model/elements/id-489949d363237a2f7adbd891701f9cc7.html
@@ -0,0 +1,107 @@
+
+
+
+
+ Acquired system or system element
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Acquired system or system element
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
System or system element (product or service) delivered to the acquirer from a supplier consistent with the delivery conditions of the acquisition agreement.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-4b3affb30d8d22da686da4609a483b01.html b/id-iso15288-model/elements/id-4b3affb30d8d22da686da4609a483b01.html
new file mode 100644
index 0000000000000000000000000000000000000000..ee22dd639baf580e1261e953a7caeecff2af05c2
--- /dev/null
+++ b/id-iso15288-model/elements/id-4b3affb30d8d22da686da4609a483b01.html
@@ -0,0 +1,115 @@
+
+
+
+
+ Breakdown structures
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Breakdown structures
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Hierarchical representations of project aspects into smaller components providing the necessary frameworks to accomplish the project objectives and create the required deliverables.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-4db06f9b342d7fac735a10d0d37b9fb7.html b/id-iso15288-model/elements/id-4db06f9b342d7fac735a10d0d37b9fb7.html
new file mode 100644
index 0000000000000000000000000000000000000000..3f971b87f2d3c1475196359f79bf89133d09b8bd
--- /dev/null
+++ b/id-iso15288-model/elements/id-4db06f9b342d7fac735a10d0d37b9fb7.html
@@ -0,0 +1,173 @@
+
+
+
+
+ Tailoring
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Tailoring
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [Annex A.2.1] The purpose of the tailoring process is to adapt the life cycle processes included in this document [i.e. ISO/IEC/IEEE 15288:2023] to satisfy particular circumstances or factors that:
+
+a) surround an organization that is employing ISO/IEC/IEEE 15288 in an agreement;
+
+b) influence a project that is required to meet an agreement in which ISO/IEC/IEEE 15288 is referenced;
+
+c) reflect the needs of an organization in order to supply products or services.
+
+See detailed description in the INCOSE Handbook v.5, page 215
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-515a59f0cd26f910c56f8610a8896817.html b/id-iso15288-model/elements/id-515a59f0cd26f910c56f8610a8896817.html
new file mode 100644
index 0000000000000000000000000000000000000000..82e776baefacf6378bbd7836e14c8d71301493e8
--- /dev/null
+++ b/id-iso15288-model/elements/id-515a59f0cd26f910c56f8610a8896817.html
@@ -0,0 +1,115 @@
+
+
+
+
+ Qualified personnel
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Qualified personnel
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Individuals equipped to perform duties on behalf of the organization, including officers, employees, and contractors. (Adapted from ISO/IEC/IEEE 24765, 2017)
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-521794de211046964adcd4457eb1a4b8.html b/id-iso15288-model/elements/id-521794de211046964adcd4457eb1a4b8.html
new file mode 100644
index 0000000000000000000000000000000000000000..e4c56f2d8193ea5ddfe0a4f4515f36eb7e20ab2a
--- /dev/null
+++ b/id-iso15288-model/elements/id-521794de211046964adcd4457eb1a4b8.html
@@ -0,0 +1,123 @@
+
+
+
+
+ Project decision gate or review result
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Project decision gate or review result
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Decision gate and review artifacts that are expected through conduct of the decision gate or technical review and that can be considered elements of exit criteria. (Adapted from ISO/IEC/IEEE 24748–8, 2019)
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-52361dccd931c6b2ffee945862f67ab5.html b/id-iso15288-model/elements/id-52361dccd931c6b2ffee945862f67ab5.html
new file mode 100644
index 0000000000000000000000000000000000000000..977f7482d75a1c7c019c308a03e3c5474ea49618
--- /dev/null
+++ b/id-iso15288-model/elements/id-52361dccd931c6b2ffee945862f67ab5.html
@@ -0,0 +1,115 @@
+
+
+
+
+ Stakeholder identification
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Stakeholder identification
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
List of individuals or organizations having a right++ share, claim, or interest in a system or in ist possession of characteristics that meet their needs and expectations. (Adapted from ISO/IEC/IEEE 15288, 2023)
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-576a4827df53f38c839a6d197bf6dcba.html b/id-iso15288-model/elements/id-576a4827df53f38c839a6d197bf6dcba.html
new file mode 100644
index 0000000000000000000000000000000000000000..7fc628ecc8b32c8b311a37db167af7114d989f80
--- /dev/null
+++ b/id-iso15288-model/elements/id-576a4827df53f38c839a6d197bf6dcba.html
@@ -0,0 +1,137 @@
+
+
+
+
+ Situational
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Situational
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Situational represents those typical inputs and outputs that are situational with respect to the execution of the system life cycle processes (i.e., they are invoked when needed).
+
+They can come from any life cycle process.
+
+They go into a select number of system life cycle processes, specifically:
+
+Decision Management,
+
+Risk Management,
+
+Configuration Management,
+
+Information Management, and
+
+System Analysis.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-5a2cbaf289eca2e14648ad4dbf55925b.html b/id-iso15288-model/elements/id-5a2cbaf289eca2e14648ad4dbf55925b.html
new file mode 100644
index 0000000000000000000000000000000000000000..047cec99b7c9bdc9ff0708b8316dc098aa6d84d5
--- /dev/null
+++ b/id-iso15288-model/elements/id-5a2cbaf289eca2e14648ad4dbf55925b.html
@@ -0,0 +1,249 @@
+
+
+
+
+ System Architecture Definition
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ System Architecture Definition
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.4.4.1] The purpose of the Architecture Definition process is to generate system architecture alternatives, to select one or more alternative(s) that frame stakeholder concerns and meet system requirements, and to express this in a set of consistent views. See detailed description in the INCOSE Handbook v.5, page 118
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-5dd795b55b41d2465f0d5255eb4c5745.html b/id-iso15288-model/elements/id-5dd795b55b41d2465f0d5255eb4c5745.html
new file mode 100644
index 0000000000000000000000000000000000000000..ffe1c6c29596012f8d868ff5985eb2381a3f1f78
--- /dev/null
+++ b/id-iso15288-model/elements/id-5dd795b55b41d2465f0d5255eb4c5745.html
@@ -0,0 +1,123 @@
+
+
+
+
+ Project lessons learned
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Project lessons learned
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Project-related lessons learned. Results from an evaluation or observation of an implemented corrective action that contributed to improved performance or increased capability. A lesson learned also results from an evaluation or observation of a positive finding that did not necessarily require corrective action other than sustainment.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-5ed41ac7d00d175bb565d9c4a9c8f9c3.html b/id-iso15288-model/elements/id-5ed41ac7d00d175bb565d9c4a9c8f9c3.html
new file mode 100644
index 0000000000000000000000000000000000000000..20b4cda90d2faaf58a162f828ca0b20ec2d6ad3c
--- /dev/null
+++ b/id-iso15288-model/elements/id-5ed41ac7d00d175bb565d9c4a9c8f9c3.html
@@ -0,0 +1,125 @@
+
+
+
+
+ Measurement data
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Measurement data
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Measurement data from all applicable life cycle processes, including: critical performance measurement data, organizational measurement data, and project measurement data.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-6123b223eb8fd36e162a1747a982fa92.html b/id-iso15288-model/elements/id-6123b223eb8fd36e162a1747a982fa92.html
new file mode 100644
index 0000000000000000000000000000000000000000..43f268f23d79c8f10ba5a6747c83285c0f1f5e4e
--- /dev/null
+++ b/id-iso15288-model/elements/id-6123b223eb8fd36e162a1747a982fa92.html
@@ -0,0 +1,215 @@
+
+
+
+
+ Portfolio Management
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Portfolio Management
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.2.3.1] The purpose of the Portfolio Management process is to initiate and sustain necessary, sufficient and suitable projects in order to meet the strategic objectives of the organization. See detailed description in the INCOSE Handbook v.5, page 57
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-61c5ab3fd1fd478e55d2325fc36240c9.html b/id-iso15288-model/elements/id-61c5ab3fd1fd478e55d2325fc36240c9.html
new file mode 100644
index 0000000000000000000000000000000000000000..704223760f49ecd21e174ecd00176e9815f26ce7
--- /dev/null
+++ b/id-iso15288-model/elements/id-61c5ab3fd1fd478e55d2325fc36240c9.html
@@ -0,0 +1,190 @@
+
+
+
+
+ Configuration Management
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Configuration Management
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.3.5.1] The purpose of the Configuration Management process is to manage and control system elements and configurations over the life cycle. CM also manages consistency between a product and its associated configuration definition. See detailed description in the INCOSE Handbook v.5, page 87
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-6367012fdea357df1436aa160499e2df.html b/id-iso15288-model/elements/id-6367012fdea357df1436aa160499e2df.html
new file mode 100644
index 0000000000000000000000000000000000000000..96347e715e8ac39934b28840d8f74db4e8e14b63
--- /dev/null
+++ b/id-iso15288-model/elements/id-6367012fdea357df1436aa160499e2df.html
@@ -0,0 +1,225 @@
+
+
+
+
+ Supply
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Supply
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.1.2.1] The purpose of the Supply process is to provide an acquirer with a product or service that meets agreed requirements. See detailed description in the INCOSE Handbook v.5, page 48
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-69d5eff18537d0dd36fe7b477d997e7c.html b/id-iso15288-model/elements/id-69d5eff18537d0dd36fe7b477d997e7c.html
new file mode 100644
index 0000000000000000000000000000000000000000..8cfa769d9ea1778fc780b3f4203dae27d5989fd8
--- /dev/null
+++ b/id-iso15288-model/elements/id-69d5eff18537d0dd36fe7b477d997e7c.html
@@ -0,0 +1,235 @@
+
+
+
+
+ Project Planning
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Project Planning
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.3.1.1] The purpose of the Project Planning process is to produce and coordinate effective and workable plans. See detailed description in the INCOSE Handbook v.5, page 70
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-6abea8ee530a2e76e494f64e5468b071.html b/id-iso15288-model/elements/id-6abea8ee530a2e76e494f64e5468b071.html
new file mode 100644
index 0000000000000000000000000000000000000000..0141ef94ab04730706276839f64812bc88dd2510
--- /dev/null
+++ b/id-iso15288-model/elements/id-6abea8ee530a2e76e494f64e5468b071.html
@@ -0,0 +1,115 @@
+
+
+
+
+ Supply agreement
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Supply agreement
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Mutual acknowledgment of terms and conditions under which a working relationship is conducted between a supplier and an acquirer. (Adapted from ISO/IEC/IEEE 15288++ 2023)
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-6daffb4f2adac5a7ae41d89943f7c7e1.html b/id-iso15288-model/elements/id-6daffb4f2adac5a7ae41d89943f7c7e1.html
new file mode 100644
index 0000000000000000000000000000000000000000..fed90ed2457abd0fe07c2168e1052518097849ce
--- /dev/null
+++ b/id-iso15288-model/elements/id-6daffb4f2adac5a7ae41d89943f7c7e1.html
@@ -0,0 +1,115 @@
+
+
+
+
+ Supplied system or system element
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Supplied system or system element
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
System or system element (product or service) delivered from a supplier to an acquirer consistent with the delivery conditions of the supply agreement.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-70933caddf9b31cabf309bc404f1fbfb.html b/id-iso15288-model/elements/id-70933caddf9b31cabf309bc404f1fbfb.html
new file mode 100644
index 0000000000000000000000000000000000000000..eb5765ac4118280537633ad36e699e0db57e6e27
--- /dev/null
+++ b/id-iso15288-model/elements/id-70933caddf9b31cabf309bc404f1fbfb.html
@@ -0,0 +1,224 @@
+
+
+
+
+ System Requirements Definition
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ System Requirements Definition
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.4.3.1] The purpose of the System Requirements Definition process is to transform the stakeholder, useroriented view of desired capabilities into a technical view of a solution that meets the operational needs of the user. See detailed description in the INCOSE Handbook v.5, page 112
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-710d6728fd5c05b14df1082d6e9bc1e0.html b/id-iso15288-model/elements/id-710d6728fd5c05b14df1082d6e9bc1e0.html
new file mode 100644
index 0000000000000000000000000000000000000000..cdf9e84c1858120165d4e5583a88a2a7a3c7717f
--- /dev/null
+++ b/id-iso15288-model/elements/id-710d6728fd5c05b14df1082d6e9bc1e0.html
@@ -0,0 +1,163 @@
+
+
+
+
+ Decision Management
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Decision Management
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As defined by ISO/IEC/IEEE 15288:2023, [6.3.3.1] The purpose of the Decision Management process is to provide a structured, analytical framework for objectively identifying, characterizing and evaluating a set of alternatives for a decision at any point in the life cycle and select the most beneficial course of action. See detailed description in the INCOSE Handbook v.5, page 78
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-798ab48c39542cf2dfa6355aa516e553.html b/id-iso15288-model/elements/id-798ab48c39542cf2dfa6355aa516e553.html
new file mode 100644
index 0000000000000000000000000000000000000000..056bd7997a3265e6aa3f8387206ac10811c84168
--- /dev/null
+++ b/id-iso15288-model/elements/id-798ab48c39542cf2dfa6355aa516e553.html
@@ -0,0 +1,192 @@
+
+
+
+
+ Standards
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Standards
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
This handbook and relevant industry, country, military, acquirer, and other specifications and standards. Includes new knowledge from industry sponsored knowledge networks.
As stated in ISO/IEC/IEEE 15288:2023, [6.4.2.1] The purpose of the Stakeholder Needs and Requirements Definition process is to define the stakeholder requirements for a system that can provide the capabilities needed by users and other stakeholders in a defined environment. See detailed description in the INCOSE Handbook v.5, page 107
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-7e5ce537e6951e50658b39f8114e5328.html b/id-iso15288-model/elements/id-7e5ce537e6951e50658b39f8114e5328.html
new file mode 100644
index 0000000000000000000000000000000000000000..0f77f4bae0a25fad81730b03090cefab31441691
--- /dev/null
+++ b/id-iso15288-model/elements/id-7e5ce537e6951e50658b39f8114e5328.html
@@ -0,0 +1,214 @@
+
+
+
+
+ Traceability mapping
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Traceability mapping
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Records the relationship between two or more artifacts of the development process (e.g., requirements, functions, system elements, verifications, and validations, tasks). (Adapted from ISO/IEC/IEEE 24765++ 2017)
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-86338c66ecee3573404dd64e68a4c0de.html b/id-iso15288-model/elements/id-86338c66ecee3573404dd64e68a4c0de.html
new file mode 100644
index 0000000000000000000000000000000000000000..9f283ffcc3d024e4d8da3b17211039b6478fd963
--- /dev/null
+++ b/id-iso15288-model/elements/id-86338c66ecee3573404dd64e68a4c0de.html
@@ -0,0 +1,179 @@
+
+
+
+
+ System Analysis
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ System Analysis
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288, [6.4.6.1] The purpose of the System Analysis process is to provide a rigorous basis of data and information for technical understanding to aid decision-�making across the life cycle. See detailed description in the INCOSE Handbook v.5, page 129
Structured collection of the requirements [characteristics, context, concepts, constraints and priorities] of the stakeholder and the relationship to the external environment. (ISO/IEC/IEEE 29148, 2018)
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-8788012a0ab34ddc31eda0d9bb6ce8e8.html b/id-iso15288-model/elements/id-8788012a0ab34ddc31eda0d9bb6ce8e8.html
new file mode 100644
index 0000000000000000000000000000000000000000..c3d24604369ea1ef95334cd6ab8f242d8410fb16
--- /dev/null
+++ b/id-iso15288-model/elements/id-8788012a0ab34ddc31eda0d9bb6ce8e8.html
@@ -0,0 +1,115 @@
+
+
+
+
+ Project budget
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Project budget
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Estimate of the costs associated with a particular project. Includes labor, infrastructure, acquisition, and enabling system costs along with reserves for risk management.
Provides results of configuration management verifications and audits to ensure adequate traceability, control, and visibility. It includes evaluation criteria.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-92a8f3903d0396700517927d31134f6b.html b/id-iso15288-model/elements/id-92a8f3903d0396700517927d31134f6b.html
new file mode 100644
index 0000000000000000000000000000000000000000..6c4a3e0549a378b860d97c69a045e518babc2385
--- /dev/null
+++ b/id-iso15288-model/elements/id-92a8f3903d0396700517927d31134f6b.html
@@ -0,0 +1,123 @@
+
+
+
+
+ Verification criteria
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Verification criteria
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
The verification criteria (the measures to be assessed), who will perform verification activities, and the verification environments of the system-of-interest.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-97215e10a56c3e69dfc1ab2fd7244ae2.html b/id-iso15288-model/elements/id-97215e10a56c3e69dfc1ab2fd7244ae2.html
new file mode 100644
index 0000000000000000000000000000000000000000..6ce5f9d05eca961528371228836e28965d4d44a4
--- /dev/null
+++ b/id-iso15288-model/elements/id-97215e10a56c3e69dfc1ab2fd7244ae2.html
@@ -0,0 +1,165 @@
+
+
+
+
+ Human Resource Management
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Human Resource Management
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.2.4.1] The purpose of the Human Resource Management process is to provide the organization with necessary human resources and to maintain their competencies, consistent with business needs. See detailed description in the INCOSE Handbook v.5, page 60
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-9a6ee7f2443aa80b6a04abfee0abcef0.html b/id-iso15288-model/elements/id-9a6ee7f2443aa80b6a04abfee0abcef0.html
new file mode 100644
index 0000000000000000000000000000000000000000..95a4a0e9ffb3e6e4f1a1e60a050c8061587482d9
--- /dev/null
+++ b/id-iso15288-model/elements/id-9a6ee7f2443aa80b6a04abfee0abcef0.html
@@ -0,0 +1,107 @@
+
+
+
+
+ Risk register
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Risk register
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
A repository that supports the availability for use and communication of all relevant risk information in a timely, complete, valid, and, if required, confidential manner.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-9c38c7c7a9301a714177f7a4368d9a02.html b/id-iso15288-model/elements/id-9c38c7c7a9301a714177f7a4368d9a02.html
new file mode 100644
index 0000000000000000000000000000000000000000..cd025d94143e1603d8df6878017f86eb898892c9
--- /dev/null
+++ b/id-iso15288-model/elements/id-9c38c7c7a9301a714177f7a4368d9a02.html
@@ -0,0 +1,123 @@
+
+
+
+
+ Organization lessons learned
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Organization lessons learned
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Organizational-related lessons learned. Results from an evaluation or observation of an implemented corrective action that contributed to improved performance or increased capability. A lesson learned also results from an evaluation or observation of a positive finding that did not necessarily require corrective action other than sustainment.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-9ee728b017c941c8a3dfcb1b9973f9d2.html b/id-iso15288-model/elements/id-9ee728b017c941c8a3dfcb1b9973f9d2.html
new file mode 100644
index 0000000000000000000000000000000000000000..9ba3cdc4d700f9c0103a9c84510bdf22b8b62cd6
--- /dev/null
+++ b/id-iso15288-model/elements/id-9ee728b017c941c8a3dfcb1b9973f9d2.html
@@ -0,0 +1,155 @@
+
+
+
+
+ System viewpoints views and models
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ System viewpoints views and models
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Definitions of viewpoints to document the procedures for creating, interpreting, analyzing, and evaluating architectural data. One or more views of the system. Each architectural view is a representation of the complete system from the perspective of one or more system concerns, for its stakeholders. (Adapted from ISO/IEC/IEEE 15289, 2019)
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-a23964f074d5ff800d10cfc1c5a928e4.html b/id-iso15288-model/elements/id-a23964f074d5ff800d10cfc1c5a928e4.html
new file mode 100644
index 0000000000000000000000000000000000000000..c6efa369f345c5edb68b968ed2cfa3371af9eba6
--- /dev/null
+++ b/id-iso15288-model/elements/id-a23964f074d5ff800d10cfc1c5a928e4.html
@@ -0,0 +1,115 @@
+
+
+
+
+ Acquisition agreement
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Acquisition agreement
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Mutual acknowledgment of terms and conditions under which a working relationship is conducted between an acquirer and a supplier. (Adapted from ISO/IEC/IEEE 15288, 2023).
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-a869ede9033db73de151f726c5835845.html b/id-iso15288-model/elements/id-a869ede9033db73de151f726c5835845.html
new file mode 100644
index 0000000000000000000000000000000000000000..c6bb2ce9284e812b9886bf2be21c714d94d93b47
--- /dev/null
+++ b/id-iso15288-model/elements/id-a869ede9033db73de151f726c5835845.html
@@ -0,0 +1,205 @@
+
+
+
+
+ Acquisition
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Acquisition
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.1.1.1] The purpose of the Acquisition process is to obtain a product or service in accordance with the acquirer's requirements. See detailed description in the INCOSE Handbook v.5, page 45
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-aa2ab1a499aa193f89dd4b4579874a83.html b/id-iso15288-model/elements/id-aa2ab1a499aa193f89dd4b4579874a83.html
new file mode 100644
index 0000000000000000000000000000000000000000..b4cf1a8a428288522088a21572a250e93ec6d67a
--- /dev/null
+++ b/id-iso15288-model/elements/id-aa2ab1a499aa193f89dd4b4579874a83.html
@@ -0,0 +1,219 @@
+
+
+
+
+ Implementation
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Implementation
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.4.7.1] The purpose of the Implementation process is to realize a specified system element. See detailed description in the INCOSE Handbook v.5, page 132
An account prepared for interested parties in order to communicate the status, results, and outcomes of the stakeholder needs and requirements definition activities.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-b373095ae0294e4a0c01a9733962f63b.html b/id-iso15288-model/elements/id-b373095ae0294e4a0c01a9733962f63b.html
new file mode 100644
index 0000000000000000000000000000000000000000..710b0b134314c14aef38d963c7fee4d82adb5c69
--- /dev/null
+++ b/id-iso15288-model/elements/id-b373095ae0294e4a0c01a9733962f63b.html
@@ -0,0 +1,107 @@
+
+
+
+
+ Decision register
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Decision register
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
A repository that supports the availability for use and communication of all relevant decision information in a timely, complete, valid, and, if required, confidential manner.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-b6079f4e7c235d9ec259ea5731ea9c72.html b/id-iso15288-model/elements/id-b6079f4e7c235d9ec259ea5731ea9c72.html
new file mode 100644
index 0000000000000000000000000000000000000000..6a066a50f95f5ca9dcf4450fa98b990e2932c636
--- /dev/null
+++ b/id-iso15288-model/elements/id-b6079f4e7c235d9ec259ea5731ea9c72.html
@@ -0,0 +1,224 @@
+
+
+
+
+ Business or Mission Analysis
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Business or Mission Analysis
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.4.1.1] The purpose of the Business or Mission Analysis process is to define the business or mission problem or opportunity, characterize the solution space, and determine potential solution class(es) that could address a problem or take advantage of an opportunity. See detailed description in the INCOSE Handbook v.5, page 103
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-b646cc8365fcc57e8df8c9dca79538f5.html b/id-iso15288-model/elements/id-b646cc8365fcc57e8df8c9dca79538f5.html
new file mode 100644
index 0000000000000000000000000000000000000000..0927b98a031d37a6ece13b99f2b42140538f7c3c
--- /dev/null
+++ b/id-iso15288-model/elements/id-b646cc8365fcc57e8df8c9dca79538f5.html
@@ -0,0 +1,199 @@
+
+
+
+
+ Disposal
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Disposal
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.4.14.1] The purpose of the Disposal process is to end the existence of a system element or system for a specified intended use, appropriately handle replaced or retired elements, and to properly attend to identified critical disposal needs. See detailed description in the INCOSE Handbook v.5, page 156
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-b8408f7f1eaea29aaab46eb07bd456b9.html b/id-iso15288-model/elements/id-b8408f7f1eaea29aaab46eb07bd456b9.html
new file mode 100644
index 0000000000000000000000000000000000000000..9799e25d983c1cd943a7194b521e4a8b370cacee
--- /dev/null
+++ b/id-iso15288-model/elements/id-b8408f7f1eaea29aaab46eb07bd456b9.html
@@ -0,0 +1,123 @@
+
+
+
+
+ Validation criteria
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Validation criteria
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
The validation criteria (the measures to be assessed), who will perform validation activities++ and the validation environments of the system-of-interest.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-bc4487fbe79c4ee535d3038024441e01.html b/id-iso15288-model/elements/id-bc4487fbe79c4ee535d3038024441e01.html
new file mode 100644
index 0000000000000000000000000000000000000000..87a7203ff5a940f3cde0c734b4d0ddffbba5bf44
--- /dev/null
+++ b/id-iso15288-model/elements/id-bc4487fbe79c4ee535d3038024441e01.html
@@ -0,0 +1,115 @@
+
+
+
+
+ Project schedule
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Project schedule
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
A linked list of a project milestones, activities, and deliverables with intended start and finish dates May include a top-level milestone schedule and multiple levels (also called tiers) of schedules of increasing detail and task descriptions with completion criteria and work authorizations.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-bd8ecb828ad657398312864a5462f612.html b/id-iso15288-model/elements/id-bd8ecb828ad657398312864a5462f612.html
new file mode 100644
index 0000000000000000000000000000000000000000..0e38125ebb259d942b1873711acbe7eee6a523fc
--- /dev/null
+++ b/id-iso15288-model/elements/id-bd8ecb828ad657398312864a5462f612.html
@@ -0,0 +1,147 @@
+
+
+
+
+ System design rationale
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ System design rationale
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Rationale for design selection, system element selection, and allocation between system requirements and system elements. Includes rationale of major selected implementation options and enablers.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-c386c79371816578874373c86033b9c8.html b/id-iso15288-model/elements/id-c386c79371816578874373c86033b9c8.html
new file mode 100644
index 0000000000000000000000000000000000000000..c9542438ba32e2238e1ee56f43e258860bade9e3
--- /dev/null
+++ b/id-iso15288-model/elements/id-c386c79371816578874373c86033b9c8.html
@@ -0,0 +1,131 @@
+
+
+
+
+ System requirements
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ System requirements
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Structured collection of the requirements [functions, performance, design constraints, and other attributes] for the system and its operational environments and external interfaces. (ISO/IEC/IEEE 29148, 2018)
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-c6fdeeb79671869631ec0a5b238213d3.html b/id-iso15288-model/elements/id-c6fdeeb79671869631ec0a5b238213d3.html
new file mode 100644
index 0000000000000000000000000000000000000000..910b7a94c548940b28f92ed40f28dece3799a11f
--- /dev/null
+++ b/id-iso15288-model/elements/id-c6fdeeb79671869631ec0a5b238213d3.html
@@ -0,0 +1,180 @@
+
+
+
+
+ Knowledge Management
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Knowledge Management
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.2.6.1] The purpose of the Knowledge Management process is to create the capability and assets that enable the organization to exploit opportunities to re-�apply existing knowledge. See detailed description in the INCOSE Handbook v.5, page 67
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-c7a7b8dfc8439098ffab79d4b441b9ac.html b/id-iso15288-model/elements/id-c7a7b8dfc8439098ffab79d4b441b9ac.html
new file mode 100644
index 0000000000000000000000000000000000000000..220a220df899081ac7b4b7e00c859a8b039f87a9
--- /dev/null
+++ b/id-iso15288-model/elements/id-c7a7b8dfc8439098ffab79d4b441b9ac.html
@@ -0,0 +1,123 @@
+
+
+
+
+ Supply response
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Supply response
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Prepared by a potential supplier to support the offer of a contract bid, including cost, schedule, risk statements, methodology to satisfy the request for supply, experiences and capabilities, any recommendations to tailor the request for supply or contract, and the signature of the supplier's approving authority. Informally, may be prepared within an organization. (Adapted from ISO/IEC/IEEE 15289, 2019)
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-ca50a9d505982a27fa2e6d4aa55260c6.html b/id-iso15288-model/elements/id-ca50a9d505982a27fa2e6d4aa55260c6.html
new file mode 100644
index 0000000000000000000000000000000000000000..d2643a78a6bcd7427e0904a67f3585cc3355f76a
--- /dev/null
+++ b/id-iso15288-model/elements/id-ca50a9d505982a27fa2e6d4aa55260c6.html
@@ -0,0 +1,107 @@
+
+
+
+
+ Take due account of the life cycle structures recommended or mandated by standards
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Take due account of the life cycle structures recommended or mandated by standards
+
+
+ ()
+
+
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-cd3f9d9e27accbf5cf6025888d31b215.html b/id-iso15288-model/elements/id-cd3f9d9e27accbf5cf6025888d31b215.html
new file mode 100644
index 0000000000000000000000000000000000000000..3f6ffa6abab1a3b93375fe0f092e4d5e697a9cf5
--- /dev/null
+++ b/id-iso15288-model/elements/id-cd3f9d9e27accbf5cf6025888d31b215.html
@@ -0,0 +1,199 @@
+
+
+
+
+ Operation
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Operation
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.4.12.1] The purpose of the Operation process is to use the system to deliver its services. See detailed description in the INCOSE Handbook v.5, page 152
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-cde520f5cf114ed38e5b8e0850564928.html b/id-iso15288-model/elements/id-cde520f5cf114ed38e5b8e0850564928.html
new file mode 100644
index 0000000000000000000000000000000000000000..7c15a46249d1664befbd55ef10b707bcf4c56cd1
--- /dev/null
+++ b/id-iso15288-model/elements/id-cde520f5cf114ed38e5b8e0850564928.html
@@ -0,0 +1,107 @@
+
+
+
+
+ Measurement register
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Measurement register
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
A repository that supports the availability for use and communication of all relevant measures in a timely, complete, valid, and, if required, confidential manner.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-cf6cb997ccfb6b02d1c141ec78346bd4.html b/id-iso15288-model/elements/id-cf6cb997ccfb6b02d1c141ec78346bd4.html
new file mode 100644
index 0000000000000000000000000000000000000000..efc6acb8329745ba80daf63873ab779f3ffb62d3
--- /dev/null
+++ b/id-iso15288-model/elements/id-cf6cb997ccfb6b02d1c141ec78346bd4.html
@@ -0,0 +1,123 @@
+
+
+
+
+ Systems engineering management plan (SEMP)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Systems engineering management plan (SEMP)
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Presents how the project processes and activities are executed to assure the project’s successful completion, and the quality of the deliverable product or service. (Adapted from ISO/IEC/ IEEE 15289, 2019)
Action to eliminate the cause or reduce the likelihood of recurrence of a detected organizational nonconformity or other undesirable situation. (Adapted from ISO/IEC 19770–1++ 2017)
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-d03a9e7fd8fee49582a155c23b989af7.html b/id-iso15288-model/elements/id-d03a9e7fd8fee49582a155c23b989af7.html
new file mode 100644
index 0000000000000000000000000000000000000000..b095df8b49582fc6fff76a0cec52565316bb9e03
--- /dev/null
+++ b/id-iso15288-model/elements/id-d03a9e7fd8fee49582a155c23b989af7.html
@@ -0,0 +1,249 @@
+
+
+
+
+ Design Definition
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Design Definition
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.4.5.1] The purpose of the Design Definition process is to provide sufficient detailed data and information about the system and its elements to enable the imple- mentation consistent with architectural entities as defined in models and views of the system architecture. See detailed description in the INCOSE Handbook v.5, page 124
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-d779de405ef48c52eecec2f329288a4a.html b/id-iso15288-model/elements/id-d779de405ef48c52eecec2f329288a4a.html
new file mode 100644
index 0000000000000000000000000000000000000000..80c9abba7be5e11be5b339c1cb5aaf3bcca48870
--- /dev/null
+++ b/id-iso15288-model/elements/id-d779de405ef48c52eecec2f329288a4a.html
@@ -0,0 +1,237 @@
+
+
+
+
+ Project Assessment and Control
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Project Assessment and Control
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.3.2.1] The purpose of the Project Assessment and Control process is to assess if the plans are aligned and feasible, determine the status of the project, technical and process performance, and direct execution to ensure that the performance is according to plans and schedules, within projected budgets, to satisfy technical objectives.
+
+See detailed description in the INCOSE Handbook v.5, page 75
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-d87c15289dd6be94a6180147026a044e.html b/id-iso15288-model/elements/id-d87c15289dd6be94a6180147026a044e.html
new file mode 100644
index 0000000000000000000000000000000000000000..25a006cc290d4e32c90e17691d26a4ee3e193137
--- /dev/null
+++ b/id-iso15288-model/elements/id-d87c15289dd6be94a6180147026a044e.html
@@ -0,0 +1,179 @@
+
+
+
+
+ Change request
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Change request
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Identified anomaly, required, or recommended enhancement to a project, from the time an idea is recorded until the disposition by a designated change authority. (Adapted from ISO/IEC/IEEE 24765, 2017).
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-dd6cf1d87fb6df01557c10158b7b0c3a.html b/id-iso15288-model/elements/id-dd6cf1d87fb6df01557c10158b7b0c3a.html
new file mode 100644
index 0000000000000000000000000000000000000000..70e522b3b44aa0a09dd7c59d3aedf8c9d1249ec4
--- /dev/null
+++ b/id-iso15288-model/elements/id-dd6cf1d87fb6df01557c10158b7b0c3a.html
@@ -0,0 +1,239 @@
+
+
+
+
+ Verification
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Verification
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.4.9.1] The purpose of the Verification process is to provide objective evidence that a system or system element fulfils its specified requirements and characteristics. See detailed description in the INCOSE Handbook v.4, page 138
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-e11ea374218ac0ea29fa27c1de14f35b.html b/id-iso15288-model/elements/id-e11ea374218ac0ea29fa27c1de14f35b.html
new file mode 100644
index 0000000000000000000000000000000000000000..c7fdccd5078af3f7066bf5b8ec139a0b90d468db
--- /dev/null
+++ b/id-iso15288-model/elements/id-e11ea374218ac0ea29fa27c1de14f35b.html
@@ -0,0 +1,155 @@
+
+
+
+
+ Risk Management
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Risk Management
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.3.4.1] The purpose of the Risk Management process is to identify, analyze, treat and monitor the risks continually. See detailed description in the INCOSE Handbook v.5, page 81
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-e219e212ad0a3439b9985e90e56683d1.html b/id-iso15288-model/elements/id-e219e212ad0a3439b9985e90e56683d1.html
new file mode 100644
index 0000000000000000000000000000000000000000..3f71036bcdf80f0c8b7d4a0ec7fd44ad3b4e8502
--- /dev/null
+++ b/id-iso15288-model/elements/id-e219e212ad0a3439b9985e90e56683d1.html
@@ -0,0 +1,165 @@
+
+
+
+
+ Infrastructure Management
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Infrastructure Management
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.2.2.1] The purpose of the Infrastructure Management process is to provide the infrastructure and services to projects to support organization and project objectives throughout the life cycle. See detailed description in the INCOSE Handbook v.5, page 54
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-e3172a84813086be8a248a53d5933d7c.html b/id-iso15288-model/elements/id-e3172a84813086be8a248a53d5933d7c.html
new file mode 100644
index 0000000000000000000000000000000000000000..19b7ffc12b8659829ed578624ef16d29f1235535
--- /dev/null
+++ b/id-iso15288-model/elements/id-e3172a84813086be8a248a53d5933d7c.html
@@ -0,0 +1,316 @@
+
+
+
+
+ External
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ External
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
External represents those typical inputs and outputs that come from, or go to, beyond the set of system life cycle processes (i.e., they do not come from, or go to, another system life cycle process).
+
+Note that these can be either
+
+internal (e.g., Organization strategic plan) or
+
+external (e.g., Applicable laws and regulations) to the organization.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-ec90e4b436491a8806dcc2ebb9a72289.html b/id-iso15288-model/elements/id-ec90e4b436491a8806dcc2ebb9a72289.html
new file mode 100644
index 0000000000000000000000000000000000000000..28b93bf02feb2e6774f0601ee00aa8adda9774ec
--- /dev/null
+++ b/id-iso15288-model/elements/id-ec90e4b436491a8806dcc2ebb9a72289.html
@@ -0,0 +1,123 @@
+
+
+
+
+ Variance or deviation or waiver request
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Variance or deviation or waiver request
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Request, temporary or permanent, to accept a configuration item or other designated item which, during production or after having been submitted for inspection, is found to depart from specified requirements, but is nevertheless considered suitable for use as is or after rework by an approved method. (Adapted from ISO/IEC/IEEE 24765, 2017)
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-ed9b17fac31261a7ea2e4bd09009788f.html b/id-iso15288-model/elements/id-ed9b17fac31261a7ea2e4bd09009788f.html
new file mode 100644
index 0000000000000000000000000000000000000000..664ee4ee0e1f07277079965e0b1b1493da22b6a8
--- /dev/null
+++ b/id-iso15288-model/elements/id-ed9b17fac31261a7ea2e4bd09009788f.html
@@ -0,0 +1,194 @@
+
+
+
+
+ Maintenance
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Maintenance
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
As stated in ISO/IEC/IEEE 15288:2023, [6.4.13.1] The purpose of the Maintenance process is to sustain the capability of the system to provide a service. See detailed description in the INCOSE Handbook v.5, page 154
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-f37ab4d8469c2b5570da1b3c7595d9ef.html b/id-iso15288-model/elements/id-f37ab4d8469c2b5570da1b3c7595d9ef.html
new file mode 100644
index 0000000000000000000000000000000000000000..7621e3f7542b251e0946a6e14b0bd7a70508a62e
--- /dev/null
+++ b/id-iso15288-model/elements/id-f37ab4d8469c2b5570da1b3c7595d9ef.html
@@ -0,0 +1,123 @@
+
+
+
+
+ Configuration baseline
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Configuration baseline
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Configuration information formally designated at a specific time during the life of a product, product component, service, or service component. (Adapted from ISO/IEC/IEEE 24765, 2017).
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-f522a38586ebe4ec6f31c3c66cf57484.html b/id-iso15288-model/elements/id-f522a38586ebe4ec6f31c3c66cf57484.html
new file mode 100644
index 0000000000000000000000000000000000000000..db88cfc52ecfa884cf448d6455a1283311ac9915
--- /dev/null
+++ b/id-iso15288-model/elements/id-f522a38586ebe4ec6f31c3c66cf57484.html
@@ -0,0 +1,107 @@
+
+
+
+
+ Project control request
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Project control request
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Project directives based on action required due to deviations from the project plan. If assessments are associated with a decision gate, a decision to proceed or not to proceed, is taken.
+
+
+
\ No newline at end of file
diff --git a/id-iso15288-model/elements/id-fab76531a1b98e61db59bf269fa6a721.html b/id-iso15288-model/elements/id-fab76531a1b98e61db59bf269fa6a721.html
new file mode 100644
index 0000000000000000000000000000000000000000..cccee3dcc8dd7477c682c968e9649c1a93078973
--- /dev/null
+++ b/id-iso15288-model/elements/id-fab76531a1b98e61db59bf269fa6a721.html
@@ -0,0 +1,107 @@
+
+
+
+
+ Information register
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Information register
+
+
+ ()
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
A repository that supports the availability for use and communication of all relevant project information artifacts in a timely, complete, valid, and, if required, restricted manner.