Design Objective
To reduce the implementation efforts and system maintenance, and to increase independence from legacy applications, the prototype must be developed in a way that avoids complex interfaces.
01
Producer metadata and the represented concept document.
Concept identity
design-knowledge/unchaining-social-crowdlending-do17design-knowledge/unchaining-social-crowdlending-do17.mdTo reduce the implementation efforts and system maintenance, and to increase independence from legacy applications, the prototype must be developed in a way that avoids complex interfaces.
This design objective is proposed by Unchaining Social Businesses - Blockchain as the Basic Technology of a Crowdlending Platform (Andre Schweizer, Vincent Schlatt, Nils Urbach, Gilbert Fridgen, 2017).
02
Concepts connected by incoming or outgoing native Markdown links.
03
Directed links from Markdown. Heading context is displayed as derived metadata, not as a formal OKF predicate.
04
One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.
2 of 2 concepts · 2 directed relationships
05
The complete producer frontmatter, serialized without server paths or runtime data.
{
"type": "design-objective",
"title": "DO17 - Avoidance of complex interfaces",
"description": "To reduce the implementation efforts and system maintenance, and to increase independence from legacy applications, the prototype must be developed in a way that avoids complex interfaces.",
"resource": "https://aisel.aisnet.org/icis2017/TransformingSociety/Presentations/8",
"source_paper": "Unchaining Social Businesses - Blockchain as the Basic Technology of a Crowdlending Platform",
"label": "DO17",
"tags": [
"unchaining-social-crowdlending",
"design-objective",
"social-business",
"crowdlending",
"fintech",
"platforms"
]
}