screencast

In GreenDesk^®, a single 'login user' may have more than one 'user role'. User roles determine which features the user may access and what model data may be viewed and edited. This tutorial explores the case of a 'concrete' user (such as an authorised 3rd-party concrete supplier) accessing credits related to concrete.

In GreenDesk^®, points towards the Credits of green rating schemes and industry standards are earned by completing one or more Activities (tasks), which can be allocated to one or more Actors (human resource roles) for project management.

This video shows how GreenDesk Activities (tasks) can be easily allocated to Actors (human resource roles) from many page views and tables involving Activities.

This video shows how to target and un-target Credit points in GreenDesk^® using auto-targeting buttons, inplace points editing, or the edit page of a Credit.

GreenSoft Pty Ltd is offering a limited-time-only TRIAL of GreenDesk^® for Green Star^® Design & As Built offering access to selected Materials-related GreenDesk credit worksheets for concrete, cement, steel, timber, and PVC-related materials.

Audience: Users of MagicDraw SysML or Cameo Systems Modeler who are experimenting with creating custom stereotypes that extend Block.

This screencast video has been created to demonstrate some issues that can arise if you "naively" create a custom stereotype that extends Block without: (1) closing then re-opening your project; (2) creating an appropriate MD Customization. It is not about any actual "bug" in MagicDraw/Cameo (as long as you follow the recommended procedure). If you watch it, please do watch it to the end to find how to handle such stereotypes properly.

Audience: Users of MagicDraw SysML or Cameo Systems Modeler who are experimenting with creating custom stereotypes for SysML.

This screencast video has been created to illustrate some pros and cons of using custom stereotypes in combination with Block inheritance and Part Property structures, and demonstrates some possible "gotchas". It concerns especially use of custom stereotypes to indicate: (1) cross-cutting aspects such as model layer membership; (2) use of tagged values to carry per-Element metadata.