Requirements-Management: Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
| Zeile 9: | Zeile 9: | ||
;Steps | ;Steps | ||
| + | |||
| + | {| class="wikitable" | ||
| + | ! Schritt !! TOGAF !! Tailoring IVS-Rahmenarchitektur !! Anleitung !! Artefakte {K=Katalog, M=Matrix, D=Diagramm}, O=Other Deliverables | ||
| + | |||
| + | |- | ||
| + | |- style="vertical-align:top;" | ||
| + | ||1 | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | |||
| + | |||
| + | |- | ||
| + | |- style="vertical-align:top;" | ||
| + | ||2 | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | |||
| + | |||
| + | |- | ||
| + | |- style="vertical-align:top;" | ||
| + | ||3 | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | |||
| + | |||
| + | |- | ||
| + | |- style="vertical-align:top;" | ||
| + | ||4 | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | |||
| + | |||
| + | |- | ||
| + | |- style="vertical-align:top;" | ||
| + | ||5 | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | |||
| + | |||
| + | |- | ||
| + | |- style="vertical-align:top;" | ||
| + | ||6 | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | |||
| + | |||
| + | |- | ||
| + | |- style="vertical-align:top;" | ||
| + | ||7 | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | |||
| + | |||
| + | |- | ||
| + | |- style="vertical-align:top;" | ||
| + | ||8 | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | |||
| + | |||
| + | |- | ||
| + | |- style="vertical-align:top;" | ||
| + | ||9 | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | |||
| + | |||
| + | |- | ||
| + | |- style="vertical-align:top;" | ||
| + | ||10 | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | || | ||
| + | |||
| + | |||
| + | |} | ||
Version vom 13. Juni 2016, 10:34 Uhr
Architektur Requirements-Management
- Allgemeine Infos
- Das Requirements-Management wird während den Steps zur Entwicklung einer IVS-Architektur kontinuierlich angewendet. Es handelt sich hierbei um einen dynamischen Ansatz, bei dem innerhalb der Phasen Anforderungen an die Architektur identifiziert werden.
Zudem werden im Requirements-Management spätere Änderungen und daraus resultierende Anforderungen an die Architektur in den jeweiligen Phasen eingepflegt.
- Identifikation von Anforderungen
- Um Anforderungen, die der Architektur-Vision entsprechen, zu ermitteln, kann die Technik der Business-Szenarios angewandt werden. Sie dient der Identifikation und Dokumentation von Anforderungen. Genaueres hierzu siehe: Business-Szenarios
- Steps
| Schritt | TOGAF | Tailoring IVS-Rahmenarchitektur | Anleitung | Artefakte {K=Katalog, M=Matrix, D=Diagramm}, O=Other Deliverables |
|---|---|---|---|---|
| 1 |
| |||
| 2 |
| |||
| 3 |
| |||
| 4 |
| |||
| 5 |
| |||
| 6 |
| |||
| 7 |
| |||
| 8 |
| |||
| 9 |
| |||
| 10 |
|