Title: RE: (ROSE) More than one deployment diagram
Vicky,
 
(1) Auditing
The usual 'good sytle' is to use getter/setter operations instead
of a fundamental type change, as these rules are probably dependant
on the (business) object itself. You might think about a special
stereotype for these operations (but that may interfere with the
code generator, so a naming convention might do the same).
 
(2) Security levels
The systems that I saw (and that I cannot distribute due
to copyright/privacy issue of my customers:-) have different
levels:
* simple: UserManager component
  - queried/called by the objects as needed
* middle: User Management subsystem
  - Login
  - manages policies
  - called by every object as needed
  - still some parts of the system don't need UserManagement
* Large Scale: subsystem User Management + Architectural mechanism
  - every user action needs the User Management subsystem
  - view concepts (who can read what)
  - replacement rules (holidays, illness, etc)
  - personalization
  - ...
 
(3) Where to find more?
For the terms 'subsystem', 'architectural mechanism', please
refer to RUP.
Maybe the PearlCircle Auction System on Rational Developer Network
(www.rational.net) can give you some ideas. (But you would need to
at least Rational XDE to have a look at the models...) It has
a basic user management (login, shopping cart).
 
Kind regards,
Volker
-----Urspr�ngliche Nachricht-----
Von: Vicky Pyne [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 22. Oktober 2002 14:06
An: [EMAIL PROTECTED]
Betreff: (ROSE) Auditing/securing individual attributes

Hiya,
 
I'm trying to work out how to model a couple of things in my model.
 
1.) Auditing needs to be done at the attribute level. For example, when details on a customer agreement have changed, a department expects a mail. Also there are some attribute for which the history of what was changed and who changed it is stored. One way to implement this that I have considered includes the concept of introducing specialised classes for String, Boolean etc. as TrackedString, TrackedBoolean. What are other people's thoughts on this?
 
2.) Security levels/groups need to be implemented at an attribute level. Once again, I could introduce a specialised type but I have more fundamental issues relating to this. Has anyone else come across this situation?

Cheers

Vicky

You wouldn't recognize a subtle plan if it painted itself purple and danced naked upon a harpsichord singing "Subtle plans are here again." 
 
~~Edmund Blackadder~~

______________________________________________________
Vicky Pyne - Systems Analyst - Information Systems
Channel Four Television
t: 020 7306 1037 | m: 07740 85 99 88 | e: [EMAIL PROTECTED]
a: 124 Horseferry Road, London, SW1P 2TX



Any views or opinions are solely those of the author and do not necessarily represent those of Channel Four Television Corporation unless specifically stated. This email and any files transmitted are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify [EMAIL PROTECTED]



Reply via email to