diff --git a/Writerside/images/image_410.png b/Writerside/images/image_410.png new file mode 100644 index 0000000..863ca0d Binary files /dev/null and b/Writerside/images/image_410.png differ diff --git a/Writerside/images/image_411.png b/Writerside/images/image_411.png new file mode 100644 index 0000000..a2c4c1b Binary files /dev/null and b/Writerside/images/image_411.png differ diff --git a/Writerside/images/image_412.png b/Writerside/images/image_412.png new file mode 100644 index 0000000..a394434 Binary files /dev/null and b/Writerside/images/image_412.png differ diff --git a/Writerside/in.tree b/Writerside/in.tree index 7429007..822be49 100644 --- a/Writerside/in.tree +++ b/Writerside/in.tree @@ -40,6 +40,7 @@ + diff --git a/Writerside/topics/OOAD/RequirementsAnalysis.md b/Writerside/topics/OOAD/RequirementsAnalysis.md new file mode 100644 index 0000000..6a64b93 --- /dev/null +++ b/Writerside/topics/OOAD/RequirementsAnalysis.md @@ -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 +![image_410.png](image_410.png) +- 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 +- ![image_411.png](image_411.png) +- Identifizierung: + - ![image_412.png](image_412.png) \ No newline at end of file