Commit f48b63

2026-04-27 20:03:58 lisa: Essential Terms: switch Obsidian callouts to OtterWiki folded blocks Obsidian's '> [!note]- Term' syntax was rendering as plain blockquotes on OtterWiki. Converted all 26 entries to '>| ### Term' folded-block syntax (per OtterWiki syntax guide), so each term is a click-to-expand summary with the definition revealed below.
sd/C02/Essential Terms.md ..
@@ 20,83 20,83 @@
## Glossary
-> [!note]- Actor
-> An entity that can interact with the software solution as shown in a use case diagram
+>| ### Actor
+>| An entity that can interact with the software solution as shown in a use case diagram
-> [!note]- Association
-> A relationship between two elements in a use case diagram
+>| ### Association
+>| A relationship between two elements in a use case diagram
-> [!note]- Close-ended questions
-> Questions that can be answered with a finite set of responses
+>| ### Close-ended questions
+>| Questions that can be answered with a finite set of responses
-> [!note]- Context diagram
-> A visualisation of a system in its entirety that indicates the data that is passed into and out of the system
+>| ### Context diagram
+>| A visualisation of a system in its entirety that indicates the data that is passed into and out of the system
-> [!note]- Data
-> Raw, unprocessed facts and figures
+>| ### Data
+>| Raw, unprocessed facts and figures
-> [!note]- Data flow
-> The movement of a piece or collection of data within an information system, as shown in context diagrams and data flow diagrams (DFDs)
+>| ### Data flow
+>| The movement of a piece or collection of data within an information system, as shown in context diagrams and data flow diagrams (DFDs)
-> [!note]- Data flow diagram (DFD)
-> A graphical visualisation of the flow of information within a system, including data provided by external entities
+>| ### Data flow diagram (DFD)
+>| A graphical visualisation of the flow of information within a system, including data provided by external entities
-> [!note]- Data store
-> A representation of a collection of data that is stored in some way within a system
+>| ### Data store
+>| A representation of a collection of data that is stored in some way within a system
-> [!note]- Entity
-> The users or external systems that interact with the system being created
+>| ### Entity
+>| The users or external systems that interact with the system being created
-> [!note]- Extend
-> A relationship between use cases where one use case has optional or additional functionality, which is represented in a use case diagram as a second use case
+>| ### Extend
+>| A relationship between use cases where one use case has optional or additional functionality, which is represented in a use case diagram as a second use case
-> [!note]- Generalisation
-> A parent-child relationship between two elements in a use case diagram
+>| ### Generalisation
+>| A parent-child relationship between two elements in a use case diagram
-> [!note]- Include
-> A relationship between use cases where one use case is tied to, or relies upon, the functionality contained within another use case
+>| ### Include
+>| A relationship between use cases where one use case is tied to, or relies upon, the functionality contained within another use case
-> [!note]- Interview
-> A face-to-face meeting between people for consultative purposes
+>| ### Interview
+>| A face-to-face meeting between people for consultative purposes
-> [!note]- Observation
-> A method of data collection that involves physically observing how a system operates and how it is used
+>| ### Observation
+>| A method of data collection that involves physically observing how a system operates and how it is used
-> [!note]- Open-ended questions
-> Questions where the number of potential answers is infinite
+>| ### Open-ended questions
+>| Questions where the number of potential answers is infinite
-> [!note]- Process (context diagram)
-> An abstract representation of the whole system being created
+>| ### Process (context diagram)
+>| An abstract representation of the whole system being created
-> [!note]- Process (data flow diagram)
-> An abstract representation of a function within a system
+>| ### Process (data flow diagram)
+>| An abstract representation of a function within a system
-> [!note]- Qualitative data
-> Data that consists of descriptive details, usually gathered via surveys or interviews
+>| ### Qualitative data
+>| Data that consists of descriptive details, usually gathered via surveys or interviews
-> [!note]- Quantitative data
-> Data that can be easily processed in a statistical manner, usually composed of definite numbers
+>| ### Quantitative data
+>| Data that can be easily processed in a statistical manner, usually composed of definite numbers
-> [!note]- Relationship
-> The connections between elements within a use case diagram
+>| ### Relationship
+>| The connections between elements within a use case diagram
-> [!note]- Report
-> A written document providing a summary or finding in relation to the context or system being analysed
+>| ### Report
+>| A written document providing a summary or finding in relation to the context or system being analysed
-> [!note]- Survey
-> A set of questions that ask for a response to be selected from a list of alternatives
+>| ### Survey
+>| A set of questions that ask for a response to be selected from a list of alternatives
-> [!note]- System boundary
-> A rectangle around relevant use cases that indicates the use cases that are within the scope of the solution
+>| ### System boundary
+>| A rectangle around relevant use cases that indicates the use cases that are within the scope of the solution
-> [!note]- Unified Modeling Language (UML)
-> A general-purpose visual modelling language
+>| ### Unified Modeling Language (UML)
+>| A general-purpose visual modelling language
-> [!note]- Use case
-> A representation of the transactions or functions a user (actor) can complete in a system, as shown in a use case diagram
+>| ### Use case
+>| A representation of the transactions or functions a user (actor) can complete in a system, as shown in a use case diagram
-> [!note]- Use case diagram (UCD)
-> A method of describing how a user interacts with a system, using Unified Modeling Language (UML)
+>| ### Use case diagram (UCD)
+>| A method of describing how a user interacts with a system, using Unified Modeling Language (UML)
---
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9