|
|
| Regel 1: |
Regel 1: |
| {{#Elementtype: | | <!--TS:20170830195000-->{{#defineArchiMateElementtype:elementtype={{PAGENAME}}}}<!--This page is part of WikiXL SmartConnectArchiMate™. © 2016-2017 XL&Knowledge. Usage without proper license is strictly prohibited. Contact us at [mailto:support@xl-knowledge.com support@xl-knowledge.com]. Any changes to this page will be overwritten by module upgrades.--> |
| |Paginanaam=Principle
| | <!-- |
| |Kennismodel=KnowledgeModel ArchiMate v2.1
| | Note: to add custom properties and/or add to or change the display template associated with this elementtype, use one of the following: |
| |Elementtype-icoon=ArchiMate_Principle.png
| | * Create Template:SmartCoreEpilogue for any wiki code that should be added to the default display template for any element |
| |Elementtypedefinitie=Een principe is een normatieve eigenschap van alle systemen in een gegeven situatie of van de wijze waarop die systemen worden gerealiseerd.
| | * Create Template:<Elementtype>Epilogue for any wiki code that should be added to the default display template for any element of a specific elementtype |
| |Elementtypecategorie={{PAGENAME}}s
| | * Create Template:<Elementtyoe>Custom for wiki code that should override the default display template |
| |Elementtypeoverigecat=ArchiMateConcepts, ArchiMateElements, MotivationExtension
| | --> |
| |Elementtypebron=ArchiMate 2.1
| |
| |Elementtypeverwijzing=http://pubs.opengroup.org/architecture/archimate2-doc
| |
| |Elementtypeopmaaksjabloon=DisplayArchiMateElement
| |
| }} | |
| {{#elementtypeproperties:
| |
| |Kennismodel=KnowledgeModel ArchiMate v2.1
| |
| |Elementtype-eigenschappen=ImportDateTime, ImportSource, ImportJobID, Label, Documentation, CustomProperties
| |
| }}
| |
| {{#elementtyperelation:
| |
| |Kennismodel=KnowledgeModel ArchiMate v2.1
| |
| |Elementrelatie=Occurs in model
| |
| |Eindpunten=ArchiMateModel
| |
| }}
| |
| Uit ArchiMate:"Principles are strongly related to goals and requirements. Similar to requirements, principles define intended properties of systems. However, in contrast to requirements, principles are broader in scope and more abstract than requirements. A principle defines a general property that applies to any system in a certain context. A requirement defines a property that applies to a specific system.
| |
| | |
| A principle needs to be made specific for a given system by means of one or more requirements, in order to enforce that the system conforms to the principle. For example, the principle 'Information management processes comply with all relevant laws, policies, and regulations' is realized by the requirements that are imposed by the actual laws, policies, and regulations that apply to the specific system under design.
| |
| | |
| A principle is motivated by some goal. For example, the aforementioned principle may be motivated by the goal to maintain a good reputation and/or the goal to avoid penalties. The principle provides a means to realize its motivating goal, which is generally formulated as a guideline. This guideline constrains the design of all systems in a given context by stating the general properties that are required from any system in this context to realize the goal. Principles are intended to be more stable than requirements in the sense that they do not change as quickly as requirements may do. Organizational values, best practices, and design knowledge may be reflected and made applicable in terms of principles."
| |
