This scripts lists all non-system attributes from the open module.
Open the module. Then use from the Tools > Edit DXL menu
AttrDef ad = null
Module m = current Module
print name m "\n"
for ad in m do
{
if (!ad.object) continue
string s = ad.description
if ( s!= "System Attribute") {
print ad.name ";" ad.description"\n"
}
}
ISO/IEC/IEEE 42010:2011 defines a system architecture as the fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution. Essentially, the system architecture provides concise and correct description of the system of interest. An architecture description includes one or more architecture views. An architecture view (or simply, view) addresses one or more of the concerns held by the system’s stakeholders. An architecture view is composed of one or more architecture models. An architecture model uses modelling conventions appropriate to the concerns to be addressed. These conventions are specified by the model kind governing that model. Within an architecture description, an architecture model can be a part of more than one architecture view. This case study descibes how AVION developed concise architecture of the high speed rolling stock for a prestigious UK project.
The science of workplace sociology is fascinating. With a committed focus to promote development of employees, for a very long time, organisations have believed in ‘rolling out the training programmes and getting people to sign an attendance sheet’ as the most accepted and preferred way to develop their employees. But how exactly does an organisation know if the workforce is actually developing? As a manager or an employee, do we need to be more focused on the actual ‘developmental value’ of a training?