Re: [soa-rm-ra] Views and viewpoints

[Danny Thornton <danny_thornton2@yahoo.com>]

The distinction between a view and viewpoint is not
all that clear to me.  The concept of a view and
viewpoint is not consistent between RM-ODP, DODAF, UML
2.0 Views, etc.   I would like to nail down what the
SOA RA means by viewpoint and view.

The SOA RA refers to the ANSI/IEEE std 1471-2000 for
definitions of a view and a viewpoint.

View - A representation of the whole system from the
perspective of a related set of concerns.

Viewpoint - A specification of the conventions for
constructing and using a view.  A pattern or template
to develop individual views by establishing the
purposes and audience for a view and the techniques
for its creation and analysis.

For each top level view (Service as business, Service,
Security, etc.) do we have a viewpoint specification?
It looks like we are leaning towards a view having a
viewpoint and a view being composed of one or more
models.

Danny

--- Francis McCabe <frankmccabe@mac.com> wrote:

> We had a discussion about formalizing a views and
> viewpoints in the  
> face to face; and we had another discussion on the
> matter during  
> today's telcon.
> 
> In order for this approach to make sense, it is
> important to have the  
> right number of views; too many and it becomes
> unwieldy, too few and  
> it becomes less useful.
> 
>  From this point of view (sic), we identified the
> following major  
> views of the RA. The titles of these views are
> intended to be  
> suggestive of the viewpoint; but are not cast in
> stone.
> 
> ServiceAsBusiness view
>    "How are business needs met using SOA?" is the
> key question.
>    Models in this view would fold existing sections:
> 
>    Needs and capabilities
>    Participants
>    Real World Effect
>    Business Processes
> 
> Service view
>    "What are services, what support is needed and
> how are they  
> realized?"
>    Models in this view would consist of:
> 
>    Service Description
>    Service Visibility
>    Interacting with services
>    Service Transactions
>    Service Composition and Choreography
> 
> Security in SOA
>    "How can we be assured of the safety of using
> services?"
>    Models in this view would include
> 
>    Security Threats
>    Security policies
>    Trust model
>    Security enforcement
> 
> Deployment of SOA
>    "What does it take to deploy SOAs?"
>    This view would include the models:
> 
>    Management of services
>    Governance in SOA
>    Compliance
>    Testing models for SOAs
> 
> Policies and Contracts
>    "How do people express constraints in an SOA
> context?"
>    In one reading, policies and contracts represents
> an important  
> infrastructural element that needs to be focused on.
> Policies and  
> contracts could be modeled in each of the views
> above, or in their  
> own view.
>     Specifically, we would model
> 
>    Policy and contract descriptions
>    Policy/contract enforcement
> 
> 
> We decided to open this discussion to the list
> before committing it  
> to the WIKI. Comments would be welcome.
> Frank
> 
> 
> 
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com