vault backup: 2023-11-08 09:55:54
This commit is contained in:
parent
a45b54172b
commit
7f8e02e61a
2 changed files with 18 additions and 9 deletions
10
.obsidian/workspace.json
vendored
10
.obsidian/workspace.json
vendored
|
@ -13,7 +13,7 @@
|
|||
"state": {
|
||||
"type": "markdown",
|
||||
"state": {
|
||||
"file": "4a1s/RAS/Solution architecture.md",
|
||||
"file": "4a1s/RAS/PL - Aula n.md",
|
||||
"mode": "source",
|
||||
"source": false
|
||||
}
|
||||
|
@ -85,7 +85,7 @@
|
|||
"state": {
|
||||
"type": "backlink",
|
||||
"state": {
|
||||
"file": "4a1s/RAS/Solution architecture.md",
|
||||
"file": "4a1s/RAS/PL - Aula n.md",
|
||||
"collapseAll": false,
|
||||
"extraContext": false,
|
||||
"sortOrder": "alphabetical",
|
||||
|
@ -102,7 +102,7 @@
|
|||
"state": {
|
||||
"type": "outgoing-link",
|
||||
"state": {
|
||||
"file": "4a1s/RAS/Solution architecture.md",
|
||||
"file": "4a1s/RAS/PL - Aula n.md",
|
||||
"linksCollapsed": false,
|
||||
"unlinkedCollapsed": true
|
||||
}
|
||||
|
@ -125,7 +125,7 @@
|
|||
"state": {
|
||||
"type": "outline",
|
||||
"state": {
|
||||
"file": "4a1s/RAS/Solution architecture.md"
|
||||
"file": "4a1s/RAS/PL - Aula n.md"
|
||||
}
|
||||
}
|
||||
},
|
||||
|
@ -161,7 +161,7 @@
|
|||
"active": "9853b375f7893cb9",
|
||||
"lastOpenFiles": [
|
||||
"4a1s/MFES/PL - Aula 5.md",
|
||||
"4a1s/RAS/Solution architecture.md",
|
||||
"4a1s/RAS/PL - Aula n.md",
|
||||
"4a1s/MFES/PL - Aula 7.md",
|
||||
"4a1s/MFES/PL - Aula 6.md",
|
||||
"4a1s/DAA/PL - Aula 1.md",
|
||||
|
|
|
@ -1,13 +1,22 @@
|
|||
Steps:
|
||||
|
||||
## Solution architecture - Activity 1 description
|
||||
**Steps:**
|
||||
1. Analyze non functional requirements and identify the most relevant
|
||||
2. Based on relevance create a priorized list of non functional requirements
|
||||
3. Analyze architectural patterns and their characteristics
|
||||
4. Identify the best suitable patterns by mapping patterns characteristics to be priorized non-functional requirements
|
||||
|
||||
Inputs:
|
||||
**Inputs:**
|
||||
1. Non functional requirements
|
||||
2. Use cases
|
||||
|
||||
Outputs:
|
||||
**Outputs:**
|
||||
1. Decision on the architectural pattern to use
|
||||
2. Design
|
||||
2. Design decisions rationale for the selection
|
||||
Hint: Include outputs in section 5. Solution Strategy of the RAS template phase 2.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
Loading…
Reference in a new issue