(ROSE) Auditing/securing individual attributes

[Vicky Pyne]

Title: RE: (ROSE) More than one deployment diagram

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]