|
|
| 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=Requirement
| + | <!-- |
| − | |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_Requirement.png
| + | * Create Template:SmartCoreEpilogue for any wiki code that should be added to the default display template for any element |
| − | |Elementtypedefinitie=Een eis is de verklaring van een bepaalde behoefte waarin door een systeem voorzien moet worden.
| + | * 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:"In the end, a business goal must be realized by a plan or concrete change goal, which may or may not require a new system or changes to an existing system.
| |
| − | | |
| − | The term 'system' is used in its general meaning; i.e., as a group of (functionally) related elements, where each element may be considered as a system again. Therefore, a system may refer to any active structural element, behavioral element, or passive structural element of some organization, such as a business actor, application component, business process, application service, business object, or data object.
| |
| − | | |
| − | Requirements model the properties of these elements that are needed to achieve the 'ends' that are modeled by the goals. In this respect, requirements represent the 'means' to realize goals.
| |
| − | | |
| − | During the design process, goals may be decomposed until the resulting sub-goals are sufficiently detailed to enable their realization by properties that can be exhibited by systems. At this point, goals can be realized by requirements that assign these properties to the systems.
| |
| − | | |
| − | For example, one may identify two alternative requirements to realize the goal to improve portfolio management: (i) by assigning a personal assistant to each customer, or (ii) by introducing on-line portfolio management. The former requirement can be realized by a human actor and the latter by a software application. These requirements can be decomposed further to define the requirements on the human actor and the software application in more detail."
| |
