Showing all Design Documentation
-
Vision and Intent
Representation, Engagement, Collaboration, Social Learning, Perspective taking, Values, Prospects and Impacts. I am asking for advice and support to make, universally available, a general method of capturing, reflecting on, developing and representing democratically, the things people care about (their Values), and what we can do about them (our Prospects). Interpreting all social human activity as an…
-
FileNote: Naming software design docs
Status: Published The specific documents required for application software design can vary based on methodologies, project requirements, and organizational preferences. However, here are some common formal documents that are typically involved in the application software design process: The actual documents needed may vary based on the complexity of the project, the development methodology (e.g., waterfall,…
-
Using collapsible Taxonomies to represent/navigate ‘infinite’ domains.
Status: Published for comment:Development ongoing This post is a development of the text in the white paper ‘Design for Social Learning and Perspective taking’, quoted here below in itialics:- P08 Lucidity: Rollup/Drilldown (Zoom); Where practical, data will be categorised (e.g., in a hierarchy) allowing subcategories to be aggregated and displayed (‘rolled up’) in a simplified…
-
Using Logarithmic projections to represent ‘infinite’ domains.
Status: Draft Published for comment: Development ongoing This basically a file note to ensure that the option to insert a ‘fish eye’ filter over any node edge representation of the Value/Prospect domain is taken into consideration – as a way to retain more data on screen, show more relationships but allow focus on specific areas…