3

If I am planning a structure for support testing in Linux, a structure that will contain packages, such files as shell and build scripts, app configurations, DBs, sources, tests and jars for to be managed, applications for be managers, users, permissions, etc., what diagram could be used for it? Just now I am using the Component Diagram with some stereotyping, but it is not at all convenient in the part of permissions/users stuff. There are such diagrams as RBAC, but they are not UML, and it remains unclear how to combine them.

An example picture and/or a real experience description would be highly appreciated. But any fresh thought will be useful, too.

Gangnus
  • 2,805
  • 4
  • 21
  • 31
  • 1
    Related: [How to Model a simple file-system by UML class diagram](http://programmers.stackexchange.com/q/146286/25936) – yannis Jul 01 '14 at 15:02
  • @YannisRizos I am afraid that the system in this case is extremely far from being simple. And any error in permission politics in one single file will cause all the system to fail. And in your example there is not a word on permissions at all. – Gangnus Jul 01 '14 at 15:04

2 Answers2

1

I donot think that there is a good uml-diagram type to model this.

The best (but in my opinion still inapropriate) diagram i can think of is a use case diagram where the Actor can be considered as a role with certain permissions.

Use_Casees are from business-point-of-view while asking for "linux" or "file" is asking from technical-point-of-view.

k3b
  • 7,488
  • 1
  • 18
  • 31
  • The problem is, that I have a set of objects and packages. And the rights are applied to them. So, according to you, I should use Use Case diag for actor figure only, but mostly use elements from component/package/class/object diagrams. – Gangnus Jul 03 '14 at 12:05
  • The objects and packages are proxies for the actors that carry out the operations. Treat them as augmentations of the actor in the use cases. – BobDalgleish Jul 31 '14 at 23:38
-4

I think you would need more than one UML diagarams to model.

Package and component diagram to model the app, config, db etc...

Use case diagram to model the authorization and authentication part.

bhavinpatel
  • 1
  • 2