Changes between Version 3 and Version 4 of RefactoringSecurity


Ignore:
Timestamp:
12/01/10 09:36:26 (10 years ago)
Author:
pjkersha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RefactoringSecurity

    v3 v4  
    77In particular, from an application developer's point of view, applications should be unaware as to the “state” of the security infrastructure.  This idea is encoded in the following figure: 
    88 
    9 [[Image(source:TI12-security/trunk/architecture/uml/Application.JPG)]] 
     9[[Image(source:TI12-security/trunk/NDGSecurity/architecture/uml/Application.JPG)]] 
    1010 
    1111Further, we anticipate that the applications we are deploying will be in practice legacy applications, so we want if possible to completely encapsulate the security infrastructure from the applications. This concept is depicted in the inheritance relationship: 
    1212 
    13 [[Image(source:TI12-security/trunk/architecture/uml/LegacyApplications.JPG)]] 
     13[[Image(source:TI12-security/trunk/NDGSecurity/architecture/uml/LegacyApplications.JPG)]] 
    1414 
    1515