P. 1
Software Architect

Software Architect

4.33

|Views: 1,896|Likes:
Published by shakeel009

More info:

Published by: shakeel009 on Jul 02, 2008
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

03/04/2013

pdf

text

original

The choice of the word view or viewpoint is largely semantic. Neither word means
something specific, except in the context of the methodology which contains it.

As an example, consider the security view. Where is it in each of these
methodologies?

For the 4+1 view of RUP, the answer is simply wherever you want it to be.

In Zachman, it would be divided up into relevant sections within the grid. There
would be more than one, but less than thirty aspects to the security view.

In RM-ODP, security is not a view, but a function. The four functions of ODP are
Management, Coordination, Repository and Security.

So we find that the apparent simplicity of expecting a view for all architecturally
significant aspects is not delivered by any of these methods. Neither are they
wrong not to contain a security view, for Security may be offered partly by
software, partly by hardware technologies, and partly by business procedures. If
locking the door at night is part of the security of your software system, you
would contain that information in your hybrid security view in any of the
methodologies.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->