update
This commit is contained in:
parent
7264e7777c
commit
b2c2fcb398
BIN
Writerside/images/image_410.png
Normal file
BIN
Writerside/images/image_410.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 25 KiB |
BIN
Writerside/images/image_411.png
Normal file
BIN
Writerside/images/image_411.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 2.8 KiB |
BIN
Writerside/images/image_412.png
Normal file
BIN
Writerside/images/image_412.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 44 KiB |
@ -40,6 +40,7 @@
|
||||
</toc-element>
|
||||
<toc-element topic="DesignPatterns.md"/>
|
||||
</toc-element>
|
||||
<toc-element topic="RequirementsAnalysis.md"/>
|
||||
</toc-element>
|
||||
<toc-element toc-title="Rechnerarchitektur">
|
||||
<toc-element topic="Historie.md"/>
|
||||
|
23
Writerside/topics/OOAD/RequirementsAnalysis.md
Normal file
23
Writerside/topics/OOAD/RequirementsAnalysis.md
Normal file
@ -0,0 +1,23 @@
|
||||
# Requirements Analysis
|
||||
## Domain Diagram
|
||||
- Konzeptuelles Modell um ein gemeinsames Vokabular im Projekt-Team zu etablieren
|
||||
### Problem Domain
|
||||
- Devs haben ein gemeinsames Verständnis von Lösungen
|
||||
|
||||
### Solution Domain
|
||||
- Es muss ein gemeinsames Verständnis von dem Arbeitsumfeld des Klienten geschaffen werden
|
||||
|
||||
### Beispiel Domain Diagram
|
||||

|
||||
- Zeigt die wichtigsten Problem-Domains und ihre Verbindungen
|
||||
|
||||
|
||||
## UML Use Case Diagram
|
||||
- System Anforderungen erfassen
|
||||
- NUR [Functional Requirements](IntroductionOOAD.md#requirements-in-software-engineering)
|
||||
|
||||
### Notation
|
||||
#### Actor
|
||||
- 
|
||||
- Identifizierung:
|
||||
- 
|
Loading…
x
Reference in New Issue
Block a user