From d0ad0c2edcb04ecdf2144f8095f56bf4e7a6ae06 Mon Sep 17 00:00:00 2001 From: Ian Valentin Christensen Date: Thu, 1 May 2025 02:01:46 +0200 Subject: improve consistency --- portfolio1.md | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/portfolio1.md b/portfolio1.md index 607f807..302e304 100644 --- a/portfolio1.md +++ b/portfolio1.md @@ -17,7 +17,7 @@ associating tasks with a progress state as a way of managing flow of progress. Commonly a two-dimensional kanban board provides overview, with individual tasks listed vertically -and divisions of task states horisontally +and divisions of task states horizontally [@Anderson2016, p. 18]. One of the aims of these principles is to establish a sense of sustainability @@ -81,9 +81,20 @@ visualized in the roadmap at @fig-kanban. ## Diagram -TODO: Short introduction to the diagram. +We ideally wanted to create activity classes in relation to databases +to integrate parts with each other, +but we ran short on time. +Portfolio 1 might therefore seem less structured than the other parts. -![UML Class Diagram for Bachelorizer](classes.svg) +A simple UML showing an early draft idea for portfolios 1-3 as 1 program is shown on @fig-draft. + +![UML Class Diagram for Bachelorizer](classes.svg){#fig-draft} + + +A simpler diagram is shown on @fig-final, +trying to account for types and requirements for a correct program. + +![Minimum diagram for portfolio1](diagram.svg){#fig-final} ## Validity of bachelor programmes -- cgit v1.2.3