finished exercise
This commit is contained in:
BIN
readme.pdf
BIN
readme.pdf
Binary file not shown.
16
readme.typ
16
readme.typ
@@ -9,6 +9,11 @@
|
|||||||
|
|
||||||
= Exercise 01
|
= Exercise 01
|
||||||
|
|
||||||
|
- Name: Quirin Ecker
|
||||||
|
- Student ID: k12310122
|
||||||
|
- Group: 21
|
||||||
|
|
||||||
|
|
||||||
== Part 1 - Questionaire
|
== Part 1 - Questionaire
|
||||||
|
|
||||||
=== Q1: What is Dronology about, and what are its two main goals?
|
=== Q1: What is Dronology about, and what are its two main goals?
|
||||||
@@ -42,4 +47,15 @@ the `Services` layer communicates with the `CORE` layer. The `CORE` layer uses t
|
|||||||
|
|
||||||
=== Q4: Which are the available artifacts for Dronology? For each artifact, summarize which information they provide
|
=== Q4: Which are the available artifacts for Dronology? For each artifact, summarize which information they provide
|
||||||
|
|
||||||
|
- Components: Components are self contained units in a software system. They are used throughout the system.
|
||||||
|
- Use Cases: Use Cases specify the different scenarios/interactions that the system must support. Its a step by step instruction on how the user interacts with the system and how the system responds.
|
||||||
|
- Requirements: The Requirments list specifies everything that is required to meet the goal of the users and stakeholders. It describes what the system must do and how it should behave.
|
||||||
|
|
||||||
|
== Part 2 - Use Case Diagram
|
||||||
|
|
||||||
|
- Group: `21`
|
||||||
|
- UseCase: `UC3`
|
||||||
|
|
||||||
|
#figure(
|
||||||
|
image("usecasedia.png"),
|
||||||
|
)
|
||||||
|
|||||||
BIN
usecasedia.png
Normal file
BIN
usecasedia.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 90 KiB |
Reference in New Issue
Block a user