Back to Home Page

Frameworks Prototype

Contents

Instructions

You are the Thinker who would become Modeller. You will be constructing a ‘simple graphical model of your Thinking and/or Understanding’.

‘Frameworks’ modelling is rule-based.

In this Current Prototype Tool Version 3.0 - upon engaging with the tool, you are presented with the first two nodes of the Core Spinal Model in the Thinking & Modelling Space.

These are:

New nodes can be added by either clicking on the workspace or selecting the Elaborate button. New nodes will become children of whichever node is selected as active (indicated by the red circle).

The elaboration allowed is determined by the user level assigned to the model as below. The user level can be changed by clicking on the New Model Button and changing the user level.

User Levels

User Level Maximum Levels Maximum Children/Level Total Nodes
Novice 3 3 14
Intermediate 4 5 157
Advanced 5 7 2802

A list of available links for the user are provided in the left hand menu bar.

Within the main screen there are menu buttons to allow:

Button Function
New Creation of a new Link
Edit Editing of the selected link
Delete Deletion of the selected link
Clear Selection Deselect the selected link (to allow "default" nodes to be created)

Model Management

Within the main screen there are menu buttons to allow:

Button Function
New New Model Creation (and selection of User Level)
Save Saving the current model (and renaming of the model)
Save As Saving a copy of the model with a new name
Load Loading an existing saved model
Share Sharing the model with another user of frameworks
Manage Switch to the Management Screen to rename/copy or delete models
Download SVG Exporting the SVG Image of the current model
Elaborate Add new children to the currently selected node with auto spacing

Zooming and Panning

There are zooming and panning controls for moving around larger models. These buttons are located under the model construction and management buttons.

Button Action
+ Zoom in
= Reset Zoom
- Zoom Out
Pan Up
Pan Down
Pan Left
Pan Right
0 Reset Pan to 0,0
F Reset Pan to Focus
A Reset Pan to Active

Object Model

The ‘Frameworks’ Tool: “The Intelligent Frame” is object-oriented consisting of:

Frame

The Frame object manages the rendering and interactivity of the model within the SVG image on the HTML page. The frame is responsible for enforcing the constraints of the metamodel within the scope of the users'* expertise level. This includes:

Note: * - ”The “User” in ‘Frameworks’ is the “Thinker Modeller”

Methods are included for:

Node

The Node object contains the information related to each node in the model including:

The Node also contains methods to allow the node to be rendered and interacted with via the SVG representation within the frame. These methods include:

Nodes can also be protected by the metamodel to prevent certain nodes from being deleted or moved (e.g. Focus and Context Nodes).

Links are collections of HREFs with names and descriptions. When a link is selected in the link manager and a new node is added to the model, the links contents are used to populate the newly created node.

The line object provides methods for drawing and manipulating the lines connecting nodes in the SVG image within the frame. These include

Feature Suggestions

  1. Additional Managment Features
    1. Implemetation of "Projects" to group links and models together on related topics
    2. Additional "Folder" structure to support organising models and links
    3. Versioning of Models
  2. User Interface Improvements
    1. Dynamic Scaling to different screen sizes and orientations
    2. Addition of touch friendly gestures for zoom/pan etc.
    3. Implementation of Drag and Drop for Links

Deployment

  1. The current code base is deployed via a CICD Pipeline integrated to an Azure Static Web App.
  2. A pull request to main will trigger a deployment to a test clone environment with a unique URL to test.
  3. Merging the Pull Request will trigger a full re-deployment to the main environment.
  4. The database for storing the models needs to be build manually via from the scripts in the SQL directory.
  5. The connection to the database needs to then be added to the Azure Static Web App Environment Variables as SqlConnectionString.
  6. The current deployment shares the production database with the test environments that are created by the CICD pipeline.

Dependencies

  1. The code requires an Azure Static Web App which can be set up folling instuctions here.
  2. The Azure function app will need a version 4.0 API Enabled following instructions here.
  3. The code also requires a SQL Azure Database which can be set up following instructions here
  4. The Framworks Schema should be created following documentation in the SQL Directory of the code repository.
  5. The Connection string for the database needs to be supplied to the Azure Static Web App as a SQLConnectionString environment variable.
  6. Re-implementation of the CIDC Pipeline can be accomplished by following the instructions here.