instructional

Video: A GreenDesk mini-tutorial: Terminology: Login User vs. Author (user profile) vs. Actor (human resource role)

Keywords

GreenDesk® has features for managing the team members of a project. It distinguishes between Login Users (who have access to GreenDesk and have one or more pre-defined 'access roles') and Actor elements (human resource roles on a real-world project, which can be created freely, and can be allocated to GreenDesk activities to help track credit completion for project management).

Video: A GreenDesk mini-tutorial: Understanding login users and role-based access: Case: A ‘concrete’ user in GreenDesk for Green Star

Keywords

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.

Video: A GreenDesk mini-tutorial: How to allocate Activities (tasks) to Actors (human resource roles) for project management [SILENT]

Keywords

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.

Video: Introduction to GreenDesk for Green Star Design & As Built

Keywords

GreenDesk® is a powerful Enterprise Web Application for tracking and preparing applications for environmental rating certification schemes, industry certification schemes, and certifications for industry standards. There are different versions of GreenDesk® under development for various national and international certification schemes and standards.

Screencast: MagicDraw SysML/Cameo analysis: Possible "gotchas" when extending the SysML Block stereotype

Keywords

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.

Screencast: MagicDraw SysML/Cameo: Pros and Cons of custom stereotypes in combination with Block inheritance and Part Property structures

Keywords

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.