If we decide to include best practices under the
general Adoption Blueprint "umbrella", it would be helpful to understand the
relationship between the blueprint and associated best practices. Immediate
questions I have is whether we will create "one off" best practices related to a
specific blueprint or whether we would try to make them generic enough to be
used within other blueprints. If that is the case, do the best practices deserve
to stand on their own and should we create a classes of best practices that can
be reused within Adoption Blueprints (or even separately).
Theo
From: John Harby [mailto:]
Sent: Tuesday, January 24, 2006 12:38
To:
Subject: Re: [soa-blueprints] To
Proceed - Best Practices
Possibly although I think there are loopholes within the charter that
would allow us to specify best practices. Firstly, the Generico blueprint has
some treatment of best practices therefore inclusion and advancement of those is
included by this statement:
Circulate, improve, maintain and standardize the existing "Generico"
blueprint to be contributed, in the form of a basic Adoption Blueprint.
On 1/24/06, Beack,
Theo <>
wrote:
Don,
I'm
not convinced that we agreed on the role or place for best practices
as
part of the Blueprints TC. I reviewed the charter of this TC
(
http://www.oasis-open.org/committees/soa-blueprints/charter.php) and
it
made no mention of best practices. Not that I think it is a bad
idea.
The notion of creating best practices could be of
value.
However, we need to determine whether this TC will focus it's
efforts on
only creating SOA blueprints (+ anti-patterns) or whether best
practices
will be included in these efforts.
I think one of the
dangers of trying to focus our efforts on best
practices, is that we might
enlarge the scope to the extent that it will
be difficult to focus and get
some real blueprint work done. It is
definitely a topic worth
discussing.
Regards
Theo
-----Original
Message-----
From: Don Flinn [mailto:
]
Sent: Monday, January 23, 2006 13:57
To:
Cc:
Subject: Re: [soa-blueprints] To Proceed
Agreed.
In
addition, I believe that one of the goals that was agreed upon
is
developing best practices, BP. These could be partitioned
into the
following categories:
- General BP, which would be applicable
to all domains
- Domain Specific BP, where the domains might
be:
- Financial
-
Manufacturing
- Retail
- Professional
services
- Business services (not SOA services)
- Media & Marketing
-
Education
- Government
Each of these could be further
subdivided, but too fine a subdivision,
IMHO, is not in the spirit of a
specification. If we could come up with
best practices at this
level we would deliver information that would be
useful to a broad category
of people. We could point out significant
exceptions or
additions for subcategories of the chosen domains.
Although the primary
effort would be to generalize the BP as much as
feasible while still
making them useful.
Don
On Mon, 2006-01-23 at 11:49 -0600,
wrote:
> To All,
>
> Here is what I gather from the group as
a whole:
>
> 1. Need a context on what we are
doing.
> - 2 cents: A problem
statement would be a great start with
audience, etc...
>
> 2.
Need to defining use cases to provide context on the blueprints
defined
> - 2 cents: establish a
use case document that can be expand on
> this and may have domain
related spin offs
>
> 3. Need to establish what a blueprint
is.
>
> I think everyone should start adding to this list and
adding opinions,
etc...
>
> This may help to create a bit of
focus or strategy.
>
> Thanks,
>
>
Dan
>
--
Don Flinn
President, Flint Security LLC
Tel:
781-856-7230
Fax: 781-631-7693
e-mail:
http://flintsecurity.com
