Hi,
upgrading our ARIS server with ARIS98 for the new university year, i want to optimize ARIS user management in our context. Let me present our use case... In our university, 3 departments are using the ARIS server
- the computing department for 120 students (licence). initiation on ARIS, only model design with a standard report
- the computing department for 120 students (master). project of 10 weeks, with a complete design of business requirements and two solutions, a centralized one on ERP, and a "best of breed" one. They have to build their one report script, and to use some tools (generation of model, comparison, matrixs...
- the engineering department, for 90 student (master), focusing on business analysis and requirements
- the DISP laboratory for use in 2 or 3 thesis (model, script, evaluation, XML export)
Last year, we have created 4 ARIS tenants, to separate manual management of users; database and scripts... But that requires 4 licences... and the management of tenants (at this moment, issue with upgrading tenants..)
So, could you give an advice on the better solution based on your experience, depending of the following questions:
1/ separate tenants for each department. ?
2/ use of LDAP synchornisation (not possible last year because our system admin need not find how to code password in exchange betwwen ARIS and LDAP...)
3/ definition of ARIS group using automatic assignement of user group based on LDAP attributes..
thanks for your help
regards
pam
Hello pam,
unless people are supposed to modify the method configuration of the tenant, I do not see the need to have multiple tenants. You can distribute people in different user groups per department and give each their database(s), filters, and access permissions based on user group membership. If you want to evolve the method for different departments permanently and independently, derive new model types, symbol types and attribute types as necessary leaving the original types untouched, so any department using the standard types can continue to do so without impact.
If you want them to create and modify scripts and reports, organize the scripts in categories per course, for example, and require them to use naming conventions for their scripts.
I cannot help you with the details of LDAP integration.
If anyone is allowed to fiddle around with the method configuration, which is not intended to be permanent, then provide him a separate tenant, which you can reset to standard configuration after the term is over. This tenant would have the character of a "test" or "laboratory" system.
Regards, M. Zschuckelt
